A customer buys a $400 dress on Thursday, wears it to a wedding on Saturday, and returns it Monday with the tags carefully reattached. Nothing was defective. Nothing was a mistake. It's a transaction retailers have a name for: wardrobing, and it's quietly eating into small business margins that are already thin.
If you sell physical products — online, in a storefront, or both — some percentage of your "returns" aren't returns at all. They're a form of shrinkage that shows up disguised as customer service. Here's how to recognize it, what it costs you, and the specific bookkeeping and policy controls that catch it before it becomes a habit among your customer base.
What Return Fraud Actually Looks Like
"Return fraud" is a catch-all term, but it covers several distinct behaviors, each with a different fix:
- Wardrobing — buying an item, using it once (a dress for an event, a power tool for a weekend project, a camera for a vacation), and returning it as if new. This is the single most common form of return abuse.
- Receipt fraud — using a stolen or forged receipt to return merchandise the person never purchased, often shoplifted from the same store.
- Price arbitrage / cross-retailer returns — buying a cheaper version of a product elsewhere and returning it at a store that sells a pricier version, pocketing the difference.
- Bracketing — ordering multiple sizes or colors of the same item with the explicit intent to return all but one. Increasingly common with online apparel, and not always fraud in a legal sense, but it carries the same cost.
- Empty-box returns — returning a box that's been emptied of its actual contents, particularly common with electronics.
- Employee-assisted returns — a staff member processes a fake or friend's return without a corresponding original sale.
Each of these hits your books differently, which is exactly why lumping them all together as "just returns" makes them hard to catch.
The Numbers Behind the Problem
Return fraud isn't a rounding error. Industry estimates put fraudulent and abusive returns at roughly 10–15% of total returns, and return fraud overall costs U.S. retailers more than $100 billion a year. Wardrobing specifically is the most common type of return abuse — a majority of retailers report being affected by it in any given year, and close to two-thirds of consumers admit to at least one costly return behavior, whether that's wardrobing, bracketing, or sending back a different (cheaper) item than the one they bought.
The per-return cost adds up fast even before fraud enters the picture. Processing, restocking, and reshipping a single return typically costs a retailer somewhere between $10 and $65, depending on the product and shipping distance — so a fraudulent return isn't just lost revenue, it's lost revenue plus the operational cost of handling it.
For a small business, this hits differently than it does for a national chain. A big-box retailer can absorb a few thousand fraudulent returns a year and barely notice. A boutique, a specialty tool rental counter, or a small e-commerce shop selling event wear or outdoor gear can see wardrobing alone erode several points of margin — margin that often isn't there to spare.
Where It Shows Up in Your Books
Return fraud rarely announces itself. It shows up as pattern anomalies, if you're looking for them:
- A spike in "returns and allowances" relative to sales, without a corresponding rise in product defects. If your Sales Returns and Allowances account (a contra-revenue account that reduces gross sales on the income statement) is climbing faster than revenue, that's your first flag.
- Repeat returners. A handful of customer accounts or names generating a disproportionate share of returns is the single strongest signal. Most legitimate customers return rarely; habitual wardrobers return constantly.
- Seasonal spikes tied to events, not product problems. A surge in dress, tool, or camera returns right after a wedding season, a holiday, or a home-project weekend is a wardrobing tell, not a quality-control issue.
- Returns with tags reattached, or "like new" items that show wear when your intake process actually inspects them (which, if you're not doing this consistently, is worth fixing on its own).
- Refunds issued without a corresponding original sale in your point-of-sale or e-commerce system — a strong indicator of receipt fraud or employee-assisted fraud.
If your bookkeeping treats every return as an undifferentiated debit to Sales Returns and Allowances with no memo, tag, or reason code, you have no way to see any of this. That's the first thing to fix.
Building the Controls: Policy First
Before you touch the accounting, tighten the policy that generates the transaction in the first place.
Require proof of purchase. A receipt, an order number, or a card used at time of purchase should be non-negotiable for any refund (not just store credit). This alone eliminates most receipt fraud and a good chunk of cross-retailer arbitrage.
Set a real return window and enforce product-condition standards. Thirty days with unworn/unused condition and original packaging is a common standard. Publish it at the point of sale, in your online checkout flow, and on your receipts — not just buried in a terms page. Vague or unenforced policies are what wardrobers count on.
Consider a restocking fee for opened, non-defective items. Where state law allows it (and most states require you to disclose it up front — check your state's rules before implementing), a 10–20% restocking fee changes the math for a customer who was planning to "borrow" merchandise for free.
Use ID verification and a returns-tracking system. Track returns against a customer account, phone number, or ID, not just a transaction — one-off receipt matching lets serial returners spread abuse across "unconnected" transactions. Retail return-authorization software (or even a disciplined spreadsheet, if you're small) that flags an ID or account after two or three no-fault returns is enough to catch the pattern before it becomes routine.
Train staff to inspect, not just accept. A five-second visual check for wear, odor, tag reattachment, or missing components stops a large share of wardrobing at the counter, before it ever reaches your books.
Building the Controls: The Bookkeeping Side
Policy stops some fraud at the door. The rest you catch by making your books legible enough to spot the pattern.
Use reason codes on every return, and post them to distinct sub-accounts. Instead of one lump Sales Returns and Allowances account, break it into something like: defective/damaged, wrong item shipped, customer changed mind, and no-reason/suspected-abuse. This turns a single opaque number into a diagnostic tool — if "customer changed mind" is 80% of your returns and climbing, you have a wardrobing problem, not a quality problem.
Set a returns reserve based on your actual trailing return rate, and revisit it monthly. GAAP calls for estimating expected returns and recording a reserve against revenue rather than waiting for the return to happen. Beyond the accounting-accuracy benefit, watching that reserve rate drift upward over a few months is often the earliest warning sign you'll get — well before it's obvious on the sales floor.
Reconcile refunds to original sales, every time, not just at month-end. A refund issued without a matching original transaction in your POS or e-commerce platform is either a data error or a red flag worth investigating immediately, not three weeks later during reconciliation.
Run a monthly report of returns by customer, not just by product. Most accounting and point-of-sale systems can generate this if you ask; most small businesses never do. It's the single fastest way to spot a repeat wardrober or an employee running fake returns for a friend.
Track restocking-fee revenue and waived-fee frequency separately. If a staff member is habitually waiving restocking fees for the same customers, that's worth a conversation — it can be an innocent customer-service habit or something closer to employee-assisted abuse.
None of this requires expensive software for a small operation. It requires treating "returns" as a category worth the same granularity you'd give sales, expenses, or payroll — because the abuse hides in exactly the aggregation you'd otherwise use to save time.
Keep Your Return Data as Clean as Your Sales Data
Catching return fraud isn't really a loss-prevention problem — it's a bookkeeping visibility problem. The businesses that catch it early are the ones whose books break returns down by reason, customer, and trend, not the ones with the biggest security budget. Beancount.io gives you plain-text accounting that makes that kind of granular tracking straightforward — every return, reason code, and reserve adjustment lives in version-controlled, fully transparent records you can query and audit yourself, with no black-box software standing between you and your own numbers. Get started for free and see what your returns data has been trying to tell you.