Headquarters
175 S Main St Suite 1310,
Salt Lake City, UT 84111
Cycle counting is a way of auditing inventory by counting a small part of your stock on a regular schedule, instead of closing the store for a full physical count. Over a few weeks or months every item gets counted, and mistakes are caught while they are still small.
Accurate inventory numbers keep your promises. When counts are off, online orders get routed to stores that can't fill them, pickup orders are canceled, and customers leave disappointed. This guide covers what cycle counting is, the main types of cycle counts, how often to count, the process step by step, and the best practices that keep store counts accurate.
Cycle counting breaks an inventory audit into manageable pieces. Instead of counting every item at once, retailers count a subset of SKUs during each session, often starting with high-value, fast-moving, or high-risk products. By spreading counts across days or weeks, teams keep inventory accurate without disrupting store operations, and they spot shrinkage, mispicks, and process gaps early.
Each count compares what the system says is on hand with what is actually on the shelf. The difference is the variance. Reviewing and correcting variances regularly is what keeps inventory trustworthy between full counts.
A full physical inventory counts everything at once, usually once or twice a year, and often means closing the store or counting overnight. Cycle counting spreads the work out, so the store stays open and the count never gets that big.
| Factor | Cycle counting | Full physical inventory |
|---|---|---|
| What gets counted | A small set of SKUs each time | Every item in the store |
| How often | Weekly or monthly, on a rolling schedule | Once or twice a year |
| Impact on the store | Store stays open | Often closed or counted overnight |
| When errors are found | Within weeks | Months later |
Many retailers use both: cycle counts through the year, and a full count when an audit or year-end requires it.
There is no single way to cycle count. Most retailers combine a few of these methods.
ABC cycle counting ranks products by value or sales volume and counts the most important ones most often. "A" items, the small share of SKUs that drive most of your revenue, are counted most frequently. "B" items are counted less often, and "C" items, the long tail, the least. Effort goes where an error costs the most.
In a directed count, head office decides exactly what each store counts: specific SKUs, a category, or a location in the store. Directed counts are useful after a sale event, for products with frequent variances, or for items that online orders depend on.
A control group count repeats the same small set of items several times over a short period. It is a way to test and tighten the counting process before rolling it out to the whole catalog.
A random sample count picks items at random for each session. Over time every SKU has the same chance of being counted, which helps catch errors in products nobody is watching.
Some counts are triggered by events rather than a schedule: an item hits zero, a store rejects an online order because it can't find the item, or a delivery arrives with discrepancies. Counting at that moment corrects the record before the next order relies on it.
It depends on how fast products sell and how costly an error is. A common starting point is to count "A" items monthly, "B" items quarterly, and "C" items once or twice a year, then adjust based on the variances you find. Fast-moving products, high-value items, and anything sold online from store stock deserve more frequent counts, because a wrong number there turns directly into a canceled order.
The right cadence is the one your stores can keep. A small count every week does more for accuracy than a large count that keeps getting postponed.
Inventory teams create counts centrally and assign them to specific stores or departments, from a handful of SKUs to a full store. With the right cycle count software, retail ops can upload a list and distribute hundreds of items across dozens of locations in minutes, then track progress for every store in one dashboard.
Before a count begins, store managers review what is assigned to them. Each count shows its scope, start time, and due date, so managers can plan labor and pick a quiet time, such as before opening or after close.
On counting day, associates scan barcodes on a handheld device or tablet instead of writing on clipboards. Each scan updates the tally, which removes typos and mis-keyed quantities. Large counts can be split by zone, department, or shift so several associates work at once, with each session recording its own timestamps.
As items are scanned, barcodes that don't match a product are flagged to be matched later, and scans of items that aren't part of the count are set aside. Items without barcodes can be hand counted. At the end of the session, associates mark anything they couldn't find and resolve open issues before submitting.
Once a store submits a count, operations teams review the results. Variances are highlighted, and a threshold helps separate small differences from the ones that need a closer look or a recount. Adjustments can be approved one by one or in bulk.
Only approved adjustments change inventory, and they sync to eCommerce and the ERP so every system shows the same stock. Completed counts keep their session history, variance summary, and approval record for future audits.
Spreadsheets work for a single shelf counted by one person. They struggle as soon as several associates, days, or stores are involved. Data piles up across tabs, formulas for error checks and progress tracking make the file harder to maintain, and version control issues (the dreaded "final_final_v2.xlsx") make it hard to trust any one file. There is also no clean way to flag exceptions, so notes end up in margins and separate forms.
Most counting errors come from a few predictable places. Items aren't always where the system expects, such as on a fitting room rack or shelved in another department. Rushed associates count the wrong SKU or the wrong location. Manual entry leaves room for typos. Damaged or obsolete stock gets counted as sellable. When there is no review step, small errors post straight to inventory and snowball into bigger variances.
A few habits make the biggest difference. Count during low-traffic hours so walk-in sales don't change stock mid-count. Use directed counts for the products that matter most, and ABC ranking to decide how often. Scan instead of typing. Split large counts by zone so no session drags on.
Most important, review variances before they post. Recount large differences instead of accepting them, and track the reasons behind recurring variances, whether receiving, theft, or mispicks, so the root cause gets fixed and not just the number. Variances often start at receiving, which we cover in why receiving is where inventory accuracy is decided.
Warehouses have dedicated staff, fixed bin locations, and time set aside for counting. Stores don't. Store associates count between serving customers, products move around the floor, and shoppers can buy an item mid-count. That is why store cycle counting works best with short, directed sessions, guided scanning on a device associates already use, and a head-office review before anything changes.
* * *
HotWax Commerce brings this process to store teams inside Shopify POS. Retail ops plan and assign directed cycle counts across stores, associates count in guided scanning sessions, and head office reviews variances against a threshold before approved adjustments sync to eCommerce and the ERP. It is part of HotWax store inventory management, alongside receiving and transfers.
Book a demo to see how accurate cycle counts support reliable omnichannel operations with HotWax Commerce.
175 S Main St Suite 1310,
Salt Lake City, UT 84111