Availability & promising in customer journey

Introduction

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 Developer Docs for more information on the respective endpoints.

Product overview

Request the current availability for a list of products

  • Stock availability in the network (stocks summaries REST API):

    • Are the requested products in stock?

    • How much of the requested products is available?

Product detail page

Request the general availability on item and facility level

Shopping cart

Request the availability for a basket of products & get information on fulfillment options

  • Delivery dates within time period (checkout options time period REST API): Which delivery dates are available for a basket of items, considering country, and region-specific operating days in a specified time period? More information

  • Fulfillment options (checkout options REST API): In which facilities can the order be fulfilled considering stock availability & fences and what kind of fulfillment options do these facilities offer? What is the estimated delivery time and the respective latest possible acceptance time for the order? More information

Checkout

Request fulfillment options in the last step of the journey when all order relevant information is already known

  • Delivery promise (delivery promise REST API): How and where would the order be fulfilled if placed now (pre-reservation can be already made here)? What is the estimated delivery time and the respective latest possible acceptance time for the order? More information

Last updated