What Is a Cycle Count?

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 full cycle everything gets verified without ever shutting the operation down. It is the working alternative to the wall-to-wall annual count: instead of one disruptive event a year, counting becomes a small, continuous habit that keeps records honest.

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, and inventory accuracy is the score that tells you whether it does.

What you will learn

• How cycle counting works
• ABC cycle counting and the 80/20 rule
• Cycle counting methods beyond ABC
• How often to cycle count - and the maths
• What a good count sheet looks like
• Why counts come back wrong
• Measuring whether it is working
• Cycle count vs physical inventory
• Can cycle counting replace the stocktake?
• Cycle counting equipment, not just stock
• Habits that make counts stick
• FAQ

How cycle counting works

A working cycle count follows the same loop every time:

1. Pick the slice. A location, a category, or a set of items due under the rotation schedule.
2. Set a cut-off. Agree a freeze point after which no transactions post against the items being counted, or the count is measuring a moving target.
3. Count blind. The counter records what is physically there without seeing the expected quantity first - showing the “right answer” invites confirmation rather than counting.
4. Recount the exceptions. Anything that disagrees with the system gets counted again, ideally by a second person, before anyone touches a record.
5. Compare and investigate. Variances are checked against recent receipts, issues, transfers and returns before anything is changed. A discrepancy found within days of its cause is explainable; one found at year-end is a mystery.
6. 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 in the audit trail.

The loop only works on top of a perpetual inventory: a system that updates the recorded quantity as goods are received and issued. Cycle counting does not create accurate records, it verifies and repairs them.

ABC cycle counting and the 80/20 rule

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. It is Pareto’s 80/20 rule applied to counting - a small share of your SKUs usually accounts for the large majority of stock value or movement, so that small share deserves most of the attention.

A typical split looks like this:

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. Two cautions. First, rank by the risk you actually care about: unit value is the usual axis, but a cheap component that stops a production line when it runs out belongs in A regardless of price. Second, re-run the classification periodically, because yesterday’s A item quietly becomes dead stock and a new item takes its place.

Cycle counting methods beyond ABC

ABC is the best-known method, not the only one, and for smaller operations it is often not the best one.

• ABC / Pareto. Count by value or velocity class, as above. Strong when you have thousands of items with a wide value spread.
• Control group. Pick a small fixed set of items - a few dozen - and count them repeatedly over a short period. Because the same items keep coming back, any variance almost certainly exposes a flaw in your counting technique or your transaction flow rather than a genuine loss. It is the method for debugging the programme itself before scaling it.
• Random sample. Count a randomly chosen set each day. In a constant population sample, every item stays in the pool and can be drawn again, which is simple but leaves coverage to luck. In a diminished population sample, counted items drop out of the pool until everything has been covered, which guarantees full coverage within the cycle.
• Usage-based. Count what gets touched most. Items with high transaction counts have the most opportunities to go wrong, whatever they cost.
• Opportunity-based. Count at natural trigger points instead of on a calendar: when goods are received, when a picker empties a bin, when an item hits its reorder point, or when someone reports a stockout. It costs almost nothing because someone is already standing there.
• Geographic or location-based. Walk the shelves in physical order - one aisle, one rack, one cupboard at a time - rather than chasing a SKU list around the building. Far fewer steps per item counted, and it finds stock sitting in the wrong place.
• Hybrid (cost x usage). Rank by value multiplied by transaction frequency, so an item that is both expensive and constantly moving rises to the top.

Which one to pick? If you have hundreds of items rather than thousands - a store cupboard, a tool crib, a van stock - geographic or opportunity-based counting almost always beats ABC. The classification overhead of ABC only pays off once the catalogue is large enough that counting everything frequently is genuinely impossible. Start with a control group to prove the method works, then switch to a geographic rotation.

How often to cycle count - and the maths

The frequency calculation is one line:

Items to count per day = (number of items x counts per year) ÷ working days per year

A worked example: 1,000 items, each counted four times a year, over 250 working days. That is 4,000 counts a year, or 16 items a day. Run the sum separately per ABC class and add the results, so a handful of A items counted monthly does not drag the whole catalogue onto the same frequency.

A starter schedule for a 200-item store cupboard, stationery store or small consumables shelf:

• A items (roughly 20 items): monthly - 12 counts a year each.
• B items (roughly 60 items): quarterly - 4 counts a year each.
• C items (the remaining 120): annually.
• Floor rule: everything gets counted at least once in twelve months, no exceptions.

That works out at 240 + 240 + 120 = 600 counts a year, which over 250 working days is between two and three items a day, or roughly one shelf a week. That is the point of the maths: it turns “we should count more often” into a number small enough that somebody actually does it.

Two timing rules make each count cheaper. Count near the reorder point, when quantities are at their lowest - counting an item the day after a delivery takes an hour, counting it before the delivery takes minutes. And count when nothing is moving: not mid pick-wave, not during active receiving, and not with open transfers still unposted. Early morning before the day starts is the classic window.

What a good count sheet looks like

