Storage Location
Last updated
Last updated
A storage location is a physical location where stock can be located. Since there might be more than one product located on the same location, more than one stock can be connected to a single storage location.
Depending on the facility type, a storage location can represent different concepts, e.g., the showcase area or the supply room in stores, or a compartment on the shelf or a pallet space in warehouses.
Storage locations represent the available storage space in a facility. A given stock can either be generically assigned to a facility, or it can be assigned to a specific storage location by linking the stock to the storage location.
Storage locations can be grouped in zones.
Storage locations can be assigned traits, which they in turn inherit to all stocks linked to them.
Please go to the for more information on managing storage locations via API. The API documentation can be found here.
Storage locations can be ordered in a (running) sequence by defining the previous and next location.
Depending on the sequence type that was defined, the sequence is considered in picking or stowing.
The running sequence defined for a storage location is prioritized over the running sequence that can be set on listing or order line item level.
Storage locations can either have the type "single storage" or the type "bulk storage".
On locations with type "single storage", several items of the same product can be stored, e.g., 100 apples. If a product is already placed on a single-storage location, stowing of a different product on the same location is forbidden.
On locations with type "bulk storage", different products can be stored, e.g., 100 apples and 100 bananas.
A recommendation is requested for an existing stock based on it's stock id. The product (tenantArticleId), properties (i.e. expiry, batch) and current storage location are considered.
Only storage locations which are in the current facility, are ACCESSIBLE and are not the current storage location are considered for further evaluation.
Our first priority would be a storage location with the same article and exactly the same properties. This ensures that stocks which are treated the same by other processes are kept together.
Alternatively, if mixed storage is enabled, storage locations with the same article but different properties are considered.
In both cases, if multiple storage locations are found, we prefer locations with the least amount of combined stock on it. The idea is to spread stock evenly across storage locations and avoid overloading some locations, since we have no way to track the actual capacity and utilization.
If no storage locations are found via the rules described in (1) or (2), we recommend nothing. This does not mean that any storage locations are suitable for this article, there probably are other locations which do not contain the article yet. Since no metric allows us to rank these locations in a sensible matter, we recommend no location and allow the worker oder application to pick from the complete list of valid locations.
The graphic below is supposed to help with common problems while investigating why an expected location is not recommended when stowing.
