Amazon Inventory Data

This guide explains which Amazon inventory dataset to use for tracking stock, explaining stock changes, and planning replenishment. Each dataset comes from a different Amazon report, so they answer different questions and their numbers aren't always interchangeable.

Decision Flowchart

This diagram acts as a decision tree to identify which inventory tables address your specific needs. Start with your question (e.g. "What's my current stock?" or "Why did inventory change?") and follow the branches to locate datasets for real-time snapshots, historical trends, restock alerts, or logistics planning.

Inventory Datasets

All tables live in either the RAW_INVENTORY or SELLING_PARTNER schema (noted per table below).

Start here: covers most questions

History: snapshot tables vs. tables loaded with history

Inventory tables fall into two groups, depending on what Amazon lets us collect. This matters when you need data from before you connected your account.

For specific needs

Legacy or internal: avoid querying directly

How Tables Connect

The diagram below traces how raw Amazon reports feed into the transformed views available in your database.

Practical Scenarios & Example Queries

Everyday FBA stock questions

"What's my current FBA stock?"

Use SELLER_INVENTORY_FBA_SUMMARIES, your default for FBA stock.

SELECT MARKETPLACE_KEY, SKU, ASIN, AVAILABLE, RESERVED_QUANTITY, INBOUND_QUANTITY, UNFULFILLABLE_QUANTITY, TOTAL_QUANTITY
FROM SELLER_INVENTORY_FBA_SUMMARIES
WHERE TOTAL_QUANTITY > 0
ORDER BY AVAILABLE DESC;

"How has my stock changed day by day?"

SELECT SNAPSHOT_DATE, MARKETPLACE_KEY, AVAILABLE, RESERVED_QUANTITY, INBOUND_QUANTITY
FROM SELLER_INVENTORY_FBA_SUMMARIES_HISTORY
WHERE SKU = 'X'
ORDER BY SNAPSHOT_DATE DESC;

"Does Amazon recommend any action on my stock?"

Use SELLER_INVENTORY_FBA_PLANNING_LATEST for aging and recommendations.

Key columns:

• recommended_action: Amazon's pricing/removal advice
• inv_age_365_plus_days: units aged over 1 year
• estimated_storage_cost_next_month: projected fee exposure

SELECT SNAPSHOT_DATE, ASIN, SKU, RECOMMENDED_ACTION, INV_AGE_365_PLUS_DAYS, ESTIMATED_STORAGE_COST_NEXT_MONTH
FROM SELLER_INVENTORY_FBA_PLANNING
WHERE SKU = 'X'
ORDER BY SNAPSHOT_DATE DESC;

"Which aged SKUs should I remove to avoid storage fees?"

SELECT SKU, INV_AGE_365_PLUS_DAYS, RECOMMENDED_ACTION, ESTIMATED_STORAGE_COST_NEXT_MONTH
FROM SELLER_INVENTORY_FBA_PLANNING_LATEST
WHERE INV_AGE_365_PLUS_DAYS > 0;

"Amazon says restock, but I have inventory. What's going on?"

The likely explanation: what you're counting as "my inventory" is total units, but Amazon's restock alert is based on available, which is sellable stock only. A SKU can have plenty of total inventory while very little of it is actually sellable, if a large share is inbound, reserved, being researched, or unfulfillable.

First, check the breakdown in SELLER_INVENTORY_FBA_SUMMARIES:

SELECT AVAILABLE, RESERVED_CUSTOMER_ORDER, RESERVED_FC_TRANSFER, RESERVED_FC_PROCESSING,
       RESEARCHING_QUANTITY, UNFULFILLABLE_QUANTITY,
       INBOUND_WORKING, INBOUND_SHIPPED, INBOUND_RECEIVING
FROM SELLER_INVENTORY_FBA_SUMMARIES
WHERE SKU = 'YOUR_SKU';

If reserved, researching, or unfulfillable units account for a large chunk of the total, that's inventory that exists but isn't currently sellable, which explains the alert despite what looks like enough stock.

If available genuinely looks sufficient, check weeks_of_cover_t30 in Planning: a low value means Amazon's recommendation is forward-looking. It's forecasting that your current stock won't cover projected demand, not claiming you're already out.

SELECT WEEKS_OF_COVER_T30, DAYS_OF_SUPPLY
FROM SELLER_INVENTORY_FBA_PLANNING_LATEST
WHERE SKU = 'YOUR_SKU';

