Cycle counting cadence playbook — ABC stratification done right.
A printable playbook for cycle counting on a real schedule: ABC tiering, count frequency by tier, variance thresholds, and how to keep ops on the rhythm without freezing the floor.
The short answer
Counting cadence should follow the cost of being wrong, not the size of the catalog. Stratify SKUs into ABC tiers by annual usage value, then count A items monthly, B quarterly, and C annually. The aim is to count each SKU often enough that an error surfaces before it costs a sale.
Worked example
With 900 SKUs on an A monthly, B quarterly, C annually cadence, the A tier is roughly 180 SKUs needing 180 counts a month, B adds about 135 across a quarter, and C about 585 across the year. That totals near 200 counts a month, or about 9 a working day — a task for part of one person's morning, not a shutdown.
Cadence is a budget decision
Every count costs labour, so the schedule has to fit the people you actually have. Set the cadence first, work out the daily count volume it implies, and check that against the time available. A schedule that needs 40 counts a day from a team that can do 10 will be abandoned in a fortnight.
If the numbers do not fit, tighten the A tier definition rather than stretching the cadence. Counting your top 100 SKUs monthly and reliably beats a plan to count 400 monthly that never happens.
Set variance thresholds per tier, and act on them
A threshold is what turns a count into a decision. Below it, post the adjustment and move on. Above it, recount before adjusting anything, because a large variance is more often a counting or location error than genuine missing stock.
Thresholds should be tighter on A items. The same percentage variance represents materially more money on a high-value SKU, so a tolerance appropriate for C items would let real losses through unnoticed at the top of the catalog.
Frequently asked questions
How often should you cycle count?
Match frequency to value. A common cadence is A items monthly, B quarterly, and C annually, where the tiers come from ranking SKUs by annual usage value. Tighten the A cadence if those items move quickly or carry high margin.
Is cycle counting better than an annual physical count?
For most operations, yes. An annual count gives one accurate day and costs a day of trading, while cycle counting delivers continuous accuracy concentrated where errors are most expensive, and turns repeated variance on a SKU into a signal you can act on.
Do I have to stop picking during a cycle count?
No, and needing to is a sign the tier is too large. Counting a small number of SKUs per day means you can work locations that are quiet, which is the practical advantage over a full physical count.