When the ERP Gets Blamed for a BOM Problem
A $200 million manufacturer brought us in convinced their business system was the problem. The signs looked like a classic software failure: inventory accuracy was a disaster, expediting charges were bleeding money every month, and quarter after quarter, purchase price variance swings were tanking the bottom line. Leadership was already shopping for a replacement system.
The system wasn’t the issue. Production was changing bills of material on the fly, on the floor, without looping in sustaining engineering or inventory control. Every change was a small, reasonable decision in the moment. None of them made it back into the system of record.
The fix wasn’t a new ERP. We worked through every BOM with the production floor, processed the backlog of change orders, and got engineering, inventory, and production talking on the same page again. Once the data matched reality, the system started working exactly the way it was supposed to.
Before you sign off on an upgrade or a full replacement, check whether your teams are actually talking to each other. Most of the time, that’s the real fix.
Author Profile
Latest entries
- August 20, 2026InsightsWhy Most ERP Implementations Fail Before Go-Live — And How We Do It Differently
- August 18, 2026AllEnd-to-End Plex ERP Implementation: ProSpot International Case Study
- August 17, 2026InsightsMonth-End Close Shouldn’t Feel Like Damage Control
- August 17, 2026InsightsMonth-End Close Shouldn’t Feel Like a Hostage Situation


