Availability & promising in customer journey
Last updated
Last updated
The customer journey in the web shop typically involves various steps, from searching for an item on an overview page to completing an order on the checkout page. Each step requires a different level of detail on the "available to promise" (ATP) information. In general, the responses of the ATP calls get more and more specific the further the user proceeds in the checkout journey.
This page gives an overview of the different requests that are recommended for each step in the (checkout) journey.
Please go to the for more information on the respective endpoints.
Request the general availability for a list of products
Stock availability in the network:
Are the requested products in stock?
How much of the requested products is available?
Request the general availability on item and facility level
Stock availability in facilities: Is the selected product available at the desired pick-up location?
Product availability for specific delivery date: How much stock is available for a certain delivery date in specified facilities?
Earliest possible delivery date: What is the earliest possible delivery date for a list of items and what carriers are available considering country and region-specific operating days?
Request the availability for a basket of products & get information on fulfillment options
Delivery dates within time period: Which delivery dates are available for a basket of items, considering country, and region-specific operating days in a specified time period?
Fulfillment options: In which facilities could the order be fulfilled considering stock & fences and what kind of fulfillment options do these facilities offer?
Request fulfillment options in the last step of the journey when all order relevant information is already known
Delivery promise: How and where would the order be fulfilled (pre-reservation can be already made here)?