Warehouses → Zones → Racks → Positions
A four-level topology that means a pallet 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 details and a capacity in pallets, and the warehouse list shows how much of that capacity is in use as a percentage. Zone: a region inside the warehouse with a type. Seven types come built in — receiving, processing, storage, staging, shipping, quarantine and recycling — and your organization can add its own zone types when the building has a room the defaults didn’t anticipate. Rack: a code, a name, and a grid of rows by columns inside a zone. Position: one slot in that grid, with a row, a column, a barcode, a maximum weight and a blocked flag for the slot with the leaking roof above it.
Positions carry Code128 barcode labels, printable from the rack detail page; scanning a position label tells the platform exactly where the operator is standing and what should be in front of them.
Where the layout is managed
Creating warehouses, editing them, adding zones and shaping the rack layout all happen under Settings > Core > Locations. The warehouse cards and the detail page link straight to it. Removing a zone stays there too, because that is where the dependency checks live — the platform will not let a zone with pallets in it disappear because the layout looked tidier without it.
The rack grid
/core/storage-racks/[id] is an interactive grid of the rack. Your team can drag a pallet from one slot to another, assign an existing unplaced pallet to a slot, create a new pallet and stage it in a slot, remove a pallet, block or unblock an empty position, and open the inventory filtered to that rack. Changes are staged in a local buffer and saved together in one go — or thrown away together. Try to leave with pending changes and the page warns you. It is one of those small mercies that keeps a warehouse from becoming a puzzle with invoices.
The transfer log
The Transfers tab on a warehouse — also available as its own page for bookmarking — is the movement history of assets and pallets: from which rack, zone or warehouse to which, when, and by whom. It is a log, not a workflow: there is no transfer to approve, ship or reconcile, only the record of what moved. Search runs across the whole history of the warehouse before the page is cut, with the total and page jumps below the list. When a client asks where their pallet spent March, the answer is a filter, not a memory.
Why four levels
Because “storage” is not an address. A receiving zone that fills up, a quarantine zone that must stay separate, a blocked position that everyone knows about except the new operator — the platform can only enforce those things if it knows where things are at the level a forklift understands. A row in a database is not glamorous. Neither is walking the aisles at 17:40 looking for a pallet that left on Tuesday.