Amazon Global Warehousing & Distribution (GWD)

What operators should know

• Use GWD for origin-side bulk inventory when delaying destination allocation can reduce early storage commitments and when Amazon's cross-border replenishment path fits the channel plan.
• Use AWD as destination-market bulk storage feeding Amazon fulfillment, subject to current eligibility and inbound rules. GWD and AWD solve different inventory-placement problems and should not be treated as interchangeable names for the same service.
• Use FBA for sellable inventory that is already positioned inside Amazon's consumer-fulfillment network. FBA is a downstream fulfillment layer, not a substitute for origin storage, import receiving, prep, or every multi-channel warehouse task.
• Keep an independent U.S. warehouse in the design when inventory needs Big, Heavy, and Bulky handling, FBA prep, pallet or LTL work, Walmart or Wayfair routing, B2B distribution, DTC fulfillment, returns inspection, or reserve stock outside Amazon's network.
• For imported inventory that reaches the U.S. and still needs those physical workflows, Broadi can operate between international inbound and marketplace replenishment without requiring every unit to enter Amazon storage immediately.
• Treat Amazon's published savings and speed claims as program-specific benchmarks, not universal outcomes. Compare them with duty timing, destination storage, replenishment cadence, channel mix, and the cost of inventory that must remain outside Amazon.

Questions this topic covers

• How is Amazon GWD different from AWD?
• What is Amazon's Global Inventory Pool model?
• When should inventory stay near the factory instead of moving early into the U.S.?
• Which warehouse work still needs to happen after GWD inventory reaches the U.S.?
• How should GWD, AWD, FBA, and an independent 3PL work together?

Current official-source updates

Primary search intent

Related Broadi pages