The sheet is where the discipline lives. Header fields:

• Date and cut-off time - the moment after which no transactions post against these items
• Location, aisle or bin range
• Counter’s name, and the recounter’s name
• Class or slice being counted

Line fields, one row per item:

• Item code / SKU and description
• Location or bin
• System quantity - hidden from the counter
• Physical quantity
• Variance
• Recount flag and recount quantity
• Final quantity, reason code, and the named owner of the follow-up

Two disciplines decide whether the resulting number means anything.

Blind counting. The counter never sees the expected figure. Show it and you get agreement, not evidence - the human eye is extremely good at finding the number it was told to find. A blind count is the only kind that can actually disprove your records.

Recount before adjustment. No record changes on the strength of one person’s count. A second counter verifies every variance first, which filters out simple miscounts before they become permanent adjustments.

Add one more: segregation of duties. The person who owns the stock should not be the only person who ever counts it, and ideally should not be the person who posts the adjustment either. This is a small piece of internal controls that costs almost nothing in a team of five and matters enormously to an auditor. See segregation of duties for the general principle.

Why counts come back wrong

A repeat variance is a process failure, not a counting failure. Adjusting the number without finding the cause guarantees you will adjust it again next cycle. The usual root causes, worth turning into a short fixed list of reason codes so patterns become countable:

• Receiving lag. Goods put away today, booked in tomorrow - or never.
• Pick and putaway errors. The right quantity of the wrong item, or the right item to the wrong bin.
• Unrecorded internal transfers. Stock moved between rooms, vans, sites or departments with no record following it.
• Unit-of-measure mismatch. Bought by the case, issued by the each; stored by the pallet, picked by the carton. One of the most common and most invisible causes.
• Damage and write-offs never posted. The item is gone from the shelf and still on the record.
• Returns. Customer or internal returns that come back physically but not systemically.
• Cut-off and timing gaps. A transaction that lands seconds after the count - a false variance that wastes an afternoon.
• Misplaced rather than missing stock. A false shortage in one bin and a matching false surplus in another. Always separate “missing” from “in the wrong place” before adjusting anything.
• Weak item master data. Duplicate records, ambiguous descriptions, no standard location convention - so movements split between two records that should be one.
• Genuine shrinkage. Loss and theft are real, but they are the residual after the boring causes above have been eliminated, not the first explanation to reach for.

If the same item is wrong every cycle, look for an unrecorded usage path - a bill of materials consuming components the system does not know about is a classic.

Measuring whether it is working

A counting programme with no metric is a ritual. Three numbers tell you whether yours is working.

Inventory record accuracy (IRA). The headline measure:

IRA = (1 - [sum of absolute variances ÷ total system quantity]) x 100

The word absolute is doing the heavy lifting. If one bin is 10 units short and another is 10 units over, the net variance is zero and your records look perfect - while two separate processes are broken. Take the absolute value of every variance before summing.

Line accuracy is stricter and often more useful: the percentage of counted lines with zero discrepancy. A single line can be wrong by one unit and still fail, which is exactly the sensitivity you want when judging whether a process is under control. Value accuracy weights by money and is what finance cares about, but it hides many small errors behind one large item - track it alongside line accuracy, never instead of it.

Process metrics. Two honest ones: adjustment rate (how much quantity or value you are correcting per cycle, which should trend down) and count completion rate (counts done versus counts scheduled, which is the first thing to slip when the operation gets busy).

Set tolerance bands as a deliberate policy, not an accident:

• Zero tolerance on high-value or serialised items - a laptop is either there or it is not.
• Plus or minus one unit on mid-value items where a genuine miscount is plausible.
• A small percentage on bulk consumables measured by weight or eye - screws, cable ties, cleaning supplies.

Write the bands down and apply them consistently, or your trend line means nothing. Well-run operations sit in the high nineties on line accuracy for their A items; the more important number is whether your own figure is improving.

Cycle count vs physical inventory

The wall-to-wall stocktake 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 enough to their cause that they can still be explained. A full physical inventory count answers “what do we have right now?”; cycle counting answers “can we trust the system on any given Tuesday?”.

Can cycle counting replace the stocktake?

Sometimes, under conditions - and the conditions are the point. A cycle counting programme is generally only accepted in place of a full count when it is:

• Documented - a written procedure covering scope, frequency, blind counting, recount, tolerance and adjustment authority.
• Complete - every item in scope is demonstrably counted at least once within the period, with coverage you can evidence rather than assert.
• Sustained - record accuracy is measured, reported, and consistently high, not high once.
• Investigated - variances have a documented cause and an adjustment trail, rather than silent corrections.

In practice most organisations do not choose one or the other. They run cycle counts through the year to keep the records honest, and still perform a full count at the financial year-end. Whether a programme substitutes for that year-end count is a conversation to have with your auditor before you rely on it, not a decision to make unilaterally - and the strength of your audit trail is usually what settles it.

Cycle counting equipment, not just stock

