Knowledge articles
Custom or config
Adopt standard processes where practical, use configuration where needed, and reserve bespoke code for essential requirements that justify its ongoing cost.
Finding the right ERP solution requires understanding these distinctions. Calling every departure from a standard process “customisation” can lead organisations to reject a suitable platform—even when supported configuration could meet their needs without bespoke code. Here’s a guide on what this means:
Swipe or scroll sideways to view the full table →
| Approach | What it means | ERP example | Relationship to adopt vs adapt |
|---|---|---|---|
| Standard configuration | Using built-in, vendor-supported settings as intended, without bespoke code. | Setting up legal entities, approval thresholds, user roles and financial periods. | Usually adoption. Adopting SaaS still requires configuration to reflect your organisation. |
| Non-standard configuration | Using available settings and tools in unusual or complex combinations. It may remain vendor-supported and require no code. | Combining additional fields, rules and approval stages to accommodate a specialist business process. | Usually adaptation. Can address legitimate requirements, but may increase testing and maintenance effort. |
| Code customisation or bespoke extensions | Creating functionality beyond available configuration, through bespoke code. | Building a specialist pricing engine or an extension for complex calculations. | Adaptation. Adds responsibility for support, maintenance and compatibility testing. |
These labels are not universal: ask suppliers how a requirement would be met, whether the approach is supported, and what happens when the platform is updated.
The aim is to meet genuine business needs without unnecessary complexity. Non-standard configuration can be a sensible compromise; bespoke code should have a clear, compelling business case.