FBA returns reimbursement: reconcile the refund and the unit

An FBA customer refund and a seller reimbursement are different transactions. To investigate a return discrepancy, follow the order from refund or replacement through the physical return, inventory disposition and any reimbursement. A refund without a visible return is a question to investigate, not proof that a payment is due.

This checklist is for seller-side FBA return investigations. Read Amazon’s customer-returns policy and the relevant claim rules in your marketplace. It does not cover a shopper’s refund request or a merchant-fulfilled claim process.

Build an order-level timeline

Record the Amazon order ID, SKU or FNSKU, quantity and marketplace. Add the refund or replacement date, any shopper drop-off information, the recorded return event and the inventory disposition. Keep each date separately: a refund date and a return drop-off date are not interchangeable.

Distinguish the unresolved issue

Separate a return not received, a unit received with an unexpected condition or identity, and an item already restored or financially resolved. Do not treat every unsellable return as an Amazon-caused loss.

In Amazon staff guidance on an FBA return case, the response distinguishes sellable stock restored to inventory from unsellable stock assessed for responsibility. That distinction is useful when organizing evidence; your account’s current policy determines the claim.

Check the applicable clock before filing

Open the claim rule that applies to this event in Seller Central and record the earliest submission date, deadline and triggering date. Public Amazon pages describe different date triggers and windows across return contexts. Avoid calculating a deadline from a generic blog table or from the wrong order date.

Check existing investigations and resolved cases while establishing eligibility. If a waiting period has not elapsed, record a review date. If the case is eligible and unresolved, assign an owner before the deadline.

Prepare evidence for the specific discrepancy

• Order ID, product identifier, affected quantity and marketplace.
• Refund or replacement record and dated return-report rows.
• Inventory disposition and any linked reference IDs.
• Relevant condition evidence, if available and required for the issue.
• Reimbursement transactions, reversals and prior case IDs checked.
• The applicable policy, event trigger and submission window.

Submit once and follow the resolution

Use the return-specific investigation route shown in your account. Explain the order, event and unresolved quantity, with the relevant records attached. Follow the general claim-filing checklist for case ownership and tracking.

When Amazon responds, reconcile both the decision and the transaction. A closed case, an inventory movement and a reimbursement are separate records. Keep them together so another team member does not re-submit the same event.

Choose the next workflow

If the issue concerns warehouse stock rather than a customer return, use the lost-inventory guide. For fees, use the reimbursement fee calculator with your own quote.

Explore the Rivet Rocket reimbursement preview to see the record-review direction. Confirm support for your specific return discrepancy and marketplace with Alfredo; this guide does not establish that those claim types are available in the product.

Save a case log before you submit

Download the blank reimbursement case log (CSV). Keep one row per investigated event. It includes fields for identifiers, policy dates, evidence, prior resolutions, the filing owner and the outcome. It contains column headers only and does not determine eligibility or calculate deadlines.

Use your current Seller Central account to fill the route, required documents and claim window. Leave a field unverified until a source supports it. A tool-generated record and this checklist do not replace Amazon’s eligibility decision.