Home›
E-commerce

How to handle customer returns: two kinds, one runbook

VerifiedVerified & Reviewed
Handling a customer return is the sequence from the request to the refund: authorize, transport, inspect, decide, settle and route the item. The part most operators miss is that returns are two populations, not one. A return you caused, a wrong pick or a damaged parcel, has a resolution that's not a refund, and it was visible in your own systems before the customer ever asked.
Jevon Le Roux
Founder & CEO, Keeyu
jevon-le-roux
Read time
7 Min Read
Copy LinkCopy

What handling a return actually involves

Handling a customer return is the sequence a seller runs from the moment a customer asks to send something back to the moment the money is returned and the item is either back in sellable stock or written off: authorize, transport, inspect, decide, refund, restock or dispose. Most advice treats every return as the same event, and it's not. Some returns are a customer changing their mind. Some are your own failure arriving back at the warehouse in a box, and running both through one queue is why returns feel unmanageable. I have watched a single wrong pick become a return request, a refund, a replacement order and a support ticket, all of it set in motion in the warehouse before the customer knew anything was wrong.

The volume isn't marginal. NRF's 2025 returns research puts 19.3% of online sales returned that year.

Two kinds of return, and why they need different handling

Split the population by cause, not by product.

  • Returns you caused: the wrong item, the wrong size picked against the order, damage in transit, a short shipment, a delivery exception that landed the parcel too late to be useful. Every one was visible in your warehouse or in a carrier scan before the return request existed.
  • Returns the customer chose: fit, color, a change of mind, two sizes ordered to keep one. Legitimate, expected, and a policy and prevention problem rather than an operations problem.

The split pays because the first group has a resolution that's not a refund: a replacement sent before the customer asks, a returnless refund on a low-value damaged item. The second group runs the standard process below. Both sit inside a growing total. Consumers returned $849.9 billion of merchandise in 2025, 15.8% of annual sales, according to NRF and Happy Returns, against the $890 billion and 16.9% the same research recorded for 2024. One in five orders hits an operational break after checkout, and the returns those breaks create are the part of the queue you can do something about.

The steps of handling a return

Every guide on returns carries a version of this list, so the list isn't the value. The condition standard in step three and the clock in step five are.

  1. Take the request and authorize it against the policy. Your RMA process is where volume turns into an operational problem, so decide up front what approves automatically and what a person looks at.
  2. Get the item moving, with a label the customer doesn't have to source themselves. The failure mode here is the return that's authorized and never scanned.
  3. Receive and inspect it against a written condition standard. If nobody wrote down what unused means, two receivers will grade the same item differently and neither decision will survive a dispute.
  4. Decide the outcome: refund, exchange, store credit, repair, or no return at all because a replacement already shipped.
  5. Settle the money on a clock, not when somebody gets to it. The clock is what the customer experiences as the return.
  6. Route the item: back to sellable stock, out to a secondary channel, or to disposal. Grade it at inspection so nothing waits in a bay for a second decision.

What the law actually requires

The legal position is the part every page on this topic skips. There's no general legal right to a refund for a change of mind, and the policy you post is what governs, as California's Attorney General states plainly.

What binds you is delivery. Under the FTC's Mail, Internet, or Telephone Order Merchandise Rule you need the buyer's consent to a delay when you can't ship in the time promised, and a refund owed must be sent within seven working days of the buyer's right to it arising, or within one billing cycle where you extended the credit yourself. The prompt delivery rules set the 30-day default when you promised no date.

Some states make the posting itself the obligation: California Civil Code section 1723 tells a retailer whose policy is more restrictive than a full refund within seven days to post it conspicuously, or be liable to a buyer returning within 30 days.

The legal floor is a floor, not a target. Most brands I talk to argue about a 30-day window against a 60-day one while missing the seven-working-day clock that already binds them.

What belongs in the return policy

Six decisions. Make them explicitly, write them down, and every step above has something to measure against.

  • Window: how long, counted from what date, and whether it differs by category.
  • Condition: what unused means in writing, because inspection needs a standard rather than an opinion.
  • Who pays return shipping: the single most consequential line in the document.
  • What the customer gets: refund to the original method, exchange or store credit, and the order in which you offer them.
  • Exceptions: final sale, hygiene, perishable, custom and personalized items.
  • How to start: the one route a customer should take, stated in the policy rather than left to an agent to explain.

Return shipping is the expensive line and the one shoppers weigh hardest. The NRF and Happy Returns 2025 Retail Returns Landscape, linked above, found 82% of consumers call free returns an important consideration when shopping online, and NRF's release on the same research puts 71% as less likely to shop with a retailer again after a poor returns experience. Decide which of those you're buying.

Where handling breaks: the return that arrives and stops

