Reserved Inventory on Amazon: What It Means and When to Worry

The inventory dashboard says two hundred units in stock and forty reserved, the listing shows less than the seller thinks it should, and the forum thread that follows asks whether Amazon has lost the stock. Usually not. Reserved is a state with three causes, all of them ordinary, and the column tells which. The trouble is that it looks the same as a problem, and the two are told apart by how long it lasts.

This is what reserved means in each case, what normal looks like, how to read the report so the number is a fact rather than a worry, and the one situation where reserved units become a reimbursement claim.

Reserved units are stock Amazon holds and cannot sell at that moment, for one of three ordinary reasons: they belong to customer orders not yet shipped, they are moving between fulfilment centres, or they are being counted or measured after arriving. The listing sells only from available units, so a product can show out of stock with units in the network.

Customer orders clear within a day or two, transfers within days to two or three weeks, and processing within hours to days. Units that sit reserved in transfer or processing at the same figure for weeks are stuck, and that is when a case is worth opening.

Illustrative figures. The dashboard shows 200 units and 40 reserved, and the inventory report splits the 40 three ways: 12 for customer orders, 25 in transfer and 3 in processing.

The 12 are orders already placed and will ship within a day or two; they are sales, not a problem. The 3 in processing are a recent delivery being counted, and they will be available within days. The 25 in transfer are the figure to watch: after a shipment lands they move in waves, and the number should fall week by week.

Write the transfer figure down each week. If it falls from 25 to 10 to nothing, the network was doing its job. If it reads 25, 25 and 25 three weeks running, those units are stuck, and the case to Amazon says exactly that, with the three readings as its evidence.

Amazon's FBA inventory report gives three: reserved for customer orders, reserved for transfer between fulfilment centres, and reserved for processing. The first is the healthiest number on the account: a customer has placed an order and the unit is set aside until it ships, which at volume means a standing reserved count that rises with sales. The second is Amazon moving stock around its network to be nearer the customers who buy it, and a shipment received at one centre is often partly in transfer for a week or two afterwards. The third is the unit being counted, measured, or checked, which happens on receipt and during periodic counts.

The report breaks the reserved total into those three, and reading it that way turns the number into three numbers, each with its own normal. Orders: a day or two per unit, continuously. Transfers: days to two or three weeks, in waves after an inbound shipment or before a peak. Processing: hours to days, in waves on receipt.

Reserved units confuse the reorder decision as often as they confuse the listing. Each of the three kinds belongs in a different place in the arithmetic.

Reserved for customer orders. These are already sold. They leave the account within days and should not be counted as stock the business still has to sell. A reorder plan that counts them overstates the cover.

Reserved for transfer. These are still the seller's to sell and will become available when they arrive at their new fulfilment centre. Count them as stock arriving soon, much like inbound units, rather than as stock available today.

Reserved for processing. These are being checked, measured or investigated, and some may not come back as sellable. Count them cautiously, and not at all if they have been in processing unusually long.

An illustrative plan. 200 units in total, 40 reserved: 12 for orders, 25 in transfer, 3 in processing. Stock that will be sellable soon is the 160 available plus the 25 in transfer, about 185. The 12 are sold, and the 3 are uncertain. At 10 units a day, that is about 18 days of cover, not the 20 the total suggests.

Read days of cover from the right figure. Days of cover worked out from the total, rather than from available and transferring units, makes every product look a little safer than it is, which is how reorders end up a few days late. Amazon inventory management sets out the full reorder calculation.

A product selling ten units a day with forty reserved is a product with four days of orders in flight and nothing wrong. A product selling one unit a day with forty reserved after a shipment arrived last week is in transfer, and the units come back to available as they land. A product with forty units reserved for processing for three weeks is the case to look at, because processing does not take three weeks; it is stock that went into a check and did not come out, which usually means a discrepancy the centre has not resolved.

The tell is the trend rather than the number. Reserved units that rise and fall with sales and shipments are the network working. Reserved units that sit at the same figure for weeks, in the transfer or processing category, are stuck, and stuck is the word to use in the case. The inventory management article covers the wider question of how much to hold so a transfer wave does not become a stock out on the listing.

