Who does what when several warehouses count at once

With several warehouses counting at once, the trouble is rarely a barcode that will not scan. It is an error that nobody owns: a bin is missed because everyone assumed another team had done it, two files arrive in different formats and nobody standardises them, a disputed document gets a different ruling at each site. The remedy is not complicated. Before the count, write down what each role does, so that every task has one named owner.

Six roles, each with a job

• Coordinator: one person for the whole operation. Keeps the signed cut-off and document rules, manages the in-transit register and the progress board, rules on disputed documents and is the single point of contact for head office.
• Site lead: one per warehouse. Assigns zones, confirms that every bin has been scanned, checks the site's totals and reports to the coordinator at agreed times.
• Scanners: two to four per site. Each takes a zone, scans it and notes exceptions on the spot, but does not decide what happens to a difference.
• Recounters: recount bins that have been flagged, and are never the person who scanned that bin originally, so there is a second pair of eyes.
• Data clerk: one person, on site or at head office. Collects the exports at set times, checks file names and formats, merges them and runs the first checks.
• Finance contact: not necessarily on site, but reachable all day to answer questions on documents, cost and booking method.

In a small warehouse one person can hold two roles, for instance a lead who also scans. The recounter must still never be the scanner of the same bin, and that rule should not be bent.

Three principles for dividing work

1. The person who looks after the goods does not count them alone. A storekeeper may help, but someone else scans the quantity.
2. Every change leaves a trace. A scanner reports a problem to the site lead, the lead posts it in the group, anything needing a ruling goes to the coordinator, and nobody quietly edits a file.
3. Language and communication must reach everyone. If managers and floor staff speak different languages, choose site leads who can talk to both, and put the key instructions on a one-page picture card at each warehouse door.

The rhythm of the day

Set fixed reporting points in one shared format that is understood at a glance. Every hour, for example, each site lead posts a single line in the group:

Site B | 10:00 | bins 38/120 | exceptions 2 | expected finish 15:30

The coordinator collects these into a table with one row per site, so a site that is falling behind is visible immediately, and moves people in time instead of finding out at the end.

A rough shape for the day: a short briefing fifteen minutes before the start, a call from each site lead when counting begins, an hourly progress line, a first export and merge about halfway so that format problems surface early, and at the end each lead signs off that all bins are scanned and files handed in before the coordinator closes the count.

A staffing example

Suppose three warehouses count together: one coordinator, three site leads, six scanners (two per site), two recounters and one data clerk, thirteen people in all, with one finance contact on call.

At ten in the morning site A reports bins 52/90, site B 38/120 and site C 20/40. The coordinator sees that B is behind and sends one recounter to take over a zone there, and by three in the afternoon all three sites are finishing at about the same time. Without a common progress table, no such rebalancing would be possible.

Common failures

• No one owns the bins that were missed, because each person assumed someone else scanned them.
• Two people scan the same zone, and the quantity doubles when files are merged.
• The original scanner recounts the bin, and the mistake is repeated.
• A site lead edits a file after export and records nothing.
• A site falls behind and says so only at the end.

In short

Clear roles, a steady rhythm of reports and traceable changes let several warehouses count like one team. InventoryHub schedules multi-warehouse counts around a shared cut-off, with several teams counting at once and the scan records merged by SKU into a single table.