Amazon Rolls Out External Fulfillment APIs: Unified Inventory, Shipping, and Returns Management Across Channels
On Jan 1 2025 Amazon launched a unified External Fulfillment API suite—Inventory, Shipping and Returns—that lets sellers push location‑specific stock, generate cross‑border labels and query returns with a single credential set and sandbox environments in North America, Europe and Asia.
Overview
On January 1 2025 Amazon launched a new suite of External Fulfillment APIs that bring inventory, shipping and returns under a single integration umbrella. The tools are aimed at sellers who ship orders outside of Amazon’s own fulfillment network and need a streamlined way to coordinate multiple fulfillment programs. Consolidating these functions reduces custom code, limits data mismatches and helps sellers scale across domestic and international markets.
Key Points
- Three‑API bundle — Amazon released Inventory, Shipping and Returns APIs that replace the former patchwork of separate endpoints.
- Location‑specific stock — Sellers can now publish inventory counts for each warehouse or fulfillment center, rather than a single account‑wide figure.
- Single credential model — One set of API keys authenticates calls for FBA, MFN and any third‑party fulfillment program.
- International order support — The Shipping API automatically generates customs paperwork, labels and invoices for cross‑border shipments.
- Sandbox environments — Static test sandboxes are available in North America, Europe and Asia, allowing full end‑to‑end validation before production rollout.
How the External Fulfillment APIs Work
- Inventory API – Push and Pull Location Data — Sellers transmit exact stock levels for each physical site from their ERP or WMS; for example, a retailer can send 120 units of SKU 12345 from a Dallas warehouse and 45 units from a Chicago hub, while also marking 30 units as “reserved” and therefore not sellable. The same endpoint can be queried to retrieve current on‑hand and sellable quantities per location.
- Shipping API – Order Retrieval and Fulfillment Execution — The API returns a list of pending external‑fulfillment orders, including buyer address, shipping method and any pre‑scheduled pickup slots. A seller can then create a shipment record, attach package dimensions, generate a carrier label and upload a customs invoice in a single call. For instance, an order destined for Berlin triggers the creation of a DHL label, a EUR‑valued commercial invoice and the required HS‑code data automatically.
Analysis & Recommendations
Why This Matters
The three new APIs consolidate inventory, shipping and returns into one workflow, preventing oversell by allowing per‑location stock (e.g., 120 units in Dallas, 45 in Chicago). Automatic customs document creation speeds international shipments, and sandbox testing lets sellers validate end‑to‑end flows before going live.
Key Takeaways
- Three APIs (Inventory, Shipping, Returns) were released on Jan 1 2025, replacing separate legacy endpoints.
- Inventory API supports per‑location stock; sellers can publish counts such as 120 units for Dallas (location 001) and 45 for Chicago (location 002).
- Shipping API automatically generates customs paperwork, carrier labels and HS‑code data for cross‑border orders (e.g., DHL label for Berlin).
- A single credential set and the ExternalFulfillmentFullAccess role are required; sandboxes are available in NA, EU and Asia.
Recommended Actions
- →In Seller Central, request the ExternalFulfillmentFullAccess role via Settings > Developer Settings > API Access before implementing.
- →Use the Inventory API’s CreateLocation call to register each warehouse (e.g., location 001 for Dallas) and push separate stock levels per SKU.
- →Run end‑to‑end tests in the North America sandbox: push inventory, retrieve a mock order, generate a label, simulate a return, then migrate the sam...
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!