Reserved sits in a row with four other states, and the confusion usually comes from reading one without the others. Available is what the listing sells from. Inbound is what has been shipped and not yet received, with its own three stages: working, shipped and receiving. Unfulfillable is stock Amazon holds and will not sell, damaged, expired or customer returned in a condition it will not relist, and it is the column that turns into removal fees if it is not read. Researching is the small category of units Amazon is actively looking for, which is where a lost unit sits before the ledger decides it is lost.

Read as a row, the five columns tell the product's story for the week: what sold, what is on the way, what is moving inside the network, what came back broken, and what nobody can find. Read as five separate numbers on five separate days, they tell nothing, which is how a normal transfer wave ends up as a support case about missing stock.

Reserved numbers rise in the fourth quarter and around large sales events, for reasons that are mostly normal, and sellers who do not expect it spend those weeks chasing problems that are not there.

More orders in flight. Higher sales mean more units reserved for customer orders at any moment. A reserved count that doubles in Black Friday week, alongside doubled sales, is a sign of demand, not loss.

More stock on the move. Amazon moves stock between fulfilment centres to sit closer to where it will sell, and does more of it before and during peak. Transfers can also take longer when the network is busy.

Slower receiving and processing. Inbound shipments take longer to receive, and units in processing may wait longer to be resolved, in the weeks when every seller is sending stock at once.

Plan the buffer for it. Because more units are tied up in transfer and processing in these weeks, a product needs more total stock than usual to keep the same number available. The buffer for peak should allow for it.

Wait before investigating. A transfer that would be overdue in March may be normal in December. Give reserved units longer to clear in the busy weeks before treating them as lost.

Then check in January. Units still reserved for transfer or processing well after peak are the ones to investigate, and the claims calendar's January audit is the time to do it.

The listing sells from available units, not from the total. A product with two hundred units in the network and sixty in transfer offers one hundred and forty, and if those sell out, the listing shows as out of stock while sixty units sit on a truck between two centres. That is the case that costs sales, and the answer is the forecast: an inbound shipment is placed so that the transfer wave after it lands before the available units run out, which means the shipment is timed on the available count rather than the total. During the holiday inbound period, when Amazon says its centres focus on receiving, the transfer and processing waves are longer, and the shipment calendar allows for it.

Most reserved units clear on their own. A short monthly look finds the few that do not, early enough to act on them.

Reserved by type, product by product. From the inventory report, the units reserved for orders, for transfer and for processing on each product, against last month.

Orders reserved in line with sales. Units reserved for orders should move roughly with sales. A product whose order reservations are high while sales are flat is worth a closer look at its order status.

Transfers that are not moving. A product whose transfer count stays the same, month after month, may have units stuck in transit between centres. Note the product and the units.

Processing that does not clear. Units in processing for weeks rather than days are the ones most likely to have been lost or damaged. Note those too.

Match the stuck units to the ledger. The inventory ledger shows each unit's movements. Units that left one centre and never arrived at another, or entered processing and never came out, are the candidates for the claim described below.

Keep the readings. A month's figures kept beside the last few months' show whether reserved stock is behaving normally for the season or building up somewhere, which is the pattern that matters.

A unit that entered processing and never came out, or a transfer that shows as reserved long past any reasonable transit, is inventory Amazon has and cannot find, and after the reconciliation window it is reimbursable: lost in the warehouse, or lost in transfer. The claim is built from the inventory ledger, which shows the unit's every movement, and the reserved report, which shows where it was last said to be. The reimbursements article has the method and the windows; the reserved column is where the first sign appears, weeks before the ledger calls the unit lost.

For the brands we run under Amazon marketplace management, the reserved report is read weekly with the ledger: orders reserved against sales, transfers reserved against recent inbounds, and anything reserved for processing older than a fortnight opened as a case that day. The units are usually found. The point of looking is the week it saves when they are not, and the cost of looking is ten minutes. Where the stock goes when it is not reserved but is moved between centres by Amazon's own placement decisions is a separate subject, and the fee that comes with it is in Amazon seller fees explained.