The RMA process is a set of timers, not a flowchart

What the RMA process actually is

The RMA process is the sequence an e-commerce brand runs when a customer sends an order back: the request, the approval, the return merchandise authorization number that makes it official, the return leg, inspection, disposition, and the refund that closes it out. Every version of it you'll find drawn is a line that finishes. The ones that break don't fail at a step, they stall between two of them, and every stall has a clock running against it that nobody is watching. When we point Keeyu at a brand's returns queue and ask how many are stuck, the answer is a list: parcels booked in at the warehouse, stock never put back, refunds never issued, all of it days old.

This is volume, not an exception. NRF and Happy Returns put 19.3% of online sales on the return path in 2025, against 15.8% of annual sales across retail.

The seven states an RMA moves through

Before any of this there are rules: the return window, whether a restocking fee applies and at what percentage, and who pays return shipping. On Shopify those are return rules set at store level before a single request arrives. Then the return moves. What matters isn't the order of the states, which nobody disputes, but who's holding the order in each one and what has to be true for it to leave.

1. Requested: the customer asks. Held by the storefront or the returns portal. Leaves on a decision.
2. Approved or declined: held by whoever owns the policy. Leaves on an RMA number being issued.
3. Authorized, not yet shipped: held by the customer. Leaves on the first carrier scan.
4. In transit: held by the carrier. Leaves on delivery to the returns address.
5. Received, not yet inspected: held by the warehouse. Leaves on an inspection outcome.
6. Dispositioned: held by whoever decides restock, refurbish, scrap or reject. Leaves on that decision being recorded against the RMA.
7. Closed: refunded, replaced or exchanged. It leaves nowhere. This is the end.

The clocks nobody puts on the process map

A process map tells you the order of things and nothing about how long any of them is allowed to take. The law already answered that, and most brands have never read the answer.

• US, mail and internet orders: the FTC's Mail, Internet, or Telephone Order Rule defines a prompt refund as one sent within seven working days of the buyer's right to it vesting.
• US, card refunds: Regulation Z gives a merchant seven business days from accepting the return to transmit the credit statement to the card issuer, and the issuer three business days to credit the account.
• EU: the Consumer Rights Directive requires reimbursement within 14 days of the trader being told of the withdrawal, though it may be withheld until the goods are back.
• UK: the Consumer Contracts Regulations set the same 14 days, counted from the day the goods come back or the day the customer produces evidence of sending them, whichever is earlier.

Read those as an operator. The clock doesn't start when somebody gets around to the RMA, and it doesn't pause because a parcel sits unscanned on a receiving dock. Every state above burns a statutory deadline, and in most brands nothing is counting.

The four places an RMA stalls

In each of these the systems are individually correct and the customer is individually stranded. Nothing is broken. Everything is stalled.

Authorized, never shipped. The number is issued and the parcel never enters the carrier network. Nobody notices: the return reads as in progress, and inventory stays committed to a unit still in the customer's hallway.

Delivered, never received. The carrier scan says the parcel reached the returns address and no warehouse system has booked it in. The customer notices first, holding a delivery confirmation nobody can match. USPS returns postage is charged when the label is used, a signal the merchant pays for and never reads.

Received, never inspected. The item is booked in and joins a queue waiting on a disposition decision. Nobody notices, because every system believes its own leg completed.

Inspected, never refunded. Disposition is recorded and the money doesn't move, because the refund is a manual step somebody has to remember. Shopify's documentation is blunt that return fees aren't deducted from a refund automatically, so this state needs a person and stalls without one.

At most brands nothing fires until the customer emails, and the RMA becomes a ticket. Name that default precisely: a helpdesk is a system for replying about problems, not for resolving them. Answering the customer and moving the return are different jobs, and only one stops the clock. The second is proactive e-commerce operations, not a better helpdesk.

What to measure on the return path

Return rate is a demand metric. It tells you how much is coming back and nothing about whether your process is moving it. Measure durations instead, against the seven states.

