On this page (9 sections)
What a cycle count is (and is not)
A cycle count is a partial inventory count done on a recurring schedule — typically counting one section or category per week — instead of a full annual physical inventory. The goal is to keep perpetual inventory accurate without shutting down operations for a full count. Cycle counts work best when each count covers a manageable slice (200–1,000 SKUs) and is finished in a single shift.
A cycle count is not the same as a stocktake. Stocktakes are full counts that pause operations. Cycle counts run alongside normal operations, which means you must handle in-and-out stock during the count window.
Why phones work for cycle counts
Phone cameras read Code 128, EAN, UPC, and QR codes accurately at retail-printed sizes. They struggle with very small (under 8pt), damaged, or glossy barcodes — but those are typically under 5% of SKUs in a maintained warehouse. For the other 95%, a phone is as fast as a dedicated scanner, and a lot cheaper.
The break-even math: a $200 dedicated scanner pays for itself only if you scan more than 5,000 items per month, every month, for years. For weekly cycle counts of 500–1,000 SKUs, the phone is the better tool.
Phase 1 — Prep (15 minutes)
- Print a cycle count worksheet listing the SKUs you will count, grouped by bin location. Sort the list by bin, not by SKU number — you will walk the bins in order.
- Open ScanSheet on a laptop at the counting station. Pick the Inventory template.
- Click Create session and scan the QR with Phone A (the scanner).
- On Phone B (the verifier), open the same ScanSheet URL in a browser tab. The verifier sees the live table as scans come in.
- Pre-load the bin column from your printed worksheet: paste bin labels into the note column in bulk so each scan picks up the bin automatically.
Phase 2 — Scan (45 minutes per 500 SKUs)
- Scanner walks the bins in worksheet order, scanning each SKU once.
- If a SKU has no barcode (rare in maintained warehouses), the scanner reads the SKU aloud and the verifier types it into the laptop table.
- If a SKU has multiple units, the scanner scans one unit and types the count into the quantity cell via the laptop.
- If the same SKU appears in multiple bins, scan it in each bin — ScanSheet will merge rows by barcode, but the note column will show the bin locations separated by a delimiter.
Phase 3 — Reconcile (20 minutes per 500 SKUs)
Export the ScanSheet table to CSV. Open it in Google Sheets next to your perpetual inventory export. Use VLOOKUP to compare scanned count vs system count. Any row with a mismatch is a variance to investigate.
Common variance causes: mislabeled bins (scanner scanned the right SKU in the wrong bin), shrinkage (the SKU is gone but the system still has it), receiving errors (a recent PO was not booked in), and returns not processed. Investigate the top 3 variances by dollar value, not by quantity — a 100-unit variance on a $0.50 item is less urgent than a 1-unit variance on a $500 item.
Phase 4 — Report (10 minutes)
Summarize the cycle count in a one-page report: total SKUs counted, total units, variance count, variance dollar value, top 3 variances investigated, and adjustments made. File it with the inventory lead. Repeat next week with a different section.
KPIs to track
| KPI | Target | Why it matters |
|---|---|---|
| Count completion rate | 100% of planned SKUs | Partial counts hide variances |
| Scan accuracy | ≥99.5% | Below 99% means scanner training issue |
| Variance rate | ≤2% of SKUs | Above 5% means process issue, not shrinkage |
| Variance dollar value | ≤0.5% of inventory value | The number finance cares about |
| Time per SKU | ≤8 seconds | Slower means workflow bottleneck |
Common pitfalls
- Counting during peak receiving hours — received stock inflates the count. Pause receiving during the count window.
- Scanning barcodes on the wrong side of the box (UPC on front, ISBN on back) — verify the barcode matches the SKU label before scanning.
- Forgetting to scan returns and damages — these are SKUs that left the shelf but were not booked out.
- Editing quantities in the laptop mid-scan — wait until the scan phase is done, then reconcile. Editing mid-scan breaks the count rhythm.
- Not pre-loading bin locations — without bin labels in the note column, the reconciliation step takes 3x longer because every row needs manual bin lookup.
When this workflow is not enough
This phone-based workflow scales to about 5,000 SKUs per shift per scanner. Beyond that, you need either multiple scanners running in parallel (open multiple ScanSheet tabs, one per scanner, combine CSVs after) or a dedicated scanner + WMS combo. The phone workflow also does not handle batch pick-and-count (picking customer orders while counting), which requires a WMS that can pause picks in the count zone.
Run a warehouse cycle count without buying scanners
60-second walkthrough — recording this week.
A short demo of the steps described in this article.