Bins-USA WMS CloudBins-USA WMS Cloud

How to Do a Cycle Count Inventory: A Step-by-Step Guide for 2026

By the Bins-USA team · Inventory & fulfillment guides for multichannel sellers

Shutting down your warehouse for a full physical inventory count once a year is a painful, outdated practice. Cycle counting lets you verify stock in small, rolling batches — so your numbers stay accurate every single day without ever closing your doors.

WMS dashboard showing a cycle count schedule with bin locations, expected quantities, and counted quantities side by side
A modern WMS dashboard makes it easy to schedule, assign, and reconcile cycle counts in real time.

What Is a Cycle Count — and Why It Beats Annual Inventory

A cycle count is a scheduled, partial inventory audit in which a specific subset of your SKUs or bin locations is counted on a rotating basis throughout the year. Instead of counting everything at once, you count a small section of your warehouse each day, week, or month until every SKU has been verified at least once per cycle.

The benefits over a traditional full physical count are significant:

  • No warehouse shutdown or lost selling time
  • Errors are caught weeks after they happen, not 12 months later
  • Staff build counting skills through repetition
  • Discrepancies are smaller and easier to investigate

For multichannel sellers managing stock across Shopify, Amazon, Faire, eBay, and Walmart, accurate counts are even more critical — a single miscounted SKU can trigger overselling across every channel simultaneously. See how this connects to broader multichannel inventory management best practices.

Step 1 — Choose Your Cycle Count Method

Before you count a single item, decide which method fits your operation:

  • ABC analysis (most common): Rank SKUs by sales velocity or value. "A" items (top 10–20% by revenue) are counted monthly, "B" items quarterly, and "C" items once or twice a year. High-movers get the most attention because they carry the most risk.
  • Control group counting: Count the same small group of SKUs repeatedly over a short period to identify systemic process errors before rolling out a full cycle program.
  • Random sampling: A random selection of SKUs is counted each day. This works well in large, stable warehouses but can miss fast-moving problem items.
  • Location-based counting: Count every SKU in a specific bin zone before moving to the next. Great for warehouses organised by bin number rather than product category.

Most small-to-mid-size sellers get the best results starting with ABC analysis because it focuses effort where inventory errors are most expensive.

Step 2 — Set Up Your Count Schedule and Assign Zones

A cycle count only works if it happens on a predictable cadence. Build a 12-month calendar that maps each SKU group or bin zone to a specific count week. Then:

  1. Divide your warehouse into clearly labelled zones or bin ranges (e.g., A-01 through A-20).
  2. Assign a responsible counter — ideally someone who does not normally pick from that zone, to reduce bias.
  3. Print or digitally issue a count sheet that lists bin location and SKU, but deliberately hides the system's expected quantity. Blind counts are far more accurate.
  4. Set a firm deadline: counts should be completed and submitted before the next pick wave starts so stock can be frozen briefly if needed.

If your WMS supports it, generate count tasks directly from the system so assignments, due dates, and zone maps are tracked automatically.

Step 3 — Execute the Physical Count

This is where accuracy lives or dies. Follow these field rules every time:

  • Freeze movement during counting: Pause picks and putaways in the zone being counted, even if only for 15–30 minutes. Any movement during the count introduces instant discrepancies.
  • Count blind: Counters record what they physically see — they should not check the system quantity first.
  • Count twice if needed: If the first count doesn't match the system, a second independent counter verifies the same location before any adjustment is made.
  • Note conditions: Record damaged units, items in the wrong bin, or unlabelled stock separately rather than folding them into the main count.
  • Use a barcode scanner or mobile WMS app where possible to eliminate transcription errors from paper sheets.

Step 4 — Reconcile Discrepancies and Adjust Stock

