If you sell through Fulfilled by Amazon, you have likely experienced the sinking feeling of watching a shipment status show "Delivered" while your inventory dashboard stays at zero. The carrier has proof of delivery. Amazon's receiving dock accepted the pallets or boxes. Yet your units sit in limbo, neither available for sale nor formally lost. This gap can cost sellers hundreds or thousands of dollars in tied-up inventory, missed sales, and laborious follow-up.
This scenario is distinct from an account suspension or a policy violation, but it shares one critical trait with those situations: documentation quality determines the outcome. Sellers who submit vague cases without proof often receive partial reimbursements or outright denials. The same discipline required to write a strong plan of action template applies here: specific evidence, structured arguments, and patient escalation.
AppealsPro.ai was built for exactly these documentation-heavy scenarios, and its Case Management feature is particularly useful for tracking deadlines, case IDs, and every piece of correspondence during a long reconciliation.
Why FBA Shipments Go Missing After Delivery
Amazon's receiving process at a fulfillment center involves multiple handoffs: dock acceptance, item-level scanning, stow operations, and finally inventory reconciliation against your shipment plan. Any one of those steps can produce a discrepancy.
Common causes include:
- Receiving delays — Large fulfillment centers sometimes take weeks to fully check in a shipment, especially during peak seasons like Q4.
- Stow errors — Units are physically received but scanned to the wrong ASIN or stowed without being linked to your seller account.
- Carrier misdelivery — A box is marked delivered by UPS or an Amazon Partnered Carrier but was actually delivered to the wrong dock or facility.
- Shipment plan mismatches — If you sent more or fewer units than your shipment plan specified, Amazon's system flags the discrepancy and may hold reconciliation.
- Lost at dock — In rare cases, pallets are accepted but separated from the associated paperwork, creating an orphaned receiving event.
Understanding the root cause shapes the evidence you need. A receiving delay requires patience and a timeline. A carrier misdelivery requires a proof-of-delivery (POD) document. A stow error requires a unit-level discrepancy report.
"Sellers frequently underestimate how much carrier documentation matters in these cases. A clean, timestamped proof of delivery from the carrier, matched against the Amazon shipment ID, is the single strongest piece of evidence you can submit in the first 72 hours." — Miriam Kowalczyk, Senior Inventory Disputes Analyst, Harborview Commerce Advisory
For related step-by-step guidance, see the complete guide to Amazon FBA.
How to Confirm the Shipment Is Truly Missing (Not Just Delayed)
Before opening a case, verify you have a genuine missing-inventory situation rather than a processing delay. Amazon typically asks sellers to wait before escalating, and opening a case too early can hurt your credibility with the Seller Support team reviewing it.
According to Amazon's shipment reconciliation policies, sellers should generally allow up to 14 business days after the expected check-in date before escalating, though in practice the window may be shorter for small parcel shipments versus LTL or FTL freight.
Use Seller Central's Shipping Queue to compare:
- The shipment status shown in your FBA Shipment Report
- The carrier's confirmed delivery date and time
- The "Units Received" count versus "Units Shipped" in your shipment plan
If the carrier shows delivery, more than 14 business days have passed, and your received count is still below your shipped count, you have a legitimate claim.
How to File an FBA Lost Inventory Claim: Step by Step
The reconciliation and reimbursement process follows a specific sequence. Deviating from it, or skipping steps, typically results in case closures without resolution.
For related step-by-step guidance, see Amazon lost your FBA shipment.
- Pull your shipment discrepancy report. In Seller Central, navigate to Reports > Fulfillment > Inventory Adjustments and filter by your shipment ID. Export the full report, noting every ASIN and unit count flagged as discrepant. This becomes the backbone of your case documentation.
- Gather carrier proof of delivery. Contact your carrier (UPS, FedEx, or the Amazon Partnered Carrier portal) and request a signed POD or delivery confirmation that includes the fulfillment center address, date, time, and receiving agent signature. This single document resolves the majority of "did it arrive?" disputes quickly.
- Compile your shipment plan documentation. Download the original packing list, box content files, and any weight or dimension records you submitted when creating the shipment. Amazon's system compares what you said was in each box against what their scanners found; your documentation proves your claim.
- Open a case in Seller Central using the correct category. Go to Help > Get Support > FBA Issue > Shipment to Amazon > Missing or Lost Inventory. Choosing the wrong category routes your case to a team without reconciliation authority, wasting days. Attach all documents in the initial submission; do not wait to be asked.
- Submit a formal reconciliation request if the initial case closes without resolution. If Seller Central responds with a generic "investigation complete" message but your units remain missing, do not accept it. Reply to the same case thread citing your shipment ID, the carrier POD date, and the specific unit count discrepancy. Request escalation to the FBA Inventory Reimbursement team explicitly.
- Follow up at the 45-day mark if still unresolved. Amazon's reimbursement eligibility window is typically nine months from the shipment date, but the process moves faster when sellers follow up consistently. Cite the case ID, the days elapsed, and the dollar value at stake in each follow-up message.
- Request a manual audit if electronic reconciliation fails. In some situations, Amazon will conduct a physical audit of the fulfillment center to locate orphaned inventory. Request this explicitly in writing, referencing your case ID and all prior correspondence.
AppealsPro.ai's Document Checklists feature generates a violation-specific list of exactly the evidence types you need for FBA inventory disputes, so you do not discover a missing document after the case has already been closed.
Writing an Effective Escalation Message
The quality of your written case message matters as much as your documentation. Amazon's Seller Support teams handle enormous case volumes. Vague messages get templated responses. A clear, structured message gets read.
Your escalation message should include:
- Shipment ID and ASIN(s) at the top line, so the reviewer can pull your records immediately.
- Carrier name, tracking number, and POD date so there is no ambiguity about delivery confirmation.
- Exact unit count discrepancy stated as a specific number, not an approximation.
- Dates of prior contact and the case ID for every previous interaction.
- A specific, reasonable ask: reimbursement at the standard FBA lost-and-damaged rate for the confirmed missing units.
For related step-by-step guidance, see Amazon 24-month FBA inventory removal.
For sellers who have never written a formal Amazon case message, the Appeal Letter Generator produces structured, policy-aware correspondence that mirrors the format Amazon's internal teams expect. While the feature is primarily designed for suspension appeals reviewed through AppealsPro.ai's account deactivation knowledge base, its output discipline applies directly to escalation letters in inventory disputes.
Avoid emotional language, threats to leave the platform, or references to competitor marketplaces. Keep the message factual, numbered where possible, and under 400 words.