How to reduce apparel returns: the levers sellers report actually working

Online skews returns, and apparel skews worst of all. The NRF and Happy Returns' 2025 Retail Returns Landscape (published October 15, 2025) puts estimated 2025 returns at 19.3% of online sales against 15.8% of total retail — and clothing is the category where the customer never got to touch the product before buying. So the question isn't whether you'll have returns; it's which levers actually shrink the number, and how you'd know.

The uncomfortable answer from merchants who've worked on it: most of the gain comes from unglamorous fit infrastructure measured per SKU, not from policy changes or fees. This piece walks the sequence in order — baseline your returns by reason, pull the fit levers sellers report working, fix the ads that oversell, and run one lever per season so you can tell signal from noise.

Baseline first: returns by SKU and by reason

You can't reduce what you haven't decomposed. Before touching a single product page, pull your last 90 days of online returns and build two views:

• Return rate by SKU. Which products return at 3× your store average? Those are your lab.
• Return rate by reason. Shopify records a reason per return; export it and count.

Here's an illustrative pull for a store selling heavyweight hoodies and merino hiking socks, online-only:

Against 1,480 orders shipped, that's a 14.5% return rate. The sizing-reason share is the number that matters most: 96 of 214 returns, or 45%. Two implications follow immediately.

First, the ceiling. If every fit fix worked perfectly, your rate falls to (214 − 96) ÷ 1,480 = 8.0%. Fit levers cannot touch the other 55% — changed minds and ad overselling live elsewhere. Second, the realistic target. Halving the sizing share takes the rate from 14.5% to about 11.2%, and that would be an excellent season's work. Merchants who promise to "eliminate returns" are promising to eliminate customers.

One bookkeeping warning while you're in the data: don't net returns against sales velocity naively when you reorder, or your best-fitting SKUs look slower than they are. The clothing inventory guide covers size-curve buying and how to book returns against velocity without corrupting it — this article stays on the reduction side of that line.

The fit levers sellers report actually moving the number

Two r/shopify threads in 2026 asked essentially the same thing — one in October asked sellers what they'd tried to cut apparel returns and what genuinely moved the figure; one in March described returns creeping up with the merchant suspecting their own ads. The answers cluster on the same short list. Framing matters here: these are merchant reports, not audited benchmarks. The honest status of each lever is "sellers credit this," and the only number that counts is your own before/after.

Garment measurement charts, not S/M/L labels. Flat-lay measurements per size — pit-to-pit, body length, sleeve, rise — let a buyer compare against a garment they already own and love. Letter sizes are a bet; inches are an answer. This is the most-cited lever in the threads, and it's cheap: one measuring session and one table per style.

A "runs small / runs large" note on the product page. One specific line per style, written from your own returns data: "Runs one size small; size up for a layering fit." Vague guidance helps nobody, and style-specific guidance kills a slice of sizing returns on its own.

Model-size and garment-fit disclosure in the photos. "Model is 180 cm / 83 kg wearing L" plus a sentence on the cut ("boxy, drops a size"). Several sellers in the October thread credited better photo accuracy with fewer "not as described" returns — the photo that flatters the fabric but misrepresents the drape is quietly manufacturing returns.

Review-mining for fit language. Your reviews and support inbox already contain the fit truth. Mine them quarterly for phrases like "sleeves short" or "waist tight," and feed the language back into the product page and the size note. Customers trust other customers' fit descriptions more than yours anyway — free copy, already tested.

Exchange-first flows. When a return request comes in, offer the exchange before the refund; Shopify's native returns flow supports this (Shopify Help Center, accessed October 2026). Why it matters for inventory specifically is below.

Packaging that survives one try-on. The cheapest poly mailer tears on first opening, and now a fit exchange has become a "damaged" return. If your packaging can't survive the customer trying the garment on once and repacking it, you're converting would-be exchanges into full refunds to save pennies on a mailer.

The ads angle: overselling creative manufactures returns

The March 2026 thread contained the sharpest self-diagnosis in either discussion: returns creeping up, and the merchant suspecting the ads were overselling the product. The mechanism is worth spelling out because it produces a specific return signature. Creative that exaggerates drape, color saturation, fabric weight, or fit creates an expectation the delivered product can't meet, and the mismatch comes back as "not as described" returns concentrated on the SKUs you're pushing hardest.

