Amazon Seller Central Reserved Quantity Breakdown (FC Transfer, FC Processing, Customer Order)
Amazon's Reserved figure isn't one field in Power My Analytics: it's split across three different reports (Inventory (FBA), Restock Inventory (FBA), and Manage Excess Inventory (FBA)), each with its own version of FC Transfer, FC Processing, and Customer Order. This article maps out where each one lives, and walks through the checks to run first if any of them read zero or lower than you expect.
Where the Reserved Quantity Breakdown Lives
| Report | PMA Field(s) | Notes |
| Inventory (FBA) | Afn Fc Transfer Quantity | Sits alongside the documented Reserved Qty. FC Processing and Customer Order aren't broken out in this table. |
| Restock Inventory (FBA) | Customer Order, Fc Processing, Fc Transfer | A separate report, alongside Available, Inbound, Receiving, Working, Shipped, and Unfulfillable. |
| Manage Excess Inventory (FBA) | Reserved - Customer Orders, Reserved - FC Processing, Reserved - FC Transfer, Reserved Staging, Total Reserved Quantity | The fullest breakdown. The first four sum to Total Reserved Quantity. |
All of these follow the same rule as the rest of PMA's Amazon inventory tables: they hold lifetime, point-in-time values and can't be broken down by date.
Why a Reserved Field May Read Zero
If FC Transfer, FC Processing, or Customer Order is reading zero (or lower than Amazon's own report shows) in a Data Studio report, Google Sheet, or Excel file, work through these in order:
- Inventory paired with a date dimension. All inventory reports are lifetime values and can't be broken down by date. Pairing an inventory field with a date dimension is the single most common source of unexpected zeros. Remove the date dimension and re-run.
- Backfill window. Seller-Fulfilled and FBA Inventory backfill only 1 day, far shorter than most other Amazon tables. If the report window starts before the connection date, there's no historical data to show.
- Missing Marketplace dimension. Multi-marketplace data is always returned for a connected Region, even for a single-country seller. Add Marketplace as a dimension and filter, or values get misattributed across marketplaces (this is also the leading cause of inflated or incorrect inventory totals generally; see Incorrect Inventory Numbers from Amazon Seller).
- Cached vs. live. Pairing a unique metric with the date dimension forces a cached-data request, so only cached data will show up in that report or chart.
If you've ruled out all four and the field still reads zero, check the field in the Schema Explorer, then submit a ticket with the affected field, an example SKU, and a screenshot of the same figure in Amazon's own report.
A quick way to sanity-check any of these fields against Amazon's own numbers: open the SKU's inventory detail page in Seller Central, where Amazon shows Reserved broken into Customer order, FC transfer, and FC processing for that one item.
A Note on Reserved - FC Processing
Reserved - FC Processing values are available and mapped. As with any Amazon Seller Central field, reported values through the API may differ from Amazon's own UI by roughly 1-5%, and that gap can be a little wider on short date ranges. If your Reserved - FC Processing figure looks off by more than that, submit a ticket with the specific SKU and the two numbers side by side (yours and Amazon's) so support can compare them directly.
Related Articles
- Incorrect Inventory Numbers from Amazon Seller
- Find Your Amazon Seller Central Fields in PMA: see the FBA Inventory > All SKUs and FBA Inventory > Restock field mapping tables
- Still not resolved? Submit a ticket with the affected field, an example SKU, and a screenshot from Amazon's own report.