We are extending the meets_delivery_promise to orders on non-Amazon channels. Rates for these orders will now be assessed against the order’s due date.
This affects two endpoints:
- Rate Shopping API - applies when
due_dateis supplied in the request - Allocation Rates - applies when the order has a due date set in Veeqo
Two aspects of the response change:
meets_delivery_promisewill be returned astrueorfalseon each rate, indicating whether its estimated delivery date meets the due date. It is currently alwaysnullfor non-Amazon orders.- Rates will be returned sorted by those meeting the promise first, then by price. Rates for non-Amazon orders are not currently sorted.
Where no due date is available, behaviour is unchanged: meets_delivery_promise remains null and the rate order is unaffected.
Please review the following in your integration:
- Any logic that selects a rate by its position in the array. The first rate returned will be the cheapest that meets the due date, which is not necessarily the cheapest overall.
- Any logic that assumes
meets_delivery_promiseis alwaysnulloutside of Amazon orders.
If you select rates by evaluating the returned fields rather than by position, no change is required.
This change will start to be rolled out gradually beginning Monday 19th, so both behaviours may be observed during the transition period. Please ensure your integration handles either rather than switching behaviour on a fixed date.
If you are unsure whether this affects your integration, reply to this thread or reach out to Veeqo Support via the Support Messenger in the app or at helpme@support.veeqo.com.