Overview

Amazon's Send to Amazon workflow is the primary tool sellers use to create FBA shipments, but it can sometimes throw errors that stall the process. Understanding how to diagnose and resolve these issues on your own can save significant time and get your inventory moving to fulfillment centers faster. This guide covers the most common troubleshooting strategies for both warning and blocking errors in the shipment creation workflow.

Key Points / What Sellers Need to Know

• Yellow warnings vs. red errors — Yellow warnings are informational and won't prevent you from moving forward with shipment creation. Red errors, on the other hand, can completely block your progress and must be resolved before continuing.
• Most errors are SKU or ASIN-level issues — The majority of errors encountered in the Send to Amazon workflow stem from problems with individual SKUs or ASINs, not system-wide bugs. Investigating at the product level is usually the fastest path to resolution.
• Inventory must be fully prep-compliant — Amazon requires that all inventory is properly prepared for fulfillment center receiving before shipments can be created. Missing prep requirements are a frequent source of blocking errors.
• Error messages include helpful links — Most red errors come with built-in links that either explain the issue in more detail or direct you to the Fix SKU Defects page where you can resolve product-level problems.
• Test workflows are a powerful diagnostic tool — Creating a small test workflow with individual SKUs can help you isolate which specific product is causing an error in a larger shipment plan.

Troubleshooting Strategy: Isolate and Test

The most effective approach to resolving Send to Amazon errors is systematic isolation. Start by reviewing your full SKU list and going back through previous steps of the workflow to check whether any new errors have surfaced. If the source of the problem isn't immediately clear, create a new test workflow and add each SKU from your original manifest individually. This allows you to pinpoint exactly which product is triggering the error. If the test workflow allows you to proceed past the step where you were originally stuck, you should continue with the new workflow for shipment creation and void the old one.