How a handheld barcode count runs on the warehouse floor

From the outside, a barcode count looks simple: people walk along the racks with handheld devices and beep their way through the stock. In practice, a good count follows a fixed rhythm, and every skipped step leaves data that cannot be explained afterwards. Here is how a count runs on the floor, from the first briefing to the last export.

Before the first scan

Most of the problems of count day are decided the day before. Check these things:

• Every device is charged, and spare batteries or power banks are at hand.
• Each device has a number, and each person has a device and a zone written next to their name.
• Every bin has a label, and the team leader holds a printed list or sketch of all bins.
• The item list is loaded on the devices or available as a printout for look-ups.
• A test scan has been done on a handful of different items, including one with a worn label.

Then give a briefing of about fifteen minutes: the cut-off time, the zone boundaries, what to do with goods that have no label, and how to report a problem. Also say who has the final word when an argument breaks out on the floor.

The scanning loop for one bin

Every bin is handled the same way:

1. Scan the bin label first, so every following scan is tied to that bin.
2. Scan the items. For identical pieces, either scan each piece or scan once and enter the quantity, whichever was agreed. For cartons, scan the carton label and enter the number of cartons.
3. Close the bin. The device shows the total, and the operator takes a second to ask whether the number looks plausible.
4. Move to the next bin on the route.

One rule matters more than the others: one bin, one person, one pass. Nobody scans a bin from memory, and nobody scans on behalf of a colleague who has left.

If a label will not scan, do not just type the digits. Try another angle or wipe the label clean. If that fails, note the bin and the item on the log sheet and let the team leader relabel it for a later scan.

Recount on the spot

Compare each bin with its book quantity as soon as it is closed, and agree a tolerance in advance, for example more than five pieces or more than five per cent. Above that, a second person recounts straight away, before the team moves on. The reason is simple: the goods are still where they were, and nobody has shifted them.

Imagine a unit of 120 bins counted by four people with 30 bins each. In the first hour's export the team leader sees that bin C-14 shows 48 pieces against 84 in the books. A recount finds a pallet of the same product shelved in the neighbouring bin C-15. The error is corrected within minutes instead of becoming a mystery in next week's report.

Export during the day

Do not leave all the data on the devices until the evening. Export or synchronise after every zone, or at least every hour. Then a dead battery or a lost device costs an hour of work, not a day.

Keep a simple log sheet: device number, person, zone, start time, end time, and the first and last bin of each hour.

Closing the count

Before the team leaves, do three things:

1. Export every device and name the files with the site, device number, date and hour.
2. Compare the list of bins that were scanned with the master list of bins. Bins that appear in only one of them were missed or mislabelled.
3. Walk the site once more to check that no area was skipped, including mezzanines, back rooms and goods on the loading bay.

Only then are the files merged and cleaned into one table. A missed zone found a week later has already seen goods move, and its numbers can no longer be tied to the cut-off.

InventoryHub counts this way: handheld scanners record the bin, the quantity and the time for every scan, bins that do not tally are recounted on site, and the results are merged into a SKU-level table you can filter in Excel.