Inventory mismatch? The truth I learned after ten years in warehouse management

Last Singles' Day, at 2 a.m., I was squatting in a corner of the warehouse, staring at my phone. A customer had sent a voice message, and when I played it, she yelled at me for half a minute: "Your system says it's in stock, I ordered three days ago, and you still haven't shipped? Do you even have the item?!" I quickly checked the system—it showed 12 units in stock. But I searched every shelf and found nothing. At that moment, I felt completely numb. It wasn't the first time, but every time it happened, I wanted to smash my computer.

TL;DR: Inventory inaccuracy isn't a system problem—it's a process and people problem. It took me ten years and tens of thousands of dollars in losses to realize that inventory management is not about keeping numbers, but about managing processes. Today, I share my painful experiences and practical solutions for the three root causes of inventory inaccuracy.

Root Cause #1: The "good enough" attitude during receiving

Honestly, I used to do it too—when a supplier delivered goods, I'd roughly count them, toss them on a shelf, and update the system with a ballpark number. I thought "close enough" would work. But when it came time to ship, either the items were missing or the count was off.

Later I realized: every "good enough" in receiving is a time bomb for inventory inaccuracy.

The cost of sloppy receiving

I tracked it once: before I fixed my receiving process, inventory discrepancies caused by sloppy receiving cost me about 20,000–30,000 RMB per month. For example, one time a shipment arrived, and my staff, trying to save time, didn't open the boxes to inspect. They just scanned the barcodes and received them into the system. Later we found that one box was missing 5 units, but the system already recorded them. So our books showed phantom inventory. When a customer ordered those units, we shipped an empty box, got a complaint, and had to pay compensation.^[1]

How to implement a proper receiving process?

I eventually mandated a three-step receiving process:

• Step 1: Physical count. Check every item against the supplier's packing list. No exceptions.
• Step 2: Scan and put away. Scan each item, and the system automatically records the storage location.
• Step 3: Spot check. The supervisor randomly audits 10% of receiving records to ensure accuracy.

At first, employees resisted—they thought it was too slow. But I stuck with it for a month, and the receiving error rate dropped from an average of 15 per month to less than 1.

Comparison: Before vs. After process improvement

Root Cause #2: The "ship first, record later" habit

This was my deepest pitfall. During peak seasons, to speed up shipping, my staff would grab items and pack them first, and only record the transaction later—when they had time. But in the rush, they often forgot or misremembered the quantity. So the system showed stock that had already been shipped.

Anyone who's been there knows: ship first, record later is like planting landmines in your books.

A lesson that cost me 50,000 RMB

During last year's 618 promotion, we had a hot-selling item. The system showed 80 units in stock, and customers were ordering like crazy. We took orders based on that number. But after fulfilling 60 orders, we ran out of stock. Investigation revealed that the night before, an employee, trying to meet shipping deadlines, had taken 30 units and shipped them without recording the deduction. We oversold 20 orders, paid penalties, and got fined by the platform—total loss over 50,000 RMB.^[2]

The fix: enforce "record first, ship later"

I mandated the following process:

• Employees must scan the picking list with a PDA. Only if the system confirms sufficient stock can they pick items.
• After picking, they immediately scan to confirm the shipment, updating inventory in real time.
• Any exceptions (e.g., urgent transfers) must go through system approval; no manual operations allowed.

Efficiency dipped slightly at first, but within a week, everyone got used to it. Not only did inventory accuracy improve, but shipping error rates also plummeted.

Outbound process: Before vs. After

Root Cause #3: Treating inventory counts as a checkbox exercise

I used to hate counting inventory. I thought it was tedious and useless. Every month end, we'd stay up late counting, then adjust the system and call it done. But inventory was still inaccurate the rest of the month.

Later I understood: counting isn't a monthly surprise—it's a daily calibration.

Evolution of counting methods

I tried three approaches:

• Full count: Once a month, all hands on deck, took two days, exhausting, with limited accuracy improvement.
• Spot count: Only count high-value or fast-moving items, but you miss problem areas.
• Cycle counting: Count a portion every day, covering all inventory in a month, taking only 30 minutes each time.

I settled on cycle counting. Every day at a fixed time, an employee counts a designated zone. If discrepancies are found, they investigate and correct immediately. This spreads the workload and catches problems early.^[3]

How to implement cycle counting

• Divide the warehouse into 10 zones. Each morning, spend 30 minutes counting one zone.
• After counting each zone, the system generates a discrepancy report, and the supervisor must resolve it the same day.
• Monthly summary identifies high-frequency problem zones and items for targeted improvement.

After three months of cycle counting, inventory accuracy rose from 88% to 99.2%.

Comparison of counting methods

The ultimate solution: Let the system manage processes, not people manage numbers

Honestly, I used to think inventory management was just about keeping accurate numbers. So I bought various inventory software. But the problem persisted—numbers were still wrong. Eventually, I realized the root cause was out-of-control processes, and that was because we relied on people instead of systems.

That's why I built Shancang WMS—to embed processes into the system, letting the system manage people, not the other way around.

How the system helps

• Receiving must be scanned: The system forces every item to be scanned before it can be received. No scan, no receipt.
• Shipping must deduct: The system automatically checks inventory. If stock is insufficient, it blocks the shipment.
• Counting is auto-triggered: Based on inventory velocity, the system generates cycle count tasks and pushes them to employees' phones.
• Real-time alerts: When a discrepancy is detected, the system immediately notifies the supervisor and locks the affected items to prevent error propagation.

Since adopting Shancang, my inventory accuracy has stabilized above 99.8%, and I haven't been yelled at for inventory issues since.^[4]

Summary

Inventory management took me ten years to figure out. It's not about keeping numbers—it's about managing processes. Receiving, shipping, and counting—each step needs strict procedures and system enforcement.

Three pieces of advice from the bottom of my heart:

• Don't be "good enough" in receiving—a small gap can become a huge loss.
• Never ship before recording—"record first, ship later" is non-negotiable.
• Don't treat counting as a chore—cycle counting is the way to go.

If you're struggling with inventory accuracy, start by auditing these three areas. I promise, fixing them will take your accuracy to the next level.

---

References

1. Fortune Business Insights WMS Market Report — Referenced for WMS market size and impact on inventory accuracy
2. Gartner Supply Chain Research — Referenced for supply chain best practices and inventory process recommendations
3. McKinsey Operations Insights — Referenced for operational efficiency improvement and process optimization cases
4. China Federation of Logistics & Purchasing — Referenced for domestic warehouse management standards and practice data