Return request: the ask that starts a clock you can't see

What a return request is

A return request is the moment a customer tells an e-commerce brand, after checkout, that they want to send something back, and the record the brand creates in response. It's not a form submission. It's a customer starting a clock you're legally bound to, and the ones that cost you money started somewhere your returns portal can't see. We watch brands running a good portal that still take around 400 messages a month asking how to send an item back. Every one of those is a live request. None of them is a row in the portal.

Two adjacent things get called a return request. The RMA is the authorization you issue in reply, so it can't exist until you have answered, and it's the step where returns actually break. The refund is the last move, not the first. The volume underneath isn't small: NRF put 19.3% of online sales on the returns leg in 2025, inside a projected $849.9 billion of total retail returns, against a channel that reached 16.9% of US retail sales in the first quarter of 2026.

What is actually in a return request

Take the branding off any returns portal and the same six fields sit underneath. The first four are what every system captures. The last two decide whether the request gets resolved.

• Order and item: which order, which line, which variant. An order number alone isn't actionable on a multi-item shipment.
• Reason: the customer's own words, before your dropdown flattens them into "other". It's the only field that changes what you buy next.
• Condition claimed: unopened, worn once, faulty. A claim, not a fact, which is what the inspection step exists to test.
• Outcome wanted: refund, exchange, credit or repair. Two of those commit you to shipping something out again, which returns reporting rarely counts.
• Date of the ask: the day the customer told you, not the day your system logged it. Every clock in this article runs from that date.
• Channel it arrived on: portal, email, chat, phone or a direct message. Not metadata: it's the difference between a request your operations team can see and one only an agent can.

The three answers, and what each one commits you to

A request forces a decision, and there are only three. Each commits you to something different, costs something different, and needs different authority behind it.

• Approve: you commit to a label, an inspection, a refund and stock returning to a sellable state. The cheapest answer to give and the most expensive to leave half done. It's also the easiest answer to give without a second check.
• Decline: you commit to defending the reason. Outside the statutory windows and against a policy you actually published, a decline is fair, and a short list of exempt goods covering custom-made, perishable and sealed hygiene items holds even inside them. Inside a window and outside that list it's not a judgment call, so the answer belongs with someone senior enough to know the difference.
• Ask for more: a photo, an order number, a condition check. The only answer that doesn't stop the clock, which is why it's the one that quietly becomes no answer at all.

The real failure mode isn't a wrong answer. It's no answer: the request that sits unread over a weekend, or waits on a photo nobody opened, while the window runs down and nobody holds the file.

The request that never touched your portal

Here's the part most operations teams have never been told. A return request is whatever the customer says it is, on whatever channel they say it on, and at least one legislature has written that down. Under the UK's Consumer Contracts Regulations 2013, a customer canceling a distance contract may use the model cancellation form, or:

make any other clear statement setting out the decision to cancel the contract

That's regulation 32, and it goes further. If you offer a form on your website the customer need not use it, and if they do, you must acknowledge receipt on a durable medium without delay. In a dispute it's the customer who has to show the contract was canceled inside the period, which is exactly why they screenshot the chat window. So an email, a live chat message or a direct message is a return request. Where those regulations apply, the clock is already running. Your portal has no row for it, your returns report doesn't count it, and the first person to find out is an agent reading a thread three days later. Where the request did come through that form, the acknowledgment is a duty rather than a courtesy, and it has to leave your systems whether or not the rest of your returns stack knows the request exists.

The reason so many requests arrive as email instead is upstream. Every system after the buy button does its own job and none of them is designed to detect that the promise is breaking, so the failure is silent and the shopper improvises, which is how I described it on Marketing for SMEs. A portal collects the requests that know they are requests.

The clock that starts when the request lands

Jurisdictions time the request differently, and the three below that name a single statutory clock are UK. The one rule that holds everywhere: the dates run from the customer's ask, not your workflow.

• California, post the policy or 30 days: a retail seller with a restrictive refund policy must post it conspicuously, or owes the buyer the purchase amount on a return attempted within 30 days of purchase, under Civil Code section 1723.
• UK, 14 days to ask: the cancellation period ends 14 days after the goods reach the customer, and on a part-delivered order it runs from the last item, per regulation 30.
• UK, 14 days to send back: the customer must send the goods off within 14 days of telling you, under regulation 35, and bears the direct cost unless you never said so.
• UK, 14 days to refund: you reimburse without undue delay and within 14 days of getting the goods back or evidence they were sent, says regulation 34, deducting only for handling beyond checking the goods.

