Short answer. Your stock does not match because the write-off happens at a different moment than the physical grab from the warehouse. Everyone just takes something, nobody books it out. You do not get a grip with stricter rules, but by tying registration to an action that already exists: scanning at the production order. Then the count is correct by itself.
A stock level is a snapshot that ages immediately. In most manufacturers I see, the gap between the system and the shelves is not a few percent but a question mark. Nobody trusts the numbers, so everyone goes to look for themselves. That is the real problem: you pay twice. Once for the system that is wrong, and once for the time people lose because they do not believe the system.
Why inventory in production always drifts apart
The cause is almost never laziness. It is timing. The raw material is grabbed the moment the operator needs it, in the middle of an order. The write-off happens later, sometimes at the end of the day, sometimes at the end of the week, sometimes not at all. Between those two moments sits a gap in which the physical stock and the booked stock drift apart.
On top of that come the familiar leaks. A delivery that contains slightly more or less than the packing slip. Rejects that are not written off. A semi-finished good that moves from one order to another because it happened to be lying ready. Small things one by one, together a count that is structurally wrong. Stock discrepancies usually arise from manual errors, delayed processing, or systems that are not properly linked.
Stricter registration rules do not solve it
The reflex is understandable: add a form, agree that everyone notes down every grab. That holds up for two weeks. After that everyone grabs something from the warehouse again, because it is faster and the order has to go out the door. Registration that sits on top of the work always loses to the work itself.
What does work is registration that coincides with an action that is already there. The operator books a production order, scans the order, completes a batch. At exactly that moment the raw material can come off too, automatically, based on the bill of materials. No extra action, no extra form. The write-off happens where the grab happens.
Examine the process first, not the software
Before I build anything, I walk the route of a raw material through the building. From arrival to inside the product. Nine times out of ten I find steps that once made sense and now only cost money. An intermediate stock that nobody uses anymore. A double count because two departments do not trust each other. An article code used for three different things.
That is not a software question. That is a process question. Some of those steps can be done smarter, some can simply go. Only when the process is right do you know what a system should support. Otherwise you automate the mess and just have it faster. A high number of stock corrections is often a symptom of process quality, not of careless people.
What a standard package does and does not cover
An ERP for the manufacturing industry handles the happy path excellently. Exact Online Productie bundles inventory management, bill of materials, work orders, and planning in one system, and an APS such as Limis lays production planning on top of that. For a company with tidy orders, fixed recipes, and few exceptions, that is enough. Then you should buy it and not start building it yourself. I tell clients that too.
It pinches at the exceptions. The semi-finished goods that shift from order to order. The leftover batch you still want to use but that falls outside the standard logic. The raw material you purchase per kilo and consume per unit. The cost allocation that your bookkeeper wants differently than the package assumes. No standard fits that, and that is where I build the difference.
In practice that is rarely a new system. It is a layer on top of what you have. A scan flow that ties the write-off to the production order. A link that automatically checks incoming deliveries against the packing slip and only presents the discrepancy to a person. A dashboard that puts the actual consumption next to the bill of materials, so you can see where you structurally grab more than you calculate. That is where a grip is created: numbers that are correct because they come from the real work, not from a form that sits on top of it.
Frequently asked questions
Why does my inventory never match in production?
Because the physical grab and the booking happen at different moments. The operator takes the raw material when the order calls for it, the write-off follows hours or days later, or not at all. In that gap, system and shelf drift apart. Tie the write-off to the production order and the gap disappears.
How do you prevent stock discrepancies without extra registration burden?
By having registration coincide with an action that is already there. An operator books a production order or job regardless. Let the raw material be written off automatically at that moment via the bill of materials, with a scan. No extra form, but a correct count. Supplement it with periodic spot counts on the most expensive items.
Do I need a new ERP to get a grip on raw materials?
Usually not. An ERP for the manufacturing industry covers the standard process fine. It pinches at exceptions: shifting semi-finished goods, leftover batches, purchasing per kilo and consumption per unit. There a layer on top of your existing system works better than a replacement, and it pays for itself faster.
What is the difference between a stock discrepancy and dead stock?
A stock discrepancy is a deviation between the booked and physical count: the system is wrong. Dead stock is material that is counted correctly but is no longer used for anything and only costs space and money. A good write-off flow solves the discrepancy; a dashboard on consumption exposes the dead stock.
Further reading
- Replacing Excel for production planning
- Cost price and post-calculation per order
- Registering shop floor hours and production orders
I am Ricardo Theijs of RNT Projects. With a background in enterprise process management (UWV, Centric, G4S, MSc Business Process Management), I build systems that turn fragmented operations into one whole. I say it honestly when a standard package is enough.
Running into this yourself?
I review your process and build the solution where a standard package falls short. Remote, with visible results in two weeks.
Let's talk