Return Rate

Return rate is the share of units sold that customers send back, expressed as a percentage:

Return Rate (%) = Returned Units / Units Sold (same period) × 100

It is the single most under-tracked variable in Amazon unit economics. Sellers will optimise PPC to a tenth of a point of ACOS while leaving a SKU with a 28% return rate untouched — even though the return rate is silently destroying twice the margin PPC could ever recover.

Why return rate matters disproportionately

A return is rarely a 100% cost — it's worse. Each return typically costs:

• The refund (full ASP returned to the customer).
• The original outbound FBA fee (kept by Amazon, not refunded).
• The return inbound fee (charged to the seller).
• Refurbishment / re-grading cost (if returned in sellable condition).
• The unit itself (if returned damaged / unsellable — often 30–50% of returns).

For a €25 ASP product with €5.50 COGS:

Refund issued           -€25.00
Outbound FBA kept        -€3.40
Return processing fee    -€2.50
Unit write-off (40% chance × €5.50)   -€2.20
= Net loss per return    -€33.10

A return doesn't lose you the margin — it loses you 1.3× the ASP. This is why a 4-point return-rate reduction often beats a 4-point ACOS reduction in net P&L impact.

Benchmarks by category (DACH approximations)

These are rough benchmarks; the actionable comparison is always to your category peers, not to a universal threshold.

What causes return-rate spikes

In order of frequency:

1. Sizing/fit mismatch (apparel, shoes) — solved by a sizing guide module and accurate measurements in bullets.
2. Photo-product mismatch — over-styled lifestyle imagery oversells; the unboxing disappoints. Realistic photography lowers returns.
3. Defects / quality drift — usually batch-related; trace to specific PO and supplier.
4. Wrong product expectations — title or bullets misleadingly broad. Tightening copy on intended use case drops returns.
5. Damage in transit — packaging upgrade required.

The path to the Frequently Returned Badge

When return rate on a SKU crosses Amazon's (undisclosed, category-specific) threshold, the listing earns the Frequently Returned Item badge — a CVR-killing visible warning on the PDP. Once badged, the listing typically loses 15–35% of conversion overnight; recovery requires sustained return-rate improvement before Amazon removes the badge.

The badge is the lagging indicator. The leading indicator is the SKU-level return-rate dashboard nobody builds.

What to do about it

• Weekly: SKU-level return-rate ranking. Anything 1.5× your category healthy benchmark goes on a watchlist.
• Read return reason codes monthly. Amazon categorises return reasons; the dominant one tells you the fix.
• Photography review on every problem SKU. Photo-vs-reality mismatch is the cheapest fix when it's the cause.
• A/B test main image, bullets and A+ on returns — not just on CVR. A new bullet structure can shift return reason mix.
• Trace defects to PO. A batch issue should not pollute the rolling return rate of future POs.

Common mistakes

• Treating returns as ops cost, not marketing data. Returns are voice-of-customer; the reason codes are research.
• Aggregating return rate at brand level. Hides the one SKU dragging the average; always cut by SKU.
• Ignoring return-rate impact in PPC ROI. Real CPA includes refunded orders; aggregating gross orders inflates ROAS by 5–15%.
• Waiting for the Frequently Returned Badge to act. By that point you've lost 4+ weeks of margin and the badge takes weeks to remove.