AWD vs FBA in 2026. The Inventory Strategy Playbook.

What Amazon AWD actually is in 2026

Amazon Warehousing and Distribution is Amazon's bulk-storage warehousing service. Where FBA is built for unit-level fulfillment with rapid Prime shipping, AWD is built for pallet-level and container-level bulk storage with automatic transfer into FBA when stock levels drop.

The simplest way to think about it: AWD is Amazon's version of a backup warehouse. You park bulk inventory there at low monthly cost, and Amazon automatically pushes it into FBA when your FBA stock gets low. You also get the option to fulfill non-Amazon channels (Walmart, Shopify, wholesale) from the same AWD pool.

Built on Amazon's logistics network

AWD warehouses are operated by Amazon, not third parties. The handoff between AWD and FBA happens entirely inside Amazon's network, which means no external transfer costs, no separate inbound fees to FBA from AWD, and no broken chain-of-custody issues. The internal transfer is one of AWD's biggest structural advantages.

Multi-channel distribution layer

AWD can fulfill orders to non-Amazon channels including Walmart Marketplace, Shopify (via integration), wholesale customers, and direct-to-consumer channels. This makes AWD particularly valuable for brands diversifying off Amazon as part of a multi-channel strategy.

Requires Brand Registry

AWD enrollment requires active Amazon Brand Registry, the same prerequisite for Amazon Attribution and most other premium Amazon Advertising programs. If you are not Brand Registered, that is the prerequisite step before any AWD migration makes sense.

AWD pricing model vs FBA storage fees

The pricing difference is the whole point. AWD charges a flat $0.06 per cubic foot per month, year-round, regardless of season or product size. FBA charges by cubic foot too, but the rates vary by season and product size class. Here is the side-by-side.

Where the savings come from

The headline rate difference (40× cheaper at base, 40×+ cheaper at peak) is part of it. The bigger compounding effect is on aged-inventory surcharges. FBA layers progressively heavier penalties on inventory sitting longer than 6 months. AWD has zero aged-inventory surcharge. For brands with seasonal SKUs or buffer stock, this is where 5-figure annual savings come from.

Inbound costs are different

AWD inbound pricing is container or pallet-based rather than per-unit. This is a meaningful difference. FBA inbound has a per-unit placement fee. AWD inbound rewards bulk shipments. The breakeven shifts based on shipment size — bulk supplier shipments benefit from AWD's structure, small replenishment shipments often favor FBA's per-unit model.

The 4-stage inventory flow with AWD in the mix

Adding AWD changes the shape of your inventory pipeline. Instead of a 2-stage Supplier-to-FBA flow, you now have a 4-stage flow with AWD acting as the buffer layer between supplier and FBA. Visualization makes it clearer.

The buffer concept

The mental model that makes AWD click: AWD holds your buffer stock, FBA holds your working stock. Buffer stock is the 90-180 days of inventory you need to cover demand without stockout risk but you do not need available for shipping today. Working stock is the 30-60 days you actively ship from. AWD optimizes the buffer at low cost. FBA handles the working stock at higher cost but with full Prime shipping speed.

12-month cost math worked example

Numbers make the case better than concepts. Here is a worked example for a single SKU: an oversized kitchen product, 0.4 cubic feet per unit, 1,000 units of long-tail buffer inventory. We compare 12 months of FBA-only storage vs FBA-plus-AWD inventory placement.

That is $6,444 in annual storage savings on a single SKU. Multiply across 10-30 slow-moving SKUs in a typical $1M-$10M brand catalog and the savings compound to $50K-$200K annually. This is recoverable budget that can be reinvested into Attribution-tagged paid media, Choice badge optimization, or any other lever that drives growth.

The 5-criteria decision matrix

Not every SKU belongs in AWD. The 5 criteria below filter your catalog into the right placement. Run each SKU through this matrix and the answer becomes obvious.

The 3-bucket sort

Run your catalog through the matrix and sort SKUs into three buckets: (1) All-FBA — fast movers, standard small items, new launches; (2) Split FBA + AWD — established sellers with 60-day FBA working stock + 90-180 day AWD buffer; (3) AWD-heavy — slow movers, seasonal, oversized, B-stock. Most brands end up with 40% bucket 1, 50% bucket 2, 10% bucket 3 by SKU count. Bucket 2 is where the biggest dollar savings live.

How AWD auto-replenishment works

Auto-replenishment is what makes AWD work in practice. Without it, you would be manually moving inventory between AWD and FBA, which would defeat the operational simplicity. Here is the actual mechanism.

Setting trigger rules

Inside the AWD console, you set replenishment trigger rules per SKU. Standard config: "when FBA stock for SKU X drops below 45 days of cover, automatically push 30 days of cover from AWD into FBA." Each SKU can have a different rule. Slower-moving SKUs use longer windows (60-day trigger, 45-day push), faster-moving SKUs use shorter (30-day trigger, 21-day push).

Transfer timing

Auto-replenishment transfers typically arrive at FBA within 5-7 business days of the trigger firing. Plan your trigger thresholds to account for this lead time. If your SKU sells 50 units per day and you have 45 days of cover when trigger fires, you have approximately 38 days of cover by the time replenishment lands. Set thresholds conservatively until you have data on actual transfer speed for your specific SKUs.

Cost of the transfer

Internal AWD-to-FBA transfers do not incur additional inbound fees. The transfer is part of the AWD program. This is the key structural advantage over running a third-party 3PL where each transfer to FBA would include external inbound costs.

Override controls

