Cycle Count Program

Problem class

Annual wall-to-wall physical inventories are expensive, disruptive, and produce accuracy snapshots that degrade immediately. Cycle counting solves the "how accurate is our inventory, right now, continuously?" problem by distributing count effort across the year and focusing it where errors are most likely or costly.

Mechanism

SKUs or locations are selected for counting based on a trigger strategy: ABC velocity classification (A-items counted most frequently), exception-triggered (count after a short-ship or variance event), random sampling, or location-based rotation. Counters receive a task directing them to a location; they count physically and report the result. The system compares the count to the ledger, flags variances above a threshold, and either auto-adjusts small variances or escalates large ones for root-cause investigation. Accuracy is tracked as a KPI (e.g., % of locations within tolerance).

Required inputs

• Current ledger quantities by location (from Unit-Level Inventory Ledger)
• SKU velocity classification (from Slotting Optimization or ledger analytics)
• Count schedule or trigger rules
• Counter assignments (labor pool)
• Variance tolerance thresholds

Produced outputs

• Count results and variance reports
• Inventory adjustment transactions posted to the ledger
• Accuracy KPI dashboards (location accuracy %, SKU accuracy %)
• Root-cause investigation tickets for large variances
• Audit-ready count records for financial compliance

Industries where this is standard

• Pharmaceutical distribution (FDA 21 CFR Part 211 compliance)
• Aerospace MRO parts warehousing
• Grocery retail distribution
• 3PL contract warehousing (client SLA on accuracy)
• Automotive OEM parts distribution

Counterexamples

• Applying uniform count frequency across all SKUs — counting slow-moving C-items as often as fast-moving A-items wastes labor without improving accuracy where it matters. Count effort should be proportional to movement risk and value.
• Counting during peak picking hours in narrow-aisle environments — counters and pickers compete for aisle access, creating congestion and reducing both count accuracy and pick throughput. Schedule counts during off-peak windows.

Representative implementations

• Cardinal Health's pharmaceutical DCs running daily cycle counts to maintain >99.9% inventory accuracy required by FDA auditors.
• IKEA's distribution centers using ABC-stratified cycle counting across 12,000+ SKUs.
• DHL Supply Chain's standardized cycle-count methodology deployed across 500+ client sites globally.
• Open-source: Odoo Inventory cycle count module with ABC classification support.

Common tooling categories

WMS cycle count module + mobile RF scanning devices + variance analytics dashboard + count scheduler (ABC/random/exception-triggered).