Show all numbers
Counter progress
Per counter, refreshed on a timer. Never a request per bin.
| No data yet. |
Parked declaration alerts
Devices whose declared bins have not fully synced. Names the missing entries.
No parked alerts.
Start a new count
A guided setup. Defaults are filled in, so most steps are just Next. The count only goes live at the last step.
Name this count
Give it a name your team will recognise at muster, and pick the count type.
Advanced options (recount depth, join code)
Which warehouses?
These are the warehouses on your branch. All are selected by default, which is the usual case. Untick any you are not counting.
Upload the count sheet
This is the SAP export of the lines expected in the warehouse. Batches are read as text, so values keep their exact form.
Confirm the columns
We matched your file's columns to the fields we need. Correct any that are wrong, then import.
Resolve any issues
A suspect batch is one where Excel damaged the value (scientific notation, a coerced date). A counter typing the real batch off the carton would never match a damaged value, so each one must be fixed or confirmed before the count can go live.
Loading issues...
Go live
This opens the count so counters can join with the code below. You do not need to open it separately anywhere else.
Sessions
Create a count, open it, or close it. The console works on one active session at a time.
Active session
No active session. Create one below or sign in to a session already open.
Create a session
Name it, choose the type, pick the warehouses in scope, and choose the recount depth.
Item and bin mode cannot post batch level quantities back to the ERP. A holding extract import forces batch mode.
No warehouses loaded. Sign in through the roster to load your site's warehouses.
Import
Upload the count sheet, the barcode master, and optionally a holding extract.
Batches are read as text, never as numbers, so values like
466216 and 2.50E+22 keep their exact form.Assign bins
Assign in scope bins to counters. Counters see only their own bin addresses, never expected data.
Counters and bins for your active count load automatically below. You do not need the join code for a count you started here.
Assigning inside a count you did not start? Enter its join code
The roster is gated by the join code, so it never leaks who is counting to someone without the code.
Reconciliation
| Item | Bin on file | Batch | System | Counted | Outcome | Resolution | Note |
|---|---|---|---|---|---|---|---|
| Load a session, then pick a bucket. | |||||||
Recount queue
Lines awaiting a second or third blind count. Only counters who have not counted the line are eligible.
| Item | Bin | Batch | Status | Counts so far | Assign to |
|---|---|---|---|---|---|
| Not loaded. | |||||
Export
The ERP posting sheet for SAP, and the variance report for Finance. Only complete lines export to the ERP sheet.
SAP Inventory Counting document number
Emitted in the REMARKS column on every ERP row. Set it once SAP has created the counting document.
ERP Count Result
Eleven columns in the exact order SAP expects, one row per item, bin and batch: Location, Item Code, Item Description, Batch No., Expiry Date, Count 1, Count 2, Status, Third Count, For Posting, REMARKS. For Posting is the accepted count for each batch, and the batches of one item and bin sum to that line's accepted total.
Variance report (Finance)
Per line: system quantity, final quantity, unit variance, each count tier, the resolution type, bucket, expiry, and the net zero relabelling flag.
Settings
Branding and session maintenance.
Branding
Set once. Applies to this console and every counter phone. Status colours (green, amber, red) are fixed and never themed.
Branding here is a live preview. To make it the deployed default, set the BRAND constant at the top of the file.
Rematch session
Replays the matcher over every stored entry and recomputes all line verdicts. Safe to run repeatedly. Use it after resolving batch typos or fixing a matcher issue. Nobody re walks a bin.