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
  • Summary
  • Use case examples
  • Relocate items between locations
  • Create stock for items that are not registered yet
  • Discard stock
  • Add a reason for changing a stow line item
  • Relocate items between stocks
  • Change the priority of a stow job
  • Relocate items from one to multiple locations
Edit on GitHub
  1. Use Cases

Creating & executing stow jobs

Last updated 2 months ago

Summary

Stow jobs represent the intention or instruction to change the storage location and/or the amount of stock in a facility. While the stow job itself holds general information such as the facility or priority of the job, the stow line item contains information on the items to be moved, their quantity, location, and more. Stow line items cannot exist without a stow job.

More information can be found under .

Use case examples

Relocate items between locations

An admin wants items from a goods receipt to be stowed or items to be relocated.

  1. Create stow job using

    1. set status to OPEN

    2. use takeFrom.type LOCATION and stowTo.Type LOCATION

  2. Job is started by worker. Set status to IN_PROGRESS using .

  3. Items are taken from start location. Set TAKEN information in operative data via . A takenStockRef must be set to in order to define which stock should be reduced.

  4. Items are stowed to target location. Set STOWED information in operative data via .

    1. A stowedStockRef and stowedStorageLocationRef must be sent but can also be null.

    2. If a stowedStockRef is provided, the moved stock is added to the specified stock. If null, a new stock is created.

    3. If a stowedStorageLocationRef is provided, the stock will be created on that location. If null, a stock is created without a reference to any location.

  5. Repeat step "3." & "4." until everything is stowed.

  6. Set status to CLOSED via .

Create stock for items that are not registered yet

An admin wants new stock to be booked to location.

    1. set status to OPEN

    2. use takeFrom.type UNREGISTERED and stowTo.Type LOCATION

  1. If new stock should have properties or traits, it can be defined in the stockInformation of the takeFrom object.

Discard stock

Admin wants stock to be discarded.

    1. set status to OPEN

    2. use takeFrom.type LOCATION and stowTo.Type DISCARD

Add a reason for changing a stow line item

Admin wants stock to be discarded and worker specifies a reason for discarding, e.g., "BROKEN".

    1. set status to OPEN

    2. use takeFrom.type LOCATION and stowTo.Type DISCARD

    1. AstowedStockRefmust be sent but can be null since the stock is deleted after stowing was completed.

    2. The reasons array of the corresponding stow line item can have one or multiple reasons. Each reason must be one of the following:

    3. An object containing tenantReasonId: <tenantReasonId> of an (active) preconfigured external stock change reason.

  1. Follow the steps above.

Relocate items between stocks

Admin wants a specific stock to be relocated. This could, for example, be the case if there are multiple expiry dates for the same item on one location.

    1. set status to OPEN

    2. use takeFrom.type STOCK and stowTo.Type STOCK

If no stowedStockRef is defined, a new stock will be created.

  1. Repeat step "3." & "4." until everything is stowed.

Change the priority of a stow job

Relocate items from one to multiple locations

Admin wants items to be moved from one location to multiple other locations. This could, for example, be the case if items should be stored after a goods receipt was completed.

    1. set status to OPEN

    2. use takeFrom.type LOCATION and stowTo.Type LOCATION

    3. define all target locations along with the respective quantities in the stowTo array

    1. Define the ID of the stowTo object that should be updated.

    2. It is necessary to send the complete stowTo array, even if only one object should be updated.

    3. A stowedStockRef and stowedStorageLocationRef must be sent but can also be null.

    4. If a stowedStockRef is provided, the moved stock is added to the specified stock. If null, a new stock is created.

    5. If a stowedStorageLocationRef is provided, the stock will be created on that location. If null, a stock is created without a reference to any location.

  1. Repeat step "3." & "4." until everything is stowed.

Create stow job using

Job is started by worker. Set status to IN_PROGRESS using .

Items are taken up by the worker. Set TAKEN information in operative data via . A takenStockRef must be sent but can be null since a new stock will be created based on data in taken.takenQuantity and takeFrom.stockInformation.

Follow steps "4." to "6." from .

Create stow job using

Job is started by worker. Set status to IN_PROGRESS using .

Items are taken from start location. Set TAKEN information in operative data via . A takenStockRef must be set to in order to define which stock should be reduced.

Items are discarded. Set STOWED information in operative data via . AstowedStockRefmust be sent but can be null since the stock is deleted after stowing was completed.

Set status to CLOSED via .

Create stow job using

Job is started by worker. Set status to IN_PROGRESS using .

Items are taken from start location. Set TAKEN information in operative data via . A takenStockRef must be set to in order to define which stock should be reduced.

Items are discarded and worker defined reason for discarding stock. Set STOWED information in operative data via .

An object containing id: <id> of a preconfigured (active) .

An object containing reasonLocalized: <LocalizedString>. See for the format of LocalizedString. For this option, the reason does not need to be preconfigured. The object can optionally contain a tenantReasonId, if there is no preconfigured with that Id.

Set status to CLOSED via .

Create stow job using

Job is started by worker. Set status to IN_PROGRESS using .

Items are taken. Set TAKEN information in operative data via . A takenStockRef must be set to in order to define which stock should be reduced.

Items are stowed. Set STOWED information in operative data via . AstowedStockRefmust be sent but can also be null.

Set status to CLOSED via .

The priority can be defined on stowJob level. Any value can be set meaning users can define their own logic. Priority can be set using .

Create stow job using

Job is started by worker. Set status to IN_PROGRESS using .

Items are taken from start location. Set TAKEN information in operative data via . A takenStockRef must be set to in order to define which stock should be reduced.

Items are stowed to target location. Set STOWED information in operative data via .

Set status to CLOSED via .

Products – Stow Jobs
POST /api/stowjobs
StartStowJobAction
ModifyStowLineItems action
ModifyStowLineItems action
CloseStowJobAction
POST /api/stowjobs
StartStowJobAction
ModifyStowLineItems action
POST /api/stowjobs
StartStowJobAction
ModifyStowLineItems action
ModifyStowLineItems action
CloseStowJobAction
POST /api/stowjobs
StartStowJobAction
ModifyStowLineItems action
ModifyStowLineItems action
external stock change reason
CloseStowJobAction
POST /api/stowjobs
StartStowJobAction
ModifyStowLineItems action
ModifyStowLineItems action
CloseStowJobAction
PATCH /api/stowjobs/{stowJobId}
POST /api/stowjobs
StartStowJobAction
ModifyStowLineItems action
ModifyStowLineItems action
CloseStowJobAction
above
external stock change reason
Localization