ERP systems
Why traditional ERP systems fail in manufacturing
Almost every ERP system I've seen over the past eighteen years grew out of accounting. First invoicing, then the warehouse, and production somewhere at the end, if at all. The problem is that in a manufacturing company it works exactly the other way around. First the order is created, then production, and invoicing is the last step, not the first.
When a system is built on accounting logic, production has to be squeezed into it afterward. And that's exactly when the compromises start that end up costing the company time and money within a few months.
Accounting counts, production plans
An accounting system asks what has already happened. How much has been invoiced, how much is in stock. Production needs something different: to know what needs to happen next. When a machine is free, who has capacity, what's waiting on materials.
This isn't just a different view of the same data. It's a different way of thinking about the company. When the two get mixed up, you end up with production modules that are really just stock cards with a different name.
Where it hurts the most
I see it over and over. A salesperson promises a deadline that production can't meet, because the system never gave them a real picture of capacity. Or production falls behind, because the system can't connect a change in the plan with what's already on order in the warehouse.
The people struggling to make sense of the system aren't to blame. The system is — designed from the start for different work than what the company actually does. When something goes wrong, a person gets blamed, even though the problem sits one floor down, in how the system was designed.
What to build instead
A good system for a manufacturing company starts with the order and product configuration, not the invoice. Only once it's clear what needs to be made and when can it derive the warehouse, planning, and finally invoicing from that.
When companies keep their own spreadsheet alongside an expensive ERP system, it's usually not laziness. It's a natural reaction to a system that doesn't speak the language of their operation. Excel at least speaks their language, even if it's fragile and unreliable.
What to take away from this
If you feel like your system is holding you back more than it's helping, try asking where it actually came from. If the answer is "from accounting," you've probably just found the reason.