Mon – Sat: 9:00 AM – 7:00 PM IST
Warehouse

What is cycle counting?

Counting a little, often, instead of everything once a year — and why it finds causes rather than just differences.

In short

Cycle counting is the practice of counting a small subset of stock continuously, so that every item is counted several times a year without stopping the warehouse. High-value or fast-moving items are counted more often than slow ones. The point is not the count itself: it is that a discrepancy found within days can still be traced to its cause, while one found at year-end cannot.

Why It Matters

Why this matters in practice

The annual count tells you that you are wrong, not why. By the time a difference surfaces in December, the transaction that caused it happened in March and nobody can reconstruct it. Cycle counting narrows the window to days, which turns stock accuracy from an accounting exercise into an operational one that can actually be improved.

Finds discrepancies while the causing transaction is still traceable
Avoids shutting the warehouse for a full count
Concentrates effort on the items where error costs most
Produces a running accuracy measure rather than one annual verdict
How It Works

How it works in practice

Classify the stock

Usually by ABC analysis — value, movement, or both. The classification determines count frequency.

Set frequencies

A items perhaps monthly, B quarterly, C once or twice a year. The target is that every item is counted at least annually and the valuable ones far more.

Generate count tasks

The system issues a short daily list, by location or by item. Short lists get done; long ones get deferred.

Count blind

The counter should not see the expected quantity. A displayed figure is a strong hint and compromises the count.

Investigate, then adjust

The adjustment is the easy part. The value comes from asking why, and fixing the process that caused it.

Worked example

A worked example: an ABC schedule sized honestly

A warehouse holds 4,200 SKUs. Classified by annual movement value, about 340 are A items, 980 are B and the remaining 2,880 are C. The team has one person who can give roughly ninety minutes a day to counting.

Counting A monthly, B quarterly and C annually produces 340 × 12 plus 980 × 4 plus 2,880 × 1, which is 10,880 counts a year, or about 44 per working day. At ninety minutes that is roughly two minutes per count — tight but achievable for bin-level counts of discrete items, and clearly not achievable if each count means weighing or opening cases.

The useful part of this arithmetic is that it is done before the schedule is published. A cycle counting programme that is quietly impossible gets abandoned in the third month and taken as proof that cycle counting does not work. If the number comes out impossible, the honest responses are to widen the C interval, narrow what counts as an A item, or ask for more time — not to publish the schedule and hope.

Key terms

The vocabulary, briefly

Term What it means
ABC classification Ranking items by value or movement so counting effort follows importance rather than being spread evenly.
Count frequency How often a class is counted — A items perhaps monthly, C items once or twice a year.
Tolerance The variance threshold below which a count is accepted without investigation. Setting it too tight buries the team in noise.
Reason code The recorded cause of a variance. Without it you know the size of your problem and nothing about its source.
Blind count Counting without seeing the expected quantity, so the counter cannot unconsciously confirm it.
What Goes Wrong

Common mistakes worth avoiding

Adjusting without investigating

If every discrepancy is simply posted away, accuracy never improves and the count becomes a monthly write-off ritual.

Counting only what is easy

Counting accessible locations and skipping the awkward ones produces a reassuring and meaningless accuracy figure.

Showing the expected quantity

Blind counting is the whole discipline. Once the number is visible, the count tends to confirm it.

No management attention

Cycle counting decays quickly without someone reviewing accuracy trends and acting on causes.

What to measure

Numbers worth tracking

Metric What it tells you What distorts it
Count accuracy by class The share of counts within tolerance, split A/B/C. One number across all classes hides where the problem is. Including zero-stock locations, which count as accurate and inflate the figure.
Variance by reason code Which process is causing error — receiving, picking, a shared pick face, unrecorded moves. A large 'unknown' bucket, which means the codes are not being used honestly.
Counts completed vs scheduled Whether the programme is actually running or quietly slipping. Rescheduling missed counts forward, which makes completion look perfect.
Net vs absolute variance Absolute variance is the real error; net variance can be near zero while two large errors cancel. Reporting net only, which is the single most common way accuracy gets overstated.
FAQ

Questions we are asked about this

Generally yes, where it is documented, performed consistently and shows acceptable accuracy. Many auditors prefer it to an annual count because the control is continuous. Confirm with yours before dropping the annual count.
Most well-run operations target 97–99% location-level accuracy on A items. The trend matters more than the absolute figure — improving from 88% to 95% is the useful work.
In many cases yes, and that is usually the business case. Auditors will generally accept a well-run cycle counting programme in place of a full physical count where you can show adequate coverage, documented procedures, variance investigation and management review. Talk to your auditor before you assume it, because the evidence they want should shape how you record counts from the start rather than being reconstructed afterwards.
Tight enough that real errors get investigated, loose enough that the team is not chasing rounding. A common shape is a small percentage for high-value items with a minimum absolute quantity, so a two-unit discrepancy on a box of ten thousand washers does not trigger the same response as two units of a motor. Set it per class, review it after three months, and expect the first version to be wrong.
Someone other than the person responsible for that stock, where you can manage it, and ideally blind. This is not about suspicion — it is that a person who knows the expected number tends to find it. Rotating counters across zones also spreads knowledge of the building, which has value of its own when somebody is away.
Investigate before adjusting, which is the opposite of what time pressure suggests. Recount first, since miscounts are more common than losses. Then check for the ordinary explanations: stock in a staging lane, a putaway not confirmed, a transfer received but not scanned, an unprocessed return. Adjusting first destroys the evidence, and the reason code you then record is a guess rather than a finding.
Related

Where to read next

ABC analysis for inventory

Read more

What is a WMS?

Read more

ERP with warehouse management

Read more

Need this applied to your own systems?

We build and support the systems this page describes. Start with a free working proof of concept — no cost, no commitment.