Update: Enhancements to the Amazon Warehousing and Distribution API
Amazon’s Warehousing & Distribution API was refreshed this month, adding a numeric totalInboundQuantity field to listInventory, a transitStatus attribute, and expanding batch size to 1,000 SKUs per call while raising rate limits by 20 %. These changes let sellers see in‑transit stock and automate variance detection.
Overview
Amazon has rolled out a refreshed version of its Warehousing and Distribution (W&D) API, going live this month. The upgrade introduces additional data elements and new workflow options that let sellers track inbound shipments with finer granularity and confirm exactly what arrives at Amazon fulfillment centers. Sellers who depend on the API for inventory planning, shipment reconciliation, and stock‑on‑hand reporting need to adjust their integrations to capture the new fields.
Key Points
- totalInboundQuantity field — The
listInventoryendpoint now returns a numerictotalInboundQuantitythat sums every unit currently on its way to a W&D location for each SKU, enabling a single‑call view of in‑transit stock. - SKU‑level reconciliation — By exposing both
expectedQuantity(what the seller shipped) andreceivedQuantity(what Amazon records), the API allows automatic per‑SKU variance calculations without manual spreadsheet cross‑checks. - Real‑time transit visibility — A new
transitStatusattribute reports whether inventory is “in‑transit,” “arrived,” or “delayed,” giving sellers an up‑to‑the‑minute signal of inbound movement. - Enhanced error reporting — When a shipment deviates from expectations, the response includes an
errorCodeand a readableerrorMessagethat identify issues such as labeling mismatches or carrier exceptions. - Batch processing support — Calls to
listInventorycan now request up to 1,000 SKUs in a single request, dramatically cutting the number of HTTP calls required for large catalogs. - Rate‑limit adjustments — Authenticated sellers receive a 20 % increase in throttling limits, allowing more frequent inventory checks during peak periods without hitting caps.
How the Updated API Works
- Initiate listInventory request — The seller issues a
GET /wds/v1/inventorycall, optionally filtering by SKU, warehouse ID, or date range; the response now bundles , , and detailed for each line item.
Analysis & Recommendations
Why This Matters
The totalInboundQuantity gives a single‑call view of units in transit, preventing stock‑outs, while transitStatus enables real‑time stock availability updates. The 20 % higher throttling and 1,000‑SKU batch reduce API calls, crucial during peak seasons.
Key Takeaways
- listInventory now returns totalInboundQuantity, expectedQuantity, receivedQuantity and transitStatus per SKU.
- Batch requests can include up to 1,000 SKUs, cutting HTTP calls for large catalogs.
- Authenticated sellers receive a 20 % increase in rate‑limit throttling.
- Error responses now contain errorCode and errorMessage for issues like LABEL_MISMATCH.
Recommended Actions
- →Update your API wrapper to parse totalInboundQuantity, transitStatus, expectedQuantity and receivedQuantity from GET /wds/v1/inventory responses.
- →Modify inventory sync jobs (e.g., in Seller Central or your ERP) to add inbound totals to safety‑stock calculations and trigger alerts when varianc...
- →Adjust your request logic to request up to 1,000 SKUs per call and handle nextToken pagination in the integration.
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!