When an Amazon AWD Shipment Cannot Be Delivered: The Hidden Risk in Q4 Inventory Planning

As e-commerce operators, we make inventory decisions months before customers see the result. We forecast demand, calculate lead times, and plan replenishment, all to protect the business from stockouts during the busiest season of the year. In theory, shipping inventory earlier should reduce risk.

This year, that was exactly our approach.

We are a Canadian company selling into the U.S. market, and we expected potential changes to U.S. tariffs on goods imported from Canada. Rather than risk higher costs on inventory we would need for Q4 anyway, we decided to send several months of stock to Amazon Warehousing and Distribution (AWD) before any changes could take effect. Last year's experience also shaped the decision. After September, inbound capacity became much more limited — delivery appointments for both FBA and AWD were increasingly difficult to find, and getting inventory into Amazon's network when we needed it most became a real challenge.

So we acted early. We created the AWD shipment in early August and planned for delivery by the end of the month.

The carrier followed Amazon's assigned delivery instructions.

Then the shipment could not be delivered.

The facility was not ready

The carrier attempted delivery to the AWD facility Amazon had assigned in Southern California. The shipment was rejected because the facility was "NOT OPEN YET."

This was not a wrong address, a missing label, or a carrier at the wrong location. The carrier went exactly where Amazon sent it — the facility was not yet accepting inbound inventory at the time of delivery. The carrier issued a written notice confirming this, and the shipment stayed with the carrier.

What started as a proactive inventory decision had become an operational disruption.

A timeline that kept moving

We opened a Seller Support case right away. Amazon later confirmed that the facility was not open and that no delivery appointment existed in the system.

A few days later, a new problem appeared. When the carrier tried to schedule delivery through Carrier Central, the system reported that the purchase order was not valid for the original facility. Amazon then redirected the shipment to another AWD facility, and we had to confirm that the existing carton labels were still valid and that the new facility would accept the shipment. Amazon confirmed both.

We expected delivery to proceed. Instead, the date kept changing — first September 16, then September 18, then a Delivery Disruption notice moving it to September 22.

Each new notice meant more uncertainty, more coordination with the carrier, and more days with our inventory sitting outside Amazon's network.

The hidden cost of a delivery disruption

An inbound delay sounds like inventory arriving a few days late. The reality is more expensive.

While the shipment remained undeliverable, the carrier charged daily storage fees on top of the transportation costs caused by the failed attempt, the destination change, and the repeated rescheduling. Over time, these costs grew into thousands of dollars.

The inventory also could not do its job. It could not replenish FBA, support planned advertising, or protect stock levels heading into Q4. And behind every notice was operational work — support follow-ups, carrier coordination, appointment tracking, and repeated attempts to reach the right Amazon team.

A scheduled delivery date does not mean the inventory has been received. A received shipment is still not inventory that is processed and available for replenishment. Each stage is a separate risk.

Why this hits small businesses harder

For a large marketplace, a delayed inbound shipment is one case among thousands. For a small business, the same delay touches cash flow, inventory availability, advertising plans, and the ability to stay in stock during the most important sales period of the year — and resolving it can take weeks, even when the cause is entirely outside the seller's control.

For a cross-border seller, the pressure is even greater. The whole reason for shipping early was to manage tariff risk and protect costs. When the inventory then sits undelivered and accumulates fees, part of the value of that early decision is lost.

When a marketplace assigns a delivery location that cannot receive inventory, the impact does not stop at one shipment. It runs through purchasing, replenishment, advertising, sales, and cash flow.

We are still working toward final delivery and pursuing recovery of the costs caused by this disruption.

Takeaway

Shipping early before Q4 is still the right instinct. But this experience changed how I think about what "early" protects against. It protects against capacity limits and tariff timing — not against the network itself being unready. Two things I would now build into any Q4 inbound plan:

• Add buffer weeks to the inbound timeline itself, not just to the stock level, and assume the first delivery date may not hold.
• Confirm the carrier's storage and redelivery fee terms before shipping, so the cost of a failed delivery is known in advance rather than discovered while it grows.

For other sellers — especially those shipping across the border — have you experienced inbound disruptions like this with AWD or FBA, and what has your contingency plan looked like?