ERP customization: when should you change the system—and when should you change the process?
A familiar screen is not a business requirement. Decide which changes protect a necessary outcome, which belong in another system, and which should not be built.
- 01Question
- 02Compare
- 03Approve
- 04Prove
- 05Maintain
Use standard setup or change the process when it delivers the required business outcome without weakening controls. Customize only when a valuable, necessary requirement cannot be met that way, and approve the ongoing maintenance, upgrade testing and ownership alongside the build. Integrate when another system should remain responsible for the job. Reject changes that only reproduce old habits, bypass approvals or have no credible support plan. The right choice preserves the outcome, not necessarily the old screen.
Should you pay to make the new ERP work like the old one? Before approving another change request, separate what the business must achieve from how people are used to achieving it. A different approval step might remove unnecessary work. It might also remove a control that prevents the wrong order being shipped. The decision needs more than “standard is cheaper” or “our business is different.”
When is ERP customization worth considering?
Contractors planning live-job migration can use the ERPNext construction implementation guide to assess job controls, claims and cutover.
ERP means enterprise resource planning: software joining work such as sales, purchasing, stock, production and accounts. ERP customization changes or adds behaviour beyond the standard setup. It can be justified when an important customer commitment, operating requirement or necessary control cannot be met through the existing features and a workable process. Familiarity alone is a weak reason.
Start by rewriting the request without naming a screen. “Rebuild our order spreadsheet” might become “Sales must see which customer orders are waiting for approval, and warehouse staff must not dispatch them early.” Those are outcomes you can demonstrate. The spreadsheet is only one possible way to achieve them.
Then ask the process owner what happens if the requirement is not met, how often it arises, and which real orders show the problem. Separate evidence from preference. If the requirement is a legal or contractual obligation, identify the applicable rule or commitment and its reviewer rather than accepting “compliance” as a self-explanatory label.
Microsoft’s extension guidance warns against reproducing a legacy system before understanding the new platform’s existing features. It also recognises that extensions can be necessary. The useful question is not whether customization is good or bad, but whether this change earns its ongoing burden.
Should you configure, customize, integrate or change the process?
Configuration uses existing settings and rules. Customization adds or changes behaviour, often through an extension—a separately maintained addition to the software. Integration connects the ERP to a system that should keep doing part of the job. Process change changes how people work, including their responsibilities and checks. A useful design can combine these routes.
| Route | Good fit | What you still have to own | Poor-fit warning |
|---|---|---|---|
| Configure existing features | The product can meet the outcome through settings, permissions, supported forms or standard workflows. | Settings, access, data quality, user training and tests after relevant changes. | A setting makes the screen look right but does not enforce the rule on imported orders. |
| Customize through an extension | A necessary, valuable gap remains after the standard process has been demonstrated. | Design, development, tests, documentation, maintenance and compatibility with future releases. | A large rebuild preserves old habits or changes essential records without clear controls. |
| Integrate another system | Another application should remain responsible for a specialist job or a trading partner’s records. | Record ownership, connection fees, monitoring, failure recovery and coordination between providers. | Both systems can independently change the same value, with no rule for resolving disagreement. |
| Change the business process | The standard flow produces the required result, and the team can adopt it without losing a necessary control. | Training, job instructions, responsibilities, transition work and checks that people follow the new flow. | “Use standard” means more rekeying, hidden spreadsheets or removing a required approval. |
Vendor terminology overlaps. A form change may be called customization even when an administrator can make it without programming. For example, the official ERPNext Customize Form documentation describes adding fields and changing standard-field properties through a form tool. That is not the same work as developing a new order-release rule. Ask what is actually changing, how it is stored and how it will be tested—not just whether the quote says “no code.”
A prebuilt app or connector is another candidate, not an automatic escape from maintenance. Check who publishes it, which product versions and hosting arrangements it supports, what it costs to keep, and who fixes a failure. Microsoft’s guidance on partner solutions explicitly calls for checking support and alignment with continuing updates.
Do not rebuild a specialist system inside the ERP just to have fewer applications. Equally, do not add another application when a supported setting would meet the need. Ask which system should own the decision and which others only need its result.
What must a change request prove before you approve it?
Use this approval scorecard for each material request. Mark every row Ready when evidence and an owner are recorded, Unresolved when something still needs investigation, or Stop when the proposal would break a required control or has no acceptable operating plan. This is a decision aid, not a numerical rating: a serious control failure cannot be offset by several attractive features.
| Approval question | Evidence needed for Ready | Who confirms it | Reason to pause or stop |
|---|---|---|---|
| What outcome are we buying? | A specific business result, affected transactions and consequence of doing nothing. | Process owner; finance or compliance reviewer where relevant. | The request only names the old screen or says everyone needs it. |
| Have we compared the alternatives? | The same scenario demonstrated with standard setup, process change, an existing app and integration where relevant. | Process owner with implementation lead. | Development is proposed before anyone has tried the supported flow. |
| Do required controls survive? | Permissions, approvals, record history and finance consequences checked across every entry route. | Finance and operational control owners. | An import or connection can bypass an approval that the screen enforces. |
| Can staff use it in real work? | Normal, exception and busy-period cases with the users and devices involved. | Team lead and representative users. | The design works only when a consultant talks people through it. |
| Is the ongoing commitment affordable? | One-off work, recurring fees, internal effort, update testing and uncertain costs separated. | Budget owner. | The build is priced but keeping it working is assumed to be free. |
| Who fixes a failure? | Named support lead, provider boundaries, access, service hours and recovery instructions. | Business owner and support lead. | The ERP supplier and connector supplier can each send you to the other. |
| Can we update and eventually replace it? | Supported change method, release-test plan, code or package access terms, documentation and data-exit route. | Technical lead, explained to the sponsor. | It relies on unsupported changes or knowledge that only one unavailable person holds. |
Approve when the outcome is justified, every required gate is Ready, and the cost and delivery terms are accepted. An Unresolved row calls for a bounded investigation or demonstration—not permission to build everything. Stop the current design if it weakens a necessary control; revise the design rather than accepting the risk through a feature score.
Distinguish a defect, where agreed behaviour fails, from a new requirement, where the business now wants something else. Record the expected result, actual result and original scope reference before deciding how work is charged. Once the change is justified, use the ERP implementation quote-comparison guide to put it into the written scope instead of treating a meeting conversation as spending approval.
What does that decision look like for a distributor?
Consider an illustrative distributor introducing a new ERP while keeping its trade ordering portal. Sales asks for a custom “order release module” resembling a spreadsheet. On inspection, the request contains several different needs. The following choices are constructed examples, not a client project or a claim that every ERP has the settings described.
| Request underneath the module | First route to investigate | Approval condition | What would change the decision? |
|---|---|---|---|
| Show waiting orders in the familiar spreadsheet layout. | A standard filtered list and a revised daily review process. | Sales can find the orders, reasons and responsible approvers without maintaining a second master list. | Important information is genuinely unavailable or the standard steps add unacceptable daily effort. |
| Block warehouse release until an authorised person approves a held order. | Existing approval and permission settings, if available. | The hold applies to manual entries and portal orders, and a sales user cannot approve their own restricted exception. | The product cannot enforce the necessary rule across all entry routes; investigate a bounded extension or reconsider fit. |
| Tell portal buyers whether their ERP order is accepted or held. | A connection sending the ERP-owned status to the portal. | A failed update is visible and can be retried without creating another order or falsely showing acceptance. | The portal cannot represent the required states; scope a portal change as well, not a duplicate ERP approval rule. |
| Require a customer-specific packaging check before selected orders can be released. | First prove whether existing checklists and release rules can enforce it. | If a gap remains, an extension records the check and approver and prevents release through every agreed route. | The request is only an occasional preference that can be handled safely by an existing documented process. |
The packaging rule is a plausible customization candidate only after the standard route fails and the customer commitment is confirmed. Give it a narrow boundary: the affected customer orders, the required check, the authorised approver and the event that allows warehouse release. Do not use it to replace the whole order process.
For an approval demonstration, attempt release before the check, with an unauthorised user, and after changing a previously approved order. Try both a manually entered order and one received from the portal. Agree which changes require fresh approval. Pass only when the release decision and its history remain explainable across those cases.
Keep commercial states separate. An accepted order is not a shipped order; an authorised release is not proof of dispatch or payment. If the portal update fails after the ERP accepts the order, repair that update against the existing order. Do not create a replacement order merely because the customer cannot yet see the status.
What will the change cost after the developer finishes?
Ask for more than a development fee. Configuration, process change and integration also consume staff time and support effort. Compare the same planning period and business outcome for every route, with uncertain amounts shown as unresolved. Do not invent a maintenance percentage or assume the cheapest build has the lowest continuing cost.
| Commitment | What to include | Responsibility to settle |
|---|---|---|
| Design and introduction | Discovery, standard-flow demonstration, development or setup, initial tests, documentation and training. | Who supplies sample orders, approves the rule and accepts the result? |
| Recurring operation | App or connector subscriptions, hosting where needed, support, monitoring and manual exception work. | Who checks failed work, and which charges are already included elsewhere? |
| Updates and corrections | Review of product changes, a safe test copy, compatibility work, retesting and release attendance. | Who watches release notices, tests the change and pays when a dependency changes? |
| Internal capacity | Process-owner reviews, finance checks, user practice and time to handle exceptions. | Which named staff have time allocated, including during busy periods? |
| Replacement or retirement | Removing the extension, exporting needed records, replacing the connection and retraining people. | Who can hand it over, what access is retained and how will old records remain understandable? |
Separate support promises. Fixing a defect against the agreed requirement, adapting to a new software release, answering a user question and adding another workflow are different tasks. Get their commercial treatment in writing. A response target says when someone responds; it does not necessarily promise when trading will be restored.
Microsoft’s support guidance separates scope, team and operations, including service hours, geography, access and escalation. Apply that discipline to the whole changed workflow. The person who takes the incident needs a way to coordinate the ERP, extension and connection providers, even if different suppliers own each part.
Before acceptance, require a handover pack: the business rule, settings or code/package location, agreed access and usage rights, supported versions, dependencies, test cases, recovery steps and support contacts. Confirm whether another qualified maintainer can take over and what contractual limits apply. Do not assume paying for development automatically gives you all source-code or ownership rights.
How do you protect upgrades, support and working records?
A supported extension method can reduce unnecessary interference with the standard product; it does not guarantee that every future update will work without attention. Ask whether the proposal changes the underlying product directly or uses its supported settings, extension or connection methods. Require an explanation of the implications for your actual hosting arrangement and support contract.
Microsoft’s extension strategy identifies maintenance, provider dependence and continuing product changes as explicit concerns. Its testing guidance defines regression testing as checking the system after changes or updates. In plain English: when this change or its dependencies change, rerun the important work that used to pass.
- Write the expected result before the test. Include a normal transaction, a rejected transaction, an unauthorised attempt and a correction to an existing record.
- Follow the result into the next job. Check order release, stock, shipment or accounts where the change affects them; a correct screen is not enough.
- For a connection, interrupt an update and send it again. Prove that the existing record can be recovered without a duplicate or an unexplained status change.
- Run the affected work on an access-controlled test copy after a relevant software, app or connection update. Mask customer data where appropriate and disable live emails, payments and external updates. Record the tested versions and who accepted the result.
- Agree the interim operating process if the change fails. Name who can pause work, authorise a workaround, reconcile affected records and approve a return to normal.
Removing a customization and restoring business records are not the same operation. Turning off a release rule does not undo a shipment. Restoring an old backup after live trading can discard later orders and payments. Have the support lead explain how to preserve and reconcile real transactions if a change must be withdrawn; do not accept “we can roll back” without that explanation.
For a wider production implementation, the ERP testing guide for manufacturers covers the full flow and go-live decision. This change checklist belongs within that programme, not in place of it.
For each country and legal entity affected, have the relevant finance or compliance reviewer identify the actual requirements affected by the change. A display field, a printable invoice and an external reporting connection are different deliverables. Do not let a layout change stand in for proof of an underlying requirement, and do not assume that a change accepted for one entity is valid for all of them.
When should you reject or defer an ERP change?
Reject the proposed design when it bypasses required approval, hides changes to important records, creates conflicting owners, or depends on unsupported behaviour with no acceptable maintenance route. Reject the request itself when its only benefit is copying a familiar screen and the supported process meets the agreed need with acceptable effort. Explain the evidence; “we do not customize” is not an adequate answer to a real operating gap.
Defer when the requirement is useful but not needed for the first phase, or when a demonstration or small investigation would resolve uncertainty. Record the interim process, its workload and control owner, the trigger for revisiting the request and a review date. Deferral without an owner can turn into permanent spreadsheet work.
Approve when the required outcome is clear, alternatives have been tested, controls survive, users can perform the work, and continuing cost and support are accepted. Limit the approval to the written change. Another customer, warehouse, workflow or reporting requirement may need a separate decision.
Repeated requests to replace core order, stock or accounting behaviour are a reason to revisit product fit before commissioning more changes. A carefully bounded extension can close a gap; rebuilding the operating model may mean the selected system or project scope needs another look.
Take one completed scorecard, a difficult real transaction and the supplier’s proposed maintenance terms to an ERP implementation discussion. If another application should retain the job, scope the integration and automation work separately. Decide what must remain true for the business, then choose the smallest supportable change that proves it.
Bring one real order, the systems it crosses and the exceptions your team handles manually. We can turn that journey into an implementation scope.