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
  • Expiry date as special stock property
  • Effects of stock properties on storage
Edit on GitHub
  1. Inventory Management
  2. Stock

Stock properties

PreviousStock availabilityNextStock updates

Last updated 5 months ago

Introduction

Stock Properties allow tracking of specific values on a set of items, a . A common example for properties are values such as expiry date or batch identifiers. Stock properties are represented by a map of key-value pairs.

Often it is useful to limit and enforce which stock properties are tracked for which type of product. For example, it might be required to track the expiry date during goods receipt for certain items. This can be configured in the .

Both keys and values os stock properties must be strings. However, strings can be used as representations of other data types like ISO-Date-Strings.

Expiry date as special stock property

Stock properties allow storing any information to a stock, as key and value can be defined by the user. However, properties with key "expiry" are treated differently in the platform. A property with key "expiry" is treated as the expiry date of the stock. This information is used in the following areas:

  • Calculate the date of the stock which defines until which point in time the stock can be sold.

  • Used in routing and picking to select the best stock for FEFO (first expired first out) strategy

Effects of stock properties on storage

The inventory configurations allow users to define the storage principles of their network or facility. If isMixedStorage is set to false, stock with the same tenant article ID and different stock properties should not be stored on the same location. Users will receive a modal warning them not to mix different properties on the same location when stowing in the inventory app. However, there is no technical constraint forbidding this behavior.

In addition, if isMixedStorage is set to false, storage location recommendations are adapted so that no locations are recommended where the same item with different stockProperties is already stored.

For more information on inventory configurations please click .

stock
here
listing
availableUntil