Counting is not the problem. Reconciling is.
Most operations can count. What they struggle with is what happens next: variance spread across paper sheets, a recount nobody can trace, an adjustment posted to the ERP weeks later with no evidence behind it, and an auditor asking who approved it.
Stock Count runs the whole cycle on the device and keeps the trail. A count is planned, assigned, counted blind, recounted if it breaches tolerance, approved by the right person, and only then posted.
What Stock Count does
Blind and open counting
Counters see the bin and the item, not the expected quantity. Open counting is available where your process genuinely needs it.
Bin, batch and serial
Count to the level your stock is actually held at, including batch-managed and serialised material.
Cycle and wall-to-wall
Run continuous ABC cycle counts without stopping operations, or lock the warehouse for a full count.
Tolerance and recount
Set a variance tolerance by value or by quantity. Breaches trigger an automatic recount before anything reaches an approver.
Role separation
Counter, supervisor and approver are distinct roles. The person who counted cannot approve their own variance.
Variance reporting
Variance by bin, item, counter and reason code — so you can fix the cause, not just the number.
ERP posting
Approved adjustments post to SAP Business One or your ERP through a documented interface, with the count reference carried across.
Works offline
Counting continues in freezer aisles and dead zones. The device syncs when it regains coverage.
Full audit trail
Every count, recount, approval and posting is stamped with who, when and from which device.
How a count runs
Plan
A supervisor creates the count — full warehouse, a zone, an ABC class or a specific item list — and sets the tolerance.
Assign
Bins are assigned to counters. Two counters never receive the same bin in the same pass.
Count
The counter scans the bin, scans or selects the item and enters quantity. Blind by default, offline-capable, photo optional.
Recount
Any line breaching tolerance is reissued automatically, usually to a different counter.
Approve
The approver sees expected, counted, variance and value, with a reason code required above a threshold.
Post
Approved adjustments post to the ERP. The count stays queryable with its full history.
What you need
- Android handheld or rugged device — Zebra, Honeywell or standard Android with a barcode engine.
- Barcoded bins and items — we can help with the labelling scheme if it does not exist yet.
- An ERP or WMS to reconcile against — SAP Business One, or any system with an interface.
- Wi-Fi where practical — not required during counting, only to sync.
- Named approvers — the control only works if the roles are real.
What changes
- Shorter count windows — cycle counting replaces the annual shutdown.
- Traceable adjustments — every posting has evidence and an approver behind it.
- Fewer repeat variances — reason codes expose the process fault causing them.
- Audit-ready records — the trail is a query, not a search through folders.
- Better availability — accurate stock means fewer phantom picks and short shipments.
Start with one zone
We usually pilot Stock Count on a single zone or ABC class so you can compare the result against your current method before rolling it out.