In short: A return costs far more than the refund. Outbound shipping, return handling, loss of value on the goods, wasted ad spend and tied-up capital all stack up — often €15–€25 on a single unit. Measure the return rate per ASIN rather than per account, understand why customers send items back, and fix the listing and packaging causes that drive avoidable returns.

The return that costs more than the refund

Most sellers watch the refund figure and stop there. But the refund is only the visible part of a return. The real damage sits in a handful of costs that never appear as one tidy line in Seller Central — and because they are scattered across shipping fees, storage reports and advertising, they usually go unnoticed until the margin has already gone.

The trap is simple: a product with a 3% return rate and a product with a 20% return rate can post identical top-line revenue. On the sales report they look the same. On the contribution margin after returns, one is comfortably profitable and the other is quietly bleeding. This guide breaks down where the money actually goes, how to measure the rate cleanly, and where to intervene.

The six cost blocks in every return

Before you can reduce anything, you need to see the full bill. A return is made up of these components:

Why this matters: None of these blocks is dramatic on its own. It is the sum that hurts — and because it is spread across four or five different reports, it almost never gets added up.

A worked example: one return, added up

Take a single mid-priced electronics unit sold via FBA and returned opened. Here is what one return actually costs once you total the blocks:

That is €21.50 on a single return, before you even count the storage and the capital tied up while the unit is out of circulation. Now put that next to your margin per unit: if you make €12 gross on the product, a single return does not just wipe out that unit's profit — it eats the profit of the next one too. This is the calculation almost nobody runs, and it is the one that changes decisions.

The numbers above are an illustration. Your real figures depend on your category, size band, fulfilment method and cost of goods. Pull your own outbound fee, return handling fee and cost price from Seller Central and rebuild this table for your actual ASINs — the ratios matter more than the absolute euros.

The return processing fee — and when it hits you

Beyond the operational costs, Amazon applies a return processing fee to units in categories where your return rate exceeds a defined threshold. The idea is straightforward: products that are returned far more often than the category norm carry an extra per-unit charge, because they generate disproportionate handling load in the fulfilment network.

Two things are worth knowing. First, the fee is assessed per ASIN against your category's threshold, not against your whole account — a single problem product can trigger it while the rest of your catalogue stays clear. Second, the exact categories, thresholds and amounts change over time.

Check the current rates: As of this writing, the categories, thresholds and amounts are published on Amazon's official help page for the return processing fee. Always confirm the figures that apply to you in Seller Central rather than relying on a number quoted in any article — including this one.

Measure the return rate per ASIN, not per account

The account-level return rate is almost useless for decisions. It blends a returns-heavy apparel line with a rock-steady spare-part ASIN into one average that describes neither. The moment you need to act, you need the rate broken down per ASIN.

In Seller Central, look at the SKU-level economics and returns reports, where returns are attributed to individual products. Track each ASIN over time — a rate that is stable and below your category threshold is fine; a rate that is creeping up month on month is the early warning you want to catch before the processing fee or the reviews follow.

This is the kind of per-ASIN view Sellercore is built to surface, so you can see contribution margin after returns rather than raw revenue.

Why customers actually return — four root causes

Reducing returns starts with knowing why they happen. Almost every avoidable return maps to one of these four causes:

How to reduce the rate on purpose

Each cause has a concrete fix. The goal is not to sell less or say less — it is to sell to the right customer, so the wrong ones never buy in the first place.

When to fix and when to delist

Not every high-return ASIN should be saved. Do the maths before you decide: subtract all the return costs from the contribution margin and see what is left. Some products carry themselves despite a high return rate because the margin is fat enough. Others are mathematically dead at 20% returns but still look healthy in the revenue report.

Only when the contribution margin after returns is persistently negative — and the cause is not something you can fix in the listing or the packaging — is delisting the honest answer. Fix what is fixable first; delist what refuses to earn its shelf space.

Bottom line

Returns are not a customer-service footnote — they are a margin line, and usually an invisible one. The sellers who protect their profit do three things: they add up the true cost of a return instead of watching the refund, they measure the rate per ASIN rather than hiding behind an account average, and they trace each return to its root cause and fix it at the source. Do that, and you stop losing the profit of the next unit to the return of the last one.

See what Sellercore can do for you

Sellercore gives Amazon sellers the tools to grow: repricing, ads optimisation, inventory and profit analytics in one place. Try it free today.

Get started free

Frequently asked questions

What is a good return rate on Amazon?

There is no universal number — the spread between categories is huge. Clothing naturally sits at several times the rate of spare parts or office supplies. Two comparisons help you more than any industry average: your own trend over the last few months, and the threshold at which Amazon applies the return processing fee in your category. If you stay below your category threshold and your rate is not getting worse, you are in good shape.

Where can I see whether the return processing fee applies to me?

In Seller Central, per ASIN in the SKU-economics reports and in your transaction details, where the fee shows up as its own line item. The categories, thresholds and amounts that currently apply are published on Amazon's official help page for the return processing fee — always confirm the figures there rather than relying on a number quoted in an article.

Why is my return rate rising even though I haven't changed the product?

Usually it is not the product. Three common reasons: your sales mix has shifted and a returns-heavy ASIN has grown; the season — returns rise almost everywhere after Christmas; or your advertising is bringing in a new audience whose expectations fit the product less well. That is why you should always look at the rate per ASIN, not just for the account.

Should I delist an ASIN with a chronically high return rate?

Do the maths first, then decide. Subtract all return costs from the contribution margin and see what is left. Some products carry themselves despite a high rate because the margin is big enough. Others are mathematically dead at 20% returns but look fine in the revenue report. Only when the contribution margin after returns is persistently negative and the cause is not in the listing is delisting the honest answer.

Do more cautious product images and shorter copy reduce the return rate?

No — that mostly reduces your conversion. It is not about less information, but more honest information. A listing that clearly shows dimensions, material and scope of delivery sells to the right people and spares you the returns from the wrong ones.