Skip to content

Floor count

The counter’s screen (/floor/count/:id). Three steps, and the third one is the whole job.

  • The loop
  • Blind counting
  • What happens next
  • See also
  1. Scan the bin — confirms which location you are counting.
  2. Scan the item — confirms what you are counting.
  3. Enter what is really there — the number in front of you.

That third step is phrased deliberately. Not “confirm the quantity”, not “is this correct?” — enter what is really there. The screen is asking for an observation, not an agreement.

Where the count is blindBlind countA count where the counter never sees the expected quantity, so the number they report is genuinely independent rather than a confirmation of what the system already believed. Read more → , the counter never sees the expected quantity.

The counter’s job ends at the number. What happens to it is somebody else’s decision:

  • Matches — the count closes.
  • Differs — the count goes to Needs review, not straight into your stock figures.

A count goes for review once every bin is done: each item counted, each bin with nothing on the sheet looked into and confirmed empty. If a counter cannot finish, Can’t finish? Send what I have in the ⋯ menu names the bins still open and asks why (out of time, can’t reach a bin, something else). Those bins and items go as not counted, never as zero: their stock stays as it is, and the review shows them first.

The approval queue in Counts is where someone decides whether the count was right (adjust the system) or wrong (recount). Approving posts a reason-coded adjustment into the movement ledger.

Separating the two roles is what keeps counting honest: the person holding the goods reports what they see, and nobody is asked to both observe and adjudicate.