After counts are submitted, compare physical counts against system quantities. For every discrepancy:

  1. Investigate before adjusting. Check recent pick history, receiving logs, and return queues. A missing unit might be on a shelf in the wrong bin rather than genuinely lost.
  2. Set an approval threshold. Small variances (e.g., ±1 unit on a high-velocity SKU) may be auto-approved; larger variances should require a manager sign-off.
  3. Commit the adjustment in your WMS so the corrected quantity immediately flows to every connected sales channel. This is the step that stops overselling on Shopify and other platforms before it starts.
  4. Document the root cause. Was it a receiving error? A mispick? A labelling issue? Tracking root causes over time reveals the systemic fixes that reduce future discrepancies.

Step 5 — Track Accuracy KPIs and Refine Your Program

A cycle count program that doesn't measure itself will slowly drift into a rubber-stamp exercise. Track these metrics monthly:

  • Inventory record accuracy (IRA): Percentage of SKUs counted that matched the system quantity. World-class operations target 99%+.
  • Adjustment rate: How many counts required an adjustment? A rising rate signals a process problem upstream.
  • Shrinkage value: Dollar value of net adjustments over a period. This is your real cost of inaccuracy.
  • Time to reconcile: How quickly are discrepancies investigated and closed? Long lag times mean bad data is live on your channels longer than necessary.

Review these KPIs quarterly and adjust your ABC classifications as your product mix and sales velocity change. A SKU that was a "C" item in January can become an "A" item by peak season.

How a Cloud WMS Makes Cycle Counting Faster and More Reliable

Manual spreadsheet-based cycle counts are error-prone, slow to reconcile, and completely disconnected from your sales channels. A cloud WMS centralises the entire process: it generates count tasks automatically, enforces blind counting, flags discrepancies in real time, and — critically — pushes corrected quantities to every channel the moment an adjustment is approved.

For sellers on multiple platforms, that instant sync is the difference between a clean adjustment and an overnight oversell. Pair your cycle count program with solid multichannel inventory management processes and you'll spend far less time firefighting stockouts or angry customer emails.

▶ See it in action — the 2-minute Bins-USA demo.

Run Smarter Cycle Counts with Bins-USA

Bins-USA is a bilingual cloud WMS built by a real multichannel seller, designed to make cycle counting effortless — with automated count schedules, blind count enforcement, and instant inventory sync across Shopify, Amazon, Faire, eBay, and Walmart the moment you approve an adjustment. Available in both English and Spanish, Bins-USA helps your entire warehouse team count accurately and reconcile fast. Start your free trial today and see your inventory record accuracy climb.

Start free →   See all integrations

Frequently asked questions

How often should you do a cycle count?
It depends on your ABC classification. High-velocity or high-value 'A' items should be counted monthly, 'B' items quarterly, and slower-moving 'C' items once or twice a year. The goal is that every SKU is counted at least once per full cycle, while your riskiest stock gets the most frequent attention.
Do you have to stop warehouse operations to do a cycle count?
No — that's one of the biggest advantages of cycle counting over a full physical inventory. You only need to briefly pause picks and putaways in the specific zone being counted, typically for 15–30 minutes. The rest of your warehouse keeps operating normally throughout the process.
What is an acceptable inventory record accuracy (IRA) rate after a cycle count?
Best-in-class warehouses target an IRA of 99% or higher. If your IRA is consistently below 95%, it's a strong signal of a systemic upstream issue — such as receiving errors, mislabelling, or process gaps at the pick station — that needs to be addressed at the root cause level.
What is the difference between a cycle count and a full physical inventory?
A full physical inventory counts every SKU in the warehouse at the same time, usually requiring operations to shut down for hours or even days. A cycle count divides that work into small, continuous batches spread throughout the year, so you maintain accurate stock levels without ever closing your warehouse.
How does cycle counting help prevent overselling on Shopify or Amazon?
When a cycle count reveals a discrepancy, a good WMS adjusts the quantity and immediately pushes the corrected number to all connected sales channels. This means your Shopify store, Amazon listing, and every other channel always reflects real on-hand stock — reducing the risk of selling units you don't actually have.