Plan a warehouse structure graphically
Use the warehouse layout editor to build a physical warehouse directly on the canvas. Storage areas, constraints, racks, storage bins, and standard load carriers are stored as the same tenant-bound records shown in the warehouse lists.
Use the domain terms consistently
- A warehouse is the operational and spatial context of the editor.
- A storage area is a structural part such as a building, storey, hall, room, outdoor area, aisle, rack, or level.
- An area type describes its business meaning. Your organization can add tenant-specific types.
- A structural kind controls the stable hierarchy. The server derives it from the selected area type.
- A storage bin is a concrete, addressable inventory location.
- A constraint is blocked or restricted space, not a storage area.
Prerequisites
- Open a physical warehouse and select Warehouse structure > Warehouse layout.
- Publish a storage-bin class revision with geometry before creating racks.
- You need warehouse-layout read and plan permissions, plus activation permission when releasing a layout.
Build the warehouse
- Select Draw storage area, choose the area type in the properties panel, and drag the required area. Dimensions use millimetres and snap to the grid. An area of 4,000 × 4,000 mm is 4 × 4 m.
- Draw constraints for columns, fire lanes, no-storage zones, or safety clearance inside a storage area. Choose Rectangular for square columns and areas or Round for round columns before drawing.
- Select Place rack, a published storage-bin class, and the bay and level counts. Workspace creates the rack, levels, and storage bins atomically.
- Drag standard objects into free storage space. The catalog includes EPAL pallets and box pallets, CP1–CP9, VDA R-KLT, ISO footprints, and ISO containers.
- Select a rack and open Front view to inspect levels and storage bins. Use Top view for the complete structure.
Create new storage areas in the warehouse layout. The Storage areas tab shows the resulting hierarchy and master data, but does not create areas without geometry.
Edit elements
Drag storage areas, racks, constraints, and free objects to move them. Edit position, rotation, and the dimensions of resizable areas in the properties panel. Enter width, depth, and height in millimetres for storage areas and rectangular constraints. Round columns use diameter and height. Standard objects such as EPAL pallets retain their standard dimensions.
Right-click an element to open the standard context menu. You can edit its properties, focus its size fields, or remove an empty planning element. Active areas, occupied bins, and objects linked to handling units remain protected.
If another user saves the element first, Workspace reloads the current revision instead of overwriting it.
Validate and activate
Select Validate. Workspace checks the hierarchy, parent bounds, geometry, collisions, and constraints on the server. Then select Activate to move areas, storage bins, and constraints from planning into operations together.
Returning to planning is blocked while inventory, active handling units, open movements, replenishment tasks, or count work refer to affected storage bins.
Configure navigation per warehouse
Open the Configuration group in the warehouse details. Select a navigation mode and a grid size in millimetres:
| Mode | Active areas used | Suitable for |
|---|---|---|
| Disabled | none | warehouses without digital route planning |
| Explicit aisle network | aisles | fixed walking or vehicle paths, especially for picking |
| Free space | free storage areas | open halls and flexible floor use |
| Aisle network and free space | aisles and free storage areas | mixed warehouse layouts |
Workspace derives the navigation graph from the active layout for every request. Active blocking constraints remove nodes and connections. A smaller grid represents routes more precisely but creates a larger graph. A fixed node limit rejects graphs that are too large; increase the grid size or divide the traversable areas into smaller business areas in that case.
The read-only route POST /api/v1/pim/warehouses/{warehouseId}/layout/route connects two active storage bins in the same tenant and warehouse. Its response binds waypoints and distance in millimetres to the applied spatialRevision. Use this point-to-point route for general route planning or as one leg of a picking route. Multi-pick sequencing, TSP/VRP optimization, vehicle profiles, traffic rules, and persisted routes are outside this first contract.
Represent physical obstacles as active blocking constraints and place storage bin origins at reachable access points. Otherwise route calculation returns a business error instead of assuming a path through unknown or blocked geometry.
Addressing and previous codes
Under Addressing, define how storage-bin codes are composed from the warehouse, hierarchy, and a sequence. Review the preview before applying new codes. When a bin is renumbered, Workspace keeps its previous code. Scanners continue to accept that code and resolve it to the current storage bin.
The editor does not post inventory or move handling units. Operational movements remain in Inventory workflows.