Cycle counting—the practice of regularly counting portions of inventory—is the foundation of inventory accuracy. Done well, it eliminates the need for disruptive annual physical counts while maintaining accuracy above 99%.
This guide covers everything from program design to execution, including ABC classification, frequency scheduling, and root cause analysis.
Why Cycle Counting Beats Physical Inventory
Traditional annual physical counts have serious drawbacks:
- Operational disruption – You shut down receiving and shipping for days
- Temporary accuracy – Accuracy degrades immediately after the count
- Rush errors – Counting everything at once leads to mistakes
- Root cause blindness – You see variances but not patterns
Cycle counting spreads the workload across the year, catches problems early, and provides data for continuous improvement.
For a detailed comparison, see our article on cycle counting vs physical inventory.
ABC Classification: The Foundation
Not all inventory deserves equal counting attention. ABC classification prioritizes based on value and velocity:
A Items (High priority)
- Top 20% of SKUs by movement or value
- Count weekly or bi-weekly
- Typically 80% of your inventory value
B Items (Medium priority)
- Middle 30% of SKUs
- Count monthly
- Moderate value contribution
C Items (Low priority)
- Bottom 50% of SKUs
- Count quarterly
- Low individual value
Calculating ABC class: 1. Export 12 months of movement data 2. Rank SKUs by total units moved (or dollars) 3. Assign A to top 20%, B to next 30%, C to remaining 50% 4. Update quarterly as patterns change
Scheduling and Volume
Determine daily count volume:
Formula: Daily locations to count = (Total locations × Count frequency) ÷ Working days per year
Example:
- 5,000 locations
- A items (1,000 locations): 52x/year = 52,000 counts/year
- B items (1,500 locations): 12x/year = 18,000 counts/year
- C items (2,500 locations): 4x/year = 10,000 counts/year
- Total: 80,000 counts/year ÷ 250 working days = 320 counts/day
Scheduling tips:
- Count early in the shift before order picking begins
- Assign dedicated cycle counters when volume justifies it
- Don't schedule counts near shift changes when accuracy dips
Executing Counts
Blind counting vs. audit counting
*Blind counts* hide system quantity from the counter. They must count from scratch, reducing bias. Best for routine daily counts.
*Audit counts* show expected quantity and ask for verification. Faster but prone to confirmation bias. Use for recounts only.
Count procedure: 1. System generates count sheet or mobile assignment 2. Counter physically counts all units in location 3. Counter enters counted quantity 4. System flags variance if threshold exceeded 5. Variance requires recount or investigation
Recount threshold: Set automatic recount triggers (e.g., >5% variance or >10 units). Never adjust inventory on first count if variance exists—always recount.
Root Cause Analysis
Counting without fixing root causes is pointless. Track variance reasons:
Common root causes:
- Receiving errors – Wrong quantity or wrong item booked in
- Picking errors – Wrong item or quantity picked
- Putaway errors – Items placed in wrong location
- Cycle count errors – Miscount (should decrease over time)
- System errors – WMS bugs or integration issues
- Theft – Unfortunate but real
Pareto analysis: Track which SKUs have repeated variances. If SKU X shows variance 5 counts in a row, investigate that item specifically—packaging confusion, multiple locations, or training issues.
Process fixes > adjustments: When you find a root cause, fix the process. Simply adjusting inventory perpetuates the problem.
KPIs to Track
Measure program effectiveness:
Location accuracy
- Formula: (Locations with no variance ÷ Total locations counted) × 100
- Target: >99%
SKU accuracy
- Formula: (SKUs with no variance ÷ Total SKUs counted) × 100
- Target: >99%
Unit accuracy
- Formula: 1 - (|Variance units| ÷ Total units counted)
- Target: >99.5%
Variance trend
- Are variances increasing or decreasing over time?
- Track by root cause category
Count productivity
- Locations counted per hour
- Helps with scheduling
Common Mistakes
Over-adjusting Adjusting on every variance without investigation masks root causes and inflates error rates.
Undercounting C items Low-value items still matter. A wrong C item shipped creates the same customer complaint as a wrong A item.
Ignoring count productivity If counters are averaging 10 minutes per location, investigate. It should be 2-3 minutes maximum.
No accountability Track accuracy by counter. Persistent low performers need additional training or reassignment.
Skipping recounts Recounts feel redundant but catch counting errors. Skip them and you're adjusting based on mistakes.