What is cycle counting?
Cycle counting is an inventory auditing method where you count a portion of your stock, a specific set of SKUs, locations, or categories, on a rotating schedule, so that over the course of a year (or another defined period) every item gets counted at least once, without ever halting normal operations to count everything simultaneously.
It stands in contrast to a physical inventory count, which counts the entire inventory at once, typically annually, and usually requires freezing receiving and shipping for the duration. Cycle counting instead works in small batches, woven into daily operations, so records stay current continuously rather than only right after a big annual reset.
Why cycle counting matters
Inventory records drift from physical reality constantly: a miscount at receiving, a scan that never happened, damage that never got logged, all quietly accumulate between counts. A single annual count catches this drift only once a year, by which point the error has had months to compound and its root cause is often long forgotten.
Cycle counting catches discrepancies, shrinkage, data-entry errors, and fulfillment mistakes closer to when they happen, while the cause is still traceable. It also avoids the operational cost of a full shutdown: counts happen in small batches during normal business, not as a disruptive event that stops receiving and shipping for a day or more.
Cycle counting methods
There are several established ways to decide what gets counted next. Most businesses pick one primary method, though larger operations sometimes blend methods across different parts of the catalog.
- ABC analysis: rank SKUs by value or velocity into A, B, and C tiers, and count A-items (highest value or fastest-moving) most often, monthly is common, B-items quarterly, and C-items once or twice a year. This is the most widely used method because it puts counting effort where an error would cost the most.
- Control group method: repeatedly count a small, fixed set of items to calibrate and validate counting accuracy and process before rolling the method out to the full catalog.
- Random sample method: select items at random to count, useful for catalogs with many similar-value items where an ABC split does not add much differentiation.
- Usage-based (opportunity) counting: count items whenever they naturally hit a trigger point, such as a bin going to zero or a receipt being processed, catching errors at the moment stock changes rather than on a fixed calendar.
- Hybrid method: combine two or more of the above, for example ABC tiers for scheduling frequency plus opportunity counts whenever a bin empties out between scheduled counts.
Calculating a daily cycle count sample size
To turn a target counting frequency into a daily workload, use: Daily sample size = (Total SKUs × Target counts per SKU per year) ÷ Working days per year. A catalog of 600 SKUs, counted 4 times a year on average, across 250 working days, works out to (600 × 4) ÷ 250 = 9.6, roughly 10 SKUs counted per day to hit that target.
Run this calculation separately per ABC tier rather than once for the whole catalog, since A-items typically need a much higher count frequency than C-items and blending them into one number hides that difference. See the cycle count sample size calculator to run this on your own numbers.
Cycle counting vs. physical inventory count
A physical inventory count covers the entire inventory in one pass, typically annually, and usually requires halting normal operations for the duration. Cycle counting instead checks a rotating subset continuously, in small batches, without a full shutdown.
The two are not strictly either-or. Many businesses run cycle counts throughout the year to catch and correct discrepancies continuously, while still performing one annual full physical count, since financial reporting or audit requirements often specifically call for a comprehensive count on a set schedule rather than accepting cycle count coverage alone.
How a cycle count works in practice
Pick a method (ABC analysis is the standard starting point), break the SKU list into manageable daily or weekly batches by location rather than scattered SKUs, and assign the counts to a specific person or small team as a routine part of their day. Use barcode scanning to record counts directly into the system, since a manual paper-to-spreadsheet transcription step is a common source of its own errors.
When a count does not match system records, investigate before adjusting: an isolated variance is often a simple miscount, but a SKU that keeps showing a discrepancy across multiple cycles usually points to a process issue, mislabeling, a receiving error, or shrinkage, that is worth fixing at the source rather than repeatedly correcting the number. For the full step-by-step setup, including building the schedule and reconciling discrepancies, see how to set up cycle counts.
Run cycle counts without leaving your inventory system
StockFlow lets you schedule and scan cycle counts by location, flag discrepancies automatically, and track accuracy trends over time, no spreadsheets required.
Trusted by small businesses
What our customers say
“Super Kind! Quick replies from their support and very easy fixes, changed the dashboard a bit and customized it. Also gave me 450 items extra on the free plan just for me. Highly recommend and again great service!”
“Best customer service! Stockflow's customer support is fast and extremely helpful. They assisted me with customization of the software to improve my experience as a user.”