The Monday recount

A worked example, not a customer testimonial.

The job

It is Monday, the floor has drifted from the books over the weekend, and you want a real count before ordering. Four hundred items across a storefront and a back room, and the back room is where phone signal goes to die.

The arithmetic, stated so you can check it

Assume roughly two seconds per scan — point, beep, next. Four hundred items is about 13 minutes of actual scanning. The clipboard alternative — write it down, walk back, retype a line into a spreadsheet at maybe fifteen seconds a line — is about 100 minutes, before the transcription errors. Those are our assumptions, not your measurements; time one shelf of your own and redo the math with your numbers.

Set up: one group, two counters

In the web dashboard, create a group — call it Recount 2026-07-28. Invite your colleague if they are not already in the workspace (a Team workspace shares all scans; splitting an aisle between two counters is the intended workflow). Agree on the split: one takes the storefront, one takes the back room.

Count

Scan everything, moving the fast way, not the careful way:

• A repeat scan is not a mistake. Scanning a barcode that exists raises the count on that record — the database does the increment under a row lock, so both of you can hit the same SKU at the same moment and both land.
• The dead zone does not matter. In the back room, scans queue on the phone with their capture time and GPS, and replay in order when you walk back into signal. The 9:40 scan is recorded as 9:40 even if it syncs at 11:15.
• Tag the odd finds. The pallet that should not be there gets a place name typed on the spot: “Back room, wrong bay”.

Reconcile

At the desk, open the dashboard. The count is already there — search it, filter by the group, sort by scan count. If the server refused anything during replay, you were told how many and why; nothing disappears silently.

Export and done

Export the group as CSV — the columns you need, in the order you tap them — and hand it to whatever the ordering decision lives in. The file the phone would produce is byte-identical, but you are at a desk, so use the browser.

What this playbook leaned on

Offline scanning for the exact queue contract, invite your team for roles and shared workspaces, and export fields and formats for the file itself. All of it works on the free early-access Team claim — no card, one founding code from us — so you can run one real recount before deciding anything.