Sellers are reporting that Amazon Warehousing & Distribution (AWD) is refusing new inbound shipments — either flagging facilities as full or hanging indefinitely mid-workflow. If AWD is part of your Q4/Q1 replenishment plan, this is worth checking before you commit inventory to a container.
What sellers are reporting
- Repeated attempts to create AWD inbound shipments over a multi-day stretch returning a “full” / no-capacity message.
- The issue persists across both small and large shipment quantities, suggesting a capacity or system-level constraint rather than a volume threshold problem.
- A separate failure mode: the shipment creation workflow reaching a specific step and then loading indefinitely, never completing.
- No clear signal from Amazon in-console about expected resolution timing, leaving sellers unsure whether to wait or reroute.
Why this matters
- AWD is frequently used as the low-cost buffer between an overseas shipment and FBA replenishment. When intake stalls, that buffer disappears.
- Freight already in transit or booked against an AWD destination may need re-labeling or re-consigning, which adds cost and delay.
- Extended AWD outages push inventory decisions back onto direct-to-FBA sends, where restock limits and IPI constraints apply instead.
Practical steps while intake is blocked
- Confirm whether it’s capacity or a bug. A “full” message on both small and large shipments points to capacity; an infinite spinner at a fixed step points to a console defect worth a Seller Support case with screenshots and timestamps.
- Try an alternate browser session. Clear cache or use an incognito window before concluding the workflow itself is broken — this rules out a client-side cause on the hanging step.
- Open a case and document attempts. Log dates, times, and error text. This creates a paper trail if you later need to dispute storage or freight costs caused by the delay.
- Build a direct-to-FBA fallback plan. Identify which SKUs you’d send straight to FBA if AWD stays closed, and check your current restock limits against that plan.
- Prioritize by velocity, not by convenience. If you can only move part of your inventory, move the SKUs that will actually stock out first.
How Squatio helps
When inbound capacity is constrained, the decision shifts from “send everything” to “send the right things first” — and that requires knowing which SKUs carry real demand risk.
- Use Squatio Decode (ASIN lookup, listing visibility & Sentiment IQ review analysis) to check current listing visibility and demand signals on your own ASINs, so you can rank which SKUs genuinely can’t afford a stockout while AWD intake is stalled.
- Use Reveal (Reverse ASIN) to see which keywords your at-risk SKUs actually rank for — losing rank on a high-value term during an out-of-stock window is far more expensive than on a long-tail one.
- Use Squatio Optimize (PPC intelligence) to pull back ad spend on SKUs you can’t reliably replenish, and reallocate toward the ones you can actually keep in stock.
Has anyone gotten a straight answer from Seller Support on AWD capacity timing, or found a specific region/facility that’s still accepting inbound shipments?
Source: Can’t create shipments to AWD — r/FulfillmentByAmazon