Update: Fulfillment Outbound API v2020-07-01 adds deliveryOffers and updates getFulfillmentOrder and createFulfillmentOrder
Amazon's Fulfillment Outbound API v2020‑07‑01, launched early 2024, adds a new deliveryOffers operation and expands getFulfillmentOrder and createFulfillmentOrder payloads with a deliveryOffer array and deliveryOfferId field. The endpoint now allows up to 10 calls per second and returns new error codes like DeliveryOfferNotFound.
Overview
Amazon has rolled out a refreshed version of the Fulfillment Outbound API (v2020‑07‑01) that introduces a deliveryOffers operation and modifies the payloads of getFulfillmentOrder and createFulfillmentOrder. Launched in early 2024, the update gives Multi‑Channel Fulfillment (MCF) sellers real‑time visibility into Amazon’s delivery choices for any SKU that can ship to a U.S. ZIP code or be located via a U.S. IP address. Sellers using the API for automated routing must adapt their code to capture the new fields and to process the expanded response structures.
Key Points
- Dynamic deliveryOffers endpoint — Returns live Amazon shipping options such as Same‑Day, One‑Day, and Two‑Day for a given SKU when a destination ZIP or IP is supplied, allowing instant price and ETA calculations.
- Expanded getFulfillmentOrder payload — Includes a deliveryOffer array that enumerates every applicable service, its estimated window, and any fees tied to the specific order.
- createFulfillmentOrder now accepts deliveryOfferId — Enables sellers to request a precise delivery service (e.g., One‑Day) by passing the identifier obtained from the deliveryOffers call.
- Optional field extensions — Elements like shipFromLocationId and fulfillmentPolicy now support extra enumeration values that correspond to the newly exposed delivery choices.
- Higher rate limits — The deliveryOffers operation can be called up to 10 times per second, twice the previous ceiling, to accommodate high‑volume MCF workflows.
- New error codes — Errors such as DeliveryOfferNotFound and InvalidZipOrIp give clearer diagnostics when a request cannot be fulfilled.
How the Updated Outbound API Works
-
Request delivery offers —
- Invoke the deliveryOffers operation with a valid SKU, a destination ZIP (e.g., “30301”) or a U.S. IP address (e.g., “198.51.100.23”), and optionally a quantity.
Analysis & Recommendations
Why This Matters
Sellers can now query real‑time Amazon shipping options (Same‑Day, One‑Day, Two‑Day) for any SKU and select a specific service via deliveryOfferId, improving price accuracy and buyer expectations. The higher 10 req/s rate limit supports high‑volume MCF workflows, while new errors (DeliveryOfferNotFound, InvalidZipOrIp) require updated handling.
Key Takeaways
- deliveryOffers endpoint returns live Amazon shipping options and can be called up to 10 times per second.
- createFulfillmentOrder now accepts a deliveryOfferId to lock in a specific service.
- getFulfillmentOrder response includes a deliveryOffer array with id, service, fee, and estimatedDelivery.
- New error codes DeliveryOfferNotFound and InvalidZipOrIp provide clearer diagnostics.
Recommended Actions
- →Add a pre‑order call to the deliveryOffers endpoint (SP‑API /fulfillment/outbound/2020-07-01/deliveryOffers) in your integration code and store the...
- →Update your createFulfillmentOrder payloads in Seller Central's API console or code to include "deliveryOfferId": "<ID>".
- →Implement handling for DeliveryOfferNotFound and InvalidZipOrIp errors in your order processing flow, falling back to a default shipping method.
Comments
Join the discussion
Log in or create an account to share your thoughts on this update.
No comments yet. Be the first to share your thoughts!