The return process, and the decision inside every stage

What the return process is

The return process is the sequence an e-commerce brand runs after checkout, from the moment a customer asks to send something back to the moment the money or the replacement lands and the unit is accounted for: request, label, receive, inspect, decide, resolve. Every guide describes it as a conveyor, work that happens with nobody named. It's not. It's a chain of decisions with a legal clock running on it, and the part that costs real money is the decision that never gets made. When we scanned one brand's returns portal, RMA workflow, store and 3PL together, we didn't find a broken step. We found six returns sitting unprocessed for five to fourteen days each, stock not put back, refunds not issued, fifty days of backlog nobody had a number for.

It's also not the return policy: the policy is the rulebook, the process is what runs against it. NRF puts 19.3% of online sales on the returns leg in 2025.

The six stages, end to end

Stage counts differ from one guide to the next. The chain underneath does not, and Return isn't a blog construct: ASCM carries it as one of the top-level processes in the SCOR reference model, alongside plan and source. Here it's with an actor named at every stage, because the actor is the part that goes missing.

1. Return request and authorization: the customer names an item, a reason and the outcome they want, and the brand checks it against policy and issues an authorization number, which is what an RMA is.
2. Label and return shipping: prepaid label, customer-paid postage, or a QR code at a drop-off point. USPS prices its return services per label scanned, so you pay only for labels that get used, which is also why unused ones sit invisible.
3. Receiving and intake: the parcel arrives and is scanned against the original order. This is the hinge of the sequence: until that match is made, every system in the business still believes the goods are in transit, and nothing downstream can start.
4. Inspection and grading: condition is assessed against a grade, and the reason the customer gave is confirmed or corrected. A worn item and an unopened one take different paths from here, and the grade decides which.
5. Disposition: the graded unit goes one of five ways: back to sellable stock, to refurbishment, to a liquidator, to donation, or to disposal. That's a margin decision, made per unit, and usually made by a rule.
6. Resolution and closeout: refund, exchange or credit is issued, the inventory position is updated, the order is closed. It's a line-item decision rather than an order-level one, which is why partial returns break more systems than whole ones.

The decision inside each stage

Read those six again and notice what is missing. Everyone writes them in the passive, as work that happens. Every one of them is a decision, and in most brands the thing making it is a person reading a queue.

• Authorization: is this within policy, and does the exception get made? Owner today: a support agent with the policy page open in another tab.
• Shipping: who pays for the return leg, and does the label go out at all? Owner today: whoever configured the portal once, months ago.
• Intake: did this parcel get matched to its order? Owner today: nobody, until somebody asks.
• Inspection: is this condition acceptable, and against whose grade? Owner today: a warehouse operator working from a printed sheet.
• Disposition: is this unit worth more restocked or liquidated? Owner today: an inventory rule nobody has reviewed this year.
• Resolution: refund now, on receipt, or on inspection? Owner today: a finance approval queue.

Look at what Shopify asks of an operator and the shape is unmistakable: processing one return is five separate manual actions in the admin, each needing somebody to come back to it. Your order management system records the state those actions leave behind. It makes none of them.

The clock nobody puts on it

The US isn't one clock. There's no federal right to return an unwanted item, which surprises people. State law is what exists: California requires a retail seller with a restrictive refund policy to display it conspicuously, and one that doesn't is liable to the buyer for the purchase amount if the goods come back on or before the thirtieth day after purchase.

The replacement leg of an exchange is a shipment in its own right, so the FTC's Merchandise Rule applies: ship inside the window you advertised, or 30 days if you advertised none, and where you cannot, 16 CFR 435.2 requires you to offer the buyer a delay or a prompt refund.

If you ship into the UK or the EU, the clock is uniform and tighter: three statutory deadlines run against this sequence. The consumer has 14 days from delivery to cancel, then 14 more days to send the goods back, and the trader must reimburse within 14 days of receiving them or of evidence they were sent, whichever is earlier. The same regulation lets the trader deduct value lost to handling beyond what was necessary to establish the nature, characteristics and functioning of the goods, the legal footing under stage four's grading. The EU consumer rights directive carries the same three windows. A deadline on a decision nobody owns gets missed quietly.

Where the return process stalls

One in five orders hits an operational break somewhere after checkout. A stalled return is the most expensive place for it to happen. A stall doesn't look like a failure. It looks like nothing happening, inside a flow NRF sizes at $849.9 billion for 2025.

