A cycle count is a partial inventory count done on a rotating schedule, checking a subset of items so stock stays accurate without a full shutdown.
A cycle count is a partial inventory count carried out on a rotating schedule - a small subset of items checked today, a different subset next week - so that over a cycle everything gets verified without ever shutting the operation down. Fast-moving items, the ones driving inventory turnover, get counted often; slow movers less so. The goal is not the count itself but trustworthy records: a stock system is only useful while the quantity on screen matches the quantity on the shelf.
How cycle counting works
A working cycle count follows the same loop every time:
- Pick the slice. A location, a category, or a set of items due under the rotation schedule.
- Count blind. The counter records what is physically there without seeing the expected quantity first - showing the “right answer” invites confirmation rather than counting.
- Compare and investigate. Variances are checked against recent receipts, issues, and returns before anything is changed. A discrepancy found within days of its cause is explainable; one found at year-end is a mystery.
- Adjust and log. The record is corrected the same day, and the reason - mis-pick, unrecorded usage, damage, theft - is noted so patterns become visible.
ABC cycle counting
Most schedules use ABC analysis: rank items by value or movement, then count A items (the few that carry most of the value) frequently, B items moderately, and C items (the long tail) once or twice a year. The logic is simple - an error on a pallet of laptops costs more than an error on a box of cable ties, so it deserves more counting effort. The same rotating logic works for equipment as well as stock: a caterer might verify one shelf of catering equipment each week rather than auditing the whole store before every season.
Cycle count vs annual stocktake
The wall-to-wall stocktake pauses operations, drafts in extra people, and produces one accurate snapshot a year - after which accuracy decays for twelve months until the next one. Cycle counting spreads the same effort across the year, keeps disruption near zero, and catches errors close to their cause. Many auditors accept a well-documented cycle counting programme in place of a full annual count, though that is a conversation to have with the auditor, not an assumption to make.
Habits that make counts stick
- Schedule it like a meeting. Counting “when things are quiet” means never. A fixed slot and a named owner survive busy weeks.
- Count when stock is low. Counting an item near its reorder point takes minutes; counting it the day after a delivery takes an hour.
- Fix causes, not just numbers. If the same item is wrong every cycle, the adjustment is treating the symptom - look for an unrecorded usage path or a BOM consuming parts the system does not know about.
- Adjust same-day. A variance left unposted is a second error waiting to compound the first.
In practice, the count needs an expected picture to count against. Where consumables live in a register such as AMPthilly - SKU, target stock, and reorder point per item - the day’s count sheet is a CSV export away, and every correction is logged in the audit history with who changed what, when.
Related terms
- Inventory Turnover - the velocity measure that decides which items deserve frequent counts
- Dead Stock - the stale inventory cycle counts tend to flush out
- Lead Time - why accurate counts matter before every reorder decision
- Just-in-Time Inventory - a strategy that only works on top of accurate records
- Bill of Materials (BOM) - the parts list that explains where component stock quietly goes