The location hierarchy & codes
Warehouse Layout models a warehouse as a five-level tree. Understanding the levels — and how codes are built — makes the whole screen predictable.
The five levels
| Level | Letter | Holds | Example |
|---|---|---|---|
| Zone | Z | Aisles | Ambient Storage, Cold Chain · 2–8°C |
| Aisle | A | Racks | Aisle A |
| Rack | R | Shelves | Rack 01 |
| Shelf | S | Bins | Shelf 1 |
| Bin | B | Inventory | Bin 01 |
A location can only hold children of the next level down: a zone takes aisles, an aisle takes racks, and so on. A bin is the leaf — it’s where inventory actually sits. That’s why the “add child” action on each row is labelled with the single next type (a zone shows + Aisle, a rack shows + Shelf), and a bin shows no add action.
How codes are built
Each location’s code is its parent’s code plus a one-letter type prefix and a two-digit number:
Z01 ← first zoneZ01-A01 ← first aisle in Z01Z01-A01-R01 ← first rack in that aisleZ01-A01-R01-S01 ← first shelf in that rackZ01-A01-R01-S01-B01 ← first bin on that shelfWhen you add a child, the code is auto-generated from the parent and the next available number — you can’t mistype it. The number counts existing siblings of the same type, so the second aisle under Z01 becomes Z01-A02.
Chips and the summary rail
Every row shows a coloured type chip with the level’s letter (Z / A / R / S / B), darkest at the top of the tree and lightest at the bin. The summary rail at the top counts each level across the whole warehouse, so you can see the shape — “4 zones, 4 aisles, 4 racks, 2 shelves, 2 bins” — without expanding anything.
Status
Each location is Active or Inactive. Inactive locations stay in the tree (and keep their code) but signal that they shouldn’t be used for new put-away — useful for a quarantine zone or a rack being re-built.