Every ERP project receives customisation requests. Some are essential; many recreate old habits in new software. Deciding well keeps the project on budget and the system easy to upgrade. These are the rules we follow.
Configure before you customise
Modern ERP platforms offer custom fields, workflows, print formats, reports and permissions without code. We always try configuration first. Most requests can be met this way.
Customise when the process creates advantage
If a process is what makes your business better than competitors, such as a special costing method, quality inspection or customer service model, it is worth supporting properly, even with custom development.
Change the process when it is just habit
When a request exists only because “we always did it this way”, we show how the standard process works and what it would cost to customise. Often teams prefer the standard approach once they see it.
Questions we ask for each request
- What problem does this solve, and for whom?
- What happens if we use the standard feature instead?
- How often is it used?
- Will it complicate future upgrades?
Build customisations to last
When customisation is the right answer, we build it as a separate app or extension on platforms such as Frappe, document it and test it with upgrades in mind, so your system stays maintainable.
Frequently asked questions
Will customisations break when ERP is updated?
Not if they are built as separate extensions and tested before each upgrade, as we do.
Related reading
For the product view of this topic, read Standard vs Customised ERP: What Enterprises Need on the Reckon ERP blog.
Planning a project? Book a free consultation with our team, or see our ERPNext implementation service.
