Amazon FBA Inventory Tracker

Out of stock by zone

Zones with zero on-hand for a SKU. Ranked by velocity — biggest revenue hits first.

Zone SKU Sales/day Inbound Days OOS

Less than 7 days cover (with in-transit)

Zone runs out in < 7 days even after counting in-transit stock.

Zone SKU On hand Inbound Days left

Less than 7 days cover (on-hand only)

Days left from current stock alone, ignoring in-transit. Inbound shown so you can see what's coming.

Zone SKU On hand Inbound Days left Days left (with inbound)

Less than 14 days cover (on-hand only)

Broader watch list — days left from current stock alone, ignoring in-transit. Click a row for per-FC dispatch dates.

Zone SKU On hand Inbound Days left Days left (with inbound)

OOS — units reserved / under research

FCs where sellable = 0 but units exist in Reserved or Researching status. Reserved = pending orders + FC transfers + FC processing. Researching = Amazon investigating (lost/found).

Zone SKU Sellable Reserved Researching Inbound Days left (with inbound) Sales/day (7d)

< 7 days cover — units reserved / under research

FCs with < 7 days of sellable cover (on-hand only) where additional units are in Reserved or Researching status.

Zone SKU Sellable Reserved Researching Inbound Days cover Days left (with inbound) Sales/day (7d)

Today's reports

Positions by status

Critical — ship now

Stockout in < 7 days or already out.

Low cover

Stockout in 7–14 days.

Trending up

Sales up ≥ 25% vs prior 30 days.

Trending down

Sales down ≥ 25% vs prior 30 days.

Stalled

No sales in last 30 days but stock on hand.

Overstocked

> 90 days of cover at this FC.

Recent uploads

UploadedFileSnapshot date RowsReplaced

By zone — planning-level, aggregated across FCs in each zone

By fulfillment center — drill-down view

Network-wide (all FCs)

Trending up

30d avg up ≥ 25% vs prior 30d.

Trending down

30d avg down ≥ 25% vs prior 30d.

Unusual spikes

Single-day sales ≥ 2σ above baseline.

SKU trends — entire account — aggregated across every tracked FC

SKU 7d 30d 90d 7d/day 30d/day Trend Best DoW Zero days (30d) Spikes Days since sold

SKU trends by FC — slice by FC to compare

Showing aggregate across all tracked FCs.
SKU 7d 30d 90d 7d/day 30d/day Trend Best DoW Zero days (30d) Spikes Days since sold

Open inbound by SKU

Every SKU that has at least one open shipment in shipments_in_transit. Click a row to see the shipment-level detail. Outstanding = qty_sent − effective received (manual qty_received, or auto-detected from Detailed Ledger Receipts).

SKU On hand Outstanding Total sent Received Shipments FCs First dispatch Last dispatch

Customer Returns

Units returned by customers (CustomerReturns events from the Inventory Ledger Detailed report). Upload a Ledger Detailed CSV via the Upload tab to populate — data also refreshes automatically with each SP-API sync.

All Return Events

Date SKU Product FC Disposition Return Order ID Qty
SKUASIN FCDispositionQty
Forecast uses day-of-week + annual seasonality.
SKU On hand Inbound Avg/day 30d forecast Days cover Send (net) Data (days)

Sync from Amazon (SP-API)

One click pulls the Inventory Ledger (Summary + Detailed) and the FBA inbound shipments straight from Amazon — no Seller Central downloads needed.

Checking SP-API status…

Daily upload workflow

Pull these two reports from Seller Central after 3:00 PM IST every day, then drop both CSVs into the upload box below.

  1. 1. Inventory Ledger — Summary view
    Set Time range to Last 3 days · View = Summary · Download CSV
    Provides per-FC on-hand and daily customer shipments.
  2. 2. Inventory Ledger — Detailed view (recommended)
    Same link, switch View to Detailed · Time range = Last 3 days (or longer)
    Has a Reference ID column on Receipts events that lets the app auto-reconcile shipment receipts: as units land, they're auto-deducted from your in-transit shipments without you updating qty_received.
  3. 3. FBA Inventory (Planning)
    Click Request CSV, wait a minute for the file to build, then Download
  4. 4. (Optional) Shipments-in-transit CSV
    Maintain a small CSV of open inbound shipments to get real per-FC inbound. Required columns:
    shipment_id, date_dispatched, sku, fulfillment_center, qty_sent (optional: qty_received, status)
    Each upload replaces the in-transit table. With the Detailed Ledger above also uploaded, qty_received is auto-detected from Receipts events — you only need to add new shipments and remove fully-closed ones.
  5. 5. Upload all files here
    Select every CSV in the picker — they upload one after the other, and the app auto-detects which is which.
Supported file formats (auto-detected)
  • Inventory Ledger — Summary view — per-FC on-hand + daily customer shipments. Has Ending Warehouse Balance column.
  • Inventory Ledger — Detailed view — per-event transactions with Event Type and Reference ID. Used to auto-reconcile shipment receipts.
  • Inventory by Fulfillment Center — per-FC quantity only.
  • FBA Inventory Planning — per-SKU open inbound (inbound-working, inbound-shipped, inbound-received).
  • Shipments in transit — manual CSV with shipment_id + qty_sent. Gives real per-FC inbound; overrides the SKU-level estimate.

Each upload replaces data for the dates / table it covers (snapshot semantics).

Cleanup — purge stale on-hand rows

If a previous misdetected upload left bad rows in the on-hand table, wipe them by date or SKU here. The next Summary upload will repopulate.

Lists every date currently in the on-hand table with row counts. Rows missing the Customer Shipments column — the most likely sign of a misdetected upload — are flagged.