The audit takes an hour. Take your top three ads by spend, put the ad still-frame next to a photo of the actual delivered product, and check every implicit claim: how the fabric hangs, how saturated the color is, how fitted the cut reads. If your highest-spend creative features a model swimming in an oversized sample while the real garment is semi-fitted, you've found a return machine. Either fix the creative or fix the garment — but stop paying to create the mismatch every day.

Why exchange-first beats refund-first for inventory

An exchange keeps the unit sold. The customer keeps their money inside your store, the revenue stays on the books, and the physical event is a size swap instead of a sale reversal. A refund zeroes the margin, puts a tried-on unit back on the shelf, and still re-runs the whole pick-pack cycle for the replacement order.

Exchange-first also quietly fixes the sizing problem itself: the customer who ordered M and needed L resolves it in one flow, at one shipping cost, instead of refunding and re-ordering — or walking. For sizing-driven returns, the exchange isn't the consolation prize; it's the actual fix.

The physical side — receiving the returned unit, inspecting it, deciding whether it can restock as new — is a separate discipline with its own decision table; returned inventory processing owns that flow. Reduction is about stopping units from traveling that road in the first place.

What doesn't move the number

Two popular "fixes" fail in predictable ways:

• Making returns hostile. Banning returns or burying the policy doesn't stop fit-driven returns — it stops fit-driven purchases. The measured return rate falls while silent churn rises, which is the same loss wearing a disguise. Policy design (window length, condition rules, who pays freight) is its own craft; returns policy design covers what a workable apparel policy looks like.
• Blanket restocking fees. A flat fee on every return taxes your honest fit-uncertain buyer — the exact person a measurement chart would have saved — as heavily as the serial abuser. It changes who returns more than why they return, and it trains customers to overstate reasons. The tradeoffs and the narrow cases where fees earn their keep are laid out in the restocking fee guide.

Neither touches the sizing-reason share, which is where your reducible percentage actually lives.

The measurement loop: one lever per season

The failure mode of return-reduction projects is doing six things at once, watching the number move, and having no idea which lever did it. The alternative is boring and works: one lever per season per category, tracked by SKU.

The attribution is the point. If you changed four things between two seasons, a move from 14.5% to 12% tells you nothing about what to double down on. One lever per season tells you exactly what to keep, and the SKU-level view stops a soft category from hiding a hoodie problem — store-wide averages dilute exactly the SKU that's paying for the lever.

When you price whether a lever was worth it, use what each return actually costs you as the unit of account. A prevented return saves its full cost — label, labor, refund, and the worn unit back in stock — and that number is what the measuring session and the photo reshoot are competing against.

Common questions

What is a normal return rate for online apparel? Online skews returns: the NRF/Happy Returns 2025 Retail Returns Landscape (October 15, 2025) estimates 19.3% of online sales returned versus 15.8% of total retail, with apparel at the high end. Your benchmark is your own history by SKU — a store-wide average hides the hoodie returning at 30%.

Do size charts actually reduce returns? Sellers in r/shopify consistently credit garment-measurement charts — flat-lay inches, not S/M/L — with cutting sizing returns, but there's no public benchmark. The honest test is your own: pull the sizing-reason share, add the chart, and compare sizing returns on that SKU season over season.

Are restocking fees a good way to reduce returns? They change who returns more than why. A blanket fee taxes the honest fit-uncertain buyer as hard as the abuser and can push fit-shy purchases to competitors with free returns. If you use one, scope it narrowly — the restocking-fee tradeoffs deserve their own read before you commit.

Do exchanges count as returns? The request may be booked as a return, but an exchange keeps the unit sold: revenue stays on the books, and the physical event is a size swap rather than a refund. That's why exchange-first flows lower the cost of returns without necessarily moving the request rate itself.

Could my ads be causing my returns? If "not as described" returns concentrate on the SKUs you advertise hardest, yes — oversold creative manufactures expectation mismatch. Lay your top ads' still frames next to the delivered product and check drape, color, and fit claims. Fix the creative or the garment; stop paying for the gap.

Next step

Pull the 90-day reason-code table — Shopify's returns report exports take ten minutes — and compute your sizing share. That one number decides everything: if it's over 40%, start with a measurement chart on your single worst SKU this week. One lever, one season, one before/after you'll actually check. For the buying-side implications of what you find — size curves, and how returns should and shouldn't adjust velocity — the clothing inventory guide picks up where this one stops. When the return reason is transit damage rather than fit, the workflow shifts — customer damage claims covers the triage.