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
  • Working with external stock change reasons
Edit on GitHub
  1. Inventory Management

External stock change reasons

Last updated 2 months ago

Introduction

External stock change reasons represent user-defined reasons for stock movements within a facility. These reasons can optionally be included in stow line items to explain why a specific action was performed.

The fulfillmenttools platform does not process or react to external stock change reasons. They exist solely for user-defined purposes.

Working with external stock change reasons

External stock change reasons can be handled in one of two ways:

  1. Managed externally

    • Reasons are not preconfigured in the platform.

    • Users can provide custom reasons directly when creating stow line items.

    • Note: Custom reasons provided externally are not validated by the platform.

  2. Managed Within the Platform

    • Reasons are preconfigured via .

    • When creating stow line items, preconfigured reasons are linked by specifying either their id or tenantReasonId.

To preconfigure an external stock change reason, POST an external stock change reason, providing:

  • active: true or false (if set to false, the reason can no longer be linked in stowLineItems)

  • optional customAttributes: can contain information of interest to connectors or services outside of the fulfillmenttools platform. The fulfillmenttools platform does not process or react on .

  • reasonLocalized: Localized reasons, see

  • optional tenantReasonId: External identifier. Can be used, e.g., to map reason codes from ERP systems

external stock change reasons REST API
External stock change reasons REST API
customAttributes
Localization