Cycle Counting: What It Is and How to Set It Up

What Is Cycle Counting?

Cycle counting is an inventory method that counts a portion of your catalog every day or every week, instead of shutting down the whole operation once a year to count everything at once. The core idea is simple: instead of one massive count, you split your inventory into groups and schedule recurring counts until you've covered the full catalog within a set cycle, usually a month or a quarter.

This approach exists because the annual physical count has a practical problem: it stops sales, forces a warehouse or store to close, and squeezes into two or three days an effort that exhausts the team and still leaves errors on the table. Cycle counting spreads that effort across the year without stopping the operation.

Cycle Counting vs. Physical Inventory: Key Differences

Comparing cycle counting to a physical inventory helps clarify when to use each, because they aren't mutually exclusive — most well-run businesses use both, for different purposes.

Scope. A physical count covers 100% of the catalog in a single event. Cycle counting covers small subsets, continuously.
Frequency. A physical count usually happens once or twice a year. Cycle counting happens daily or several times a week, depending on the item.
Operational impact. A physical count almost always requires pausing sales or receiving. Cycle counting runs while the warehouse keeps operating normally.
Error detection. A physical count surfaces discrepancies that built up over months, by which point it's hard to trace the cause. Cycle counting catches a discrepancy days after it happened, while it's still possible to investigate.
Cost per event. A physical count concentrates labor, overtime, and sometimes outside staff into a few days. Cycle counting spreads that cost across short, routine counts.

Neither fully replaces the other: many companies keep an annual physical count as an accounting backup, but hand daily inventory accuracy control over to cycle counting.

ABC Classification: The Foundation of a Good Cycle Count

Counting the entire catalog at the same frequency wastes time on items that barely move and neglects the ones that actually matter. That's why cycle counting almost always relies on ABC classification:

Class A: the smallest group of SKUs, usually the one that concentrates most of the inventory value or sales volume. These are the items you can least afford to count wrong.
Class B: a middle group, with moderate value and turnover.
Class C: the largest group by SKU count, but with lower individual value or low turnover.

ABC classification doesn't have to be based on unit price alone — it can also be built around total value moved, turnover rate, or how critical an item is to fulfilling an order. Once the catalog is classified, you decide how many times a year each class gets counted, and that's where frequency comes in.

How to Set the Frequency of Cycle Counts

Cycle count frequency is decided by class, not by individual item, and it varies with catalog size and business type:

Class A: frequent counts, for example every month or every week, because an error here directly affects reported inventory value and the availability of your best sellers.
Class B: a mid-level frequency, for example every quarter.
Class C: infrequent counts, for example once or twice a year, unless recurring discrepancies show up.

That frequency tells you how many SKUs you need to count each day to cover the full cycle for each class on time. A catalog dominated by Class A items needs small daily counts; a catalog dominated by Class C can concentrate effort into a few sessions per quarter.

How to Do a Cycle Count Step by Step

To set up a cycle counting program from scratch, the typical process looks like this:

Classify the catalog with ABC. Group items by value, turnover, or how critical they are to the operation.
Set the frequency per class. Decide how often A, B, and C get counted, based on the risk each group carries.
Build the count calendar. Distribute each class's SKUs across daily or weekly counts so the full cycle wraps up within the period you defined.
Count without blocking movement. The team counts the day's subset while the rest of the warehouse keeps receiving and shipping normally.
Compare against the system. The counted quantity is checked against the on-hand quantity recorded in the inventory system at the moment of the count.
Investigate discrepancies the same day. If there's a mismatch, it gets reviewed right away: an unrecorded movement, a data-entry error, shrinkage, or a misplaced item.
Adjust and document. The record gets corrected along with the reason for the discrepancy, not just the number, so you can spot patterns later.
Track accuracy over time. Keep a metric for what percentage of counts match with no discrepancy, broken down by class and by warehouse.

The step teams skip most often — and the one with the most value — is documenting the cause of each discrepancy. Without that cause, the same error repeats cycle after cycle.

