The ERP says you have 40 units of a component in stock. The shop floor knows better: 12 of those are already staged for a job that hasn’t been logged as “started” yet, 6 are set aside for a rework, and the real available count is closer to 22. Nobody updated the ERP because updating the ERP takes longer than just grabbing the parts and moving on. Multiply that gap across every SKU in the building and it’s not hard to see why a supposedly real-time inventory count is wrong the moment anyone actually checks it.
This is the quieter cousin of the spreadsheet problem we’ve written about before. It’s not that manufacturers don’t track inventory. It’s that the tracking splits across the ERP, a shop-floor staging area nobody logs in real time, and a supplier relationship that only reports lead times when someone calls to ask.
Why the ERP Count Drifts From the Real Count
ERPs are built around transactions: a receipt, a pick, a shipment. Manufacturing floors don’t move in clean transactions. Material gets staged ahead of the job. Partial quantities get consumed and the rest gets returned to a bin that isn’t the bin it came from. A rework pulls stock without a formal transaction because the priority is fixing the part, not updating a screen. Every one of those moments is a small drift between what the ERP believes and what’s physically true, and they compound fast.
We’ve made this same argument about ERPs that don’t match how your process actually works: the system isn’t wrong, it’s just modeling a version of your operation that doesn’t account for how material actually moves on your floor. Forcing every staging and rework transaction into the ERP’s model is exactly the kind of six-figure customization quote that never gets approved, so the drift just becomes permanent.
The Supplier Side Has the Same Gap
Supply chain visibility has the identical shape, one level up. Your ERP has a promised lead time for a component. The supplier’s actual production status, whether that order is on track or already slipping, lives in an email thread or a phone call, not in a system you can check. You find out about a delay when the material doesn’t show up, not three weeks earlier when the supplier’s own schedule started slipping.
Some of this is unavoidable without supplier cooperation. But a surprising amount of it is just a status field that exists somewhere, in a supplier portal or a shared tracking sheet, and never makes it into the same view as your production schedule. That’s a visibility problem, not a supplier-relationship problem, and it’s solvable the same way.
Closing the Gap Without Replacing the ERP
The fix isn’t a bigger ERP module. It’s a lightweight layer that captures the transactions your team already does in practice, staging, partial consumption, rework pulls, without asking anyone to learn a new system, and reconciles that against the ERP’s official count. Same idea we build into replacing the spreadsheets your operation depends on: meet the real workflow where it is, then make the data flow from there instead of forcing the workflow to match the software.
If your team already knows the ERP’s inventory count is wrong and works around it instead of trusting it, that’s not a discipline problem. It’s a signal that the system doesn’t capture how material actually moves. Tell us where the count drifts and we’ll tell you what closing that gap would take.