Cycle counting explained: replace the annual stock-take
Cycle counting replaces the annual stock-take with rolling counts.
Done well, it keeps inventory accuracy above 98% without shutting the warehouse down.
Cycle counting is the practice of counting small subsets of inventory continuously throughout the year.
It replaces the annual full stock-take that shuts the warehouse down for a weekend.
Done well, it keeps inventory accuracy above 98% without disrupting ops.
The one-line definition
Cycle counting is a rolling inventory audit process where small subsets of SKUs are counted on a recurring schedule, with the goal of catching variances early enough to fix the root cause. The whole warehouse never gets counted at once; instead, every SKU gets counted at least once per year, with high-velocity or high-value SKUs counted more often.
The defining test: cycle counting catches a discrepancy within days of it appearing, not months later at the annual count.
Why cycle counting beats the annual stock-take
The annual stock-take has three problems: it shuts the warehouse down (revenue loss), it catches variances months after they happened (root cause is dead by then), and it produces one massive adjustment journal that obscures real operational signals.
Cycle counting solves all three:
- No shutdown — counts run in the background during normal operations
- Variances surface within days, so you can investigate while the trail is fresh
- Adjustments are small and continuous, not one giant year-end shock
The ABC cycle count method
The most common cycle-counting structure is ABC, which classifies SKUs by velocity or value:
- A items — top 20% by velocity or value. Counted every month (12× per year).
- B items — middle 30%. Counted every quarter (4× per year).
- C items — bottom 50%. Counted once or twice per year.
The principle: high-velocity and high-value SKUs deserve more attention because their variances cost more. C items can wait; if a slow-moving C item has miscounted by 2 units, it does not move the P&L.
Some operators use ABCD (adding a D tier for very slow movers counted once a year) or sub-divide A items into AA, A1, A2 for very high-velocity SKUs.
How a cycle count actually runs
A modern WMS generates the count list based on the schedule — typically a handful of SKUs per day or per shift. A picker (or a dedicated cycle-count team) walks to each bin, counts what is physically there, and enters the count on a scanner. The WMS compares the count to system on-hand and flags any variance above a threshold.
Variances above threshold get investigated: was it a receiving error, a picking error, a putaway error, a theft pattern, or a system bug? Root cause matters more than the adjustment journal.
What "good" cycle counting looks like
- Inventory accuracy above 98% across all SKUs, above 99% on A items
- A items reach 100% count completion every month
- Variances trend down over time as root causes get fixed
- Finance signs off on the rolling-adjustment process and skips the annual full count
Most ANZ SMBs we talk to are running on 85–93% inventory accuracy with an annual stock-take. Cycle counting consistently pushes them above 98% within 90 days of setup.
How OpsUI handles this
OpsUI's Warehouse module includes a Cycle Counting workflow — ABC schedule built in, daily count list generated automatically, scanner-driven counts on the floor, variance threshold rules per SKU class, and a sign-off flow that produces a clean audit trail for finance. No spreadsheets, no end-of-year war room.
Frequently asked
What is the difference between cycle counting and a stock-take?
A stock-take is a full inventory count, typically done once a year, that requires shutting the warehouse down. Cycle counting is a rolling audit process where small subsets of SKUs are counted continuously throughout the year — no shutdown required. The end-of-year inventory number is just as accurate, but the variances surface within days rather than months.
What is ABC cycle counting?
ABC cycle counting classifies SKUs by velocity or value and counts each class at a different frequency. A items (top 20% by velocity or value) get counted monthly. B items (middle 30%) get counted quarterly. C items (bottom 50%) get counted once or twice a year. The principle: high-velocity and high-value SKUs deserve more attention because their variances cost more.
How often should I cycle count?
Every SKU should be counted at least once per year. A-class SKUs (top 20% by velocity or value) should be counted monthly. Most modern WMS platforms generate a daily count list that distributes the work across the year — typically 10–30 SKUs per day for a mid-sized operation. The exact cadence depends on warehouse size and operational variance tolerance.
Does cycle counting work with Xero or MYOB inventory?
Not really. Xero and MYOB native inventory track cost and on-hand quantity, but they do not have bin locations, count workflows, or variance investigation tools. Cycle counting requires a WMS or ERP with a cycle-count module. OpsUI ships cycle counting in the Warehouse module, with bidirectional Xero or MYOB sync wired during rollout so the inventory adjustments flow back to your accounting ledger.
See how OpsUI approaches this differently.
No hidden fees. No six-month implementations. Just warehouse software that works.
Book a Demo