
Wardrobing costs US retail around $13 billion in lost sales a year. Fraudulent returns overall were tied to roughly $101 billion in 2024, and about 1 in 5 shoppers admit to buying something, using it once, and sending it back.
That's the scale a brand is up against, and most of it hides in plain sight as ordinary returns. The dress worn to one event, the camera used for one trip, the outfit posted once and shipped back inside the tag-on window.
The good news is that a large share of that loss is recoverable, and not by treating every customer as a suspect. The recoverable part comes from evidence and behavior, captured at the return. That's the lane Claimlane works in, and the wider fraud picture sits in the return fraud in ecommerce guide.
What wardrobing is
Wardrobing, sometimes called wear-and-return or snap-and-send-back, is buying an item to use once, then returning it for a full refund. It's a form of first-party fraud, meaning the customer themselves is the bad actor rather than a stranger using stolen details.
That makes it harder to spot than classic fraud, because the order, the payment, and the account are all legitimate. It sits alongside the patterns in return fraud prevention and the buyer motivations in the psychology behind returns.
Why it's growing, and what it costs
The behavior is common and rising. Nearly 40% of shoppers admit to wardrobing apparel, shoes, or accessories, and most of those earn over $50,000 a year, so this isn't a fringe problem driven by hardship alone.
Event culture, the desire to post a one-time outfit, and cost-of-living pressure all feed it. Treated as a recurring cost line rather than a nuisance, it belongs in the returns workflow where the brand can attribute it, and brands that track consumer buying behavior see the pattern early.
Spotting wardrobing with evidence
The cheapest place to catch a wear-and-return is at the request, before a label is issued. A photo or short video of the item, plus its condition and any serial detail, turns "it didn't fit" into something checkable.
Structured intake is what makes this scale. Capturing condition against a serial number and a clear set of return reason codes means a returned item arrives with a record, not a mystery. A consistent RMA process collects it the same way every time.
Behavior data and repeat patterns
Wardrobing rarely happens once. The same account returns high-value apparel right after weekend events, or returns a suspicious share of what it buys, and those patterns are visible if a brand is watching.
Automated review of a shopper's order history can flag the behavior and route it for a closer look before approving. The operational side of handling those accounts fairly sits in managing repeat returns, which is about precision, not punishment.
Triaging evidence at scale
Once evidence is captured, someone has to judge it, and at volume that judgment is slow and inconsistent when it's manual. This is where automation changes the math.
Rules-based review applies the brand's policy to each claim, checks the submitted images against the return reason, and auto-resolves the clean cases while routing the doubtful ones to a person. For wardrobing it means a worn item flagged against policy gets caught consistently instead of slipping through on a busy day. The capability lives in the brand's configurable claims and warranty workflows.
In practice
Skechers runs its warranty and returns claims through Claimlane, so footwear claims arrive with structured evidence and a consistent rule set instead of scattered notes. That structure is what lets a team make consistent calls on returns, including the ones that don't add up. See the Skechers case study and more customer stories.
Why stricter return policies don't pay off
The reflex is to tighten the return policy. Shorten the window, add a restocking fee, demand tags stay on. It feels decisive, and it mostly trades real revenue for a small dent in fraud.
Tighter rules treat every customer as a suspect, and most of them aren't, so conversion drops while wardrobers learn to dodge the rule within a season. Generous policies have their own trade-offs, weighed in free returns pros and cons, but the answer isn't blanket restriction. It's one consistent return policy strategy applied with evidence and behavior signals. Vendors built for warehouse-side reverse logistics, such as ReverseLogix, handle the physical flow, but the precision sits in the claims layer, as the ReverseLogix alternatives comparison lays out.
Policy levers that actually work
Some policy moves do help, as long as they're targeted. Defaulting to store credit or an exchange instead of a cash refund removes much of the upside for a wardrober while keeping the option open for honest buyers.
The trade-off between store credit and refund is worth setting on purpose, and a clear set of exchange policies gives the brand a fair path that still discourages abuse. Account-level limits, used sparingly, beat blanket window cuts.
Where wardrobing meets chargebacks
Deny a wear-and-return and a determined wardrober may dispute the charge with their bank instead. That turns a return decision into a chargeback the brand now has to defend.
Claim documentation is the defense. The same evidence captured at intake supports a chargeback response, which is why payment reversals and chargebacks and chargeback management sit downstream of the returns workflow, not in a separate silo.
Building fraud signals into the returns workflow
None of this works as a bolt-on. Evidence capture, behavior flags, automated review, and policy all have to live inside the same returns workflow, or each one becomes a manual step someone skips under pressure.
Holding the whole chain in one place means a flagged return carries its evidence, its history, and its recommended action together. That's the difference between catching wardrobing by luck and catching it by design.
Three signals to check this week
- Accounts returning a high share of high-value apparel
- Returns clustered right after weekend events
- Refunds issued without the item physically confirmed back