Every guide ends with refunding the customer. None treats the gap between "we received it" and "we refunded it" as a state anyone owns, and that gap makes the second wave of tickets. A parcel lands, gets scanned into a receiving bay, and sits. The customer is inside a refund window nobody is watching, so they open a ticket, and that ticket is a returns WISMO. Support answers it, which doesn't move the parcel. Two numbers make the state visible.

  • Received but not refunded: returns delivered to your warehouse with no refund issued, aged by day, with a threshold and a named owner.
  • Return requests with no movement: approved returns with no carrier scan against them, because until that scan happens you're holding the money and the customer is holding the goods.

Both are operational states with a threshold, not dashboard decoration. Knowing the number is still not resolution: an aging report describes a broken promise it can't keep. Something has to act on the row, and a helpdesk replying to the customer who chased you isn't that something.

Handling returns is an operations job, not a support job

A helpdesk answers the customer. It doesn't pick the replacement, release the refund or move the parcel. It's a system for replying about problems, not resolving them, and that's structural. The category that resolves them is proactive e-commerce operations: detect the break in the warehouse or the carrier scan, decide the resolution against your policy, act before the customer opens a request.

Which means being plain about what we're not, because this keyword sits beside a lot of things we don't sell. Keeyu isn't a returns portal, not a carrier, not a warehouse management system and not an order management system. We don't print your labels, run your receiving bay or hold your inventory. We sit on top of the systems that do. Every order is a promise, and a return you caused is a promise that was already broken before the box came back.

Handle the returns you caused before the customer asks

The return that started as a wrong pick or a damaged parcel was visible in your systems days before the request arrived, and so is the parcel sitting in receiving with the refund clock running. Keeyu watches orders, carrier scans and returns across the tools you already run, decides the resolution and acts on it, usually before the customer knows anything went wrong. If your unrefunded returns are aging and customers tell you first, book a demo.

Frequently Asked Questions

Do I have to accept customer returns?

In the US there's no general legal right to a refund simply because a customer changed their mind, so the policy you post is what governs, as the California Attorney General sets out. Several states regulate the posting rather than the terms: California Civil Code section 1723 requires a retailer whose policy is more restrictive than a full refund within seven days to post it conspicuously, or be liable to a buyer returning within 30 days. Faulty goods and orders you never delivered are separate matters with their own rules.

How quickly do I have to issue a refund?

Whatever your policy promises, and one federal floor underneath it. Under the FTC's Mail, Internet, or Telephone Order Merchandise Rule, a refund that's owed must be made within seven working days of the buyer's right to it arising, for example when you can't ship in the time promised and the buyer doesn't consent to the delay. Set your internal target well inside that. A customer waiting on money opens a ticket long before any legal deadline.

Why does a return policy need a written condition standard?

A written condition standard is one of the six decisions a return policy has to make explicitly, and it's the one your warehouse acts on every day. Without a written definition of what unused means, two receivers grade the same item differently on the same day, and neither grade survives a chargeback dispute, because there's nothing on file to point at. Put the standard in the policy and inspection stops being an opinion.

Should I offer free return shipping?

It's the most expensive line in the policy and the one shoppers weigh hardest. NRF's 2025 returns research found 82% of consumers call free returns an important consideration when shopping online. The workable middle is to make returns free where you caused them, a wrong item or a damaged parcel, and charge or offer store credit where the customer chose to send something back. That prices the choice without making your own mistakes cost the customer.

What is a reasonable return window?

Thirty days from delivery is the usual anchor, and it's not arbitrary: California's posting rule treats a full refund within seven days as the benchmark for a policy that needs no special notice, and gives a buyer 30 days to return against a policy that was never posted. A longer window buys goodwill and delays the moment an item comes back sellable; a shorter one recovers inventory faster and gets argued about at the edges. Pick a window you can inspect and refund inside, then measure whether you do.

How do I handle a return without an order number or receipt?

Have one lookup route and one default outcome. Search on email, phone number or card last four digits before asking the customer for anything else, and confirm the item matches something that order actually contained. If nothing is found, store credit at the current selling price is the standard resolution, because it protects the margin without turning the interaction into an argument. Write the rule into the policy so the decision isn't made differently by whoever happens to answer.

What do I do with a returned item I cannot resell?

Grade it once, at inspection, and route it immediately: refurbish or repackage if the cost is below the recovery, sell through a secondary or outlet channel if it's sellable but not as new, donate where that's worth more than the handling, and dispose only when the alternatives cost more than the item. The failure to avoid is a second decision later. An ungraded item sits in a bay, holds space, and quietly loses whatever value it still had.

How do I stop return fraud without punishing good customers?

NRF's 2025 returns research puts 9% of returns as fraudulent, which means a policy tightened for everyone taxes the other 91% to catch a small minority. Scope the exceptions instead: flag repeat high-value returners, require the original packaging only on the categories that are actually abused, inspect serial numbers on electronics, and keep a record of returns by customer so a pattern is visible. Keep the standard path fast for everyone else.

References

No items found.

Ready to Stop Reacting?

The fastest way to see how Keeyu prevents complaints is to see it in action.

In one call, we’ll map your current operations, show how our AI Agent fits in, and walk through real examples of issues fixed before customers notice.

Most teams go live within 48 hours. We never share your data.

Book a custom demoSee how it works