Amazon FBA Reserved Inventory: The 3 Real Reasons

Amazon FBA reserved inventory, in Fulfillment by Amazon, means Amazon set a unit aside, and it no longer counts as On-Hand or Unsellable. Seller Central names three reasons: a customer order being fulfilled, staging for fulfillment speed, and FC-processing. The first two need nothing from you, and FC-processing needs you only when Amazon says so.

I asked our agent why a Reserved spike had shown up on a bestselling ASIN the week before a promotion. The Slack message that started it was blunt: "why is 400 units of our best SKU suddenly Reserved, are we about to run out before the promo?" The agent read the reserved breakdown and the Manage FBA Inventory report through the Selling Partner MCP, grounded by Amazon Agent Atlas, and matched every unit to a reason.

A generic support article says reserved status "usually resolves itself." That holds for most reserves and misses the dangerous one: a reserve covering every unit of an ASIN can be a recall, and the 30-day removal window runs from the recall notice, not from when someone notices. The agent reads which bucket applies to this SKU today, and Atlas supplies the path Amazon documents for it, so the operator hears "wait" or "act" instead of the same reassurance.

Reserved has three reasons, and two need nothing from you

Amazon's Reserved Inventory help page names three reasons a unit sits in reserved status:

• Customer order: units reserved to fulfill orders. They clear when the order ships.
• Staging: units Amazon holds temporarily to ensure optimal fulfillment speed. Amazon says no action by you is required.
• FC-processing: units set aside for additional processing, such as verification of item dimensions and weight, pending investigations, or pending removal orders. Amazon notifies you if any action is required.

The agent reads the per-SKU total from afn-reserved-quantity on the Manage FBA Inventory report, then the reason split from the reserved breakdown, and returns a classification rather than a bare number:

{
  "asin": "B0EXAMPLE99",
  "sku": "TOTE-CANVAS-14",
  "reserved_qty": 42,
  "reserved_customerorders": 0,
  "reserved_fc-transfers": 0,
  "reserved_fc-processing": 42,
  "reason": "fc_processing",
  "requires_seller_action": false,
  "note": "FC-processing covers dimension/weight verification, investigations and pending removals; Amazon notifies you if action is needed."
}

Seller Central and the Selling Partner MCP split Reserved differently

Amazon describes Reserved one way in Seller Central's help and another way in the Selling Partner API, which is what the agent reads through the Selling Partner MCP. Both views have three buckets, but not the same three:

So staging can't be read through the API, and FC transfer is a reserved sub-bucket there. In Seller Central, afn-fc-transfer-quantity is its own Manage FBA Inventory column, counted in On-Hand rather than Reserved. Amazon's pages don't say whether the two transfer counts cover the same units, so the agent reports each number with its source instead of adding them together.

Either way, transfer units stay buyable. Amazon says customers can find and buy them, though they might see a future ship date, and transfers typically take 1 to 25 days, longer if delayed by weather or other factors. The Reserved Inventory help page says the same: inventory being shipped to another fulfillment center is still available for purchase.

One more column gets confused with all of these. afn-reserved-future-supply counts units customers already bought through In-Stock Head Start while your inbound shipment is still on its way. The agent reads it and afn-reserved-quantity from the Manage FBA Inventory report, and the transfer count from the reserved breakdown, so none of them collapses into one "held back" bucket.

Reserved is excluded from On-Hand: the formula the agent checks

The Reserved Inventory report's note states the line most sellers reconciling a spreadsheet miss: reserved quantity is not included in On-Hand or Unsellable quantities. The total units for a SKU in a shipment sent to a fulfillment center equal On-Hand + Unsellable + Reserved + Inbound.

Amazon's FBA Inventory overview breaks On-Hand down further, to Available + FC-transfer. A seller who compares On-Hand to the quantity shipped to Amazon comes up short by the Unsellable, Reserved and Inbound amounts, and can read that gap as missing inventory.

The agent can pull the four terms through the Selling Partner MCP and check the identity. A discrepancy the formula can't explain gets flagged as a real problem, instead of being buried under a reconciliation gap that was never a bug.

When Reserved may be a recall, and the 30-day clock that follows

A reserve that covers every unit of one ASIN, not a partial count, can be a recall. Amazon's removal help says that when an ASIN is recalled, all units of that product are reserved and can't be moved. A whole-ASIN reserve can also be an FC-processing hold on a low-quantity SKU, and the column total looks the same either way.

So the agent treats a whole-ASIN reserve as a possible recall and asks you to confirm the recall notice. If it is one, you have 30 days from that notification to create a removal order; miss the window and Amazon disposes of the units. Once you file, the order appears on the Removal Order Detail report, where In Process Qty shows the units for that order still in process.

Reserved is also not the only status that looks like this. A separate Researching status covers units misplaced or damaged at a fulfillment center while Amazon confirms them, and it never exceeds 60 days. Once the units are reimbursed or pass 60 days, the adjustment appears in the Inventory Ledger's detailed view. The claim windows and valuation rules are in Amazon Reimbursement Audit: Check FBA Claims.

What happens next: send only the holds that need you to your queue

Once the agent classifies a Reserved spike, customer-order and transfer reserves clear on their own and get logged, not escalated. Only two cases reach your queue:

• An FC-processing hold that Amazon flagged for action.
• A whole-ASIN reserve that may be a recall, with the notice to confirm.

Amazon Agent Flow lands your Selling Partner inventory data in your own lake on a schedule, next to the Amazon Ads data your Amazon Ads MCP works with. A recall-driven stockout then shows up next to the ad spend still bidding on an ASIN that's about to go unsellable. If your team wants the same check on every run, write it as a Skill your agent follows.

The three-reason split is simple once you have it in front of you. What isn't simple is remembering it the rare time the number is actually a recall.

Next: what a Researching investigation costs you if it never comes back, and how to prove Amazon owes you for it, in Auditing FBA Reimbursements.