Customization vs configuration is the choice between changing a system with its built-in settings (configuration) or by writing new code that alters how it works (customization).
ERP · Reviewed by Ray Rasouli
Ask about customization vs configuration
Plain answers, with your setup in mind.
Ask anything about customization vs configuration. For example, how it works in your current tools.
A scripted guide for now. It does not store what you type.
Configuration uses the switches the vendor already provides: approval limits, custom fields, tax rules, document layouts. It survives upgrades because the vendor supports it.
Customization means writing code to make the system do something it was not built to do. Sometimes that is worth it. A specialty manufacturer might need a pricing calculation that no standard setting can handle, and it is central to how they win work.
The trouble is that every custom piece has to be tested, documented and maintained at each upgrade. A good test is to ask whether the need makes you different from competitors, or whether you could simply adopt the standard way.
In practice
Old processes are copied instead of questioned.
Teams customize to keep a familiar step that the standard system already handles another way.
Upgrades become expensive projects.
Each custom change has to be retested and sometimes rewritten when the vendor releases a new version.
Custom code is poorly documented.
When the developer who wrote it leaves, nobody knows how it works or what depends on it.
No. It makes sense when the need is core to how you compete and no setting can meet it. The cost is the ongoing upkeep, so it should be a deliberate choice.
Anything done through the system's own setup screens, such as fields, workflows, roles, forms and rules, without writing code that changes the product itself.
A 30-minute discovery call with Ray, then a clear list of what to fix first. No obligation.
With Ray Rasouli. No obligation.