What cycle counting is and how to do it properly

Cycle counting means counting a small portion of the warehouse every week, on rotation, until the whole inventory has been covered over the year — instead of shutting the operation down once a year to count everything. The point is not to count more. It is to find out about discrepancies while you can still trace where they came from.

That is the entire advantage, and it is worth saying plainly. An annual count tells you, in December, that 40 units are missing. It does not tell you when they disappeared, in which order, or whether it was a data-entry error or a shipping error. A cycle count tells you on Tuesday, with nine days of movements to review instead of twelve months.

Why the annual count arrives too late

The annual physical inventory has three practical problems, and none of them is fixed by counting more carefully:

1. It stops the warehouse. Counting everything requires freezing receipts and shipments. One day without shipping in peak season costs more than the discrepancy you are about to find.
2. It accumulates the error. Twelve months of movements collapse into a single number at the end. If a process is broken, it has been broken for a year.
3. It leaves no trail. By the time the discrepancy surfaces, the record that would explain it is gone or nobody remembers it.

Cycle counting inverts that: count little, count often, and never stop the operation.

How to decide what to count

Counting everything at the same frequency wastes the effort. The common practice is ABC classification: rank your SKUs (each distinct product you handle, by its code) by how much they move or how much they are worth, and give each group its own frequency.

Class	What it usually is	Typical frequency
A	Highest turnover or highest value	Monthly
B	Medium movement	Quarterly
C	Long tail, low turnover	Semiannual or annual

This is not an accounting rule, it is a way to allocate effort. The logic is that an error in a product that ships 300 times a month costs you far faster than an error in one that ships three times a year.

Two extra triggers beat the calendar: count when a location hits zero (the cheapest moment to verify — there is nothing to count) and count when someone reported a discrepancy on an order.

If you want to go deeper on ranking what moves most, we wrote separately about how to calculate inventory turnover.

What tolerance is acceptable

Here it pays to be honest: there is no industry-standard figure we can quote you with a source. A reasonable tolerance depends on unit value, on whether the product is handled by piece or by case, and on whether your product sells by lot or expiration date.

What can be stated without inventing anything is the criterion: tolerance is defined by class, in advance, and in writing — never negotiated after seeing the result. A count whose tolerance is decided once the discrepancy is known is not measuring anything.

And a tolerance above zero does not mean "losing product is fine". It means a discrepancy inside the range is adjusted and logged, and one outside the range triggers an investigation before any adjustment.

What to do with a discrepancy

The most common mistake is not miscounting. It is adjusting the system to the counted number and moving on. That cleans up the figure and erases the evidence.

The order that works is the opposite:

1. Recount before touching anything. A good share of discrepancies are counting errors, not inventory errors.
2. Look in neighboring locations. The most frequent shortage is goods put away in the wrong place, not goods lost.
3. Review recent movements for that code: receipts, shipped orders, returns that came back and were never put back into stock.
4. Adjust and log the cause, not just the quantity. An adjustment without a cause is lost data.
5. Fix the process if the cause repeats.

Step 4 is what turns a count into information. By the third month, the list of causes tells you whether the problem is in receiving, in picking or in returns — and that is actionable.

What it takes to work

• Defined locations. You cannot cycle count if goods are "somewhere around". Every position needs an identifier.
• A system that records movements. Without history, step 3 is impossible. This is where our warehouse system logs every receipt and shipment with a timestamp and an owner.
• Someone counting who did not put it away. Not out of distrust, but because whoever stored the unit remembers where they think they put it.
• No counting during the shipping peak. A count taken while orders are being picked measures a snapshot that already moved.

When your logistics operator does it

If you work with a 3PL, cycle counting stops being your job and becomes part of the service — but it should be written into the contract, not assumed. Three things worth agreeing on:

• How often each product class gets counted.
• What report you receive and how often, with discrepancies and their causes.
• Who absorbs an out-of-tolerance discrepancy, and under what procedure.

That last one is the awkward part of the conversation, and exactly the one to have before signing rather than after the first shortage. In practice it goes hand in hand with what syncs between your store and your 3PL and with day-to-day inventory control, which is where cycle counting turns into stock you can trust.

Want someone else doing the counting while you just get the right number? See our warehousing service.

Frequently asked questions

Does cycle counting replace the annual physical inventory?

That depends on your accountant and your tax obligations, not on logistics. Operationally, a well-run cycle count program covers the full inventory over the year; if your accounting close also requires a full count, that is a tax decision to take up with your accountant.

How often should I count?

By class, not on a single calendar: the faster it moves, the more often. What matters is not the number of counts but that every SKU has an assigned frequency and that it is honored.

What if I find a large discrepancy?

Do not adjust right away. Recount, check neighboring locations, and review recent movements for that code. Adjusting first erases the trail you need to keep it from happening again.

Do I need to close the warehouse to count?

No, and that is the point. Cycle counting is designed to run with the operation going, counting specific locations outside the picking peak.