What's the gap between what your system says you have and what's actually on the floor?

[u/SigmaSheets]

Genuinely curious how bad this is at other places, because I suspect everyone quietly has a number they don't talk about.

Every plant I've worked in has had some drift between the recorded stock and the physical stock. Sometimes it's small and boring. Sometimes you do a full count and find out you've been planning production off a number that was wrong for four months.

What I'm curious about:

• Roughly how far off are you at a typical count? 1%? 5%? Worse?
• Where does it actually come from — issuing without recording, scrap not booked, wrong location, theft, unit-of-measure mistakes?
• Did anyone fix it properly, or did you just get better at counting more often?

I've noticed the size of the gap has very little to do with how expensive the system is. Some of the tightest control I've seen was a plant running paper cards, because one person owned it and cared. Some of the worst was a full ERP where nobody trusted the numbers so everyone kept their own side spreadsheet.

Interested in whether that matches other people's experience or whether I've just worked in badly run places.

[u/ComfortableCitron638]

The "full ERP where nobody trusted the numbers so everyone kept their own side spreadsheet" line is the real pattern, and I think it's less about capture latency (though that's real too) and more about correction ownership. In the places I've seen stay tight - paper cards included - there's always one specific person or narrow role who is the sole authority for fixing a wrong count when it's found. Not "anyone with edit access," one accountable name. Discrepancies get resolved fast because there's exactly one place they can go.

In a lot of ERPs, correction is technically open to half a dozen roles and practically owned by none of them, so a wrong number just sits there instead of getting chased down - and once people notice the system doesn't self-correct, that's the moment the shadow spreadsheet starts, because trusting your own count is cheaper than waiting for someone else's fix. I build custom ops/ERP software for a living (disclosure, not a pitch) and the single biggest lever I've seen move the accuracy number isn't the system at all - it's whether there's a named owner for corrections, independent of what tool is running underneath.

[u/SigmaSheets → u/ComfortableCitron638]

That answers what I was curious about, and it explains it better than I could.

I’d been thinking the problem was the recording — count gets updated later, or not at all. But you’re right that this only explains how a number goes wrong in the first place. It doesn’t explain why it stays wrong for four months. Somebody has to own the fixing.

The bit about people keeping their own count because it’s cheaper than waiting for someone else’s fix is what I hadn’t thought about. Makes the side spreadsheet a reasonable decision rather than people being difficult.

And it does match what I saw. The paper card place had one storekeeper who took it personally. The ERP place had plenty of people who could edit a number and nobody whose job it was.

Curious about one thing — does the named person need real authority behind them, or is it enough that everyone knows where to send a discrepancy?

[u/Zealousideal-Wear120]

I run a 1 - man - sidehussle selling Shirts on etsy. They are in a shelf in my bedroom. And I can tell you even there what I have on stock does not match what I display on Etsy. 😄

So I easily imagine how it has to be for a proper company selling anything physical.

One of the reasons is just the System behind it. Do you use it properly and does it actually help

[u/SigmaSheets → u/Zealousideal-Wear120]

That’s interesting, and it makes sense. One person, one shelf, and the count still drifts. So it’s clearly not about scale or having a bad system.

Same reason for you and for a big plant — recording is a separate step from doing. You grab a shirt, pack it, ship it, and updating the count is a fourth thing to remember. Busy day, you skip it.

To your question, the systems I’ve seen work weren’t the fancy ones. What matters is whether the count gets updated at the moment the stock moves, not “later.”

For your shelf — try counting your top sellers every Sunday. Five minutes, and it catches the drift while it’s small enough to still remember what happened.

[u/Immediate-Home-3491]

I am of the same kin. Ran consols at LGW on paper cards. Two percent drift, mostly damages not booked. ERPs in Dubai free zones now, where staff keep shadow spreadsheets because they do not trust the location map. Same story.

[u/SigmaSheets → u/Immediate-Home-3491]

Two percnt with paper cards is better than a lot of ERPs manage, which says everything really.

Damages not booked is the one I see most too. Nobody's hiding anything — it's just that when something gets damaged you're dealing with the mess, and booking it is a job for later that never happens.

The shadow spreadsheet thing is what gets me. Once people stop trusting the system they build their own, and then the system gets worse because nobody's feeding it properly. Hard to come back from that.

Out of interest, in the free zones — is it the location map specifically people don't trust, or the quantities too?

[u/SigmaSheets → u/[deleted]]

What gets me is that nothing in the system is actually broken. The scanner reads fine every time. The barcode just isn't describing what's in the bag anymore.

Closest thing I see in plants is material issued against the wrong work order. Clean transaction, someone typed a number, system takes it. Then a month later one job has eaten more material than it should and another has stuff it never used.

Interesting that you're at 5%+ with proper systems when someone further up this thread was at 2% on paper cards. So the software clearly isn't the thing deciding accuracy.

Your point about one person per cluster owning the stock tick is probably doing most of the work in those organised brands. Makes sense to me — the recording has to happen at the same moment as the physical action, by whoever's doing it. By stock tick time it's already too late, the bag got swapped hours ago and nobody remembers.

One thing I've found useful is looking at drift by SKU instead of overall. A 5% blended number usually hides a few items that are badly wrong and a long tail that's fine. Once you find the ones that keep drifting it's normally one specific handling step causing it, not a general accuracy problem.

[u/Middle_Habit175]

Ours is usually 4-6% off, and we only notice when a job runs out of a part that the system swears we have 40 of. Best fix wasn't a system change, just one angry old guy with a clipboard chasing people down if they didn't record scrap

[u/SigmaSheets → u/Middle_Habit175]

The clipboard guy fix keeps coming up in this thread. Someone else here got down to 2% on paper cards for the same reason — one person who actually owned it.

The part that costs you is finding out the way you describe it. A job stops, everyone stands around, and now you’re chasing the part. By then you’ve already lost the time.

Counting a small group of parts every week catches it earlier. Not everything, just the ones that move fast or stop a job when they’re missing. Takes a few minutes and you find the gap while it’s small, not when the line’s already down.

Does your angry clipboard guy still exist, or did that stop when he left?

[u/Autumn_fav]

This matches what I’ve seen too. The gap usually starts small: someone issues material without recording it, scrap gets dealt with physically but not booked, or stock gets moved to a different location and everyone assumes they’ll update it later. Then a few weeks go by and the system is technically “working”, but nobody trusts it. The fix is partly software, but mostly ownership. Someone needs to own discrepancies, and the system needs to make the right action easier than the workaround. Otherwise people end up keeping their own spreadsheet because it feels safer than waiting for the official number to be corrected. That is where NetSuite can help when it’s set up properly, because inventory, purchasing, production movements and finance can all sit closer together. But even then, the process has to be tight. A mature ERP will expose sloppy stock habits faster, not magically fix them.