Handcrafted Beautiful Bootstrap HTML Templates for your Business Website.
A post on Reddit’s ecommerce communities captured a frustration a lot of store owners share. An apparel merchant, about two years in, noticed a small group of customers who kept buying, returning, and apparently wearing items before sending them back. Returns were auto-approved with no flags and no customer history, so the pattern only became obvious after it had cost real money. Their question: how do you spot repeat return abuse before approving the refund?
The replies were revealing. Some said ban them. Some said charge for returns. One commenter claimed that “90% of problems often come from about 2% of customers”. Others pushed back: frequent returns might mean the sizing is wrong, not that the customer is dishonest.
Both sides are right, and that’s the challenge. The NRF and Happy Returns estimated that 9% of all returns in 2025 were fraudulent (NRF, October 2025). That’s a real cost. But the other 91% are honest, and the same report found 71% of shoppers are less likely to buy again after a poor returns experience. Clamp down on everyone and you lose more good customers than you stop bad ones.
This guide covers the common types of return fraud and abuse, the signals that identify them, and how to set up WooCommerce so risky returns get a closer look while honest customers sail through.

| Type | What happens | Typical signal |
|---|---|---|
| Wardrobing | Item bought, worn or used once (an event, a photo shoot), then returned | Fashion, occasion wear, cameras; returns just inside the window; signs of wear |
| Serial returning | A customer returns a very high share of what they buy | High return rate per customer over time |
| Empty box / wrong item returned | Box returned empty, or with a cheaper or counterfeit item | Weight mismatch; inspection finds wrong item |
| False damage claims | Item claimed damaged or defective when it wasn’t | Vague descriptions; no packaging photos; repeat claims |
| “Item not received” while receiving it | Customer claims non-delivery to get a refund, or disputes with their bank | Delivery confirmed; history of similar claims |
| Return outside the policy | Late returns, used items, excluded products, pushed through by persistence | Requests outside window; excluded categories |
| Refund double-dipping | Customer requests a return refund and files a chargeback | Dispute on an order already refunded |
Not all of these are “fraud” in a legal sense. Serial returning and late returns are often policy abuse, and sometimes not abuse at all. Your process should treat them differently.
Before tightening anything, look at why your heavy returners return.
Return reasons and history turn a vague suspicion into a clear picture. Without them, you’re guessing, and guessing usually means treating everyone the same.
Customer A has returned 6 of 9 orders this year. Every return reason is Too small, mostly on one brand of jeans. Items come back unworn with tags. Not abuse. That brand runs small. Add a sizing note to those product pages, offer an exchange, and Customer A will likely become a profitable regular.
Customer B has returned 5 of 7 orders, mostly dresses and occasion wear, each requested on a Monday or Tuesday, close to the end of the return window. Two arrived with makeup marks and creased fabric. Likely wardrobing. Hold their future returns for inspection, refund only after arrival, and enforce the condition rules in your policy.
Customer C has made three “arrived damaged” claims in two months on different products, each with a one-word description and no photos, while other customers ordering the same products report no damage. Suspicious. Require photos of the item and packaging for future claims, and hold them for review.
Three customers with high return rates, and only two of them are a problem. Reasons and history are what tell them apart.
Most abuse thrives on ambiguity: late returns that get approved because nobody checked the date, used items accepted because the policy didn’t say “unused”, gifts kept because nobody asked for them back. Tighten the policy text, then enforce it automatically so no one has to argue:
([Return policy template](/blog/woocommerce-return-policy/))

The best idea from that Reddit thread, and from others like it, was risk-based routing: automate the obvious cases, and send the rest to a human with context.
| Return | Route |
|---|---|
| Low value, trusted repeat customer, normal reason, inside window | Auto-approve |
| Exchange for a different size | Auto-approve (revenue kept, low risk) |
| High-value order | Hold for manual review |
| Customer with several recent returns | Flag for review |
| Damage claim without detail | Hold; request evidence |
| Outside window or excluded item | Reject with a clear reason (or flag if you allow exceptions) |
This keeps the experience fast for the large majority while focusing your attention where risk actually is.
For anything above a low-value threshold:
Keep it next to wherever returns are unpacked:
It takes a minute per parcel and gives you evidence if a customer disputes a refused or partial refund.
Every return should record the customer, items, reason, description, condition on arrival, decision and who made it. Patterns then become visible:
For genuine, repeated abuse, many stores’ terms reserve the right to refuse future orders or returns. Use it sparingly, based on records rather than hunches.
One form of abuse sits between returns and payments: the customer requests a return, gets refunded, and disputes the original charge with their bank. Without records, you can end up refunding twice. Your defence is documentation: the return record, the refund in WooCommerce, the gateway refund ID, and the customer emails. Respond to the dispute with that evidence promptly.
What not to do
WooCommerce has no returns system, so out of the box there’s no window enforcement, no reasons, no history and no approval step. Recirco – Returns & Exchanges for WooCommerce adds them for free:
Recirco Pro adds the risk-routing layer:
Note: the current version of Recirco requires customers to have an account to request a return. For abuse prevention that’s a benefit: every return is tied to a known customer and their history.
Fair returns
We want returns to be easy for our customers. To keep them that way:
- Returns must be requested within [30] days of delivery from My Account → Returns.
- Items must be unworn, unwashed and returned with all tags and packaging.
- [Final-sale, personalized and hygiene items] can’t be returned.
- Damage and fault claims need a short description and photos.
- We inspect every return. Items returned used, damaged by the customer or incomplete may be refused or partially refunded.
- We may decline future orders or returns where we see repeated misuse of this policy.
- This doesn’t affect your statutory rights.
What is wardrobing?
Buying an item, using or wearing it (often once, for an event), then returning it for a refund as if unused.
How common is return fraud?
The NRF and Happy Returns estimated about 9% of all US retail returns in 2025 were fraudulent.
How do I stop serial returners without upsetting good customers?
Look at their reasons first (sizing problems aren't fraud), enforce clear policy rules automatically, route risky returns to manual review, and inspect before refunding. Offer exchanges for fit problems.
Can WooCommerce auto-approve some returns and hold others?
Not natively. Recirco Pro adds conditional approval rules that approve, reject, flag or hold returns, with the deciding rule recorded in the activity log.
Should I ban customers who return a lot?
Only for clear, documented abuse. High return rates often signal a product or sizing problem you can fix.
Should I refund on approval or on arrival?
For low-risk returns, refunding on approval is a great customer experience. For high-value items or customers with a history of refused returns, refund only after the item arrives and passes inspection.