How do you resolve Amazon FBA reserved inventory?
Start with the Reserved Inventory report and classify every affected unit as a customer order, staging, or FC processing. Reconcile the same SKU against available, inbound, unsellable, and on-hand quantities before treating the reserve as missing inventory.
Reserved inventory is not automatically a defect. Customer-order reserves can remain while payment is verified, staging supports Amazon's fulfillment placement, and FC processing can cover dimension checks, investigations, or removal work. Escalate only when the status, age, and related transaction no longer explain the unit.
Build an SKU-level reserve ledger
- Record SKU, ASIN, fulfillment center, reserved quantity, reserve reason, first-seen date, last change, and available quantity.
- Capture the related order, transfer, investigation, removal, or measurement event when one exists.
- Reconcile the reserved total with on-hand, unsellable, inbound, and available inventory rather than reviewing one column alone.
- Separate units that are merely unavailable for sale from units that appear financially or physically unaccounted for.
- Save dated report exports so a changing reserve status does not erase the timeline.
Triage each reserve reason
For customer-order reserves, confirm whether the order is pending, cancelled, shipped, or returned. For staging, monitor whether units flow back to available inventory without seller action. For FC processing, check for active dimension reviews, investigations, removal orders, or other account events.
Do not open duplicate cases for the same units. One case should contain the complete SKU timeline, quantities, prior case IDs, and the specific reconciliation gap Amazon needs to explain.
Use an exception checklist before escalation
- The reserved reason is documented and still visible in the latest report.
- The same units are not counted in another inventory state or open order.
- Recent inbound receiving, transfers, removals, returns, and reimbursements have been reconciled.
- The age exceeds the account's normal pattern for that reserve reason.
- Evidence includes dated exports, transaction IDs, shipment IDs, and a calculation of the unexplained quantity.
- The requested outcome is specific: explanation, status correction, inventory adjustment, or reimbursement review.
Know when to wait and when to act
Staging and short-term FC processing may be normal, so status age alone does not prove loss. Customer-order reserves can also remain while payment verification is pending. Marketplace behavior and the underlying event determine the correct waiting period.
Escalate when the related event has closed, quantities do not reconcile, or the reserve no longer changes while no active process explains it. Review Amazon's current [Reserved Inventory report guidance](https://sellercentral.amazon.com/help/hub/reference/external/G201723860) before setting internal thresholds.
Related Amazon seller guides
- [Reconcile FBA inbound shipment discrepancies](https://amazonmargincalculator.cloud/blog/amazon-fba-inbound-discrepancy-check)
- [Build an Amazon reimbursement audit](https://amazonmargincalculator.cloud/blog/amazon-reimbursement-audit)
- [Reconcile Amazon inventory movement](https://amazonmargincalculator.cloud/blog/amazon-inventory-ledger-reconciliation)