Warehouses → Zones → Racks → Positions
A four-level topology that means an asset has an actual address, not "Building C, somewhere."
"Where is the pallet" is a question that, in too many ITAD warehouses, is answered by walking around until you find it. The platform makes the answer a row in a database.
The hierarchy
Warehouse: a physical site (Amsterdam, Rotterdam, Brussels, or wherever you operate). Each warehouse has an address, contact info, and a capacity total.
Zone: a region inside the warehouse with a type (receiving, processing, storage, quarantine, dispatch, recycling, demanufacturing). Zone types affect which workflow steps can happen there — assets in a recycling zone can’t be added to an outbound sales order without first being moved.
Rack: a physical rack inside a zone, with rows and positions. Racks have a type (standard pallet rack, server rack, secure cage, parts shelving) and a capacity.
Position: the specific slot on the rack where a pallet or asset lives. Positions have Code128 barcode labels printable from /core/storage-racks/[id]; scanning a position label tells the platform exactly where the operator is.
Transfers
/core/warehouses/[id]/transfers tracks asset movement between warehouses. Each transfer has a source, a target, an in-transit window, and a status (pending → shipped → received → reconciled). Used for moving stock to a sales-region warehouse or consolidating before a major outbound.
Capacity tracking
Each warehouse, zone, and rack tracks utilization. The dashboard widget shows capacity vs. occupied, with alerts when a zone crosses an 85% threshold. Helpful when you’re about to receive 12 pallets and need to know whether the receiving zone has room for them before the truck pulls in.