Amazon Warehousing and Distribution: when AWD is worth it
AWD sits upstream of FBA as bulk storage that auto replenishes your fulfilment centres. It solves a real problem for some brands and quietly adds cost for others.
- AWD is bulk upstream storage that automatically replenishes FBA. It is not a cheaper version of FBA.
- The real benefit is smoothing inbound and protecting against capacity limits, not the storage rate itself.
- It only pays when your demand is seasonal or lumpy enough that FBA storage costs spike at predictable times.
- If your problem is forecasting rather than storage, AWD will make the symptom cheaper and leave the cause alone.
Amazon Warehousing and Distribution sits upstream of FBA. Instead of sending stock straight into fulfilment centres, you send it into bulk storage inside Amazon’s network, and it replenishes your FBA inventory automatically as demand draws it down.
Described that way it sounds obviously good. It is not obviously good. It is good for a specific shape of business, and mildly expensive for everyone else.
The problem it is actually solving
FBA is optimised for fast moving inventory close to the customer. It is deliberately expensive to sit still in. Long term storage surcharges exist to push slow stock out, and capacity limits exist to ration space among sellers.
That creates a squeeze for any brand with lumpy demand. You need a large quantity available for a sale event or a season, but holding it in FBA for the months beforehand is punished, and sending it in late risks missing the window because inbound appointments and receiving times are not fully in your control.
AWD is the answer to that squeeze. Bulk goes upstream, cheaply, and flows down as needed. The value is in the timing, not the rate.
Read the cost as a system, not a line item
The mistake is comparing the AWD per unit storage rate to the FBA per unit storage rate, seeing a lower number, and concluding it is cheaper. That comparison ignores that you have added a movement.
Stock now travels into AWD, is stored, is transferred into FBA, and is stored again before it sells. Each of those steps has a cost and a handling risk. For inventory that would have sold within a normal FBA cycle anyway, you have inserted a node into a chain that did not need one.
The honest calculation compares two whole scenarios over the life of a purchase order. Scenario one: all units into FBA, carrying whatever aged storage surcharge they attract. Scenario two: bulk into AWD, transfers into FBA, both storage costs, plus transfer fees. Run it on the actual sell through curve of a real SKU, not on an average.
For a seasonal SKU with a sharp peak, scenario two usually wins clearly. For a steady mover, scenario one usually wins.
Where it earns its place: capacity and inbound reliability
The financial case is often secondary to the operational one.
Capacity limits are the constraint most Indian brands feel before they feel storage cost. Going into a festive period, the risk that hurts is not paying a storage surcharge. It is being unable to get enough units into fulfilment centres in time, and watching a listing go out of stock during the highest traffic week of the year.
Stock already sitting inside the network upstream shortens that path considerably. You are no longer dependent on external transport, appointment slots and receiving queues at the exact moment when every other seller is competing for the same capacity. Replenishment becomes an internal transfer.
If you have ever lost a sale event to an inbound delay, that reliability is worth more than the storage arithmetic.
The trap: cheaper storage postpones hard decisions
Here is the failure mode nobody warns brands about. AWD makes holding inventory cheaper. Holding inventory that is not selling is a problem that should hurt, because the pain is what forces the markdown, the bundle or the liquidation decision.
Lower the carrying cost and the pain reduces without the underlying problem changing. The stock is still dead. The cash is still trapped. The only thing that improved is the monthly storage line, which was never the real cost.
If you are considering AWD because your storage bill is uncomfortable, first check whether the storage bill is a symptom of overbuying. If it is, fix the forecast. Moving the stock somewhere cheaper is a way of not fixing it.
Who it fits
AWD fits brands with real seasonality, a festive or event driven demand curve, or long inbound lead times from a factory that force large purchase quantities. It fits brands that have hit FBA capacity limits and lost availability because of them. It fits SKUs with high units per order and predictable sell through where bulk economics are genuine.
It does not fit small catalogues with fast turns, brands whose constraint is cash rather than space, or anyone hoping it will substitute for demand planning.
How to trial it without committing the whole catalogue
Pick two or three SKUs with the sharpest seasonal curve, the ones where you know you will need volume available in a specific eight week window. Run them through AWD for one full cycle while everything else stays on the existing flow.
Measure three things against the previous comparable period: in stock rate during the peak window, total landed storage and handling cost per unit sold, and how many inbound emergencies your team had to manage. The third is the one that will not show up in a spreadsheet and is often the reason to keep going.
If the in stock rate improves and cost per unit sold holds flat, that is a win worth extending. If cost per unit sold rises and availability was never the problem, you have your answer and it cost you one season to learn it.