Cycle counting: swapping the annual shutdown for a daily habit

A little, constantly, in a working building

Counts are issued as tasks alongside picking and replenishment, worked by the same crews, and completed while the site trades. That means the counter meets locations in whatever state the operation left them, which is the honest state, rather than the tidied version presented on a shutdown day. It also means the programme has to cope with stock moving during a count, usually by locking the position briefly or by counting between waves.

Aim the counts, do not spread them evenly

Positions differ enormously in how likely they are to be wrong: fast-moving pick faces are touched constantly, high-value lines carry more consequence, and locations that have produced differences before tend to do so again. A workable schedule counts busy and valuable positions frequently, quiet reserve positions rarely, and adds counts triggered by events, such as a picker reporting a shortage or a position reaching zero. Counting everything at the same cadence spends most of the effort confirming positions nobody had touched.

Count blind, and count twice before adjusting

Showing the expected quantity invites confirmation rather than counting, so the counter should record what they see without knowing what the system expects. Where the figures differ, a second count by a different person distinguishes a genuine discrepancy from a miscount, and only then is an adjustment posted. Skipping the recount produces a stream of corrections that are themselves errors, which is worse than not counting at all.

The count is a diagnostic instrument

The valuable output is not the corrected figure but the explanation: an entire case missing suggests a pick error or a theft pattern, a swap between two adjacent positions suggests a putaway confirmation problem, and repeated shortages of one product suggest a unit-of-measure mismatch in the system. Grouping differences by area, shift and cause turns the programme into an improvement loop. Without that step, the site pays for counting and buys only tidier numbers.

Making room for it in the shift

Counting competes with despatch for people and equipment, so it needs a protected allocation rather than whatever time is left over. Common arrangements dedicate a small standing team, or issue counts during predictable quiet periods such as the gap between waves or the early part of a shift. Whichever is chosen, the programme needs a stated target for positions counted per period, so that a busy week does not silently suspend it.

Frequently asked questions

Can cycle counting replace a full physical count entirely?

Operationally, often yes. Whether it satisfies the auditors and the reporting obligations that apply to the business is a separate question decided with finance and the external auditor, and many sites keep a reduced full count for that purpose.

Who should perform the counts?

Not the person responsible for the area being counted, wherever headcount allows. Independence is what makes a difference credible, and it also removes the temptation to correct quietly rather than to report and investigate.