Shipping commitment days

In the pre-purchase fulfillment scenario, a fulfillment manager might have a specific requirement on how far ahead in days any listed merchandize item can be promised and fulfilled. This requirement becomes critical for time sensitive items, fashion forward items, or seasonal items with a specific duration in which a seller is willing to fulfill. In an alternative use case, a fulfillment manager might not want to promise any inventory that is too far out in the future due to uncertainties from the supply chain.

To consider shipping commitment days, use the maxFutureAvailabilityLookahead attribute to limit the duration of a promise. It is used to ensure that the number of days stay within the value that is configured from the first availability slot. You can configure this attribute at the following two levels:
Tenant
The maxFutureAvailabilityLookahead attribute that is defined at the tenant level serves as a global setting. The tenant settings API accept the maxFutureAvailabilityLookahead attribute. For more information, see Default tenant settings.
Promising Calculation APIs
The maxFutureAvailabilityLookahead attribute can be overridden at the API level. For more information, see the Calculate item delivery or pickup date using finite capacity windows and the Calculate pre-purchase shipment assignments using finite capacity windows optimizing for costs API.

Regardless of the tenant or API level, the system honors the setting for both the delivery date and for intra-node transfer evaluation. A duration limit is provided to limit the future availability that is considered during intra node transfers to fulfill an item. For more information about transfer rules, see Transfer rules.

There are different scenarios to consider when providing a shipping commitment day promise to fulfill an order. For more information, see Scenario: Shipping commitment day promises.