FBA Inventory Stuck in FC Processing but Ledger Says Sellable? 9 Checks Before You Claim a Loss

Why 86 units can be reserved while your ledger says 'sellable'

A recent seller-forum question described dozens of units held under Reserved – FC Processing for weeks while the Inventory Ledger still contained SELLABLE entries. The thread had no replies when it was found for this research. The article answers the diagnostic question, not the specific seller's account because private warehouse data is not public.

Amazon's official FBA Inventory API distinguishes Fulfillable, Reserved, Unfulfillable and Researching quantities. Reserved can mean inventory engaged in fulfillment or internal processing; it is not the same field as Fulfillable. A SELLABLE disposition on a historical ledger event does not guarantee that the same units are ready for customer orders today.

Therefore compare quantities at a common timestamp before calculating losses. A marketplace view, an FC-specific row and an older report period can produce apparently contradictory totals that refer to different inventory states.

• Amazon official FBA Inventory API terminology
• Inventory Ledger Summary vs Detailed View

The nine checks in a practical order

Perform the checks in order and write down the evidence you used. Jumping directly from 'not available' to 'Amazon lost stock' skips several explanations that could change the next action.

If the quantity is large or the hold has been unusually long, preserve the first date on which the issue appeared. Document business impact separately from inventory state; sales interruption is not itself an entitlement to a warehouse-loss reimbursement.

• 1. Confirm seller account, marketplace, SKU, FNSKU and ASIN refer to the same product.
• 2. Capture Available, Reserved, FC Processing, FC Transfer and Customer Orders quantities at the same time.
• 3. Check whether the offer is suppressed, stranded, blocked by compliance or restricted by account status.
• 4. Check transfers or other documented processing movements without assuming every FC Processing unit is a transfer.
• 5. Export Inventory Ledger Detailed for the period covering the last sellable date through today.
• 6. Filter to the exact product and inspect event type, date, reference and quantity, keeping original values.
• 7. Search for later loss, damage, found, adjustment, shipment or disposal movements that could explain a status change.
• 8. Review existing Seller Central cases and messages; identify the unanswered question, not just how long it has been open.
• 9. Request the current processing reason, recorded FC location or relevant status explanation, and the supported next action.

Worked example: ledger 84 sellable versus 86 reserved

Imagine a fictional seller sees 86 units Reserved – FC Processing and a ledger filtered to one period that totals 84 SELLABLE movements. Those numbers are not automatically inconsistent: the ledger might omit opening balance, show a different date range or include a mix of event categories. The seller must reconcile scope and the stock accounting equation before inferring a two-unit loss.

Create a snapshot showing period start balance, each movement, available quantity, reserved subcategories and the timestamp. If you cannot reconcile the difference, mark it 'status discrepancy requiring FC explanation' rather than claiming 86 lost units.

If Amazon later reports a physical loss, then the event may have to be investigated through the relevant lost/damaged category. Until then, the primary issue is availability and status reconciliation, not yet a proven missing-inventory claim.

Write a Seller Support case that asks for one answerable status explanation

Open the existing relevant case or an appropriate inventory support path and explain the exact mismatch in brief factual language. Avoid allegations of deliberate wrongdoing that you cannot document; lead with reproducible report references.

Suggested summary: 'For [FNSKU], as of [UTC date/time], Available = [number] and Reserved – FC Processing = [number]. The attached ledger export for [dates] shows [specific last event/reference]. We cannot identify a movement that explains this hold. Please confirm the current inventory status, the reason for the processing hold, the responsible team and the next action or expected status checkpoint.'

Attach the filtered ledger rows, reserved inventory snapshot and earlier case reference. If the reply only restates a generic transfer definition, ask which specific movement or status applies to this product. Do not demand internal records that the support channel has not established it can provide.

When to review for reimbursement versus release of inventory

There are two different requests. A release request asks why a unit is held and whether it can become available. A reimbursement review asks whether an eligible event caused a covered loss or damage after policy conditions are checked. They require different proof and may involve different support workflows.

If a seller has only reserved-status evidence and no qualifying lost/damaged event, the safe status is 'availability issue awaiting clarification.' If Seller Central later records loss or damage, establish the event date and marketplace-specific claim deadline; verify whether other inventory resolutions or payments already covered it.

FluxPilot's current Inventory Ledger workflow can help analyze supported loss/damage rows and optional reimbursement data. It does not release FC Processing holds, see Amazon's internal processing queue or automatically file Amazon claims.

• Current US claim-window breakdown
• Try a focused report-based FluxPilot review