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
  • Latest picking start calculation
  • General
  • Example
Edit on GitHub
  1. Availability & Promising

Latest picking start

Last updated 4 months ago

Introduction

The latest picking start (LPS) is the point in time at which the picking for the delivery must be started to arrive in time at the customer. If the latest possible picking start for a certain delivery date in a facility is not known, it can be requested via the . Our systems then calculate the latest picking start based on of carriers and the .​

Latest picking start calculation

General

When processing or orders that involve querying , it is necessary to determine the appropriate point in time to request inventory data. As a result, it can be decided if enough stock will be available at the point in time when the order must be picked latest. This ensures that the order is delivered on the customer's desired date. Especially with stock that is perishable, it makes sense to maintain to ensure goods are delivered to customers in optimal freshness.

The calculation for the LPS is performed whenever:

  • using the

  • using the

  • using the when a "desired delivery time" is included and the reservation preference mode is set to "ALAP" (as late as possible)

  • performing a routing with an order where a "desired delivery time" is included and the reservation preference mode is set to "ALAP" (as late as possible)

The latest picking start is calculated per and for potentially possible delivery days. This means that one facility could have multiple latest picking starts. Finally, the LPS with It is the most available requested stock is chosen.

The following information is required for LPS calculation:

  1. The desiredDeliveryTime in the order or in the corresponding checkout options call

  2. The reservationpreference mode "ALAP" (as late as possible)

  3. At least one active carrier

  4. At least one active facility-carrier connection

  5. A defined delivery time (with optionally, additional configuration settings)

If any required data is missing, the LPS cannot be calculated. In such cases, the system either assumes zero stock for subsequent processes (e.g., during order routing) or generates an error (e.g., when calling a checkout option endpoint).

Example

A typical use case is a customer placing an order which should be delivered at a specific day in the future (in the chart below the request is on the 26th Aug. requesting for a delivery on 23th Sept.).

For calculating a LPS, the delivery times per carrier as well as non-delivery days are checked. Afterwards the facility's , , and are examined, checking which can be reached.

checkout options REST API endpoint
checkout option REST API
future availability
"earliest" checkout option REST API endpoint
"timeperiod" checkout options REST API endpoint
checkout options REST API endpoint
facility carrier connection
fulfillment process buffer
fulfillment-times
average fulfillment duration
fulfillment capacities
expiry dates
cut-off times
cutoff-time