Warehouse Managementoperational
Storage Locations & Slotting
How are sectors, slots, and bins organized — and how does put-away work?
Each warehouse divides into sectors, and sectors into slots with an explicit capacity and capacity unit. Put-away is confirmed against a slotted location, and current-placement views show what sits in each warehouse and sector right now.
How it works
Sectors are the working subdivisions of a warehouse, and slots are the addressable positions inside them. A slot carries a capacity with its unit, so placement decisions run against stated limits rather than guesswork.
Put-away is a confirmation, not an assumption: items are confirmed into a slotted location, and current-location records keep a live picture of what is in each warehouse and sector, including whether it is slotted. The result is that "where is it" has a record-level answer.
Because slotting is configured per warehouse, the same network can run a tightly slotted central site and simpler satellite depots. Storage conditions on sectors add the second dimension — not just where goods fit, but where they are allowed to be.
What it records
Explicit slot capacity
Every slot records a capacity and capacity unit, making space a stated constraint.
Put-away confirmation
Items are confirmed into slotted locations rather than assumed to be wherever the paperwork says.
Current placement views
Per-warehouse and per-sector records show what is where right now, with a slotted flag.
Per-warehouse configuration
Slot discipline is enabled per warehouse to match how each site actually runs.
What this touches
- Multi-warehouse network
Sectors and slots live inside the warehouse hierarchy. - Storage conditions
Sector condition rules decide where sensitive goods may be placed. - Stock ledger & visibility
Ledger rows are scoped to warehouse and sector, matching placement. - Stock transfers
Bin-to-bin moves change the slotted location through a transfer record.
See storage locations & slotting running in continON.
A guided walkthrough on a sanitized demo tenant — this capability inside its module, on the shared platform.