The complaint we hear on almost every call
"We don't trust our inventory numbers."
We hear some version of this from nearly every distributor and manufacturer we talk to. The details change, but the story is the same. The system says 40 units on the shelf. The picker finds 12. Somebody keeps a "real" spreadsheet on the side because the ERP can't be trusted.
And the first instinct is always identical: blame the software.
Sometimes the software deserves it. Usually it doesn't. When we run an operational assessment for a client, the distrust traces back to the same handful of root causes, over and over, regardless of which system is running the show.
The four root causes we find again and again
1. Mispicks nobody logs
A picker grabs the wrong SKU. Maybe the bins sit next to each other, maybe the labels look alike, maybe it was just a long Thursday. The order ships, the customer complains or quietly eats it, and somebody fixes the immediate problem.
What almost never happens is a correction in the system. So the shelf and the software drift apart, one order at a time.
One mispick is noise. A few hundred a year is a slow-motion corruption of every number your team looks at. And because nobody logs them, nobody can see the pattern either.
2. The annual physical count trap
Plenty of SMBs still run one giant physical count a year. You shut down the warehouse, hand everyone a clipboard, order pizza, and count everything over a brutal weekend.
Here's the problem. That count is a snapshot, and the picture starts aging the moment you take it. By spring, the numbers are stale. By summer, they're fiction. So the operation spends eleven months coasting on data it took two days of overtime to produce.
Cycle counting fixes this, and not because it counts more stuff. It counts continuously, in small bites, so errors get caught while the trail is still warm. A discrepancy found this week has a findable cause. A discrepancy found nine months later is just a write-off.
3. The ecommerce sync gap
If you sell through Shopify, Amazon, or any other channel alongside your ERP, you have two systems that each believe they know the truth. Most of the time they agree.
"Most of the time" is a terrifying phrase in inventory management.
Every sync failure creates a small divergence. An order lands in one system and not the other. A cancellation reverses in one place only. A quantity update times out. Each one is tiny, and each one compounds. Six months later, nobody can explain why the channels oversell items the warehouse swears it has.
4. Tribal knowledge instead of process
In a lot of warehouses, there's one person who just knows. They know the overflow pallet lives in the back corner. They know receiving holds Fridays until Monday. They know which vendor's counts run short.
None of that lives in the system. It lives in Dave's head. And the system's numbers are wrong precisely because the real process runs on Dave.
This works until Dave takes a vacation, gets promoted, or leaves. Then you discover the ERP was never actually running your warehouse. Dave was.
Why new software won't save you
Here's the part nobody selling software will tell you: replace your system without fixing the four problems above, and you'll get the same bad numbers in a more expensive package.
We've watched it happen. A company spends six figures and a year of pain migrating to a shiny new platform. Eighteen months later, the pickers keep the same side spreadsheets, for the same reasons, because the mispicks still go unlogged and the counting habits never changed.
The software vendors aren't lying to you, to be fair. Their systems genuinely can hold accurate numbers. But a WMS is a mirror. It reflects the discipline of the operation around it, and a mirror can't fix your posture.
Where to start instead
Before you evaluate a single platform, do two things.
- Map your current state. Follow inventory through your building the way it actually moves, not the way the org chart or the old SOP binder says it moves. Walk the floor. Watch a pick. Watch a return. Write down every place a human touches a number.
- Find the divergence points. For each of the four root causes above, ask where it shows up in your operation and how big the leak is. Some will be trivial. One or two will make your stomach drop.
Only after that does the software question mean anything. Sometimes the answer really is a new system. Just as often, the honest answer is that the system you own would work fine if the processes around it stopped fighting it. Anyone who tells you which one it is before doing this work is guessing.
The flag worth watching
When your team stops believing the numbers on the screen, take it seriously. That side spreadsheet your inventory manager maintains isn't a quirk. It's a vote of no confidence, cast quietly, every single day.
IT can't fix that for you, and neither can a purchase order. It gets fixed on the floor, in the counting habits, in the sync monitoring, and in getting what's in Dave's head into a process anyone can run.
Fix those, and you might be surprised how trustworthy your "untrustworthy" system becomes.