General availability of Fulfillment Inbound API v2024-03-20
Amazon promoted the Fulfillment Inbound API v2024-03-20 to general availability at the start of 2024, adding selectable placement services (Standard, Fast‑Track, Consolidated), real‑time delivery‑window calls, a batch SendShipment operation and granular error codes. Sellers can replace legacy CreateInboundShipmentPlan with SendShipment, cutting integration latency by up to 70% for 5,000 SKUs.
Overview
Amazon has promoted the Fulfillment Inbound API version 2024‑03‑20 from a preview release to full production status at the start of 2024. The upgrade introduces selectable inbound placement services, real‑time delivery‑window data, and broader shipment‑management functions. Sellers who send stock to Amazon’s fulfillment centers need to adjust their integrations to take advantage of the new automation options and to cut down on manual coordination.
Key Points
- Multiple placement services — The API now lets sellers request distinct inbound placement types such as “Standard,” “Fast‑Track,” or “Consolidated,” each tied to specific volume thresholds and speed expectations.
- Visible delivery windows — A call to the service returns a roster of open arrival slots for a chosen fulfillment center, enabling sellers to lock a concrete window, for example a 10 am – 12 pm slot at the Louisville DC.
- Editable shipment records — Existing inbound shipments can be fetched, altered, or cancelled through the same endpoint, allowing rapid response when a pallet is delayed or a SKU list changes.
- Batch “Send” operation — The new Send function accepts a bulk shipment‑plan payload, collapsing dozens of individual calls into a single request for large catalogs.
- Granular error codes — Enhanced error reporting distinguishes placement‑service mismatches from delivery‑window conflicts, giving developers clearer signals for automated retries.
How Fulfillment Inbound API v2024‑03‑20 Works
- Request placement options — The seller invokes
GetPlacementOptionswith the target fulfillment‑center identifier; the response enumerates “Standard,” “Fast‑Track,” and “Consolidated” services, each accompanied by constraints such as maximum pallet counts or required lead times. - Reserve a delivery window — Using
ListDeliveryWindows, the seller receives every open slot for the selected center; a subsequentReserveWindowcall can lock a specific interval, for instance the 2 pm – 4 pm window on March 28 for a shipment destined for the Dallas DC.
Analysis & Recommendations
Why This Matters
The new API lets sellers programmatically reserve delivery slots and choose placement types, eliminating manual portal steps and shrinking planning‑to‑dispatch time. Batch SendShipment can handle thousands of SKUs in a single request, reducing call volume and latency up to 70%, which improves inventory readiness and reduces carrier penalties.
Key Takeaways
- GA of Fulfillment Inbound API v2024‑03‑20 introduces three placement services: Standard, Fast‑Track, and Consolidated.
- ListDeliveryWindows and ReserveWindow expose real‑time open slots, e.g., a 10 am‑12 pm window at the Louisville DC.
- Batch SendShipment can replace hundreds of calls; for a 5,000‑SKU catalog latency can drop up to 70%.
- New error taxonomy distinguishes PlacementServiceConflict and WindowConflict for automated retry logic.
Recommended Actions
- →Update your integration to replace legacy CreateInboundShipmentPlan calls with the SendShipment endpoint (see SP‑API docs > Fulfillment Inbound API...
- →Add calls to GetPlacementOptions, ListDeliveryWindows, ReserveWindow and schedule GetShipmentStatus checks every 30 minutes in your backend.
- →Map the new error codes (e.g., PlacementServiceConflict, WindowConflict) to fallback logic and test batch payloads of up to 5,000 SKUs in the SP‑AP...
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!