You can manually trigger a transfer outside the auto-rule. Useful during deal events, Prime Day prep, or seasonal surges where you want to pre-load FBA above the normal trigger threshold. The manual override sits alongside the auto-rules in the AWD console.

AWD vs 3PL — when to pick which

Many brands evaluating AWD already use a 3PL (ShipBob, ShipMonk, Stord) or are considering one. The decision is not always AWD-or-3PL — some brands use both. Here is the framework.

Where AWD wins

• 80%+ Amazon brands: auto-replenishment to FBA is structurally better than any 3PL-to-FBA workflow
• Oversized inventory: AWD's flat $0.06 per cubic foot per month rate undercuts most 3PLs
• Simplicity: single-platform reporting, single billing system, single inventory dashboard
• Low operational overhead: no separate 3PL contract negotiation, no 3PL software integration

Where 3PLs win

• Multi-channel brands: 3PLs offer broader channel integration (Shopify Plus, Walmart, Faire, B2B portals)
• DTC-heavy operations: 3PLs typically offer better DTC packaging, custom inserts, branded packing slips
• Returns processing: 3PLs handle returns more flexibly than AWD's currently-limited return workflows
• International: 3PLs offer broader international fulfillment options outside Amazon's network

The hybrid approach

Many $5M-plus brands run both: AWD for Amazon-feeding bulk storage and a 3PL for DTC/Shopify/Walmart fulfillment. This gives you the best AWD-to-FBA replenishment economics on Amazon while preserving 3PL flexibility for off-Amazon channels. The infrastructure is more complex but the unit economics are typically the best of both worlds.

The 30-day FBA-to-AWD migration playbook

If your catalog has slow-moving inventory bleeding FBA storage fees, here is the 30-day sequence we run for client brands.

Days 1-5: Audit FBA inventory and identify migration candidates

Pull the Inventory Age Report from Seller Central. Filter SKUs with 90+ days of cover. Cross-reference with the FBA Storage Fees report to identify the highest monthly storage bleeders. Output: a prioritized list of 10-20 migration candidates ranked by potential annual savings.

Days 6-10: Enroll in AWD and create the AWD location

Inside Seller Central, enroll in Amazon Warehousing and Distribution. Create the AWD shipment plan with the migration SKUs. Confirm cubic-foot calculations for each SKU match the dimensions in your catalog — mismatched dimensions are the most common AWD setup issue.

Days 11-18: Submit AWD inbound + initiate FBA removal orders

Submit the AWD inbound shipment from your supplier or 3PL. In parallel, initiate Removal Orders for excess FBA stock on the migration SKUs, routing the removed units to your AWD location. Track both shipments through their respective dashboards.

Days 19-25: Configure AWD-to-FBA replenishment rules

Set up automatic replenishment from AWD to FBA. Define trigger points per SKU. Test the trigger on one SKU before scaling to the full migration set.

Days 26-30: Calculate savings + scale to additional SKUs

Pull the first month's storage fee invoice and compare against the prior baseline. Document the savings per SKU. Build a second migration wave for the next 10-20 SKUs. Most brands run 3-4 migration waves to reach full optimization.

The 5 AWD mistakes

Mistake 1: Migrating new SKU launches into AWD

New SKU launches need FBA's direct shipping speed and benefit from FBA's per-unit reporting granularity. Migrating a SKU to AWD in the first 90 days of launch usually costs more than it saves because you do not yet have velocity data to model the savings properly.

Mistake 2: Setting trigger thresholds too tight

If the AWD-to-FBA trigger fires only when FBA is dangerously low, you risk stockouts during the 5-7 day transfer window. Set triggers at 45+ days of cover, not 14 days. The math: stockouts cost Amazon's Choice eligibility and BSR, both worth far more than the marginal AWD storage cost of holding slightly more cover.

Mistake 3: Ignoring AWD inbound shipment requirements

AWD inbound expects bulk shipments. Small mixed-SKU shipments do not work well in the AWD model. If your supplier ships in small batches, AWD might not be the right fit for those SKUs — the inbound friction can erode storage savings.

Mistake 4: Not modeling cubic feet correctly

AWD pricing is per cubic foot. If your catalog dimensions are wrong (especially on oversized SKUs), your AWD cost projections will be wrong. Verify cubic-foot calculations against actual product dimensions before committing to AWD migration.

Mistake 5: Treating AWD as a permanent storage solution

AWD is a buffer, not a graveyard. Inventory that sits in AWD for 12+ months without movement is signaling a SKU rationalization problem, not an AWD optimization. Review aged AWD inventory quarterly. Liquidate or remove SKUs that are not turning — AWD does not solve a velocity problem, only a storage cost problem.

How Evolve Media optimizes inventory placement

Most $1M–$10M brands have never run a serious AWD vs FBA placement analysis. The default is "everything in FBA" and the storage bleed compounds quietly month after month. We close that gap in a 30-day sprint.

Catalog audit + placement plan

Full SKU-by-SKU velocity analysis using Inventory Age Report and FBA Storage Fees data. Output is a placement plan that sorts your catalog into All-FBA, Split FBA+AWD, and AWD-heavy buckets with projected 12-month savings per SKU.

Migration execution

AWD enrollment, shipment plan creation, supplier coordination, FBA removal orders, AWD-to-FBA replenishment rule setup. We run the operational playbook so your team does not have to figure it out from scratch.

Ongoing inventory optimization

Quarterly placement reviews to catch velocity shifts that change the optimal placement decision. Monthly savings reporting. Pairing with P&L analysis to verify net contribution margin improvement from AWD optimization.