Cross-check the actual alert in RAW_INVENTORY_RESTOCK_RECOMMENDATIONS.

Everyday FBM questions

"What products are active/inactive, and what's my current price per SKU?"

Use SELLER_INVENTORY_ALL_LISTINGS, your default for FBM/MFN questions.

SELECT SKU, PRICE, STATUS, QUANTITY
FROM SELLER_INVENTORY_ALL_LISTINGS
WHERE SKU = 'X';

Cross-channel questions

"What's my combined FBA + FBM available and total stock for this SKU?"

Use SELLER_INVENTORY. It blends both channels so you don't need to join manually.

SELECT ASIN, SKU, TOTAL_AVAILABLE_QUANTITY, TOTAL_QUANTITY, FBA_LISTING_EXISTS, FBM_LISTING_EXISTS
FROM SELLER_INVENTORY
WHERE SKU = 'X';

"Is this listing only on one channel?"

SELECT ASIN, SKU, FBA_LISTING_EXISTS, FBM_LISTING_EXISTS
FROM SELLER_INVENTORY
WHERE FBA_LISTING_EXISTS = 'No' OR FBM_LISTING_EXISTS = 'No';

When you need more than a stock snapshot

"Which SKUs need urgent restocking?"

Use RAW_INVENTORY_RESTOCK_RECOMMENDATIONS, the report Amazon uses specifically for stock alerts.

SELECT SKU, ALERT, RECOMMENDED_REPLENISHMENT_QTY, RECOMMENDED_SHIP_DATE
FROM RAW_INVENTORY_RESTOCK_RECOMMENDATIONS
WHERE ALERT IN ('low stock', 'no stock');

Two things worth knowing:

• Planning has a parallel signal. recommended_action = 'GoToRestock' with recommended_ship_in_quantity / recommended_ship_in_date can carry similar guidance.
• SKU missing from this report? It likely means Amazon doesn't currently flag it as at-risk. No recent sales, healthy days-of-supply, or no projected demand are the usual reasons.

"Which FNSKU is linked to each ASIN/SKU?"

FNSKU isn't exposed on SELLER_INVENTORY_ALL_LISTINGS or on the unified SELLER_INVENTORY view (see the known gap note on the unified view's page). It is available on SELLER_INVENTORY_FBA_SUMMARIES, which lists every FBA SKU on the account, including SKUs with no stock.

SELECT DISTINCT MARKETPLACE_KEY, ASIN, SKU, FNSKU
FROM SELLER_INVENTORY_FBA_SUMMARIES;

Join on ASIN and SKU (and MARKETPLACE_KEY) to bring FNSKU onto your SELLER_INVENTORY rows.

"Where is my stock physically stored?"

Snapshots report what each marketplace can sell. For stock by location, use the ledger summary, by country or by fulfillment center.

SELECT COUNTRY, SUM(ENDING_WAREHOUSE_BALANCE) AS SELLABLE_UNITS
FROM SELLER_INVENTORY_LEDGER_SUMMARY
WHERE DISPOSITION = 'SELLABLE'
  AND DATE = (SELECT MAX(DATE) FROM SELLER_INVENTORY_LEDGER_SUMMARY)
GROUP BY COUNTRY;

"Why did my inventory drop by 200 units in a specific country/warehouse last week?"

Snapshots give you the current state, not the transaction-level reason for a change. For that, use the ledger detail.

SELECT EVENT_TYPE, QUANTITY, FULFILLMENT_CENTER, DATE
FROM SELLER_INVENTORY_LEDGER_DETAIL
WHERE MSKU = 'X'
  AND COUNTRY = 'US'
  AND DATE BETWEEN '2026-10-01' AND '2026-10-07';

"What's my net inventory change in each warehouse this week?"

Same idea, but you just want the aggregated net change, not every individual transaction.

SELECT FULFILLMENT_CENTER, DATE, STARTING_WAREHOUSE_BALANCE, ENDING_WAREHOUSE_BALANCE
FROM SELLER_INVENTORY_LEDGER_SUMMARY_BY_FC
WHERE DATE BETWEEN '2026-10-01' AND '2026-10-07';

For the same question at country level, query SELLER_INVENTORY_LEDGER_SUMMARY and use COUNTRY instead of FULFILLMENT_CENTER.