Cycle Count App: Rolling Counts Without a Full WMS
A cycle count app lets you verify a small slice of inventory on a schedule — scan each item, enter the counted quantity, export the list — without buying a warehouse management system. With DataScan on an iPhone or Android phone, Single Value Scan mode captures item-plus-quantity rows, and a spreadsheet turns them into variance reports against your system stock. Thirty minutes a week replaces the annual count nobody enjoys.
Cycle counting, briefly
Instead of counting everything once a year, cycle counting verifies a small portion of inventory continuously: aisle 3 this Tuesday, the A-item fasteners next Tuesday, seasonal stock before the season. Over a cycle, everything gets counted — most things several times — and errors surface within weeks of appearing instead of eleven months later. The payoff is real: record accuracy stays high year-round, shrinkage is caught while the trail is warm, and you never shut down for a wall-to-wall count.
The reason most small operations skip it is tooling. Enterprise WMS platforms generate count tasks automatically, but they cost more than the problem. Clipboard-and-pencil works, but transcribing paper counts into a spreadsheet quietly doubles the work. The middle path is the phone: scan-fast capture, structured export, spreadsheet reconciliation.
Set a cadence: ABC counting without the consultancy
ABC classification sounds grander than it is. Sort your SKUs by annual value (or margin, or criticality) and draw two lines:
- A-items — the vital few, typically ~20% of SKUs and ~80% of value. Count monthly, weekly if variance keeps appearing.
- B-items — the middle. Count quarterly.
- C-items — the long tail of cheap stock. Count once or twice a year, often by location rather than SKU.
Then put it in the calendar as small, named tasks — "Tuesday 8:00, aisle 3" — because a count that takes 30 minutes happens and a count that takes a day gets postponed. That is the entire method; the discipline matters more than the math.
Running the count with your phone
- Pick today's slice of inventory One aisle, one shelf, one category, or the next batch of A-items from the schedule. Small slices keep counts accurate — attention fades faster than legs do.
- Start a Single Value scan session In DataScan, open Single Value Scan and name the session after the zone and date (aisle-03 2026-07-10). Scan the item's barcode, count what is physically on the shelf, type the quantity, move to the next item. The rhythm becomes automatic within a dozen items.
- Export the count as CSV or Excel Finish the session and export: one row per item with barcode, counted quantity, and timestamp. Email it through your own SMTP server, upload via FTP/SFTP, or share the file directly. Columns and headers are configurable once, in Settings, to match your reconciliation sheet.
-
Reconcile against system stock in Excel
Export the same items' expected quantities from your ERP,
point-of-sale, or master spreadsheet. In Excel,
=VLOOKUP(barcode, counts, 2, FALSE)pulls the counted quantity next to the expected one; a variance column (counted − expected) and a filter for non-zero rows is your entire exception report. A pivot table by category shows where accuracy is drifting over time. - Investigate and adjust Zero variance: done, and the record is now verified. Non-zero: recount the location first (counting errors are more common than theft), then look for unbooked receipts and mis-picks, and post the adjustment in your system so the next count starts from truth.
Tips that keep cycle counts honest
- Count blind. Don't show counters the expected quantity — knowing the "right" answer nudges counts toward it and buries real variance.
- Timestamps settle disputes. Every scan row carries one, so "was this counted before or after Tuesday's delivery?" has an answer.
- Recount variances the same day. A discrepancy investigated while the pallet is still in receiving takes minutes; the same question three weeks later is archaeology.
- Track accuracy, not just variance. Percentage of lines with zero variance per count is the one metric worth charting month over month.
- Works in the dead zones too. Counts store locally on the phone, so basement stockrooms and racking aisles need no Wi-Fi — see the offline scanning guide.
Real-world pattern: retailers use exactly this loop to replace the annual store-closing count — the retail cycle counting case study walks through a store that counts a category per week and catches shrinkage while the security footage still exists.
Getting started this week
You can be cycle counting by Friday with an afternoon of setup. Export a SKU list with annual values from your system and mark the A-items — a simple sort and a judgment call, not a project. Build the reconciliation sheet once: expected-quantity column, VLOOKUP column, variance column, saved as a template you copy per count. Install DataScan (the 7-day free trial covers everything, so the pilot costs nothing), set the export headers to match the template, and run the first count on your ten most valuable SKUs. That first half-hour usually finds a discrepancy — which is precisely the argument for doing it weekly. If more than one person counts, assign zones and merge their exported files in the template; deployable settings keep every phone's columns identical.
When a WMS is the right answer instead
Honesty about the ceiling: if you run multiple warehouses, directed put-away, and thousands of daily picks, a WMS with integrated cycle counting earns its cost — it generates count tasks from movement data and posts adjustments without a spreadsheet in the loop. The phone-plus-Excel loop is for the very large group of businesses below that line: it delivers the accuracy benefit of cycle counting for the price of an app subscription and a saved spreadsheet template. If year-end still demands a full wall-to-wall count, the same setup scales up — see running a stocktake with iPhones, or start at the DataScan homepage.
Frequently Asked Questions
A cycle count is a small, scheduled count of part of your inventory — a few locations or SKUs at a time — repeated on a rolling basis so that everything gets verified through the year without ever shutting the operation down for a full count.
No. You need three things: a count schedule, a fast way to capture counts, and a comparison against expected stock. A phone scanning app covers the capture, a spreadsheet covers the comparison, and this guide covers the schedule. A WMS automates the loop, at WMS prices.
The usual ABC pattern: A-items (the ~20% of SKUs driving ~80% of value) monthly or even weekly, B-items quarterly, C-items once or twice a year. Adjust to your error findings — items that keep showing variance earn more frequent counts.
Yes. Give each counter a zone and their own phone; each exports their own session file and the files merge in your reconciliation spreadsheet. Settings can be deployed across devices so every phone exports identical columns.
