Amazon FBA inventory discrepancies: source-of-truth checks before reconciliation

Amazon's April 29, 2026 FBA Deep Dive forum event put shipment creation, FC receiving, reconciliation, reimbursements, capacity, restock logic, stranded inventory, and listing management in the same conversation. That matters because many FBA problems do not stay in one dashboard.

For US and UK sellers, the practical risk is simple: Seller Central may show one inventory picture while shipment processing, FC transfer, reimbursement, capacity, or listing availability seems to point somewhere else. Before opening another reconciliation case, build one source-of-truth file that explains the inventory journey in order.

Short answer: build the inventory chronology first

Do not start by choosing the dashboard that looks most favorable. Start by listing the facts that should not change across dashboards, then mark where Amazon's systems diverge. This keeps the case factual instead of argumentative.

• Record the shipment ID, marketplace, destination fulfillment center, creation date, shipment type, carrier, tracking or PRO number, and delivery date.
• List every ASIN, MSKU, FNSKU, expected quantity, box count, carton contents record, and any prep or labeling requirement tied to the shipment.
• Capture the Shipping Queue status sequence: shipped, in transit, delivered, checked in, receiving, closed, or any stalled status.
• Compare units expected, units located, units available, FC processing, reserved, stranded, removed, reimbursed, and still missing.
• Keep screenshots, shipment events, carrier proof, case IDs, reconciliation submissions, and reimbursement records in one dated folder.

Separate processing delay from a real discrepancy

A delivered FBA shipment is not always ready for reconciliation. Amazon's public FBA shipment guidance points sellers to the Shipping Queue, Shipment summary, Shipment events, and Contents tab because the status sequence matters. A shipment may still be processing, awaiting final count confirmation, or not yet eligible for the Action required options.

• Treat it as a processing question when the shipment is not closed and Amazon is still showing check-in, receiving, transfer, or final-count movement.
• Treat it as a discrepancy question when the Contents tab shows a difference between expected units and located units after eligibility appears.
• Treat it as a stronger escalation candidate when the shipment is closed, the same missing units persist, and the records show delivery and ownership.
• Treat it as a different route when the problem is not missing inventory but a listing block, stranded inventory rule, capacity limit, or payment reserve.

Match every discrepancy to two evidence lanes

Amazon forum guidance on FBA reconciliation repeatedly points sellers back to two evidence lanes: proof of inventory ownership and proof of delivery. If either lane is weak, the case often stalls even when the missing-unit count looks obvious to the seller.

• For ownership, use supplier invoices that show purchase date, product names that match the missing products, and quantities purchased.
• If you are the manufacturer, use a signed packing slip with packing date, shipment or purchase order ID, product names, quantity shipped, and manufacturer signature or stamp.
• For delivery, preserve carrier records such as proof of delivery, bill of lading, box count, pallet count, total weight, delivery appointment, and Amazon stamp where applicable.
• Use non-editable files such as PDF, JPG, PNG, or TIFF when Amazon asks for formal evidence, and avoid editable spreadsheets as the primary proof file.
• Bridge the two lanes with a simple table so the reviewer can move from invoice or packing slip to shipment ID to receiving discrepancy without guessing.

Know when the issue has moved beyond normal reconciliation

Most FBA discrepancy work should begin inside the shipment and reconciliation workflow. Northline-style account-health triage becomes more relevant when the missing inventory, reimbursement decision, or repeated claim pattern starts affecting funds, account standing, or credibility with Amazon.

• Use the FBA reimbursement route when Amazon challenges whether missing-unit or reimbursement claims are supported by shipment and ownership records.
• Use the funds-on-hold route when the main problem is withheld disbursement, reserve logic, or released reimbursements that do not reach available balance.
• Use the negative-balance route when Amazon says prior credits, reversals, fees, refunds, or claim adjustments have put the account below zero.
• Use verification or document-fit triage when Amazon is testing entity, bank, supplier, invoice, or beneficial-owner credibility beyond the shipment itself.

The practical closing test is whether a reviewer can follow the same inventory story you can: shipment created, carrier picked up, Amazon received or failed to receive, discrepancy identified, evidence attached, and the correct issue route chosen. If that story is still fragmented, return to the FBA reimbursement owner context before another case or appeal turns a data mismatch into a credibility problem.