Four new reports cover Amazon Warehousing and Distribution, so bulk stock held in AWD, the shipments sent into it and the replenishment orders drawing it down are now reportable alongside your FBA and Seller Central data.

Amazon Warehousing and Distribution (AWD) is Amazon's bulk storage tier: you send inventory there in cases, it sits outside FBA, and it is drawn down into FBA as replenishment orders. Until now none of it appeared in your reporting — inventory and shipment reports covered FBA only. Four new reports close that gap.

The four reports

• AWD Inventory — one row per seller SKU: units on hand in AWD distribution centers, units inbound from you, and units available, reserved or already in transit to FBA. A current snapshot rather than a history.
• AWD Inbound Shipments — one row per shipment you send into AWD, with status, carrier, tracking, lifecycle timestamps, origin and destination, and the quantity declared for each SKU against the quantity AWD actually received. This is the report that shows you a shortfall between what you shipped and what arrived.
• AWD Outbound Orders — one row per order moving stock out of AWD, with the products and packages requested, those AWD deemed eligible, those actually shipped, and the execution errors explaining any shortfall.
• AWD Replenishment Orders — the FBA replenishment requests raised against AWD stock, with the SKUs requested, eligible and shipped, the reasons any SKU could not be distributed, and the outbound shipments created for the order. Replenishment orders are a subset of outbound orders; this is the report that identifies them as such.

Amazon offers the AWD API in the United States only

Every AWD operation is documented for the Amazon US store, and Amazon has not opened the API in other regions yet. The AWD programme itself launched in five European markets in August 2026, but that does not extend to the API, so a European seller cannot be reported on through these reports today. Canada and Mexico are not covered either.

Because of this, each report runs only for the US marketplace on a connection. A connection covering several marketplaces will produce AWD rows for the US one and skip the others, which keeps a run successful rather than failing it and avoids writing the same AWD stock once per marketplace.

How the data is shaped

Each report has one row per entity — per SKU, per shipment, per order — and no date column. A row is rewritten in place when the record changes, matched on its own identifier, so an overlapping run updates records rather than duplicating them, and a record Amazon later drops from its listings keeps the row you already have.

Where Amazon returns a nested list, the list is kept intact as a JSON column rather than expanded into extra rows. The per-SKU quantities on a shipment are one such column, as are the products and packages on an order. This is deliberate: a shipment can carry dozens of SKUs, and flattening those into rows would repeat the shipment-level quantities once per SKU and inflate any total taken over the table. Parse the column downstream if you want a row per SKU.

One unit difference is worth knowing before you compare the reports to each other: inbound shipment quantities are counted in cases, while inventory quantities are counted in units. Each quantity carries its unit of measurement alongside it in the JSON.

Address fields are available but off by default

The origin and destination of an inbound shipment include a facility name, street address lines and a contact phone number. These are marked sensitive and are not selected by default; the city, state or region, postal code, county, district and country code are on. Select the sensitive fields explicitly if you need them.