Returns Analytics Ecommerce

The Most Common Return Reasons in Ecommerce (and What Each One Is Really Telling You)

By Sharon Nath ·

Size, fit and 'not as described' account for the majority of ecommerce returns, but the reason code your customer picks is rarely the real cause. Here is how to read return reasons properly and turn them into merchandising fixes.

Every returns dashboard shows a pie chart of reason codes. Very few of them are telling the truth.

The reason is structural: a customer selecting a return reason is trying to finish a form, not file a report. They will pick whichever option gets them to a refund fastest, which is usually whichever appears first and demands no explanation. Fix the form and the data changes overnight — without a single customer changing behaviour.

The Real Distribution

Across the catalogues we see, returns cluster into six causes:

| Reason | Typical share | What it usually actually means | |---|---|---| | Size or fit | 40-55% (apparel) | Inconsistent grading across your own SKUs | | Not as described | 10-20% | PDP imagery, colour accuracy, or material copy | | Changed my mind | 10-20% | A catch-all absorbing other reasons | | Quality below expectation | 5-15% | Genuine supplier or QC issue | | Ordered multiples intentionally | 5-15% | Bracketing — a sizing-confidence problem | | Damaged or wrong item | 3-8% | Packing or fulfilment accuracy |

Note how many rows point back to something you control before the order ships.

Reading Each Reason Properly

Size and fit This is almost never "the customer got it wrong." It is grading inconsistency: a medium in one style fitting differently from a medium in another. The diagnostic is to plot return rate by SKU against style, not against size. If two styles at the same nominal size return at wildly different rates, the problem is your spec sheet.

Not as described Run the returned items against their PDP images. Colour accuracy under studio lighting and missing scale references cause more of this than copy does. A single lifestyle shot with a human for scale typically moves the needle more than a paragraph of description.

Changed my mind Treat any share above ~15% as a data-collection failure rather than a customer-behaviour finding. Move it to last in the list, require a sub-reason, and watch it redistribute into the categories that are actionable.

Bracketing (ordering multiple sizes) Bracketing is a rational response to sizing uncertainty. Punishing it with fees pushes the whole order away. The durable fix is confidence at the point of purchase — fit guidance, per-SKU sizing notes, and honest review surfacing.

Quality The only reason on the list where the correct response is upstream, in supplier management. Isolate it by batch and supplier before you touch merchandising.

Design Your Reason Codes Deliberately

A reason taxonomy that produces usable data looks like:

  1. Fit → too small / too large / wrong shape / inconsistent with other items
  2. Item not as expected → colour / material / quality / different from images
  3. Delivery issue → late / damaged / wrong item
  4. Ordered more than one option → sizes / colours
  5. No longer needed

Make the sub-reason mandatory on categories one and two, and put "no longer needed" last. That single change usually reallocates 10-15 points of volume into actionable buckets.

Turning Reasons Into Action

Return reason data is only worth collecting if it reaches the person who can act on it. The loop that works:

EcoReturns captures structured reasons and sub-reasons at the point of request and reports them by SKU, so this loop runs without a spreadsheet. You can also model what the current mix costs you in the return cost calculator.

:::cta Want your return reasons broken down by SKU automatically? See EcoReturns.

The Number Worth Tracking

Not total return rate — preventable return rate: the share of returns whose reason maps to something you could have fixed pre-purchase. In most catalogues that is 60-70% of all returns, which is a far more motivating number than the headline rate.