October 21, 2026

Amazon Returns vs Refunds: Why Your Return Rate and Your Refunds Never Match

A refund is money, a return is a box arriving at a warehouse. Why Amazon's two numbers disagree, how to read reasons and dispositions, and what to ask Claude.

Ask two people on the same Amazon team for last month's return rate and you will often get two different numbers. Both can be right. One counted refunds, the other counted returns, and on Amazon those are different events that happen on different days, in different reports, and sometimes not at all for the same order.

This post explains the difference, the reasons the two numbers drift apart, how to read return reasons and dispositions, and the questions to ask your AI so that the answer you get is the one you meant.

A refund is money. A return is a box.

  • A refund is a financial event. It shows up in your settlements as a refund line: the principal given back, the referral fee Amazon credits back minus its refund commission, shipping, tax and promotions reversed. It answers "how much money went back to customers?"
  • A return is a physical event. For FBA it is a unit received at a fulfillment center, dated on the day it arrived. For FBM it is a return request, dated on the day the customer asked. It answers "how many units came back, and in what state?"

The returns report carries the operational details: the return reason, the request status, and for FBA the customer's comment and the condition Amazon's warehouse assigned to the unit. The refund line carries none of that. It only carries the money.

Why the two numbers never match

  • Timing. Amazon often refunds before the unit is back. A refund in the last days of September can belong to a return that lands in October, so a monthly comparison splits one order across two months.
  • Refunds without a return. Amazon sometimes refunds and lets the customer keep the item, and some units are simply never sent back. Those refunds have no return row at all.
  • Returns without a refund. A unit can come back on an order that was never refunded, or was refunded only partly.
  • Different date anchors. FBA returns are dated by warehouse receipt and FBM returns by request date. Mixing the two channels in one monthly count mixes two clocks.
  • Regional reports. Some return rows belong to the whole seller account in a region rather than to one marketplace. Add up separate exports for the US and Canada, and those rows count twice.

None of this is an error in the data. It is the reason to decide which question you are asking before you compare anything.

Three return rates, and when to use each

  1. Refunded units divided by units sold, both from the sales and traffic data. Use it to compare products and periods on the same timeline as your sales.
  2. Returned units divided by units shipped, from the returns report. Use it for operations: packaging, defects, warehouse condition, supplier quality.
  3. Refunded amount divided by sales, from settlements. Use it for margin and cash.

Pick one per question and say which one in the prompt. A common mistake is to sum the quantity on settlement refund lines and call it refunded units. In DataDoe's settlement table that field is filled from the returns reports, so for refunded units on the sales timeline use the sales and traffic data instead.

Reason and disposition are two different opinions

The return reason is what the customer said: unwanted item, not as described, defective, arrived damaged and so on. The disposition is what Amazon's warehouse found when the unit arrived: sellable, customer damaged, defective, carrier damaged or damaged. Disposition exists only for FBA returns.

The gap between the two is where the useful findings are:

  • "Defective" as the reason with "sellable" as the disposition often means the product works but confuses people. The fix is usually the listing, the instructions or the images.
  • "Not as described" clustered on one ASIN points straight at the detail page.
  • "Carrier damaged" dispositions rising after a packaging change are a supplier or prep conversation, not a listing one.

One trap: FBA and FBM use different reason codes. FBA reports UNWANTED_ITEM where FBM reports CR-UNWANTED_ITEM, and NOT_AS_DESCRIBED on FBA matches AMZ-PG-BAD-DESC on FBM. Map the equivalents before you combine the two channels, or the same reason shows up as two.

What a return costs you

The refund is only part of it. A unit that comes back as customer damaged or defective cannot be sold again, so its product cost is lost on top of the refund. In DataDoe, each return row carries the product and shipping cost you uploaded, valued as of the return date. In the profit tables, only units that come back sellable are treated as restockable. Every other disposition counts as a lost unit.

That makes a simple ranking possible: not "which ASIN has the most returns" but "which ASIN loses the most money to returns once unsellable units are counted at cost".

Questions to ask Claude

With DataDoe connected to Claude or another AI client, returns, settlements, sales and product costs sit in one schema, and your AI joins them when you ask. Questions that work:

  • "Which ten ASINs had the highest refunded-units rate last quarter, and what were their top three return reasons?"
  • "For FBA returns in the last 60 days, show reason against disposition by ASIN. Where do customers say defective while the warehouse says sellable?"
  • "What did unsellable returns cost me at product cost last month, by ASIN?"
  • "Which suppliers' products come back as defective most often?" This works when your cost upload includes a supplier name.
  • "Which refunds from more than 45 days ago have no return received, and was any of them reimbursed?" These are worth checking against FBA reimbursements.
  • "Combine FBA and FBM return reasons for my top ASIN, mapping the FBM codes to their FBA equivalents first."

For the reasons data itself and what patterns to look for, see reading Amazon's returns and refund reports. For the money side, see reconciling Amazon settlement reports.

Questions people ask

Why is my refund total higher than my returns?

Usually timing and refunds without a return. Amazon refunds many orders before the unit arrives, and some units never come back. Compare a longer window, such as a quarter, and match on order ID rather than on month.

Do FBM returns have a disposition?

No. The warehouse condition exists only for FBA returns. FBM returns have a request status, a carrier and label details instead.

Is a reimbursed return a return?

It shows up in the FBA returns report with the status "Reimbursed", meaning Amazon paid you for the unit instead of returning it to your stock. The payment itself is in the reimbursement report.

• Get started

Put this to work on your own Amazon data.

Connect Seller Central, Vendor Central and Amazon Ads in about 5 minutes, then ask your AI about your own numbers instead of the examples in this post.

  • Seller, Vendor and Ads
  • Any AI client
  • An account manager for every customer
  • $97/mo, 14-day free trial