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
  • Available traits
  • Interacting with traits
  • Locking storage locations or stocks
  • Traits in order routing and fulfillment
Edit on GitHub
  1. Inventory Management

Inventory traits

PreviousZoneNextChannel inventory

Last updated 4 months ago

Introduction

Traits provide information on how and are to be handled in operational and order processes. Traits can be set both on storage locations and stocks. If set on storage locations, they affect the handling of both storage locations and the located on them. Each stock placed on a location (by assigning it a locationRef) will inherit the traits of its storage location if nothing is specified in the stock's traitConfig.

Traits can, for example, be used to mark a location and its stock as pickable or to along with their stock. When only using stocks (and no locations) traits can be used to mark stock as pickable or lock it.

Available traits

By default, each storage location has the traits PICKABLE and ACCESSIBLE, unless otherwise specified.

Trait
Default
Description

PICKABLE

Stock on these locations can be picked for fulfilling orders. Only stock marked as PICKABLE can be considered for incoming orders.

ACCESSIBLE

The ACCESSIBLE trait indicates that stock can be removed from and new stock can be put on this location. Removing the ACCESSIBLE trait from a location locks it for picking and triggers a notification during stowing processes. Only stock marked as ACCESSIBLE can be considered for incoming orders.

KEEP_ON_ZERO

OUTBOUND

IN_MOTION

Interacting with traits

Each trait has a default value. When nothing else is specified, the enabled traits are processed on both the storage location itself and the stocks on it. The default value (whether it is enabled or not) can be overwritten individually for each trait by setting it in the traitsConfig field on the storage location or on the stock. Traits set on stocks overwrite the traits set on storage locations. All unspecified traits keep their defaults. This means that if a trait is enabled via the trait config, PICKABLE and ACCESSIBLE are set by default unless explicitly set to false.

The traitConfig should be used to write to traits. Do NOT use the trait array for that purpose.

The traitConfig can specify each trait as enabled, disabled or unset. The final trait config is determined in a cascading manner:

Trait
Default
StorageLocation
Stock
Final Config

ACCESSIBLE

true

false

true

true

PICKABLE

true

true

false

false

KEEP_ON_ZERO

true

true

Locking storage locations or stocks

To unlock the storage location, the ACCESSIBLE trait must be set (again).

Traits in order routing and fulfillment

The following storage locations and stocks are ignored in order routing and fulfillment:

  • with an empty array of traits

  • with only the trait PICKABLE

  • with only the trait ACCESSIBLE

Normally stocks are deleted when they reach 0 through operations like picking or stock movements. To change this behaviour, add the KEEP_ON_ZERO trait to the location. See .

The OUTBOUND trait marks storage locations for items that have already been picked and are ready for being handed over to a shipping provider. When configured in the , stocks and reservations are automatically booked to the defined outbound location after picking has been completed.

The IN_MOTION trait marks stock that is currently being moved as part of a stow job. This stock should be filtered out during a stock update via the .

To lock a storage location including the items placed on it, the ACCESSIBLE trait must be removed. As a consequence, the items on the location are not considered for incoming orders (i.e. picking). It is still possible to remove items from the location or put new items on it. Additionally, users are notified about the locked status when moving items from the location via or . Similarly, stocks can be locked by removing the ACCESSIBLE trait from them.

Storage locations and stock with the traits PICKABLE and ACCESSIBLEOR with no traits are considered for fences and ratings during and calculating .

order routing
stock availability
storage locations
stock
s
stock
lock locations
stocks REST API endpoints
outbound inventory tracking
stock entities with amount 0
App
Backoffice