Legacy platform

Calculation of first promised date

When an order is created, the first promised date is set by the application that is used to create the order. This can be done by passing the OrderDate element of the order line, with the DateTypeId as YCD_FTC_FIRST_PROMISE_DATE, and the ActualDate, that is, the date when the merchandise will be shipped.

If the first promised date is not passed, the application defaults this date to OrderDate + a fixed number of days that can be configured. When orders are created by using the application, the first promised date is set to the reservation date (see Setting up FTC Complicance for information about configuring delay alerts).

If reservations are not turned on in the application, the same logic that is used to determine the reservation date is used to determine the first promised date. This date is not modified unless it is reset through the UI. If the order is changed in a way such that the ship date is changed, this date can be updated to the new first promised date. This is determined by the application that is used to make the change.

When the first promised date is passed in the input to the createOrder API or changeOrder API, all the dates are reset to reflect the new promised date:

<OrderDates>
<OrderDate ActualDate="20050807"
DateTypeId="YCD_FIRST_PROMISED_DATE"/>
</OrderDates>
Note: If a line has multiple expected shipment dates, the date when the entire quantity will be shipped, is considered. Some quantity can be shipped earlier, but the shipment is completed by this date.