The Cheapest Way to Lose Money
A seller of $9 phone cases looked at the math and made what felt like an obvious call. A return costs more to process than the item is worth, so why pay for the round trip. Tell the buyer to keep it, refund the money, move on.
For a while the spreadsheet agreed. Then the refund rate on that one SKU kept climbing while the units shipped stayed flat. Same product, same price, more "keep it" payouts every month.
That is not happier customers. That is a leak.
Returnless refunds were pitched to sellers as a small operational win: skip reverse logistics on low-value goods, save on shipping and handling, keep the buyer happy. The pitch was real. The cost it ignored was the one checkpoint a refund used to require. Someone had to send the item back, and a warehouse had to look at it.
Remove that step and you have not just cut a cost. You have removed the only moment where a lie gets caught.
A Policy That Skipped the Inspection
Here is the mechanic that matters. A normal refund has a gate: the box comes back, a worker scans it, opens it, confirms the item matches what was sold. Fraud dies at that gate, because an empty box or a brick does not pass inspection.
Returnless refunds delete the gate. The money moves on the customer's word.
Happy Returns, a UPS company, put the problem in one line: if you never touch the product, you cannot know what is being returned matches what was sold. Their own pilot system, Return Vision, exists to flag suspicious returns before a human looks, because the human look is the expensive part everyone is trying to avoid.
The deterrent was never only the inspection itself. It was knowing an inspection might happen. Fraud responds to friction. Take away the friction and you have published an open invitation.
In November 2025 Amazon gave third-party FBA sellers a dashboard to set returnless refunds by price, up to a $75 item ceiling, with SKU-level and rule-based controls. In January 2026 it expanded these options to sellers globally, auto-resolving many sub-$75 items without requiring the product back. Amazon limits the option to customers without a history of returns abuse, which is the right instinct. The gap is that "history of abuse" is a blunt filter, and a lot of abuse is first-time abuse run through fresh accounts.
Follow the Money, Not the Friction
Returns are enormous and the fraud inside them is no longer a rounding error.
The National Retail Federation and Happy Returns put 2025 returns at $849.9 billion, about 19.3% of online sales, with roughly 9% of returns fraudulent. Appriss Retail, which has tracked this longer, pegs return and claims fraud and abuse near $103 billion, and frames it as a finance problem most retail CFOs overlook. NRF's longer-running figure is blunt: for every $100 in returns accepted, about $13.70 is lost to fraud.
Riskified ran the numbers on more than a million refund claims and found that nearly 1 in 4 refund dollars is abusive. The detail that should worry any seller offering "keep it" is where the abuse clusters. "Item not received" claims are about 25% more likely to be fraudulent than missing-item claims, because they exploit the exact liability gap returnless refunds widen. Claims filed in the first seven days run over 20% more abusive than average, which is the same window a fast auto-refund rewards.
Now layer in who is filing. Mastercard reports first-party fraud, the friendly kind where a real customer disputes a real purchase, is now over 45% of all chargebacks. The people most fluent in this are not your customers.
Refund-as-a-Service Is a Real Industry
The winners here are organized. There is a paid service tier for refund fraud, and it operates in the open.
Operators sell "refunds" as a service on Telegram and Discord, take a cut of whatever they recover, and run playbooks the way a sales team runs a pipeline. The methods are standardized: claim the order never arrived, report the box as half-empty, or claim damage. One favorite is to mail back garbage and let the refund fire on the outbound scan, before anyone opens the package.
Amazon sued one such ring in 2025. The group, operating as RBK, allegedly pulled in more than $4 million in refunds for items that were never returned. It charged clients up to 30% of the recovered amount and built a Telegram following of more than 1,000 subscribers. Federal prosecutors have charged other operators running schemes in the millions, some recruiting insiders at carriers to inject fake "lost in transit" scans.
A software market has formed in response. Analysts size returnless-refund-fraud detection at about $430 million in 2026, up from $380 million in 2025, projected toward $1.5 billion by 2036, with risk scoring the leading detection type at roughly 31% share. When a defense industry crosses half a billion dollars, the attack it counters is mature.
The pattern to hold onto:
- The abuse is coordinated, not casual. A meaningful share of fraudulent orders trace back to organized networks, and they share weaknesses across forums the way honest sellers share growth tips.
- It is automated. Bot and AI-agent traffic to retail rose sharply through 2025, and "item not received" claims scale cleanly when a script can file them across platforms.
- It is cross-platform. A playbook that works on one marketplace gets ported to the next. A blanket policy on any single platform is a known, mapped target.
The Blanket Policy Is the Bug
The instinct after reading the above is to roll returnless refunds back. That is the wrong move, and the data says so.
Returnless refunds genuinely work on the right items for the right customers. Reverse logistics is expensive: processing a single return runs $10 to $40, often 20% to 40% of an item's value, sometimes more. On a $9 case sent to a loyal buyer, eating the unit beats paying to ship it back. Riskified found that giving trusted customers instant refunds raised satisfaction scores by more than 20%, and over 97% of those fast approvals went to people who genuinely returned items.
The problem was never the tool. The problem is applying it as a blanket rule.
A blanket "keep it" under $75 treats a five-year customer and a one-day-old burner account the same way. It treats a SKU nobody abuses and a SKU fraud rings have already mapped the same way. A flat rule is the one thing an organized operation can study once and exploit forever.
The fix is to make "keep it" a decision, not a default. Score the risk on every return at the moment it is requested, across two axes: how risky is this customer, and how abused is this SKU. Grant returnless selectively. Deny it, or require the item back, exactly where the math says the friction is worth restoring.
| Approach | Reverse-logistics cost | Fraud exposure | Customer experience |
|---|---|---|---|
| Blanket returnless under a price cap | Lowest on paper | Highest. A fixed, mappable target for organized rings | Fast for everyone, including abusers |
| Risk-scored returnless | Slightly higher, smarter | Far lower. Friction returns only where it is earned | Instant for trusted buyers, gated for risk |
| Full rollback (require all returns) | Highest. You pay to ship back $9 items | Low, but you reintroduce cost you tried to cut | Slower for your best customers too |
What a Returns-Risk Score Reads
A useful score does not guess. It reads signals you already generate and signals a data network can supply.
- Customer-side history. Refund frequency, the share of orders that end in a claim, "item not received" rate versus the norm, account age, and whether a buyer files claims faster than legitimate damage usually surfaces.
- SKU-side reality. Per-SKU return and abuse rates, resale value, and how often a specific product shows up in coordinated claims. Some items get targeted; treat them differently.
- Pattern signals across the network. A single seller sees one buyer. A data layer across sellers sees the same address, device, or behavior pattern hitting ten of them. That cross-seller view is where blunt filters like "history of abuse on my store" finally get sharp.
Set guardrails on top. Cap returnless approvals per customer in a rolling window, and gate them by reason code. For a risk-scored buyer, switch from auto-refund to receive-and-inspect rather than denying them outright. That last move keeps a good customer who is having a bad month while closing the door on the operator wearing their behavior.
This is the difference between a policy and a system. A policy is a number in a settings panel. A system asks, every time, whether this specific refund to this specific person on this specific item is one you should pay without looking. Building that means treating returns data as a risk surface, which is the kind of work our returns and pricing intelligence solutions are built to support.
The Checkpoint Was the Point
Returnless refunds did not fail because the idea was bad. They failed where they were applied as a rule instead of a judgment.
The original logic, that inspecting a $9 return costs more than the item, was sound. What got lost is that the inspection was never only about the $9. It was the checkpoint that made lying expensive. Remove it for everyone and you have not saved money. You have moved it, quietly, from your margin into someone else's pipeline.
The sellers who win the next two years will not be the ones who say "keep it" the most, or the ones who scrap it and ship every case back. They will be the ones who can tell, in the second a refund is requested, which "keep it" is a gift and which is a withdrawal.
Make it a decision. The ones treating it as a default are already paying for the ones who are not.