The annual count is a ritual, not a control
A shutdown weekend tells you how wrong you were, long after you could act on it. Cycle counting tells you while it is still small enough to fix.
Updated August 9, 2026
Every distributor who has done a wall-to-wall count knows the routine. The warehouse closes on a Friday. Everyone available gets a clipboard and a section. Somebody recounts the disputed bins on Saturday. On Monday a variance number lands on the finance team’s desk, gets absorbed, and the year starts again.
The count is treated as a control. It is not one. It is a measurement, taken once, of a value that has been drifting for twelve months, and it arrives far too late to act on. By the time you learn that a fast-moving bearing has been running short since spring, the orders it delayed have already been late.
What the annual count actually tells you
It tells you the size of the gap. It does not tell you where the gap came from, when it opened, or whether it is still opening. Those are the questions worth answering, and a single annual snapshot cannot answer any of them.
Worse, it is measuring everything with the same effort. The bin holding a fitting you sell forty times a week gets counted exactly as often as the bin holding a part you have shipped twice since 2023. One of those is a real risk to your order promises, and the other is a shelf you could safely ignore for a year. The annual count treats them identically because it has no way not to.
Counting by risk instead
Cycle counting inverts it. Instead of counting everything once, you count each item as often as being wrong about it would hurt.
Counting built into the daily flow rather than scheduled once a year is one of the practical differences between inventory software and a warehouse management system. In Hangar that frequency is a property of the item group, not a decision somebody makes each morning. Fast movers might be counted weekly. Mid-range stock monthly or quarterly. Genuinely dead stock once a year, which is exactly what it deserves. The schedule then generates count tasks continuously and pushes them to whoever is free, in among the ordinary work.
Three things follow from that, and they are the whole argument.
You find the drift while it is small. A weekly count on a fast mover catches a problem within days of it starting, when the trail is still warm and somebody can remember what happened.
Effort goes where the risk is. Total counting hours usually go down, not up, because you stop spending the same effort on stock that never moves.
The warehouse never closes. No shutdown weekend, no overtime, no Monday morning spent reconciling clipboards.
Counts are movements too
The detail that makes this work is that a count is not a separate kind of event in Hangar. A counted difference posts to the same stock ledger as a receipt or a pick, with the reason code the counter selected on the scanner attached to it.
That means the variance is not just a number in a report. It is a row you can group and sort. Ask which reason codes account for most of your adjustments and the answer is a query, and it is usually specific enough to fix: one bin that is picked from two aisles, one item group whose receiving tolerance is too loose, one shift where the shorts cluster.
An annual count gives you a figure to absorb. Cycle counting gives you a list of things to go and fix. Only one of those is a control.
Common questions
- What is cycle counting?
- Cycle counting replaces the once-a-year wall-to-wall count with small counts that run continuously through the year. Each item is counted on a schedule set by how much being wrong about it would hurt: fast movers weekly, mid-range stock monthly or quarterly, dead stock once a year. Count tasks are generated automatically and worked in among ordinary jobs, so the warehouse never has to close to do them.
- How often should each item be cycle counted?
- By risk, not by a flat rule. An item that ships forty times a week can drift badly within days, so it earns a weekly count. A part that ships twice a year cannot get very wrong between checks. In Hangar the frequency is a property of the item group rather than a decision somebody makes each morning, so the schedule holds without anyone maintaining it by hand.
- Can cycle counting replace the annual physical count?
- Operationally, yes: a running cycle count program finds drift earlier and produces better accuracy than a single annual snapshot. Whether you can drop the year-end count entirely is a conversation with your accountant or auditor, since some still require one. Either way, cycle counting means the annual exercise stops being your only control and becomes, at most, confirmation of numbers you already trust.
- Why do counted differences need reason codes?
- Because a variance is only useful if you can explain it. In Hangar every counted difference posts to the stock ledger like any other movement, carrying the reason code the counter selected on the scanner. Group the adjustments by reason and the pattern is usually specific enough to fix: one bin picked from two aisles, one item group with a loose receiving tolerance, one shift where the shorts cluster.