Choose language · Choisir la langue · اختر اللغة
All guides
FBA inventory reconciliation

Amazon Shows “Inventory Found” but the Unit Is Still Missing — How to Trace the FNSKU

Amazon marked inventory as found but the unit is still unavailable? Trace the FNSKU across Inventory Ledger events, dispositions, transfers, and reimbursement history.

A product barcode being traced between warehouse shelves and a matching inventory record.
Inventory reconciliationIllustration · FluxPilot Field Guide
Quick answer

When Amazon shows Inventory Found but you still cannot see the unit as available, trace every later event for that FNSKU. The unit may be transferring, damaged, reserved, or reconciled elsewhere, so a Found row should not be treated as the end of the investigation.

Why the total alone is misleading

FBA inventory changes through receipts, customer shipments, returns, fulfillment-center transfers, damage, loss, found inventory, removals, disposals, and reimbursements. A snapshot total hides that history.

When a seller says inventory is overstated or understated, the useful next step is to trace the affected FNSKU through the event ledger.

Build a movement timeline

Start with the earliest suspicious date and collect all events for the FNSKU. Sort chronologically, keep the reference ID, and note each quantity change.

Then mark which events are reconciled. A lost unit followed by a found unit is a very different situation from a lost unit that remains unreconciled.

  • Receipts into FBA
  • Customer shipments
  • Customer returns
  • Adjustments for lost, found, or damaged inventory
  • Removals and disposals
  • Reimbursement transactions

Separate inventory accuracy from reimbursement eligibility

Inventory reconciliation answers what happened to the units. Reimbursement review asks whether an unresolved event is eligible for compensation under Amazon's current rules.

Keeping those two questions separate reduces false positives and makes your evidence easier to explain.

Automate the repetitive part

The repetitive work is identifying relevant rows, checking reconciliation fields, calculating age, and grouping evidence by event. That is the part software can do consistently.

Human review still matters for ambiguous events, reimbursement history, sourcing-cost evidence, and final case submission.

Sources and further reading

Workflows and examples are from FluxPilot. Amazon policies change; verify the current policy for your marketplace before filing a claim.

Amazon FBA inventory reimbursement policy