Important Updates for Amazon FBA Inventory In SP-API
Amazon is deprecating six FBA inventory report endpoints at the end of January - here's what's changing, what the new ledger reports are missing, and how to adapt.
Amazon is discontinuing multiple seller inventory reports at the end of January across both the Seller Central console and SP-API platforms. If your operations or reporting tools rely on any of the affected endpoints, you need to act now.
Deprecated Endpoints
The following six SP-API inventory report endpoints are being phased out:
GET_FBA_FULFILLMENT_CURRENT_INVENTORY_DATAGET_FBA_FULFILLMENT_MONTHLY_INVENTORY_DATAGET_FBA_FULFILLMENT_INVENTORY_ADJUSTMENTS_DATAGET_FBA_RECONCILIATION_REPORT_DATAGET_FBA_FULFILLMENT_INVENTORY_SUMMARY_DATAGET_FBA_FULFILLMENT_INVENTORY_RECEIPTS_DATA
Replacement Reports
Amazon is consolidating these into two new ledger-based reports:
GET_LEDGER_SUMMARY_VIEW_DATAGET_LEDGER_DETAIL_VIEW_DATA
The Problem with the New Reports
The new Ledger reports leave out some critical pieces of information. Most importantly, they lack inventory status breakdowns - fulfillable, reserved, inbound, researching, and other categories that show what inventory is actually available for sale versus simply present in FBA centers.
This distinction matters enormously for inventory management decisions. Knowing total units in an FBA center is very different from knowing how many of those units are actually fulfillable. The gap between those two numbers drives reorder timing, stockout prevention, and operational planning.
MixShift's Solution
To address these gaps, MixShift combines multiple data sources to provide comprehensive FBA inventory tracking. This includes FBM SKU quantities and out-of-stock detection logic, enabling better inventory management decisions during weekly reviews and reordering assessments.
If you have questions about how to adapt your inventory reporting to the new ledger-based system, reach out to the MixShift team.