A Cycle Counting Example for an Operation with Several Hundred SKUs

A cycle counting example helps make the theory concrete. Picture a distributor with 600 active SKUs, classified as follows: 90 in Class A, 180 in Class B, and 330 in Class C.

With Class A counted monthly, Class B quarterly, and Class C twice a year, the calendar might look like this: every business day, 4 to 5 Class A SKUs get counted (to cover all 90 within the month), a small group of Class B items is spread across the quarter, and Class C gets a handful of sessions spaced through the half-year.

The practical result is that, instead of a three-day year-end shutdown with the whole team counting under pressure, each warehouse worker spends fifteen to thirty minutes at the start of their shift counting the day's subset, without receiving or shipping ever stopping. Discrepancies in Class A — the items that carry the most weight in inventory value — get caught and corrected within days, not months.

Common Mistakes When Implementing Cycle Counting

These are the most frequent stumbles when a company launches its cycle counting program:

Counting without classifying first. Without ABC, the team ends up counting near-irrelevant items and critical ones at the same frequency, and the cycle becomes inefficient.
Not investigating the cause of a discrepancy. Adjusting the system number without understanding why the discrepancy happened guarantees it will happen again.
An unrealistic calendar. Scheduling more counts than the team can sustain within a normal shift leads to the program getting abandoned within a few weeks.
Relying on scattered spreadsheets. Without a centralized record, it's hard to know what was counted, when, and with what result, and accuracy tracking falls apart.
Never reclassifying the catalog. Item turnover changes over time; a Class C SKU can become Class A during peak season, and the program needs to adjust with it.

How Software Makes Cycle Counting Easier

Running a cycle counting program with spreadsheets works fine for a small catalog, but it gets hard to sustain as SKUs, warehouses, or branches grow. Inventory software built for this handles several parts of the process that, done by hand, eat up more time than they should:

Generates the count calendar automatically from the ABC classification and the frequency set for each class.
Assigns the day's subset of SKUs to the person or warehouse responsible for counting it.
Compares the counted quantity against the system's on-hand quantity in real time, and flags the discrepancy before the team's shift ends.
Logs the history of every count, with date, owner, and cause of discrepancy, to track accuracy by class and by warehouse.
Integrates with the rest of the operation — purchasing, sales, point of sale — so the inventory adjustment is reflected everywhere that on-hand quantity is used.

This kind of build rests on the same principles we cover in our guide to reorder points: having accurate on-hand quantities in the system is what lets you calculate when to restock without running short or overstocking. It also connects directly to the logistics KPIs a warehouse operation should be tracking continuously, and to practices we've already covered in our guide to what just in time is.

Frequently Asked Questions

How often should cycle counting be done?

It depends on the item's ABC classification: Class A SKUs are usually counted every month or every week, Class B every quarter, and Class C once or twice a year. There's no single frequency for the whole catalog.

Does cycle counting replace the annual physical inventory?

Not necessarily. Many companies keep an annual physical count as an accounting backup, but hand daily inventory accuracy control over to cycle counting, which catches and corrects discrepancies much sooner.

What do I need before starting a cycle counting program?

You need a catalog classified with ABC, a system that tracks the expected on-hand quantity for each SKU, and a realistic count calendar that fits your team's capacity. Without that foundation, the program is hard to sustain.

What happens if a cycle count finds a discrepancy?

It gets investigated the same day: the team checks for an unrecorded movement, a data-entry error, shrinkage, or a misplaced item. The system adjustment should always include the reason for the discrepancy, not just the corrected number.

Can you do cycle counting without specialized software?

Yes, with spreadsheets, but it gets harder to sustain as the catalog or the number of warehouses grows. A system that automates the calendar, the comparison against on-hand quantities, and the discrepancy log makes it much easier to keep the program running long-term.

If your operation loses time and accuracy to physical counts that shut down the warehouse, at AISDC we build custom software for inventory management, with ABC-based cycle counting, automatic calendars, and real-time comparison against your recorded stock.