Why AWD to FBA Transfers Go Wrong
Amazon's AWD program is designed to move bulk inventory from a distribution center to fulfillment centers automatically. When it works, inventory flows without friction. When it does not, sellers often stare at a gap between what AWD reports as "transferred out" and what FBA shows as "received."
Several factors can trigger an Amazon AWD shipment discrepancy:
- Receiving errors at the destination fulfillment center
- Label damage causing units to be stowed under an incorrect ASIN
- Partial shipments logged as complete in the AWD dashboard
- Warehouse transit delays that do not automatically update both systems
- Inter-FC transfers that reset a shipment's status in a way that hides units temporarily
Understanding the root cause shapes how you write the reconciliation case. A receiving error requires different evidence than a stowing error. That distinction matters when Amazon reviews your FBA missing inventory claim.
"Sellers who approach AWD discrepancy cases with shipment-level granularity, rather than broad account-level complaints, see far better engagement from Amazon's inventory reconciliation teams. Specificity signals credibility." — Renata Voss, Senior Supply Chain Advisor, Meridian Seller Solutions
How to Confirm the Discrepancy Before Filing
Never open a case on a hunch. Amazon's inventory systems can take 48 to 72 hours to reconcile after a transfer completes, and some units are simply in transit between FCs when you check. Before escalating, verify the discrepancy is real and quantified.
Pull two reports:
AWD Inventory Report. In Seller Central, go to Reports > Fulfillment > AWD Inventory Summary. Download the file that shows units "shipped to FBA" for the relevant transfer window.
FBA Shipment Reconciliation Report. Go to Manage FBA Inventory > Shipment Summary and filter by the date range matching your AWD transfer. The "Received" column is your baseline.
Calculate the gap: AWD shipped minus FBA received equals your missing unit count. If the number is zero after 72 hours, wait. If the gap persists beyond four business days after the transfer shows "complete," you have a real Amazon inventory reconciliation dispute on your hands.
Check your account deactivation knowledge base if inventory problems are accompanied by any performance notification, since missing stock can sometimes surface alongside broader compliance flags.
How to File an AWD Shipment Discrepancy Claim
Follow these steps in order. Skipping evidence gathering and jumping straight to a case opens the door for Amazon to close the ticket without reimbursement.
- Download and save both raw reports in CSV format, noting the exact shipment ID, transfer ID, and date range for the affected AWD-to-FBA movement. Keep originals because Amazon may request them as attachments.
- Calculate the unit gap at the ASIN level so your claim identifies each missing SKU, its quantity, and its declared unit value. A claim that says "some units are missing" is almost always denied; a claim that says "ASIN B0XXXXXXXX, 42 units, valued at $18.99 each" moves faster.
- Capture screenshots of the AWD transfer status showing "Transfer Complete" or equivalent, alongside the FBA Manage Inventory screen showing the shortfall. Timestamps visible in the screenshots strengthen your evidence package.
- Open a case in Seller Central under FBA Issue > Lost Inventory and reference the specific AWD transfer ID in the subject line. Paste your unit-level breakdown in the body and attach the CSV reports and screenshots.
- Follow up at 72-hour intervals if Amazon has not responded. Each follow-up should reference the original case number, restate the unit gap, and attach any new supporting data. Persistence is necessary; inventory cases are often worked in batches rather than immediately.
- Request escalation to the FBA Inventory Adjustments team if the first-tier response is a denial or a generic reply. In your escalation, cite Amazon's Plan of Action template guidance as evidence you understand the documented process Amazon expects sellers to follow.
- Document every communication in a central case log, including date, case ID, agent response, and your follow-up action. This timeline becomes essential if the case requires further escalation or reimbursement negotiation.
Most sellers who lose these cases do not lose them on merit. They lose them because the evidence package had gaps. Units with no documentation rarely get reimbursed. Units backed by shipment IDs, carrier documentation, and reconciliation reports move through the process in a fraction of the time.
Building Your Evidence Package
For any FBA missing inventory claim related to AWD, a complete evidence package typically includes:
- AWD Transfer ID and the corresponding FBA Shipment ID
- AWD Inventory Summary report (CSV) for the transfer date range
- FBA Shipment Reconciliation Report (CSV) showing the receiving shortfall
- Screenshots of both dashboards with timestamps
- Any carrier BOL or Amazon partner carrier confirmation for the AWD outbound movement
- A written discrepancy summary: units shipped, units received, units missing, per ASIN
The Document Checklists feature in AppealsPro.ai is built for exactly this scenario. It generates a violation-specific evidence checklist so sellers do not accidentally omit a document that Amazon's reconciliation team expects to see. Missing a single attachment can reset a case by days or weeks.
Amazon policy requires sellers to follow its Amazon Seller Code of Conduct, which includes accurate inventory representation. When you file a reconciliation dispute, your documentation also signals that you are a credible seller who tracks inventory with precision.
What Happens If Amazon Denies the Claim
A first denial is not final. Amazon's inventory reconciliation process has multiple tiers, and sellers who provide additional evidence after a denial often see reversals. When you receive a denial:
Read the denial reason carefully. Amazon typically says one of three things: units were received and are accounted for, insufficient evidence was provided, or the claim window has passed.
If the denial cites insufficient evidence, your next submission should directly address the gap. Add any document from the checklist you omitted the first time. If the denial says units are "accounted for," request a detailed inventory adjustment report for the affected ASINs during the transfer window. Sometimes units are logged under a different condition, such as damaged or unfulfillable, rather than simply missing.
If the claim window concern is raised, note the exact date of your original case opening and argue that the dispute was filed within the valid reconciliation period. Amazon's standard reconciliation window for FBA inventory discrepancies is typically up to 18 months after the issue date, though this varies.
Sellers managing multiple open disputes benefit from AppealsPro.ai's Case Management feature, which tracks each case's status, response deadlines, and follow-up schedule. Letting a case go silent for too long is the most common reason a valid claim dies without resolution.
If the case involves a notice that touches account health, explore the plan of action template for guidance on structured escalation language that Amazon reviewers respond to.