Set the scope
Choose warehouse, frequency, and start date for the count program.
Cycle counting
Count without showing the answer.
Assign blind count work, capture what is physically present, surface the difference, and protect the balance until a supervisor approves what happens next.
Blind by design
Observation comes before comparison.
The counter sees the item, location, and count reference, but not the system quantity. The observed result remains separate until submission.
That protects the count from confirmation bias while preserving who counted what, where, and when.
Torque Drive ModuleSKU DRV-TQM-45 · CD-A-01
17
System quantityProtected until submission
••
Difference after submitLinked to COUNT-260824-A-DRV
−1
Supervisor routeThe stock balance still has not changed.
RecountA controlled decision chain
Every difference reaches an explicit outcome.
Count evidence and approval stay linked so an adjustment is never a context-free quantity edit.
Issue the sheet
Name the counter, location, date, and unique blind reference.
Find the difference
Submit observed quantity and calculate variance against the protected balance.
Record the decision
Recount, adjust, or make no change with reason and supervisor approval.
What remains linked
The trail survives the adjustment.
A resolved variance still points back to the exact item, count line, sheet, location, plan, and warehouse that produced it.
Place
Warehouse and exact zone or bin remain part of the event.
Item
SKU, class, and unit identify what was physically observed.
Evidence
System quantity, counted quantity, and difference stay together.
Decision
Reason, disposition, status, and approval close the loop.
Run the Cycle Counting workspace.
This feature page introduces the process. The live page, data, and work open inside ERP.ai.