Cycle counting: how to improve stock accuracy without a full shutdown

Photo: Tiger Lily / Pexels - Pexels License.

The system says eight. The shelf holds five. Changing eight to five will get today’s order book closer to reality, but it will not explain where the other three went, or stop the gap returning next week. That is why cycle counting is worth more than a routine adjustment. By checking manageable portions of stock regularly, a warehouse can catch errors while the transactions behind them are still possible to untangle.

Prioritise items where inaccurate stock creates the greatest operational problem. Fast-moving products, valuable goods, frequently disputed SKUs and items with confusing pack quantities may deserve more attention. A slower-moving product can still be important if one missed unit would disrupt a committed customer order.

Create a schedule your team can actually maintain. Begin with a manageable group of locations or products rather than a plan that requires unrealistic daily effort. Record the selection method so coverage does not depend only on what is easiest to reach. Over time, ensure less visible areas and slow stock are also checked.

Count against a clear moment in time

Control movement in the location you are counting. If a picker takes three items after the physical count but before the system comparison, you have created a discrepancy without losing any stock. Pause activity there briefly or use a documented cut-off and reconciliation process. The rest of the warehouse can continue working; the selected count just needs a clear relationship to the transactions around it.

Identify the location, SKU, condition and counting unit. Include goods awaiting inspection, damaged items and returns in the appropriate separate status. Counting every box as available stock will not help sales if some of those goods cannot be sold. Make sure the counter can distinguish individual items from outer cartons.

A blind count, where the counter does not see the expected system quantity, can reduce the temptation to stop when the numbers look close. Agree how discrepancies trigger a recount and who performs it. The recount should verify the unit and location, not simply repeat the first number.

Check nearby locations and recent transactions before concluding that goods are missing. Products may have been put away under a similar code or moved without a completed system entry. Review open picks, recent receipts and returns. Treat the physical count as evidence within a process, rather than the only piece of information.

Before approving an adjustment, ask what explains it. Keep the expected quantity, first count, recount and reason together. Otherwise the adjustment makes the warning disappear while the underlying error carries on. Check the unit too: a carton treated as one item on receipt and twelve items on dispatch can produce a very convincing mystery.

Group causes in a practical way: receiving error, wrong pick, unrecorded transfer, pack conversion, damage or unexplained discrepancy. Avoid a long list that staff cannot use consistently. Look for repeated patterns by product, location and process. Several small discrepancies around one carton size may indicate a data problem rather than individual carelessness.

Track count completion, discrepancy frequency and repeated causes using consistent definitions. Also monitor customer-facing consequences such as orders delayed by missing stock. A higher number of discovered errors at the start can mean the new programme is revealing existing problems rather than making accuracy worse.

Start with a schedule people can sustain, then use the findings to change how goods are received, labelled, moved and picked. If the same SKU is wrong every week, counting it more often may expose the problem faster, but fixing the cause is still the job. The measure of success is dependable stock information, and fewer customers being told an item is available when nobody can find it.