ERP customisation
The step your ERP is missing, built in.
Reports, approvals, checks and bulk changes built inside the ERP you already run, to the framework’s conventions, so they carry through upgrades with little or no rework.
The workaround people live with
The ERP runs. One step still happens by hand.
“A report finance rebuilds by hand every month.” “An approval the software does not know about.” “A part used in more assemblies than anyone will edit by hand.”
The work waits on a person because the system is missing one step. That step can be built in.
How a step gets added
Find the gap. Build to fit. Prove it before it goes live.
01 / 04
Find the gap
We look at where the work stops and waits: the spreadsheet beside the ERP, the email approval, the manual check.
What you doYou describe the step people work around.
02 / 04
Build to fit
The missing step is built inside the ERP, in the documents people already use, to the framework’s conventions.
03 / 04
Test before live data
A written test procedure is signed off before anything touches live data. Bulk changes report the result of every row.
What you doYou sign off the test procedure.
04 / 04
Run in production
The work flows through the new step with the rest of the system, built to carry through upgrades.
What gets added
What can be added
- Reports that now live in a spreadsheet next to the ERP
- Approvals, validations and status tracking inside the documents people already use
- Bulk operations the standard screen cannot do safely
- Fixes to customisations a previous developer left behind
- Plugins and extensions: a feature built for one business, not a product off a shelf
Each one is built for how your business works.
Built with the framework
Built with the framework, not around it.
Customisations are built to the framework’s conventions, so they carry through upgrades with little or no rework.
Bulk changes create new revisions instead of editing in place, and every row’s result is tracked. A written test procedure is signed off before anything touches live data.
Built and in production
Swap a part across thousands of bills of materials, in one go.
Built before BI Margin, inside ERPNext, for a manufacturer. Replacing a single component can touch thousands of bills of materials and every assembly built on them, and that used to mean editing them one at a time. Now it is one reviewed run: each bill becomes a new revision, quantities and units are checked, every line reports its result, and work already on the shop floor keeps the version it started with. In production.
5+ years of hands-on software development, integration, optimisation and automation.
Whoever put the ERP there
It does not have to be an ERP we put there.
We work inside systems someone else implemented, and alongside a vendor on the parts they will not or cannot do.
Before BI Margin, we built and delivered on ERPNext; the method carries to other platforms, Odoo included.
Quoted in writing after the assessment.
Customisation has no list price. It is scoped in the Systems Assessment and quoted in writing. Book a call and describe the step people work around.
Next step