Existing features
Is the required feature already available but not configured or known?
ResourcesERP guide
Customise, extend
or replace your ERP?
A decision guide for businesses: what your existing system can still provide, when a custom application helps and when replacement deserves consideration.
Start by assessing what you have
A new requirement does not automatically call for a new system. Review these six areas with your business teams and system support.
Data quality
Are master data, stock records and responsibilities reliable enough for the new workflow?
Extension options
Which supported settings, extensions and interfaces does the system offer?
Vendor and support
Are updates, contacts and knowledge of the existing setup available?
Business requirements
Which special rules are necessary and which workflows can be simplified?
Total effort
Include rollout, licences, operation, maintenance and later changes.
The findings show whether configuration is enough, an extension is useful or the foundation itself has become the bottleneck.
Three paths for your ERP
Customise
- Supported features can meet the requirement.
- Rollout and maintenance are agreed with the system partner.
Extend
- The existing ERP should remain.
- A custom interface or business logic is needed.
- Required data access has been verified.
- Operation and responsibilities can be planned.
Replace
- Support or further development is missing.
- Essential requirements cannot reasonably be added.
- Migration and transition need their own plan.
Comparing customisation and extensions
Customisation here means configuration or a vendor-supported extension within the system. A separate application runs alongside it and exchanges data through verified access paths. Both approaches need testing and support.
Technology and data
| Aspect | ERP Customisation | ERP Extension |
|---|---|---|
| Proximity to the ERP | Existing screens and rules can be reused. | Custom screens and workflows run outside the ERP. |
| Data exchange | Data can stay within the existing system; available extension points need assessment. | Agree ownership of data, exchange and error handling. |
| Updates | Check supported extensions and their compatibility during updates. | API and data format changes may require adjustments. |
| Operation | The customisation follows the operating conditions of the existing system. | Plan for an additional application, monitoring and responsibilities. |
Effort and collaboration
| Aspect | ERP Customisation | ERP Extension |
|---|---|---|
| Starting point | Configuration may be enough. Estimate custom extensions separately. | Consider application development, integration and rollout together. |
| Business constraints | The product and vendor determine the available design options. | More control over design, with additional responsibility for the application. |
| Maintenance | Agree support and update tests with the system partner. | Coordinate support for both systems and their interface. |
| Dependencies | Review documentation, available specialists and supported extension paths. | Consider source code, components, data access and operational knowledge. |
Decision and rollout
| Aspect | ERP Customisation | ERP Extension |
|---|---|---|
| Good fit | The ERP broadly fits; a clearly defined feature is missing. | The ERP remains suitable, but a specific workflow needs its own application. |
| Trial | Test the customisation with typical cases in a test environment. | Test workflows and data exchange, including failures. |
| Transition | Plan the impact on existing workflows and training. | Explicitly agree transitions and any parallel processing. |
| Consider replacement | When support, extensibility or business suitability are no longer adequate. | When an extension would merely move the fundamental problems elsewhere. |
The right solution follows your situation
Assess the actual workflow, technical access and effort throughout operation. An extension does not automatically guarantee lower costs or simpler updates.
Where ElbDesk can fit
ElbDesk can provide the foundation for a custom application alongside your existing ERP or serve as a new system. We assess suitable modules, required development and possible integrations against your requirements.
- As an extension alongside your ERP
- As the ERP for the whole business
A pure integration or standalone application can also be built without ElbDesk.
How to prepare the decision
A defined first step provides the basis for further planning.
Recommended Approaches
- Review workflows Describe typical cases and important exceptions.
- Check access Assess interfaces and data formats in the existing system.
- Assign responsibility Decide which system owns each data set and who makes business decisions.
- Agree tests Check calculations, data exchange and behaviour during failures.
- Plan operation Clarify support, updates, documentation and training.
Avoid Common Mistakes
- Choose a solution too early Clarify the requirement before choosing customisation, extension or replacement.
- Compare development costs alone Include operation, rollout and subsequent changes.
- Assume interfaces exist Check availability, permissions and limits in the actual system.
- Leave transitions unresolved Duplicate processing and conflicting data need clear rules.
- Leave handover open Agree usage rights, documentation, data export and access in advance.
Technical background
Primary sources on extensibility and reliable data exchange. This vendor-specific documentation does not replace assessment of your system.
Clean Core Extensibility
Overview of supported extensions within and alongside an ERP system.
Retry pattern
How transient failures, retries and repeated processing relate to each other.
Contact
Customise, extend or replace?
We assess your starting point and discuss what needs checking before a decision. Technical access and effort are then examined in the actual system.
Tobias Kietzmann
Managing Director · Your permanent point of contact
Send an enquiry
Tell us briefly where things are stuck. We will get back to you personally.
Thank you, your message has arrived. We will reply personally to discuss the next step.
A short description is enough. We will work out the details together.