Many companies believe that ERP systems are either off-the-shelf or custom-built. In reality, there is a whole world of possibilities between the two. In this blog, we explain how organizations can expand their ERP systems step by step—without having to build a custom solution right away.
When I talk to companies about ERP systems, I often encounter different types of organizations.
On the one hand, there are companies that want to stick as closely as possible to off-the-shelf software.
They’ve heard stories about ERP projects that spiraled out of control due to customization: budgets that spiraled out of control, upgrades that became difficult, and a reliance on programmers.
On the other hand, there are organizations that are convinced their processes are so unique that no off-the-shelf software can meet their needs. For them, building a completely custom system sometimes seems like the most logical solution.
The majority of companies fall somewhere between these two extremes.
Whether you see yourself as a wallflower who prefers to stick to the standard approach, or as a maverick with unique processes, there are now several ways to customize ERP systems effectively.
ERP never stands alone
Virtually every company agrees on one thing: ERP must be integrated with other systems.
For example:
- online stores
- WMS systems
- point-of-sale systems
- field service solutions
- payroll
In this context, we often see two strategies.
Best-of-Breed
You select the best solution for each component and integrate them together.
Best of Suite
: You choose a single provider that offers as much functionality as possible on a single platform.
Both strategies have their pros and cons. In practice, a hybrid form often emerges.
From completely standard to fully customized
ERP projects involve varying degrees of flexibility.
1. Fully standard
Some companies prefer to adapt their processes to the software.
Templates allow us to quickly set up a standard environment.
An audit file often makes it relatively easy to migrate historical data.
This is usually the fastest and most cost-effective implementation.
2. Standard ERP with integrations
Many companies want a standard ERP system, but one that is integrated with other applications.
For example:
- WooCommerce or Shopify online stores
- logistics systems
- point-of-sale software
When these solutions are used as standard, implementations remain relatively straightforward. Complexity usually arises when other systems already contain a significant amount of custom code.
3. Expand the ERP system yourself
Sometimes an organization needs just a little more than what’s typically available.
For example, in Uniconta , users Uniconta add their own fields and tabs.
Consider:
- a "Fit " field for clothing
- a "Lumen" field for lighting
- Additional product information for sales channels
Users can often create these kinds of extensions themselves, without any programming.
4. Business Rules
Business rules represent an interesting next step. These are simple logical rules within the system:
If This → Then That.
For example:
- When a product is sent to bol.com → check the minimum number of words
- If an item is in the “Lamps” category → make the “Lumen” field required
- if a credit limit is exceeded → block the order
Rules like these help monitor processes without the need for custom development. For many organizations, this strikes the perfect balance between off-the-shelf software and custom development.
5. Add-ons and industry solutions
When companies need more specific functionality, an add-on can be the solution. The Uniconta store offers solutions from various partners.
Promentum has developed a variety of Uniconta for retail, wholesale, and logistics processes, among others.
These add-ons build on the platform without requiring any changes to the core system.
6. Customization (final step)
Sometimes, however, there remains a need that cannot be met anywhere else. In that case, a custom solution can be developed through, for example:
- the .NET API
- Web APIs
- integrations with external systems
However, in our projects, we always try to make customization the last resort. Often, configuration, business rules, or existing modules are sufficient.
ERP doesn't have to be an all-or-nothing choice
The debate surrounding ERP is often presented as a simple choice:
- standard software
- or custom solutions
In reality, ERP consists of several levels of flexibility.
From wallflower to show-off—and everything in between.
At Promentum, we help organizations strike the right balance between standardization, flexibility, and integration. This ensures that ERP serves as a stable platform for growth, without making projects unnecessarily complex.
And surprisingly often, that balance starts with something simple: a good company policy.