Warehouse location codes
Setting up a numbering system that survives contact with the floor
A warehouse location code is a short, unique label for one storage position, used so that a person or a system can say exactly where something is. A good scheme is readable by someone who has never been in the building, stays identical everywhere it appears, and matches the label physically stuck on the rack.
How a code is structured
Almost every workable scheme runs from coarse to fine, so that reading the code left to right walks you through the building. The common levels are zone, aisle, rack, shelf and position, and most warehouses use three or four of them rather than all five. A code like A-03-2 reads as aisle A, rack 03, shelf 2. Which levels you include depends on how precisely you need to point: a small stockroom rarely needs more than aisle and shelf, while a pallet warehouse usually goes down to the individual position.
The rules that make a scheme last
Keep the number of characters identical across every location and pad with leading zeros. A-3 and A-03 look the same when read aloud but sort differently in every list, which is exactly the kind of difference that costs an hour to find. Use a separator between levels so people with visual memory can hold the code in their head. Number both sides of an aisle the way a street is numbered, odd on one side and even on the other, because everyone already knows how that works. And never encode meaning that can change: a code that says which product lives there is wrong the first time you move something.
The label on the rack is part of the system
A location code only works if the physical label and the system agree, character for character. Print the label rather than writing it, place it where a picker looks and not where it happens to fit, and use the same code on the shelf edge and in any overview list. If your locations carry barcodes, the barcode content and the location name must be identical, since a scan is a literal comparison and a single leading zero difference is enough to fail. Discrepancies between rack and system are the most common cause of stock ending up in the wrong place.
How fine to go
More locations mean more precision and more work. The practical test is whether someone standing at a location can see the whole of it at a glance. If they have to search within a location, it is too big and the code stops saving anyone time. If you find yourself constantly relocating stock between neighbouring locations, it is too small and you are paying in movements for precision you do not use. Start coarser than you think you need: splitting a location later is easy, merging a scheme that grew too fine is not.
What makes a scheme fall apart
Three things kill a numbering system. The first is exceptions: one aisle numbered differently because it was added later, which forces everyone to remember a special case. The second is renaming: changing a code after it is in use makes every historical transaction misleading, so add a new location and empty the old one instead. The third is running out of room, which happens when the scheme has no space to grow. Leaving gaps in the numbering costs nothing and saves a renumbering exercise the first time a rack is added.
Setting them up in Inventory Management
Create locations from the Locations screen, either one at a time with the "Add location" button or as a whole range with "Create series", where you give a prefix, a start number and an end number. Creating A1 through A10 is a single action. Once a location exists it can be selected when registering inbound goods, outbound goods and relocations, and you can open it at any time to see what is stored there. Locations can be deleted later, but only while they are empty, which prevents stock from quietly disappearing with the location that held it.
