Amazon FBA Inventory Management — AWD vs FBA Strategy

Overview

Amazon offers two primary warehousing options for sellers: Fulfillment by Amazon (FBA) and Amazon Warehousing & Distribution (AWD). While AWD is marketed as a lower-cost bulk storage solution that auto-replenishes FBA, it carries a critical operational risk for perishable or dated goods: Amazon does not guarantee FIFO (First-In, First-Out) inventory rotation. This can cause older stock to sit while newer stock is sold, leading to expiration events and forced disposal.

This article documents the failure mode, resolution approach, and ongoing best practices developed from a live incident with ^[1].

The AWD Expiration Problem

What Happened

Doodla stored bulk inventory of 1lb black beans at an AWD center. Amazon's non-FIFO fulfillment logic allowed newer stock to be picked and sold while older units sat in AWD. When the older units approached their expiration date (December 14), Amazon flagged 600+ units and removed them from sale — eliminating available inventory and creating an urgent resolution situation.

Root Cause

• AWD does not enforce FIFO. Amazon's AWD-to-FBA replenishment algorithm optimizes for its own logistics, not product expiration dates.
• Perishable goods are high-risk in AWD. Any product with a shelf life is vulnerable to this failure mode if stored in AWD for extended periods.
• Bulk storage creates false security. Having large quantities in AWD can mask the fact that specific units are aging out.

Resolution Framework

When expiring AWD inventory is discovered, evaluate options in this order:

1. Dispose vs. Return

Default recommendation: Request Amazon disposal for expiring AWD stock. Return orders are rarely cost-effective for low-margin perishables.

2. Shift New Shipments to FBA Directly

Once the AWD issue is identified, stop sending new inventory to AWD and route all new shipments directly to FBA. This gives you:
- Direct control over which units are available for sale
- Visibility into actual inventory age
- Faster replenishment without AWD's replenishment lag

3. Apply a 3-Month Inventory Cap

Implement a strict maximum inventory policy: never send more than 3 months of projected sales volume to Amazon at one time. This limits expiration exposure even if FIFO breaks down.

4. Prioritize High-Velocity SKUs for Replenishment

After an expiration event, replenish high-velocity SKUs first (e.g., 1lb black beans) to restore sales velocity. Hold off on reordering low-velocity SKUs (e.g., 25lb kidney beans) until the AWD situation is fully resolved and new inventory policies are in place.

Ongoing Best Practices

Inventory Caps by Product Type

When in doubt, use the 3-month cap as the default for any product with an expiration date.

AWD Usage Guidelines

AWD may be appropriate for:
- Non-perishable goods with no expiration date
- High-volume SKUs where the cost savings justify the reduced control
- Situations where you have a dedicated AWD monitoring workflow to catch aging inventory

AWD is not recommended for:
- Any product with a shelf life under 18 months
- Low-velocity SKUs that may sit for extended periods
- New product launches where sell-through rate is uncertain

Monitoring Checklist

Review the following on a monthly basis for any AWD-enrolled inventory:

• [ ] Check AWD inventory age reports in Seller Central
• [ ] Compare AWD unit dates against FBA unit dates
• [ ] Flag any units within 90 days of expiration for removal or disposal
• [ ] Verify that AWD-to-FBA replenishment is pulling oldest units first (it often won't be)
• [ ] Confirm 3-month cap is not being exceeded across combined AWD + FBA stock

Decision Tree: AWD vs. FBA

Does the product have an expiration date?
├── No → AWD may be appropriate (evaluate cost savings)
└── Yes
    ├── Shelf life > 24 months AND high velocity? → AWD with close monitoring
    └── Shelf life < 24 months OR low velocity? → FBA only, 3-month cap

Related Articles

• ^[2]
• ^[3]
• ^[4]