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
  • Request & response
Edit on GitHub
  1. Availability & Promising
  2. Availability & promising in customer journey

Delivery promise

Last updated 1 month ago

Summary

The endpoint supports in the last step of the checkout journey. It can be requested when the customer has already decided on what to buy and is about to make the purchase. At this time point of time the method of delivery (e.g., the click and collect facility or the address of the consumer), the items in the cart, the delivery preferences as well as the consumer address are known. Since all relevant information is known, an order routing can be performed already and a preliminary reservation can be made.

More API information can be found here:

Request & response

When sending a "promise order", a routing decision is performed with the respective and the respective stock is reserved. The response gives information on where fulfillment can be performed, when the fulfillment can be expected to be completed and when the delivery can be completed.

If the consumer decides to buy, the promised order becomes a "normal" order for fulfillment. If the consumer decides against the purchase, the stock reservation is dissolved after a configurable timeframe.

REST API documentation – deliverypromise
DOMS configurations