Earliest possible delivery date
Last updated
Last updated
This endpoint provides the earliest possible delivery date for an item or a list of items. This information can be used on a search result or product overview page to inform the shop user about the earliest delivery date that can be expected for a specific item.
Limitations & mandatory configurations
The maximum amount of days that are checked is limited to 45 days
Since the endpoint checks for delivery days, it is mandatory to have transit times configured per carrier.
When defined for the tenant, , of the facilities, and are included in the calculation.
earliestDeliveryDate: Set to "now" by default, meaning the customer is interested in an ASAP delivery. If a different future date is specified, available delivery dates will be checked starting from that point in time (i.e., the user does not want to receive their order before a given date).
tenantArticleIds: The earliest delivery date can be calculated for a single item or a list of items. If a list of items is requested, the calculation is done for each item individually (not as a basket).
consumerAddress:The request must include at least the consumer's country. This is important because are taken into account when calculating the earliest delivery date, and these vary by country and region. It is also possible to provide a postal code in the request (e.g., for logged-in shop users). Doing so allows considering region-specific non-delivery days.
filter: Since the request does not check for fences it is possible to include filters referring to . If the request contains a filter with a custom attribute only those facilities are checked which also have the matching custom attribute attached to the facility entity.
The response contains a list of the requested items with:
earliestPredictedDeliveryDate: Earliest point in time when the user can expect this particular item to be delivered in case the order would be placed at this moment.
availableCarrier:
name: Name of the carrier (key) like "DHL"
nonDeliveryDays: regions where this particular date is a non delivery date of the corresponding carrier (e.g., DE-NW: DHL does not deliver on March 3rd 2025 in North Rhine Westphalia due to carnival)
that were announced via are also considered in the response. Only purchase orders with requestedDate.type "ASAP" are not considered as these deliveries are expected to arrive as soon as possible and there is no exact date that can be used to check the potential availability of these stocks for incoming orders.