The system says 40 on the shelf. The picker finds 12. Somewhere in the building there's a spreadsheet with the "real" number, kept by someone who stopped believing the ERP a while ago.

I hear some version of this on nearly every first call with a distributor or manufacturer. The instinct is to blame the software. Sometimes that's fair. Usually it isn't. When I follow the numbers back on the floor, the distrust traces to the same four habits, whatever system is running.

1. Mispicks nobody logs

A picker grabs the wrong SKU. The bins sit side by side, the labels look alike, it's late on a Thursday. The order ships, the customer complains or quietly eats it, and somebody fixes that one order.

Nobody fixes the system. The shelf and the software drift apart one order at a time, and because none of it gets logged, nobody can see the pattern. One mispick is noise. A few hundred a year rot every number your team looks at.

2. The once-a-year count

Plenty of smaller operations still count everything over one brutal weekend: building shut, clipboards out, pizza ordered. That count is a snapshot, and it starts aging the moment it's done. By spring the numbers are stale. By summer they're fiction.

Cycle counting fixes this because it never stops, not because it counts more. A variance you find this week still has a findable cause. One you find nine months later is a write-off.

3. Two systems that each think they're right

If you sell on Shopify or Amazon 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 scary phrase in inventory.

An order lands in one system and not the other. A cancellation reverses in only one place. A quantity update times out. Each miss is tiny, and they stack. Six months on, the channels oversell items the warehouse swears it has.

4. The process lives in one person's head

Most warehouses have someone who just knows. The overflow pallet is in the back corner. Receiving holds Friday's trucks until Monday. One vendor's counts always run short. None of that is in the system, which is why the system's numbers are off.

It works until that person takes a vacation or leaves. Then you find out the ERP was never running the warehouse. They were.

Why a new system won't fix it

Replace the software without changing those four habits and you'll get the same bad numbers in a more expensive package. I've watched a company spend six figures and a year migrating, then find its pickers back on side spreadsheets eighteen months later, for the same reasons as before. A WMS reflects the discipline around it. It can't supply that discipline.

Where I'd start

Walk the floor and follow inventory the way it moves: a receipt, a pick, a return. Write down every place a person touches a number. Then, for each of the four habits above, ask where it shows up in your building and how big the leak is. Most will be small. One or two won't be.

Only then does the software question mean anything. Sometimes the answer is a new system. Often the one you own works fine once the process stops fighting it.

That side spreadsheet your inventory manager keeps isn't a quirk. It's a vote of no confidence, cast every day. Take it seriously.