Overview

Amazon has rolled out a new, all‑in‑one FBA inventory report that consolidates data previously scattered across several legacy files. Effective immediately, the report refreshes daily and presents the full lifecycle of inventory—from inbound shipments to final ending balances. Sellers who rely on accurate stock visibility should adopt the new format to avoid gaps when the older reports are retired.

Key Points

• One report replaces five — The new file merges the functions of at least five separate FBA inventory reports, removing the need to cross‑check multiple downloads.
• Complete lifecycle coverage — It records every transaction type, including receipts, sales, returns, adjustments, reconciliations, removals, and the daily ending balance.
• Daily refresh cycle — Data is updated each night, giving sellers a near‑real‑time snapshot of inventory across all Amazon fulfillment centers.
• Legacy report phase‑out — The older reports will be deactivated on a announced schedule, forcing users to migrate any automated pulls or spreadsheet models.
• Broad applicability — Large catalog owners and high‑volume merchants stand to save several hours per week that were previously spent stitching together disparate reports.

How the Unified FBA Inventory Report Works

1. Starting Balance Capture — The report opens with the inventory count carried over from the previous day; for example, a seller with 2,400 units of a bestseller will see that figure as the baseline for the new reporting period.
2. Inbound Shipment Tracking — Each receipt at an Amazon fulfillment center is logged, showing quantity and date; a shipment of 500 units arriving on March 10 will appear as a “Received” line with the corresponding fulfillment node.
3. Order Fulfillment Logging — All customer orders shipped from Amazon’s network are recorded, allowing sellers to calculate sell‑through; if 120 units of the same bestseller were sold on March 11, the report will deduct those from the balance.
4. — Returns, damaged‑goods adjustments, and reconciliation events are grouped together; a returned pair that is deemed sellable adds back one unit, while a damaged unit is marked as unfulfillable, both reflected in the same row set.