githubEdit

Delivery promise

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.

circle-info

More API information can be found here: REST API documentation – delivery promisearrow-up-right

Request and response

When sending a promise order, a routing decision is performed with the respective DOMS configurations 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.

Create promise order

post
Authorizations
AuthorizationstringRequired
Bearer authentication header of the form Bearer <token>.
Body

PromiseRequest

customAttributesobjectOptional

Attributes that can be added to the order. These attributes cannot be used within fulfillment processes, but it could be useful to have the informations carried here.

orderDatestring · date-timeRequired

The date this order was created at the supplying system.

Example: 2020-02-03T08:45:50.525Z
statusstring · enumOptional

The state of the order. Initially it is OPEN.

Possible values:
tenantOrderIdstringOptional

Field can be used as a reference number in foreign systems, for example as a reference to the source system's identifier for this order.

Example: R456728546
Responses
post
/api/promises/deliverypromise

Last updated