Cycle counts that reconcile
A cycle count that produces a number is easy. A cycle count that closes the ledger, explains the variance, and survives an audit is what you actually want. Here's how we built it.
Most cycle-count features in inventory tools ship as a screen that lets you type a new number into a field. That's not a count — that's a manual override. A real cycle count freezes the expected quantity at the moment the count starts, records the actual quantity from one or more counters, computes the variance, and routes anything above your variance threshold to a second reviewer before the ledger moves.
The four guarantees
- Frozen snapshot: 'expected' never silently re-reads while the count is in progress.
- Blind recount: a second counter cannot see the first counter's number until both submit.
- Variance gate: anything beyond ±2% (configurable) requires a manager approval before the adjustment posts.
- Audit row: every adjustment carries the count session ID, counter identities, and timestamp.
Offline by default
Cycle counts happen on the floor, not at a desk. The OneAce mobile app caches the count sheet locally, so a counter walks the aisle with the phone in airplane mode and the count still works. When the device comes back online, the app uploads each entry as an idempotent row keyed by (session, item, counter). A retry after a flaky connection writes once, not twice.
What the report says
The end-of-count report ships in two tabs: the variance summary your operations manager wants, and the line-by-line adjustment list your accountant wants. The line list pairs every quantity delta with a journal-ready cost basis — average cost at the moment of adjustment — so the GL entry posts without a second pass.