• Time in state: how long an RMA spends in each state, read as the tail rather than the average. The average is always fine. The tail is where the refund deadline gets missed.
• Received-to-refunded: elapsed time from the item being booked in to the money moving. This is what the statutory clocks measure, and it spans the warehouse and the finance system, so it tends to live in neither.
• Return rate, split online against total: capacity planning only. It has been steady, with NRF putting returns at 16.9% of annual sales in 2024, and it says nothing about whether the queue is moving.

Every one of those is a duration, and a duration only exists if something watches between two events. Your order management system records the events. Watching the gap between them is a separate job nobody has been given.

Designing a process that does not wait for a complaint

Detect the stall from events your systems already emit: the first carrier scan, the delivery scan, the warehouse book-in, the disposition record. Every failure mode above shows up as the absence of an expected event inside an expected window, which is a detectable condition rather than a feeling. Those events are addressable: Shopify's return management documentation models requesting, approving, refunding and disposing as separate operations. What the documentation doesn't model is a judgment that a return has been sitting in one of them too long.

Decide against the promise and the clock, not against a queue position. ISO 9001 helps here precisely because it's tool-neutral. Its clause on control of nonconforming outputs treats disposition as a named, recorded decision with defined options: correction, segregation, return, informing the customer, obtaining concession. If a standards body calls it a decision, an e-commerce brand can stop calling it a step. Act: refund, replace, re-route to the correct returns address, or tell the customer where their return is before they ask. That's post-purchase operations doing the job the process map assumed somebody would do.

What this does not fix

Keeyu doesn't issue RMAs and doesn't run your returns process. We're not a returns portal, not a returns platform, not a carrier, not an OMS and not a QMS, and we replace none of them. What we do sit on is the stall between the states, the part no returns system was built to own. The other edge is worth saying too. A better RMA process doesn't reduce the number of returns you get. Sizing, product quality and expectation setting decide that, and it's a different argument. This one is about what happens to a return once it exists.

Where Keeyu sits on the return path

An RMA that's authorized and stationary isn't a support problem. It's a promise with a statutory clock running against it and no owner. Every order is a promise, and a return is that promise being renegotiated. Keeyu detects the return that has stopped moving, decides what should happen against the deadline rather than the queue, and acts: refund, replace, or tell the customer before they have to ask. See what the Keeyu platform does across your post-purchase stack.

• Federal Trade Commission. Mail Order Merchandise Rule business guide. What a prompt refund means and when the buyer's right to one vests.
• Electronic Code of Federal Regulations. 16 CFR 435.1. The rule text: a refund sent by any means at least as fast and reliable as first class mail within seven working days of the right to refund vesting, or within one billing cycle where the refund is a credit to a card account.
• Electronic Code of Federal Regulations. 12 CFR 1026.12(e), Regulation Z. Seven business days for the merchant to transmit a credit statement to the card issuer, three business days for the issuer to credit the account.
• EUR-Lex. Directive 2011/83/EU on consumer rights. Reimbursement within 14 days of the trader being informed of the withdrawal, with the right to withhold until the goods are returned.
• legislation.gov.uk. Consumer Contracts Regulations 2013, regulation 34. Reimbursement within 14 days of the goods coming back or of evidence of return, whichever is earlier, by the same means of payment and with no fee.
• National Retail Federation and Happy Returns. 2025 Retail Returns Landscape. An estimated 19.3% of online sales returned in 2025.
• National Retail Federation. Returns to reach $849.9 billion in 2025. Retailers estimate 15.8% of annual sales returned, totaling $849.9 billion.
• National Retail Federation and Happy Returns. 2024 retail returns total $890 billion. Retailers estimated 16.9% of annual sales returned in 2024, the year-on-year comparison for the figure above.
• International Organization for Standardization. ISO 9001:2015, Quality management systems. Clause 8.7, control of nonconforming outputs: disposition as a recorded decision with defined options, correction, segregation, return, informing the customer, obtaining concession.
• Shopify Help Center. Setting up return and cancellation rules. Return windows, restocking fees as a percentage, return shipping fees, and that return fees are not deducted from a refund automatically.
• Shopify. Build for return management. The platform's own return model: a return is the buyer's intent to send items back, with requesting, approving, refunding and disposing as separate operations.
• United States Postal Service. Customer returns label services. Scan-based returns are priced per piece and per label scanned, and the merchant is charged postage when the return package is shipped.