Here is the conclusion up front: with WMS cycle counting you never shut the warehouse down and never stop the lines. Count a small batch every day, thirty minutes to an hour of work, and over a year your inventory accuracy holds above 98%, with A-class items reaching 99%. If you cannot hit those numbers, the problem is not counting itself. It is the way you count. Too many warehouses do one big annual count, find hundreds of variances, and by then the root cause is long gone, so everything gets written off in one adjustment and the same mistakes repeat next year. Cycle counting flips that around: one big count becomes 200-plus small counts spread across the year, and a variance gets caught within days of appearing, while the cause is still on the floor and still fixable.
Why WMS cycle counting beats one annual shutdown count
The biggest flaw of the annual count is not the effort. It is the delay. A mistake buried in March — a picker grabbing from the wrong bin — leaves the system record wrong for nine months, and every pick, replenishment, and purchase suggestion in between is built on a wrong number. By the time the year-end count finds it, nobody on the floor remembers what happened. WMS cycle counting works the other way: a variance surfaces within days, you ask the shift that was on duty, and they still remember.
In May 2024, a third-party auto parts warehouse in Guangdong called me in to fix exactly this. One A-class brake pad SKU showed 120 units in the system. The physical count found 96. Twenty-four units short, real money. Under the old approach this would have surfaced at the year-end count. Under cycle counting, this SKU gets counted monthly, so the variance was caught in the month it appeared. Tracing it back, two adjacent bin labels differed by a single digit, and pickers had been pulling from the wrong bin for three weeks. We changed the bin codes and added a scan verification step on the pick path. That SKU then ran four straight months with zero variance. From variance to root cause fixed: under a month. With an annual count, that hole would have sat there for eleven months and grown.
Here is a contrarian judgment worth stating plainly: counting more often does not automatically mean counting more accurately. Some warehouses hear that cycle counting works and the next day order everyone to count 200 items daily. Two weeks later the team is exhausted and the numbers are still wrong. Counting is a tool, not the goal. Frequency has to match your capacity to investigate root causes. If you can properly clear 20 variances a day, do not generate 50. Count faster, investigate sloppier, go wrong faster. I have seen this pit three times, and each time it was management adding volume on a whim while the floor chased quantity to report.
ABC tiers for WMS cycle counting: who gets counted often, who gets counted rarely
The first step of cycle counting is not counting. It is classification. Not every SKU matters equally. Rank items by outbound volume or value, and typically about 20% of SKUs drive roughly 80% of volume and value. That is class A. The middle 30% is class B. The remaining 50% is class C. Frequency follows the tier: A items monthly, B items quarterly, C items once or twice a year. This is the standard industry practice, and nearly every guide on the subject recommends the same split.
The easiest trap is classifying once and trusting it for a year. An item's status changes: a new customer arrives and a C item becomes a bestseller overnight; a customer leaves and an A item stops moving for three months. Re-run the classification at least every quarter using the last twelve months of data. In November 2023, an e-commerce warehouse in East China fell into this exact hole. After the Singles' Day peak, their variance rate climbed from 0.8% to 3.2%. The investigation showed the bestseller list had changed but the count plan still ran on the January tiers, so the real high-velocity items had not been counted for a month. Once the tiers were refreshed, the variance rate was back under 1% within two months.
The table below is a workload estimate for a 5,000-SKU warehouse. The numbers are a hypothetical example, shown only to size the work:
| Tier | SKUs | Frequency | Counts per year | | A | 1,000 | Monthly | 12,000 | | B | 1,500 | Quarterly | 6,000 | | C | 2,500 | Once or twice a year | ~3,750 | | Total | 5,000 | — | ~21,750 |
About 21,750 counts a year, spread over 250 working days, is roughly 87 items a day. At an average of three minutes per count, that is about four and a half hours a day, or a little over two hours each for two people. Do this math before go-live. If the workload exceeds what the floor can carry, the plan dies in week one. My approach is to staff against this table, run it for two weeks, then adjust. Never lock it in on day one.
How the daily count list works, and how variances get dispositioned
Let the WMS generate the count list automatically. Do not schedule it by hand. Every morning the system issues a list based on the ABC rhythm: which few dozen SKUs today, which zone, which bins. The list has to meet three conditions. First, blind counts: the counter must not see the system quantity before counting, or everyone will simply "find" the system number. Second, sequence by bin location so the counter is not running back and forth across the warehouse. Third, unfinished items roll to the next day automatically instead of quietly disappearing.
Variance disposition is the part of the process most often glossed over. My rule: classify first, adjust second. Variances fall into four buckets, each handled differently: wrong pick, wrong putaway, system posting missed, physical damage or loss. The first two are process problems, so fix the process before touching the books. A missed posting means checking interfaces and documents. Only when the stock is confirmed genuinely gone do you post a loss adjustment. Keep adjustment authority tight: counters report, supervisors approve. Who adjusted what, why, and how far the investigation got must all stay in the system log.
One more rule that gets overlooked: set variance thresholds by value. A C item off by one or two units, worth a few dozen yuan, costs more to investigate than the stock is worth. Log it and adjust. An A item off by one unit, worth over a thousand yuan, must be traced to root cause. Write the thresholds into policy instead of leaving them to judgment calls.
Go-live night checklist: five pits I have seen three times
First, is blind counting actually switched on? Cycle counting without blind counts is not counting at all. Counters copy the system number onto the sheet, accuracy reads 100%, and all of it is fake.
Second, is adjustment authority tightened? In a warehouse where anyone can post adjustments, variances never get investigated, because adjusting is too easy.
Third, was the ABC table re-run within the last quarter? Counting this year's stock against last year's tiers means counting the wrong priorities.
Fourth, did anyone do the labor math on the daily list? A list of 200 items on day one means the floor fails on day one, and by day two nobody believes in the mechanism anymore.
Fifth, does the monthly variance review actually happen? Once a month, pull the top ten variance SKUs and walk through each root cause. Without that review, cycle counting is just repetitive labor, and inventory accuracy keeps failing in the same place.
WMS cycle counting is not sophisticated technology. It is replacing one year-end reckoning with a small reckoning every day. Once the mechanism is in place, the warehouse gets more accurate with every count, because each variance teaches you where the process leaks. If your warehouse cannot get there, check the five items above. You will find at least two of them apply.
By Lin Xiao, WMS Implementation Consultant









