Count task and line statuses

See how counting works for what raises a count task and how the tolerance gate decides whether a line posts on its own.

Task statuses

Status	What it means
Pending	Raised and waiting to be claimed. Nothing has been snapshotted yet.
Counting	Claimed. Expected quantities were snapshotted the moment it was claimed, and the location's lines are open for entry.
Counted	Submitted, but at least one line is outside tolerance and still waiting in the review queue.
Posted	Every line has been resolved.
Cancelled	Reached only in one narrow, automatic case — a one-tap count from the pick screen landing on a location with mixed lots. There is no control that lets you cancel a count task yourself.
Superseded	An unstarted, variant-scoped task that a whole-location task has taken over. It simply disappears from Open counts, with no message.

Posted is never a button. It's reached automatically the moment every line on a task is resolved — whether that happens in the same submit, because every line was within tolerance, or later, once a reviewer has cleared every queued line by approving, rejecting or recounting it. A task can reach Posted with nothing having actually changed in stock, if every one of its queued lines was rejected.

Line outcomes

Outcome	What it means
Pending	Not yet counted.
Auto-posted	Matched what was expected, or the variance was within both the quantity and value tolerances — posted automatically on submit.
Queued	Outside tolerance, or the variant has no cost on file — waiting in the review queue.
Approved	A reviewer approved the variance; the difference posted as a stock movement.
Rejected	A reviewer rejected the count; nothing posted and stock was left as it was.
Recount	Sent for a recount; a fresh task exists and this line hasn't posted anything yet.

What raised the count

Source	What raised it
Scheduled	The overnight coverage schedule, queuing the most overdue storage locations.
Manual	A person creating a count directly — from a new count, a new count session, a Counts due group, or the Count now control on a location's own page.
Low at pick	The one-tap prompt on the pick run screen, offered when a location's remaining stock is low after a pick.
Empty at pick	The same prompt, offered when the remaining stock is zero.
Short pick	Raised automatically when a picker confirms fewer units than the pick called for. This does not fire for the commonest case — a picker recording zero — because a zero pick can't be confirmed at all.
Recount	Raised from the review queue against a single variant.

Receiving, dispatch, in-transit and virtual locations never produce a Scheduled count, and never appear in a Counts due group or in a session scoped to a whole site or a zone — their contents are mid-flow rather than stored. They can still be counted deliberately through New count, Count now, or a session given an explicit list of locations. See how counting works.