Promise delivery date

This functionality allows your Order Management System (OMS) to set a specific date as the PROMISE_DELIVERY_DATE that is the date communicated to the customer on when expecting to receive his purchased item. For example, a store assistant can generate a pick list based on a promised delivery date. This is determined by the new First-in First-out (FIFO) rule, which ensures that stock is assigned for orders with the earliest promised delivery date.

This functionality only works for merchants using the sourcing engine in BATCH mode. The sourcing engine ensures that all new orders are sourced by the PROMISE_DELIVERY_DATE. An order with this functionality requires the attribute to have a specified source_location.


To enable this functionality:

  1. Activate the Filter options using already promised inventory option in your System Integrator (SI) Portal in Config > Stock Aggregates > Sourcing.

    Filter Promise Delivery Date

This functionality was previously configured by your SI and can be enabled in your SI Portal, which is not accessible externally yet. Please contact your Customer Success Manager (CSM) or Technical Account Manager (TAM) for assistance.


The magento.sales.order_management.create message already supports the attribute PROMISE_DELIVERY_DATE as a day time.

This functionality applies at the order and the order_line level. For more information about the sourcing engine and OMS waves, see the Sourcing engine page.

Example of an order with the promise_delivery_date functionality

  "sourcing_request": {
    "uuid": "string",
    "mode": "string",
    "order_uuid": "string",
    "order_id": "string",
    "order_creation_date": "datetime",
    "client": "string",
    "store_id": "string",
    "aggregate_id": "string",
    "shipping_method": "string",
    "shipping_address": {
    "lines": [
        "id": "string",
        "line_number": "integer",
        "sku": "string",
        "product_type": "string",
        "parent_line_id": "string",
        "allocation_attempts": "integer",
        "source_id": "string",
        "promise_delivery_date": "datetime",
        "declined_sources": [
        "custom_attributes": [
            "name": "string",
            "value": "string"
        "source_location": "string",
        "pickup_location": "string"
        "daytime": "promise_delivery_date"

The promise delivery date behaves differently depending on the type of order:

  • A promised delivery date on multiple lines (where none is sourced already) becomes the sourcing request taking the earliest date from the lines of this order.
  • A promised delivery date specified at the request level will never be overwritten no matter what is specified at an order_line level.
  • A promised delivery date on a single line (where none is sourced already) will apply the delivery date to the entire sourcing_request.

All backorders that are re-submitted to the SRCRR are added to the batch so that they are sourced together with new created orders. For more information, see the Backorders page.