Count it properly, and only once
Full and cycle counts with barcode scanning, multiple staff counting together, variance review and cost impact before you apply.
The annual one and the weekly one
They behave differently and confusing them is expensive. A full count treats an uncounted item as absent. A cycle count leaves anything you did not look at alone.
- Full stocktake. Counts everything in scope. Items in scope with no recorded count are zeroed on apply, with an explicit warning first.
- Cycle count. Counts a slice, a vendor, a category or a shelf. Only what you counted is updated, so the low-disruption weekly count is safe to run.
- Scope it before you start. All products at a location, a filtered set, or a hand-picked list of variants.
Built for a person walking a warehouse
Counts take hours and get interrupted. The screen has to survive being closed and reopened tomorrow.
- Scan and go. Barcode scanning uses the same conventions as receiving, with a scan log showing recent scans while you work.
- Count together. Multiple staff can open the same stocktake on different devices. Scans are combined, counts sync between devices, and you can see who else is counting.
- Stop and resume. A count stays open until you apply or cancel it. Come back days later and continue where you left off.
- Live variance as you work. Matched, mismatched and uncounted totals update as you go, with the cost and retail impact visible before you finish.
- Count sheets for paper. Export a count sheet as PDF or CSV when the count happens away from a screen.
The correctness details that decide whether a count is any good
Most counting mistakes are not arithmetic. They are reconciling against the wrong number, or against a number that moved while you were counting.
- Counted against on hand, not available. Units committed to unfulfilled orders are physically on your shelf. Reconciling a physical count against available inventory systematically invents shrinkage that was never there.
- Expected quantities refreshed before apply. Sales during a long count would corrupt naive variance maths, so Stockie re-reads immediately before applying and flags lines that moved while you counted.
- Applied as deltas. Adjustments post the difference rather than an absolute value, so a sale that happened mid-count is not overwritten.
- Lands in the audit trail. Counts apply through inventory adjustments using the built-in Count reason, so they appear in the adjustments report and export like any other movement.
Common questions
What happens to items I did not count?
It depends on the type. A full stocktake treats them as absent and zeroes them, with a warning before you commit. A cycle count leaves them untouched.
Can two people count at once?
Yes. Multiple staff can count in the same stocktake on different devices. Scans are combined and counts sync between devices, with staff attribution and an indication of who else is counting.
What if stock sells while we are counting?
Expected quantities are refreshed right before you apply, lines that moved during the count are flagged, and adjustments post as deltas rather than absolutes. A mid-count sale will not be overwritten.
Related features
Adjustments
Damage, shrinkage, donations and returns, recorded with a reason, a staff member and notes, then synced to Shopify.
Costs & COGS
A weighted average cost per variant, backed by a receipt ledger, so inventory valuation reflects the quantities and costs you actually received.
Reports
Stockout, stockout risk, overstocked, dead stock, sales performance, ABC analysis, inventory value and more, all exportable.
See it on your catalogue.
Install Stockie, let it read your sales history, and judge the suggestions against stock you actually know.
14 days free · no credit card at install