ERP vs a custom operations platform
I have lost count of the manufacturing and operations teams who tell me, with real frustration, that their ERP is technically working and yet nobody likes using it. That is the gap this article is about. ERP is not wrong. It is just built for a generic version of your business, and the generic version is rarely the one you run.
ERP is not always the answer
Traditional ERP categories assume a fairly standard manufacturing or distribution shape. Print shops, mixed production runs, and service-led operations rarely fit that mould cleanly. You end up with modules you do not use, terminology that does not match the shop floor, and production stages that have to be forced into fields that were never meant for them. The software is comprehensive, but comprehensive is not the same as fitting.
There is also a timeline problem. Full ERP programmes are long, and over the last couple of years buyers have become far more wary of multi-year implementations that drift past budget before anyone logs in. A focused operational layer that ships in phases is a very different risk profile.
Custom as the operational layer
A pattern we use often is to leave accounting or a legacy ERP exactly where it is, and add custom software for the workflow your team lives in all day. That might be order to dispatch, a customer portal, or the automation that removes manual handoffs between departments. The system of record stays put, and the layer your people actually touch is built around how they work.
What this looks like in production
For a printing and manufacturing client we built a single platform that carries one customer order through material reservation, purchasing when stock is short, stage-by-stage production logging, and dispatch. One order drives the whole chain. Managers, planning, warehouse, and production each get a view shaped for their role rather than one screen that tries to serve everyone.
Generic ERP forced the wrong workflow, terminology, and production stages for how this shop actually runs jobs.
When you should still pick ERP
If your processes are genuinely standard, your reporting needs match what packaged ERP reports out of the box, and you value a single vendor relationship over a tailored fit, ERP is the pragmatic choice. Custom is worth the effort when the operational layer is where your advantage lives, and when bending a generic product would cost you more in daily friction than building the right thing once.
Krish owns architecture and delivery at Aviu Solutions, from discovery blueprints through phased build, integrations, and migration off legacy tools.