Cycle counting instead of an annual stocktake

Closing the warehouse once a year and counting everything: a familiar ritual that delivers little. Cycle counting spreads the work across the year, continuously measures how reliable your stock is and corrects errors before they cause damage. This article covers how to set it up, which counting frequencies make sense and how to handle count discrepancies. How counting fits into spare parts management as a whole is in the overview guide.

Why the annual stocktake falls short

The annual count has three problems. It is a major disruption: the warehouse stops, people are pulled away from their own work, and counting quality drops as the day wears on.

The second problem is timing. An error that arises in February is discovered in December. For all those months your system showed a wrong number and decisions were made on it — orders not placed, work orders scheduled on parts that weren't there.

The third problem is that an annual count corrects but teaches nothing. You set the numbers right and start again, without investigating why they drifted.

What cycle counting is

With cycle counting you count a small part of the assortment every day or week, chosen so each item reaches its intended frequency across the year. Important items come round often, unimportant ones rarely.

The warehouse stays open, the work is manageable, and errors surface within weeks instead of after a year. On top of that, counting becomes a routine rather than an event.

Setting counting frequency

You tie frequency to the classification from your ABC analysis:

• A items — four to twelve times a year
• B items — twice a year
• C items — once a year

Work through what that means. With 2,000 items split into 400 A, 600 B and 1,000 C, and frequencies of four, two and one, you count 1,600 + 1,200 + 1,000 = 3,800 lines a year. Spread across 250 working days that is about fifteen lines a day: half an hour of work.

That is the real argument. Not that cycle counting is more accurate, but that it fits into an ordinary working day.

Alongside the fixed cycle there are triggers to count in between: an item showing zero while something is still on the shelf, a discrepancy on a related item, or a location that has just moved. Such event-driven counts catch exactly the errors a fixed cycle misses.

Measuring stock accuracy

Cycle counting produces a KPI an annual stocktake never gives you: stock accuracy, the percentage of counted lines where the found quantity equals the system quantity.

Measure it per class. Accuracy of 98 percent on A items is a realistic target; on C items it may be lower. The average across everything is a misleading figure, because the large volume of C items dominates the picture.

Important: count on lines correct, not on value. A warehouse can be financially fine while half the items have the wrong quantity — and it is that wrong quantity the shop floor suffers from.

Handling count discrepancies

A discrepancy is a signal, not an administrative act. Correct only the number and you will count the same difference again next year.

So look for the cause behind structural differences. The usual suspects:

• Issuing without registration. Someone takes a part and doesn't book it out. By far the most common cause.
• Wrong unit. The item is held in pieces but issued per box of ten.
• Parts in the wrong location. The quantity is right, but it sits somewhere else.
• Returns without a booking. A part that wasn't used and goes back on the shelf unregistered.

Record who may make a correction and from what value a second pair of eyes is required. A discrepancy that can be written off without a trace undermines trust in the numbers.

Practical implementation

Start with the A items. That is a limited group where the gain is largest, and it gives you a first measurement of your accuracy.

Count by location rather than by item number: you walk one rack once instead of criss-crossing the warehouse. Have the counter enter the found quantity without seeing the system quantity, otherwise they will unconsciously confirm what is on screen.

Scanning saves errors and time. If items and locations carry a barcode or QR code, counting becomes a matter of scanning and entering a number — see setting up your warehouse for how to build that coding.

Systems that support counts schedule the cycle themselves and keep the history. How that works in practice is on the page about warehouse and spare parts.