One clock gets missed. If the answer is an exchange, the replacement leg is a shipment in its own right, and the shipping-window standard in 16 CFR 435.2 is the one to hold it to: a reasonable basis to expect shipment inside the time advertised, or 30 days where none was advertised.

The clock only matters if something is watching it. Every point solution in the chain does its own job and none of them is built to detect that a commitment is about to be missed, so the failure is silent and the shopper is the alarm, which is how I described it on Marketing for SMEs. A refund deadline is a legal fact. Whether anyone notices it passing is an operational one.

The approved request that goes quiet

An approved request isn't a resolved one. The label is issued and never used, or never issued at all. Or the parcel is scanned in and the refund is never released. USPS prices its return services on labels scanned, not labels issued, so a label nobody used never bills you and never scans. The customer finds out first and tells you by opening a ticket, which isn't the problem but the receipt for a promise that broke days earlier.

Being straight about the edges: a helpdesk answers the customer, and it can't fix the order, because a ticket only ever opens after the break has already happened. Keeyu is proactive e-commerce operations. It's not a returns portal, not a returns management system, not a 3PL, not a carrier and not a helpdesk. We don't take the request and we don't run the return, and the full sequence sits in the return process end to end. We watch the return path against the promise, catch the step that stopped and act on it.

Every order is a promise, and a return request is a customer asking you to make good on one. If yours are approved and then go quiet, another portal isn't the fix. Keeyu detects the approval that never became a label or a refund, decides what should happen, and acts, usually before the customer knows there's anything to chase. Book a Keeyu demo and bring your oldest open return.

Silence after approval is measurable, which means it is preventable. We watch for a return that has not moved between states inside its normal window and resolve it automatically, alongside parcels that have not left the warehouse and payments that failed, which is the set I described on Add To Cart. Nobody needs to remember to check. The clock does it.

Related reading

• Return shipping fee: who pays, and who actually caused it
• Returnless refunds: the decision a price threshold can't mak
• Ecommerce returns: the half of your return rate you caused
• Delivery exception: what it means and how to act on it

• UK Government. Consumer Contracts Regulations 2013, regulation 32. A consumer may cancel using the model form or any other clear statement of the decision to cancel; a trader offering an on-site form must acknowledge receipt on a durable medium without delay; in a dispute the consumer must show the contract was canceled in time.
• UK Government. Consumer Contracts Regulations 2013, regulation 30. The cancellation period ends 14 days after the goods come into the consumer's physical possession, counted from the last item on an order delivered in parts.
• UK Government. Consumer Contracts Regulations 2013, regulation 35. The consumer must send the goods back no later than 14 days after telling the trader, and bears the direct cost unless the trader failed to say so.
• UK Government. Consumer Contracts Regulations 2013, regulation 34. Reimbursement without undue delay and within 14 days of receiving the goods back or of evidence they were sent, with a deduction only for handling beyond establishing the nature and function of the goods.
• GOV.UK. Accepting returns and giving refunds: the law. The distance selling cancellation right, and the goods that are exempt unless faulty: custom-made, perishable, unwrapped media and sealed hygiene items.
• California Legislative Information. Civil Code section 1723. A retail seller with a restrictive refund policy must display it conspicuously, or is liable to the buyer for the purchase amount on a return attempted on or before the 30th day after purchase.
• Electronic Code of Federal Regulations. 16 CFR 435.2. A seller must have a reasonable basis to expect shipment within the time clearly stated, or within 30 days where no time is stated.
• National Retail Federation and Happy Returns. 2025 Retail Returns Landscape. An estimated 19.3% of online sales returned in 2025.
• National Retail Federation. Returns projected at $849.9 billion in 2025. Total retail returns projected at $849.9 billion in 2025, 15.8% of annual sales.
• US Census Bureau. Quarterly Retail E-Commerce Sales. E-commerce at $326.7 billion in Q1 2026, 16.9% of total US retail sales.
• United States Postal Service. Business Return Services. Commercial return services priced per piece and per label scanned, and the ways a merchant can get a label to a customer once a request is approved.
• Add To Cart #578, Stop Customer Problems Before They Start: Inside Keeyu's AI Ops - stuck returns, failed payments and orders caught mid-flight.
• Give it a Nudge, Keeyu is Solving the "Where’s My Order?" Nightmare - why half of all support tickets are post-purchase.
• Retail Fest 2026, Post-Purchase Perfection: Delivering Experiences Customers Rave About - why a help desk cannot prevent a ticket.