If you have inventory, then you need a cycle counting program to properly manage and reconcile your stock counts. Cycle counting isn’t just “counting lite.” It’s a disciplined, always-on system that keeps your inventory honest without shutting down operations. Below you’ll get a practical, step-by-step way to set up your program, followed by a field-tested case study in Jon’s voice that shows exactly how to deal with the messiest part: floating paperwork and reconciliation.
What Is Cycle Counting (and Why Do It)?
Cycle counting is a perpetual inventory auditing process where a subset of items or locations is counted on a defined cadence. Unlike a once-a-year wall-to-wall stock count, it’s less disruptive, more targeted, and gives you a continuous read on accuracy and process discipline.
Core benefits you actually feel: less downtime, earlier detection of errors, and a way to constantly test whether warehouse procedures are being followed.
Choose Your Counting Method
High-ranking guides consistently recommend selecting a method first, then locking the cadence. These are the staples:
-
Geographic (location-based): march through bays/aisles so every location is counted on a schedule.
-
Rank-Based / ABC: count your highest-value or highest-velocity SKUs most often; B and C far less. (Yes, Pareto 80/20 applies.)
-
Other useful flavors: high-usage (by turns), control-group (repeat-count a small set to debug process errors), and opportunity-based (during natural pauses).
Step-by-Step: Set Up a Cycle Counting Program (That People Actually Follow)
1) Get executive commitment + define goals
If leadership won’t freeze movement during counts, approve all inventory quantity adjustments, or fund basic tools, the program dies in week two. Set targets (e.g., >97% accuracy on A items) and name an owner.
2) Classify inventory
Establish ABC classes (by cost of goods or movement). Count A’s most frequently, B’s regularly, C’s occasionally. Review and re-rank on a set interval.
3) Build your schedule
Pick method(s), then do the math on daily volume. Assign areas or item lists per day; never let the queue hit zero. (Sample schedules below from Jon’s playbook.)
4) Define roles, approvals, and reason codes
Who counts, who audits, who approves adjustments? Require a reason code for every adjustment (damage, shrink, UOM, mispick, etc.) and keep an audit trail. Most WMS/ERPs support this natively.
5) Lock the daily procedure
Finalize transactions as much as possible before counting, issue the day’s list, and make it easy for counters to record movement that happens during the count window. (Jon’s case study shows a low-tech card system that works.)
6) Reconcile like a pro
Your biggest enemy is “floating paperwork.” Adjust shelf counts for:
-
orders picked but not confirmed,
-
receipts entered but not yet shelved,
-
receipts shelved but not yet entered.
(Templates and rules in the Reconciliation section.)
7) Instrument the program
Track accuracy by class and location, monitor repeat offenders, and hold a monthly review to fix root causes (not just numbers).
8) Add tech when ready
Barcode scanners cut data-entry errors; RF mobile workflows let you count mid-day because movement updates the system in real time. If you’re on a modern WMS, look for plan/threshold-based cycle-count automation.
Sample Count Schedules (from Jon’s Framework)
Geographic Program Example
-
Assumption: 10,000 items; count each four times/year = 40,000 counts.
-
Daily load: 40,000 ÷ 250 working days ≈ 160 items/day.
Start at one end of the warehouse: Day 1 = first 160 products; Day 2 = next 160… roll continuously; when you hit the end, wrap. Count all locations for the item the same day if your system doesn’t track multi-bin on-hand separately.
Rank-Based (ABC) Program Example
-
2,000 A items × 6/year = 12,000
-
3,000 B items × 3/year = 9,000
-
4,000 C items × 2/year = 8,000
-
1,000 D items × 1/year = 1,000
Total: 30,000 counts ÷ 250 days ≈ 120 items/day.
Use staged “A/B/C/D days” to hit targets; re-rank routinely.
Reconciling Cycle Counts (Kill the “Floating Paperwork”)
When you compare shelf to system, adjust the shelf count before judging variance:
-
Add quantities that were shipped/picked before confirmation.
-
Add receipts entered but not put away (depending on your WMS timing).
-
Subtract receipts placed on the shelf but not yet entered.
Give counters a list of open transactions for items being counted each day.
Barcoding and RF: When It’s Worth It
Barcode collection eliminates re-keying and most fat-finger errors; RF/mobile updates on-hand in real time so counts can happen during business hours with minimal reconciliation. Many ERPs/WMSs (e.g., Dynamics 365, Oracle) support automated plans/thresholds for count creation and approvals.
Case Study: Daily Cycle Counts Without RF — A Field-Tested Process (Jon’s Story)
In previous articles we’ve described cycle counting, the process of counting some stock items or warehouse locations every day, as a valuable tool in ensuring the accuracy of your perpetual inventory. We’ve seen numerous cases in which organizations, after implementing a comprehensive cycle counting program, have had a much more accurate perpetual inventory than they had when they performed full physical inventories. Because accurate on-hand quantities are vital to both providing outstanding customer service and maximizing inventory turnover, it is not surprising that more and more distributors and manufacturers are implementing cycle counting programs.
But cycle counting programs can be difficult to maintain over a long period of time. Many firms become frustrated with the “coordination” problems inherent in cycle counting that are usually not found in a full physical inventory…
Here is an outline of a set of procedures we developed to accomplish this task:
1) Early each morning (or just before leaving on the previous day) the cycle counter receives the list of products to be counted that day.
2) As soon as he or she receives the list, the counter goes to each warehouse location containing a product to be counted and puts a temporary label on the bin reading “Product Being Cycle Counted”. The counter also places a card in the bin to record all material movement of the product before the cycle counting process is completed. This card contains the following information in the header: Date, Item, Bin Location. Four columns on the card allow anyone removing material or placing stock in the bin to record that transaction: Time, Type of Transaction, Order Number, Quantity.
3) After the cards and labels have been distributed, the counter will note the time, and print the count sheet… then proceed to count the items.
4) Whenever an employee fills an order or puts away a stock receipt for an item being counted, he or she will note the time, type of transaction, order number, and quantity on the card in the bin.
5) As an item is cycle counted, the cycle counter compares each transaction’s time to the count time:
• Add quantities for orders/transfers/work orders removed before the count (material off the shelf, not yet reduced in the system).
• Subtract quantities for stock receipts placed in the bin before the count (not yet included in on-hand).6) If there’s a discrepancy between the sheet and on-hand stock, note the difference (e.g., “-2 pieces”), not the raw on-hand. This lets the system be updated later—even after more transactions.
7) As each item is finished, remove the label and card from the bin.
8) If discrepancies remain, check staged orders, will-call, and tag-and-hold. Keep paperwork for filled-but-open orders in one place; add any found quantities to what was counted. If this is painful, build a report listing all outstanding orders by part number.
Result: Faster daily counts, far less reconciliation wandering, and more accurate inventories with less effort and frustration. Why not try it?
Troubleshooting & Continuous Improvement
-
Train counters and auditors; don’t rotate brand-new staff into A-item audits.
-
Separate “look-alike” items to reduce mispicks.
-
Require reason codes for every adjustment and review them monthly.
-
Track repeat-variance SKUs and fix the process (not just the number).
Conclusion
A solid cycle counting program has three pillars: a clear method and schedule, a rock-solid daily inventory counting procedure, and relentless reconciliation. Nail those, and you’ll keep accuracy high without the annual shutdown (and annual migraines). When you’re ready, add scanners/RF to shrink reconciliation to almost nothing.