fulfillmenttools
API documentationIncident ManagementFeedback
Products
Products
  • Products
  • Core
    • Fulfillmenttools and it's surrounding system
    • Facilities
      • Managed facilities
      • Supplier facilities
      • Facility groups
    • 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
  • Unmixed storage configuration
  • Outbound stock configuration
  • Short-pick configuration
Edit on GitHub
  1. Inventory Management

Configurations

Last updated 4 months ago

Introduction

Configurations in inventory management define storage principles and how to deal with special cases in inventory handling.

Configuration
Path
Description

Unmixed Storage

/api/configurations/inventory /api/facilities/{facilityId}/configurations/inventory

Outbound Stock Configuration

/api/facilities/{facilityId}/configurations/inventory

Defines if stock is booked to an outbound location after picking.

Short-pick

/api/facilities/{facilityId}/configurations/stock

Unmixed storage configuration

Storage principles for stock properties (such as expiration date) can be defined for each facility. The principle “unmixed storage” means that the same item with different properties (e.g., expiry date) must not be stored on the same storage location.

Enabling unmixed storage has the following effects:

  • If a user tries to stow the same items with different properties on the same storage location, a user prompt is shown in the .

  • For only locations are shown where the unmixed storage principle is met.

The unmixed storage configuration should be disabled if stock properties are not relevant while stowing or relocating items.

The configuration "isMixed" must be set to false to enable unmixed storage in the facility.

Activating config on network level with the .

Activating config on facility level with the .

Outbound stock configuration

Inventory levels can be tracked until items physically leave the facility and are handed over to another legal entity (e.g., customer or shipping provider).

The configurations for tracking outbound stock are defined for each facility individually.

Enabling the outbound stock configurationis has the following effects:

  • After a pick job was completed, the following actions take place:

    • stocks are reduced on the original location

    • new stock is created on the defined outbound location

    • the reservation is lifted off of the original stock and placed on the newly created stock

  • After the stock left the facility, all related stocks and reservations are deleted.

Short-pick configuration

A short-pick describes the case when an order could not be completely picked. This can happen when some ordered items were too low in stock or out-of-stock. By enabling the config, stock for an item in a facility is set to the picked amount. If nothing could be picked the stock is set to 0.

Example for the platform behavior:

Short-pick Setting

Current stock

Ordered Quantity

Picked Quantity

New Stock

ENABLED

10

5

3

0

DISABLED

10

5

3

7

Defines if stock with different (e.g., expiry date) is allowed to be stored on the same location.

Sets stock to zero for storage locations where a occurred.

Outbound inventory describes stock that has already been picked for an order and has been physically separated from other stocks. It is placed on an outbound location until being handed over to another party and finally, leaving the warehouse. The outbound location along with its items is displayed in the . The outbound storage locations can also be a virtual location and represent a set of different outbound locations in the facility.

Stock on the outbound location is still included in stock levels communicated via FACILITY_STOCK_CHANGED (however, not as ). Thus, external systems still receive accurate stock levels for items physically present in the facility.

Activate outbound stock tracking with the .

It is strongly advised to simultaneously activate theconfirmationOnShortPick in the . Otherwise systems cannot differentiate between cases where the user tried to pick an item and failed due to no available stock or cases where the pick job was re-routed before the user even tried to pick all ordered items.

Activate the config on facility level with the .

inventory configuration facility REST API
facility configuration stock REST API
available
events
properties
Stocks REST API documentation
inventory configuration REST API
inventory configuration facility REST API
storage location recommendations
short-pick
inventory app
storage location overview
picking configuration