Amazon FBA Capacity Planning & AWD Strategy

Amazon FBA capacity limits are a recurring operational constraint for brands selling on Amazon, particularly during peak seasons. A strategic split between FBA and Amazon Warehousing & Distribution (AWD) can mitigate stockout risk while controlling fulfillment costs.

The Core Problem: FBA Capacity Limits

Amazon imposes cubic-footage caps on how much inventory a seller can hold in FBA fulfillment centers at any given time. These limits fluctuate by season and seller performance tier:

• Peak season (e.g., December): Limits are tighter and costs are higher. A seller may be capped at ~1,900 cu ft during the holiday period.
• Post-peak (e.g., January+): Limits typically increase (e.g., to ~3,000 cu ft) and storage costs drop significantly.

When a seller hits their FBA capacity ceiling, they cannot ship additional inventory into FBA — even for fast-moving SKUs at risk of stocking out. This creates a direct revenue threat.

The FBA vs. AWD Decision Framework

Not all inventory should be treated the same when capacity is constrained. The key variable is velocity (how fast a SKU sells):

AWD as a Strategic Buffer

Amazon Warehousing & Distribution (AWD) is Amazon's upstream bulk storage program. Key characteristics:

• Not subject to the same capacity limits as FBA fulfillment centers
• Amazon replenishes FBA from AWD automatically as inventory is needed
• Higher per-unit storage cost than FBA in normal conditions, but lower than FBA peak surcharges
• Best used as a bridge for critical SKUs when FBA capacity is exhausted

When to use AWD:
- FBA capacity is at or near its limit
- A SKU is selling fast and at risk of going out of stock
- The cost of a stockout (lost sales, ranking damage) exceeds the AWD storage premium

Seasonal Timing Strategy

The most cost-effective approach aligns shipment timing with Amazon's capacity and pricing cycles:

1. During peak season (Nov–Dec): Ship only critical, low-stock items — route them through AWD to avoid FBA cap conflicts.
2. Early January: Ship bulk non-critical inventory directly to FBA once limits reset and storage rates drop.
3. Year-round: Monitor FBA utilization against capacity limits proactively, not reactively.

Requesting a Capacity Increase

Amazon allows sellers to submit support cases requesting a capacity limit increase. This is worth attempting when:

• A specific SKU or product line is at stockout risk
• The seller has a strong IPI (Inventory Performance Index) score
• There is documented sales velocity justifying the additional capacity

This should be treated as a parallel action, not a primary solution — approval is not guaranteed and timelines are uncertain.

Shipment Accuracy

A related operational risk is carrier scheduling errors. Incorrect pallet counts on inbound shipments (e.g., a 5-pallet pickup scheduled as 2 pallets) can cause:

• Partial pickups, leaving inventory stranded at the origin
• Delays in getting stock into FBA or AWD
• Reconciliation issues with Amazon receiving

Always confirm pallet counts and pickup details directly with the carrier before the scheduled date, and cancel/rebook incorrect shipments promptly.

Promotion as a Capacity Management Tool

When FBA is near capacity, running coupons or promotions on high-inventory SKUs serves a dual purpose:

1. Accelerates sell-through, freeing FBA cubic footage
2. Maintains sales velocity (which supports IPI score and future capacity allocations)

This is particularly effective for SKUs that are overstocked relative to their sales rate.

Client Example

This framework was applied directly to ^[1] during a December FBA capacity crunch. With a 1,900 cu ft cap blocking inbound shipments of fast-moving SKUs, the resolution plan was:

• Immediate: Route critical, low-stock items through AWD
• January: Ship remaining non-critical inventory to FBA once the limit increased to ~3,000 cu ft and costs dropped
• Parallel: Open an Amazon support case requesting a capacity increase for the constrained SKUs
• Carrier fix: Cancel an incorrectly scheduled 2-pallet pickup and confirm the correct 5-pallet count with carrier Exla

See also: ^[2] for the full discussion context.

Related

• ^[1]
• ^[3]