ASOSCraft5 min read

Returns as the real product

Fashion online only works if sending it back is boring.

The surface: The returns path in the app and site: the returns policy shown before purchase, the order history, the reason picker, the label or QR code, and the refund status.
What the user wants: I ordered three sizes because I could not tell which would fit. I want to keep one and get my money back for the others without it becoming a project.

The policy stated before purchase

The returns window and conditions are surfaced on product and checkout pages rather than buried in a footer link only.

Risk reversal

The blocker to buying clothing unseen is not price, it is the fear of being stuck with the wrong thing. Stating the return terms at the moment of hesitation removes that fear while it is live. The policy is functioning as conversion copy, not as legal text.

Ordering multiple sizes

Nothing in the flow discourages adding two or three sizes of the same item to one order, and the returns process handles a partial return of an order as a normal case.

Designing for the real behaviour

Buyers were already bracketing sizes, so the choice was whether to fight it or support it. Treating a partial return as the default path rather than an exception removes the sense of having done something wrong. The cost lands on logistics, which is a tractable problem, rather than on trust.

Picking a reason

Starting a return asks for a reason from a short list, most of which are about fit, and the flow does not require free text.

Low friction input with a second purpose

A short list keeps the step to one tap, which matters because this is the moment a frustrated customer is most likely to give up and complain instead. The structured reason also feeds sizing data back into the product pages. One tap serves the customer and the catalogue at once.

The label

The flow issues a printable label or a code scanned at a drop off point, so the customer does not need a printer.

Remove the hidden prerequisite

The printer was the real barrier in returns for years, and no amount of good copy solves a missing device. Replacing it with a code on a phone removes the step where the customer stalls for a week. Most returns friction is logistics wearing an interface costume.

Refund status

Order history shows the return moving through received and refunded states, with an expected timeframe stated.

Uncertainty reduction

The period between handing over a parcel and seeing money return is where trust is lost, because the customer has given up the goods and has nothing. A visible state, even a slow one, replaces worry with waiting. Stating the timeframe up front turns a delay into an expectation rather than a failure.

The flow that decides whether they order again

A schematic hundred returns. In a category where nobody can judge fit before it arrives, this is not a cost centre bolted onto the real product, it is the conversion surface. Every step that leaks here is a customer who orders one size next time, or none.

What not to copy

Free returns have been steadily reduced across online fashion, including at ASOS, with fees applied below spend thresholds and account action threatened for frequent returners. Building demand on a promise and then charging for it later is a bait the customer had no way to price in.
Tracking returners and restricting accounts punishes the behaviour the sizing problem causes. If the catalogue cannot tell a customer which size fits, high return rates are a product failure being billed to the user.
Refund timelines are stated as ranges and measured from receipt at the warehouse, not from drop off. The gap where the parcel is in transit and the money is gone is the worst part of the experience and is the least instrumented.
Return reasons are collected far more reliably than they are visibly acted on. Fit feedback that never changes the size guidance is data collection dressed as listening.

The takeaway

In categories where the customer cannot judge the product before it arrives, the return flow is the conversion surface. Fund it like one.

Finished the teardown? Bank it and the day counts toward your run.

Where the principles come from

Thinking, Fast and Slow, Daniel Kahneman
The Design of Everyday Things, Don Norman
Ecommerce Returns: Usability Guidelines, Nielsen Norman Group

Written from public behaviour of the product, not from inside it. Interfaces change often, so treat the flow described here as of the time of writing and check the live product before quoting it.