fulfillmenttools
API documentationIncident ManagementFeedback
Products
Products
  • Products
  • Core
    • Fulfillmenttools and it's surrounding system
    • Facilities
      • Managed facilities
      • Supplier facilities
      • Facility groups
      • Facility discounts
    • User management
    • GDPR
    • External actions
    • Notification center
    • Incident management
    • Tags
    • Stickers
    • Articles
  • Inventory Management
    • Overview inventory modules
    • Listing
    • Article categories
    • Stock
      • Stock availability
      • Stock properties
      • Stock updates
    • Reservations
    • Inbound process
    • Storage location
    • Zone
    • Inventory traits
    • Channel inventory
    • Measurement units
    • Stow jobs
    • External stock change reasons
    • Configurations
  • Availability & Promising
    • Availability & promising in customer journey
      • Earliest possible delivery date
      • Availability in delivery time period
      • Availability for specific delivery date
      • Checkout options
      • Delivery promise
    • Latest picking start
  • Distributed Order Management
    • Order management
    • Order routing
      • Fences
      • Ratings
      • Order split
      • Routing strategy
      • Item bundles
      • Re-route
      • Decision logs
      • Unroutable orders
      • Pre- and backorders
      • DOMS toolkit
  • Order fulfillment
    • Picking
    • Packing
    • Handover
    • Custom services
    • External documents
    • Load units
    • Interfacility transfer
    • Pick job target time
    • Configurations
      • Picking configuration
      • Packing configuration
      • Handover configuration
      • Printing & document configuration
      • Parcel tag configuration
  • Carrier management
    • Carriers and connection to facilities
    • Carrier country service mapping
    • Same day delivery
    • Custom carrier
    • Available carriers
  • Returns Management
    • Introduction to returns
    • Return reasons
  • Use Cases
    • Creating & executing stow jobs
    • Creating orders with interfacility transfers
    • Demand-driven replenishment
    • Expected stock in availability
    • Incoming goods & storage
    • Multi order picking
Powered by GitBook
On this page
  • Introduction
  • Running sequences on storage locations
  • Storage location types
  • Storage location recommendations
  • Working principle
Edit on GitHub
  1. Inventory Management

Storage location

PreviousInbound processNextZone

Last updated 3 months ago

Introduction

A storage location is a physical location where 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 .

  • Storage locations can be assigned , which they in turn inherit to all stocks linked to them.

Please go to the for more information on managing storage locations via .

Running sequences on storage locations

  • 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 location types

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.

Storage location recommendations

Working principle

  1. In both cases, if multiple storage locations are found, the locations with the least amount of combined stock on it are preferred. The idea is to spread stock evenly across storage locations and avoid overloading some locations.

If no storage locations are found via the rules described in (1) or (2), nothing is recommended.

"Keep on zero" for storage location recommendations

The graphic below is supposed to help with common problems while investigating why an expected location is not recommended when stowing.

A recommendation is requested for an existing based on its stock ID. The product (tenantArticleId), (e.g.,. expiry, batch) and current are considered.

Only storage locations which are in the current facility, are and are not the current storage location are considered for further evaluation.

The first priority is a storage location with the same product and the same . This ensures that stocks which are treated the same by other processes are kept together.

Alternatively, if is enabled, storage locations with the same product but different properties are considered.

When using storage location recommendations it can be helpful to set the trait "" on storage locations. When the trait is set, stocks with value 0 are not deleted from the location. As a consequence, systems still know that an item is supposed to be stowed on the location even after stock levels drop to 0.

stock
stock properties
storage location
accessible
properties
keep on zero
stock
zones
traits
facilities REST API
mixed storage
Developer Docs