Brands spend months on checkout and install a returns app in an afternoon. Yet the portal is where a disappointed customer decides whether you’re worth another try. It has steps, a conversion rate (to exchange) and abandonment: the customer who gives up and emails support, or calls their bank.

The steps

1. Find the orderA link in every shipping and delivery email that opens the return for that order. Failing that, email and ZIP or postal code. Never require an account or an order number the customer has to hunt for.
2. Pick the itemsWith photos, sizes and colors shown, so a multi-item order isn’t a guessing game.
3. Give a reasonOne tap from a specific list, with an optional line of detail. A photo only for damage or a wrong item. Chapter 10 covers the list.
4. Choose the outcomeExchange first, store credit second, refund plainly visible. Chapter 7.
5. Choose how to send itBox-free drop-off, printed label, or pickup, with any cost shown here and, earlier, on the policy page.
6. ConfirmWhat happens next and when the money or the new item moves, in dates, not “processing times vary”.

Then the messages: at first scan, when the refund or credit is issued, and when an exchange ships. They’re transactional, with no promotions stacked on top; anything promotional goes only to customers who agreed to marketing.

Make the trip itself easy

Effort is one of the two dimensions that raised purchases in the meta-analysis in chapter 2. In the 2024 NRF and Happy Returns survey, 84% of consumers said they were more likely to shop with a retailer offering returns with no box, no label and an immediate refund Reported. Happy Returns, a UPS company, runs box-free drop-off points, so that’s vendor data, and stated preferences run ahead of behavior. The direction is still right.

The customer who can’t finish your return portal doesn’t disappear. They email support, post a review, or call their bank.

Skip the return when you can

A damaged, wrong or missing item isn’t a return; it’s your mistake. Send the replacement, ask for a photo if the carrier claim needs one, and don’t make the customer ship anything back.

What to measure

Starts to completions in the portal; return tickets per 100 returns (every “how do I return” email is a portal failure); days from request to first scan; and the outcome mix, weekly.

Do this

• Return something from your own store on your phone, starting from the delivery email, with a stopwatch running. Count taps and seconds, and note every moment you’d have emailed support instead. Then do it again as a customer who deleted the email.