Inventory Is Usually Wrong Long Before the Count Proves It | Observations from the Shop Floor
Michael Gardner, COO
Most inventory problems do not begin during a physical count: the count simply reveals them.
I learned that lesson years ago through a customer phone call that started out routinely and ended with an important reminder about the difference between what the system says and what is actually happening on the shop floor.
A customer called on Monday needing a product for delivery on Thursday.
I checked inventory and saw that we had five units on hand. As I looked further, I noticed another shipment of the same product scheduled to arrive on Wednesday. Since Wednesday was our loading day, I felt confident telling the customer we could take care of his order.
Everything looked fine.
Then Thursday afternoon the customer called back. He was upset because he had not received the product.
The first question was obvious: what happened?
When we investigated, the person responsible for pulling the order told me there was no inventory in the location where the product should have been stored.
That didn’t make sense.
The system showed five units available.
As we dug deeper, we found the missing inventory sitting in our damaged material area. The product had been identified as damaged, but it had never been removed from available inventory. The employee responsible for processing damaged material happened to be on vacation that week, and the adjustment had not been completed.
The system still believed the material was available; operations knew otherwise.
At that point, I thought the Wednesday replenishment shipment should have saved us.
After all, the product had arrived exactly as expected.
Then we discovered the second problem.
The system showed the material as received, but the product was still sitting in a container on the receiving dock.
It had not yet been put away into its storage location.
Technically, the receipt transaction had been completed.
Operationally, however, the material was not available to be picked, loaded, or delivered.
The inventory existed… it simply wasn’t accessible.
That experience exposed something even more important: our receiving process was marking material as received when it arrived at the dock, not when it was actually put away and available for use.
From a system perspective, inventory had arrived.
From an operational perspective, inventory was still in transit within our own building.
The customer didn’t care about either explanation.
He only knew that we told him we had the product and failed to deliver it.
That experience taught me that inventory accuracy is not primarily an accounting issue, it is an operational discipline. Most inventory discrepancies are not created during the annual physical count. They are created weeks or months earlier through dozens of small process breakdowns:
- A damaged item that isn’t adjusted, a receipt entered before material is truly available
- A return that isn’t processed
- A substitution that isn’t recorded
- A pallet moved without updating its location
Each event seems minor at the time.
The gap between operational reality and system reality grows a little larger with every exception.
Eventually, someone performs a physical count and discovers the difference.
The count didn’t create the problem. It simply proved it existed.
That is why I often say inventory is usually wrong long before the count proves it.
The best organizations understand this. They do not treat inventory counts as an exercise in correcting numbers. They treat them as an opportunity to identify where operational truth and system truth began to diverge.
Every variance tells a story. The real question is not “What should the quantity be?”
The more important question is, “Where did the truth get lost?”
Because by the time a count proves inventory is wrong, the business has often been paying the price for weeks.
In missed deliveries, emergency purchases, excess inventory, and frustrated employees.
And sometimes, in a phone call from a customer who simply wants the product you promised him four days earlier.
Final Observation
Experience has taught me that inventory problems rarely begin with inventory. They accumulate quietly through small exceptions that seem harmless in the moment. A receipt entered a little early. A damaged item left available. A pallet moved without updating its location. None of those events feels significant by itself, yet together they slowly separate the system from reality until one day the gap becomes impossible to ignore.
Looking back, that customer call was never really about the missing inventory. It was about a process that quietly allowed reality and the system to drift apart, one small exception at a time. The organizations that maintain accurate inventory aren’t necessarily the ones that count more often. They’re the ones that consistently execute the small operational disciplines that keep the system aligned with reality.
Inventory accuracy isn’t built during the physical count.
It’s built every day, one honest transaction at a time.