Reimbursements

Evidence that wins: documentation sellers should build for lost, damaged and miscounted FBA inventory

Winning reimbursement and inventory correction cases starts before you open a claim: collect consistent, SKU-level evidence and follow a repeatable workflow so Amazon can match your records to theirs.

October 27, 2026 · 6 min read

Most reimbursement requests fail not because the seller is wrong but because the evidence is incomplete, inconsistent, or impossible to reconcile with Amazon's records. Amazon’s support teams work from the marketplace’s system data first; your job is to present documentation that ties your unit-level records to the exact inventory events Amazon saw. Do that, and you move from hand-waving to a clear, verifiable request. This post lists the specific types of documentation that matter, how to collect them reliably, and a practical, repeatable workflow for building an evidence kit you can attach to any FBA case.

The principle to follow

Treat each potential reimbursement as a traceability problem: can you take an individual unit from your books and follow it through each step—picking, packing, carrier, inbound scan, and the FC snapshot? If you can, you have evidence Amazon can reconcile. If you can’t, you’re asking them to accept a seller-side summary rather than audited artifacts, and those requests are far less likely to succeed.

Core documents and artifacts to collect

Collect these items proactively for every shipment and for any units you suspect are lost, damaged or miscounted. Don’t rely on memory or screenshots that lack system metadata; the stronger items are those with identifiers and timestamps.

Inbound shipment manifest and packing list: the original file that lists SKUs, quantities by carton, shipment ID, and carton IDs. If you use a 3PL get their pick-and-pack report with carton-level detail.
Carrier tracking and proof-of-delivery: full tracking history for each carton or pallet. If a shipment left your dock but never reached the fulfillment center, carrier logs are primary evidence.
Pre-shipment photos and video: clear photos of each packed carton showing SKU labels, carton IDs, pallet labels and any packing lists. Include a reference object or tape measure so reviewers can see scale.
Carton and pallet labels: high-resolution images of all Amazon labels and carrier labels with readable barcodes. If labels are partially ripped, document what’s still visible.
Inbound receiving exceptions: any email or case notes from Amazon indicating receiving problems, with timestamps and the inbound shipment ID.
Inventory event exports: Amazon’s inventory event reports, settlement reports and removal receipts that show the disposition of units. Export these CSVs and include the raw file (don’t paste a screenshot).
Purchase orders and vendor invoices: proof of purchase that shows quantity shipped to Amazon or to your 3PL, with SKU and lot numbers if applicable.
Warehouse packing photos and scan logs (if you use a 3PL): pick and pack scans that show which units went into which cartons and when.
Return tracking and disposition for customer returns: carrier tracking for returns, the return authorization number, and any removal order receipts showing what was returned to you or disposed.
Removal order and disposition receipts: when you ask Amazon to remove units, the resulting receipt or label is a high-value artifact for disputes about disposition.
Serial numbers, lot codes or other unique identifiers: for serialized units, include the serials on invoices and packing lists to prove which exact units were shipped.

What evidence matters most by case type

Tailor the evidence you collect to the nature of the problem. The goal is to show an unbroken link from your records to Amazon’s inventory event.

Inbound short or miscount: strongest items are carton-level packing lists, pre-shipment photos showing carton labels, and carrier proof-of-delivery into the receiving hub. If your 3PL provides carton scan logs, include those.
Lost in transit to FC: shipping manifest, carrier tracking that shows non-delivery or delays, and handover scans from the carrier.
Damaged at FC: removal receipts, photos from removal (if provided), pre-shipment photos showing units were intact when shipped, and any inspector notes from Amazon.
Customer-returned but not received: return tracking, return authorization, and removal receipts if the unit was returned to a customer or disposed.

How to collect evidence without adding daily overhead

A few small investments in process prevent weeks of scramble later. The secret is automation where possible and a single, consistent file naming and storage convention.

Standardize filenames: include shipment ID, SKU/ASIN, carton ID and a short description (e.g., inbound-packinglist). Use machine-readable formats (CSV, PDF) and avoid embedding evidence only in chat platforms.
Automate exports: schedule CSV exports of inventory events, settlements, and shipment summaries weekly. Store raw files; don’t edit timestamps or content.
Make photo capture mandatory: require that whoever packs a carton takes a short video or a set of photos that includes a timestamp and shows SKU labels, carton labels and the packing list.
Integrate 3PLs: get your 3PL to provide a daily feed of carton scans and packing manifests. If they won’t, require their PDF manifests with signatures.
Use a dedicated evidence storage folder per shipment or case: make it easy to zip and attach the full folder when you open a claim.

Common mistakes that make cases fail

Avoid these traps. They’re the most frequent reasons Amazon support finds a seller’s request unverifiable.

Submitting screenshots instead of raw files: screenshots lose metadata and can be dismissed as non-authoritative.
Mixing SKU identifiers: use the same SKU/ASIN/merchant SKU consistently across all documents. Mismatched identifiers break the trace.
Low-quality photos: unreadable barcodes or blurred labels are useless. Photos must allow a reviewer to read labels without zoom artifacts.
Late evidence hunting: trying to assemble proofs weeks after an event means important artifacts (carrier logs, packing photos) may no longer exist.
Using inconsistent timestamps: ensure dates and times in your files align and, where possible, include timezone information.

A repeatable case-opening workflow

When you spot a discrepancy, follow this sequence so every case you open is complete and easy to verify.

1) Pull export reports: inventory events, shipment history, and settlement lines covering the SKU and the time window in question.
2) Assemble shipment artifacts: packing list, carton and pallet label photos, carrier tracking and any 3PL scan logs.
3) Attach disposition records: removal order receipts, return tracking, or inspection notes if available.
4) Create a concise cover file: a single page that lists the shipment ID, SKUs affected, the evidence filenames included, and the claim you want (inventory correction, reimbursement, or replacement).
5) Open the support case with the cover file and the raw artifacts attached. Ask for the inbound shipment ID and the exact inventory event reference you are disputing so you and the rep reference the same record.
6) If the response is insufficient, escalate with the same complete evidence set rather than additional commentary—support teams need artifacts to escalate internally.

When to hire specialist help

If your volume of disputed cases is large, consider retaining a specialist who can audit evidence, prepare consolidated claim packages, and work escalations with the marketplace. Specialists add value when they standardize the process and reduce repeated manual work, but make sure any third party preserves your raw evidence and uses the same identifiers you use internally.

Where MySellerHQ fits

MySellerHQ is a read-only dashboard that surfaces the data you already have in Amazon’s Selling Partner API. It can highlight inventory anomalies, show mismatches between inbound shipment quantities and received units, flag refunds without corresponding returns, and collect the inventory and settlement exports you need for a case. Use it to prioritize which SKUs and shipments need an evidence kit assembled, but remember it does not file cases or change any inventory—decisions and communications remain yours.