The return experience: what customers actually judge you on

What the return experience is

The return experience is everything a customer goes through from the moment they decide to send something back to the moment the money is in their account: the policy they read, the request they raise, the label, the handover, the wait, the refund, and every message or silence in between. Almost all of it is waiting. The parts a brand can design are a few minutes long, and the part the customer remembers is the days of nothing that follow. The commonest version is the wrong item shipped: the customer fills in a returns form, prints a label and queues at a dropoff point to correct a pick error the warehouse record already showed, and none of that time was theirs to give. This is ordinary volume rather than an edge case: NRF and Happy Returns put returns at 19.3% of online sales for 2025.

What customers actually judge a return on

Five things decide whether a return felt good.

• Effort to start it: whether they can raise the return themselves or must email someone and wait to be allowed.
• Who pays to send it back: the most consequential line in any return policy, and the one read before the purchase.
• How they get it back to you: carrier dropoff, in store, home pickup or box-free, and how far they travel to do it.
• Whether they know where it is: the status of the return between the handover and the refund.
• How fast the money comes back: and whether it returns as money, as store credit or as an exchange.

The preferences are measured. That same NRF and Happy Returns landscape found 82% of consumers cite free returns as a major purchase consideration, up from 76% a year earlier, and 76% are more likely to choose a return option offering an instant refund or exchange. Getting it wrong costs the next order: 71% say they're less likely to shop with a retailer again after a poor experience, and four out of five tell friends and family. That's post-purchase deciding your next quarter for you.

The experience is the waiting, not the interface

Every common remedy is a change to something the customer can see: a better portal, more emails, more dropoff points, a nicer progress bar. None of them shortens the wait, and the wait is where the judgment forms. A return is a few minutes of interface followed by a stretch of silence you control and rarely measure. Three gaps do the damage.

1. Approved to first carrier scan: the label exists, nothing has moved, and nobody knows whether the customer posted it or lost it.
2. Delivered to inspected: the parcel is on your dock, scanned into a receiving bay and sitting there.
3. Inspected to refunded: the decision is made, the money hasn't left, and the customer has neither the product nor the payment.

A customer in the second or third gap has done everything you asked and is being punished for it. That's when they write in. A returns ticket is the second wave of the same WISMO problem: somebody asking where their thing is because the system that knows won't tell them. Answering that ticket doesn't move the parcel or release the money.

The worst return experiences started before the return

Two very different events arrive in the same queue and get the same treatment. A return the customer chose is fit, color, a changed mind, two ordered to keep one: legitimate, expected, and a policy question rather than an operations one. A return the brand caused is the wrong item, the wrong size against the pick list, damage in transit, a short shipment or a delivery exception that landed too late to be useful. Every one of those was visible in a warehouse record or a carrier scan before the customer typed a word. One in five orders hits an operational break after checkout, and the returns queue is where they come back wearing a customer's name.

Sorting the two changes the right answer. A customer running your returns process to correct your mistake is having an experience no portal design repairs, because the process itself is the insult. The right resolution for that group is often not a return at all: a replacement sent before they ask, a credit issued on the spot, a returnless refund on a low-value damaged item. None of those calls can be made from the returns form. They're made from the order.

The part of the return experience that is law

Refund speed gets written about as a preference. In the United States, some of it is law.

• The refund clock: under the FTC's Mail, Internet, or Telephone Order Merchandise Rule, a refund is due within seven working days of the buyer's right to it arising, and a seller who can't ship within the promised time or 30 days has to get consent to the delay or refund promptly. The FTC's prompt delivery rules cover the slipped date, and 16 CFR Part 435 is the text.
• The posted policy: california's Attorney General puts it plainly: there's no general legal right to a refund for a change of mind, and what you post governs. In California, under Civil Code section 1723, a policy more restrictive than a full cash refund within seven days must be posted conspicuously, or the seller is liable to a buyer returning within 30 days.
• What happens when you're late: a customer who stops waiting disputes the charge instead. The chargeback goes to the card issuer, which runs a billing error process on its own timetable, along the path the FTC tells consumers to take. By then the outcome is running on the issuer's timetable, not yours.

I watch brands argue about a 30-day return window while missing a seven-day clock that binds them in the situations the rule covers and a dispute that's already running.

How to measure a return experience honestly

A post-return survey measures how somebody felt about a wait you have already made them do. By then the number is a receipt. Measure the wait itself, as elapsed time in the three gaps, aged by day, with a name against each one.

• Approved, not scanned: returns authorized with no carrier movement, owned by whoever can chase the carrier or prompt the customer.
• Received, not refunded: returns delivered to your warehouse with no refund issued, owned by whoever can clear the receiving bay.
• Refunded, not told: refunds released with no message sent, owned by whoever can send it today.

Those are operational states with an owner, which is what separates them from the customer satisfaction metrics most teams report. And a number on a dashboard is still not a resolution. Something has to act on it before the customer notices.

A good return experience is an operations output

When the wait gets long enough, the work lands on a helpdesk. A helpdesk is a system for replying about problems, not resolving them. It doesn't know the parcel has stalled, decide what your policy allows, or set the refund and the replacement in motion, so the best it can do with the three gaps is describe them politely. That's the shape of the category, not a failing of the people in it.

Proactive e-commerce operations is the category that does the other half: detect, decide, act. Detect the return that has stopped moving, decide what should happen against your policy, act before the customer writes in. We're not a returns portal, not a carrier, not a warehouse management system and not an OMS. We don't design your returns interface, print your labels or run your receiving bay. A return you caused is a promise that broke before the box came back.

Shorten the wait, not just the form

The return approved and never moved, the parcel that landed and stalled, the refund clock nobody is watching, the return that should never have been a return: that's what your customer is judging, and no form redesign fixes any of it. Keeyu reads your order and returns data, decides what should happen next, and acts before the customer has to ask. Every order is a promise. If yours go quiet after the dropoff point, book a demo.

• National Retail Federation and Happy Returns. 2025 Retail Returns Landscape. Returns at 19.3% of online sales; 82% of consumers cite free returns as a major purchase consideration, up from 76%; 76% are more likely to choose a return option offering an instant refund or exchange.
• National Retail Federation. 2025 returns press release, consumers expected to return nearly $850 billion in merchandise. 71% of consumers are less likely to shop with a retailer again after a poor experience, and four out of five will tell friends and family.
• Federal Trade Commission. Business Guide to the Mail Order Rule. Formally the Mail, Internet, or Telephone Order Merchandise Rule. A refund must be made within seven working days of the buyer's right to it arising.
• Federal Trade Commission. Selling on the Internet: Prompt Delivery Rules. Shipping in the stated time or within 30 days, and what a seller owes the buyer when it cannot.
• eCFR. 16 CFR Part 435. The text of the Mail, Internet, or Telephone Order Merchandise Rule.
• California Office of the Attorney General. Refund Policies. There is no general legal right to a refund for a change of mind; the posted policy governs.
• California Legislative Information. California Civil Code section 1723. A policy more restrictive than a full cash refund within seven days must be posted conspicuously, or the seller is liable to a buyer returning within 30 days.
• Consumer Financial Protection Bureau. What is a chargeback?. What happens once a customer disputes a charge rather than waiting for a refund.
• eCFR. 12 CFR 1026.13, Billing error resolution. The creditor's obligations and timetable once a billing error notice is received.
• Federal Trade Commission. Disputing Credit Card Charges. The consumer-side path a stalled refund pushes a customer onto.