The parcel that arrived and was never scanned. The carrier delivered it, intake never matched it to an order, and every system still shows the return in transit. The refund clock has run since the day it landed and nothing is counting.

The refund approved and never issued. Approved in one system, unpaid in another, with nothing reconciling the two states. This is how a statutory deadline gets breached without anybody deciding to breach it.

The exchange promised and never fulfilled. The return closed cleanly, the replacement never shipped, and the order reads as complete to everyone except the person waiting for it.

In all three the customer finds out first, and they tell you by opening a where-is-my-order ticket about a broken promise. A helpdesk is a system for replying about problems, not resolving them, so the ticket gets an answer and the return stays where it stopped. The manual checks aren't the fault: NRF finds 9% of returns fraudulent and 45% of shoppers saying that bending the rules is acceptable, so somebody inspecting is defensible. The silence afterwards is not.

What to measure

Four numbers will tell you whether the process above is finishing.

• Return-to-refund cycle time: days from the carrier scan to the refund landing. This is the single number the statutory clock is measured against.
• Intake scan lag: hours between the delivery scan and the return being matched to its order. A rising number here is the first stall, made visible.
• Return exception rate: the share of returns that needed a human to unstick them. Not the same as your return rate, and far more useful than it.
• Resolution SLA breach rate: the share of returns that passed a statutory or promised deadline before they closed.

Track those four and the stalls stop being anecdotes.

Detect, decide, act on the return path

Here's the edge of it. Keeyu isn't a returns portal, not a returns management system, not a 3PL and not a carrier, and we don't run the process above. We watch the path each return takes and act when a step doesn't complete: the parcel that landed unscanned, the refund approved and not issued, the exchange closed and not shipped. We detect the break, decide what should happen and act, usually before the customer knows anything went wrong. That's proactive e-commerce operations, not a better helpdesk. A helpdesk answers the customer. We finish the return.

Every order is a promise, and a return is that promise being unwound, which is a promise of its own with a clock on it. If your returns stall between a portal, a warehouse and a payment system, none of the three will tell you. Keeyu watches all of them and closes the step that stopped. Book a Keeyu demo and bring your oldest open return.

• National Retail Federation and Happy Returns. 2025 Retail Returns Landscape. An estimated 19.3% of online sales returned in 2025, 9% of all returns fraudulent, and 45% of shoppers who say bending the rules is acceptable.
• National Retail Federation. Returns projected at $849.9 billion in 2025. Total returns projected at $849.9 billion, 15.8% of annual retail sales.
• ASCM. SCOR Digital Standard. Return as a top-level supply chain process in the reference model, alongside plan and source.
• United States Postal Service. Business Return Services. Priority Mail Express Return, Priority Mail Return and USPS Ground Advantage Return, all priced per piece and per label scanned, with the merchant charged when the return package ships.
• Shopify. Creating and processing returns and exchanges. Official product documentation for the Shopify admin: receiving the items, choosing a restock location, releasing exchange items, refunding shipping and issuing the refund are five separate manual actions an operator returns to the admin to perform.
• UK Statutory Instrument 2013 No. 3134. Consumer Contracts Regulations 2013, regulation 30. The cancellation period ends 14 days after the goods come into the consumer's physical possession.
• UK Statutory Instrument 2013 No. 3134. Regulation 35. The consumer must send the goods back without undue delay and no later than 14 days after informing the trader, and bears the direct cost of return unless the trader agreed otherwise or failed to disclose it.
• UK Statutory Instrument 2013 No. 3134. Regulation 34. Reimbursement without undue delay and within 14 days of receiving the goods back or of evidence they were sent, plus the deduction available where handling beyond what is necessary to establish the goods has diminished their value.
• European Union. Directive 2011/83/EU on consumer rights, consolidated text. The 14-day right of withdrawal, 14 days for the consumer to return the goods and 14 days for the trader to reimburse.
• California Legislative Information. California Civil Code section 1723. A retail seller with a restrictive refund policy must display it conspicuously, and a seller that does not is liable to the buyer for the amount of the purchase where the goods are returned on or before the thirtieth day after purchase.
• Federal Trade Commission. Business guide to the Merchandise Rule. The advertised shipping window, the 30-day default where none is advertised, and the seller's duty to offer a delay or a refund.
• Electronic Code of Federal Regulations. 16 CFR 435.2. The statutory text: shipment within the time stated or within 30 days of a properly completed order, and the consent-to-delay or prompt-refund option that must be offered no later than that time.