The same rotation logic works for equipment, but the question changes. For consumables you are verifying a quantity. For equipment you are verifying existence, location and custodian: does the laptop on the register still exist, is it where the record says, and is the named holder still the person who has it?

Run it as rolling asset verification - one department, one room or one category a month - rather than one dreaded annual sweep. Done that way, a rotation flushes out the two chronic problems in any asset register: ghost assets that are on the books but gone from the floor, and zombie assets that are still in daily use after being written off. Both distort depreciation, insurance and replacement planning.

The usual sources of drift are disposals that were never posted and leavers whose kit was never transferred, which is why the rotation should be paired with offboarding rather than run in isolation. Done consistently, it turns the fixed asset audit into a formality and makes asset reconciliation a monthly tidy-up rather than an annual excavation. A caterer might verify one shelf of catering equipment each week rather than auditing the whole store before every season; an office might walk one floor of office supplies and shared kit a month. See asset verification for the full procedure.

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.
• Adjust same-day. A variance left unposted is a second error waiting to compound the first.
• Never let people count only their own area. Rotating counters between zones finds the assumptions each person has stopped seeing.
• Keep the slice small enough to finish. An unfinished count teaches the team that counts do not have to be finished.

Programmes fail in predictable ways: counting when convenient rather than on schedule, adjusting without investigating, letting the stock owner count unsupervised, skipping the recount, and setting a rotation so ambitious that it collapses in week three. Every one of those is a decision, not bad luck.

FAQ

How often should you cycle count? Often enough that every item gets counted at least once a year, with high-value and fast-moving items counted far more frequently. A common ABC pattern counts A items monthly or quarterly, B items a few times a year, and C items annually. The honest answer for small operations is simpler: pick a small, fixed slice - one shelf, one category - and count it on the same day every week, because a modest schedule that happens beats an ambitious one that does not.

What is the difference between a cycle count and a physical inventory? A physical inventory (or annual stocktake) counts everything at once, usually with operations paused and extra hands drafted in. A cycle count checks a small subset on a rotating schedule while normal work continues. The stocktake gives one accurate snapshot a year; cycle counting keeps records continuously close to reality and surfaces the cause of errors while the trail is still warm.

What is ABC cycle counting? ABC cycle counting ranks items by value or velocity and counts them at different frequencies. A items - the small group representing most of the stock value or movement - are counted most often. B items get a moderate schedule, and C items, the long tail of cheap or slow stock, are counted least. The idea is to spend counting effort where errors cost the most, instead of treating a box of cable ties like a pallet of laptops.

What is an example of a cycle count? A practical example: on Tuesday morning, before picking starts, one person is given a sheet listing the twenty items on aisle B shelf 3. The sheet shows the item code, description and bin, but not the expected quantity. They count each bin, write the figure down, and hand the sheet back. Eighteen items match the system, one is two units short and one is three units over. A second person recounts those two, confirms the figures, and the shortage is traced to a delivery booked in the day after it was put away. Both records are corrected the same day with a reason code attached, and the shelf goes back into the rotation for next quarter.

How do you calculate how many items to cycle count each day? Multiply the number of items by how many times a year each should be counted, then divide by the number of working days in the year. For example, 1,000 items counted four times a year is 4,000 counts, divided by 250 working days, which is 16 items a day. With ABC classes, run the sum per class and add the results, so a small group of A items counted monthly does not force the whole catalogue onto the same frequency.

How is cycle count accuracy measured? The common measure is inventory record accuracy: 1 minus the sum of the absolute variances divided by the total system quantity, expressed as a percentage. Using absolute variances matters, because otherwise a shortage in one bin cancels an overage in another and the result flatters you. Many operations also track line accuracy - the percentage of counted lines with zero discrepancy - which is a harsher and more useful number for judging whether a process is under control.

The takeaway

A cycle count trades one painful annual event for a small, repeatable habit. Pick a method that fits your size - geographic or opportunity-based for hundreds of items, ABC for thousands - do the frequency maths so the daily number is small enough to survive a busy week, count blind, recount before you adjust, and record a reason code every time. Then measure it: inventory record accuracy on absolute variances, line accuracy, and count completion. The same rotation applied to equipment answers a different question - existence, location, custodian - and quietly removes the ghost and zombie assets that distort the register. Counting is not the goal; a system you can trust on an ordinary Tuesday is.

Tools that make this easier

The count needs an expected picture to count against. In AMPthilly, consumables live in the same register as equipment with a SKU, unit price, target stock and reorder point per item, so the day’s count sheet is a CSV export away and the corrected figures come back in the same way. Every adjustment lands in the asset’s audit history with who changed what and when, which is the trail an auditor asks for. For equipment rotations, the printable QR label on each item opens its profile in a normal phone browser - no app to install - so the verifier confirms owner, location and status at the shelf, and can raise a service desk ticket on the spot if something is damaged. When a count shows an item below its reorder point, the purchasing and restock module turns it into a supplier order rather than a note on a whiteboard. Start free - 3 users and 25 assets, no credit card required - or talk to us about a larger rollout.

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