Your Retail Return Policy Tracks the Wrong Number
Return rate tells you how often things come back. It never tells you how many of those dollars stay in the store, and almost nobody tracks that number.
Two returns happened at the counter on the same Tuesday, coded identically in the system: sweater, wrong size, $68. One customer left with the charge reversed on their card. The other left holding a medium instead of a small, and the same $68 stayed in the drawer. Your monthly report calls both of those events a return. Your bank account knows they were nothing alike.
Most stores build their retail return policy around the wrong number. You track return rate, the share of sales that come back, because it's the figure every POS report puts in front of you unasked. But you can only push that number down by making returns harder, which just pushes the complaint online. What shows up on the P&L isn't how often things come back. It's how many of those dollars, once they're back in your hands, leave the building versus stay in it.
Is a retail return policy required by law?
No federal law forces a retail store to accept a return; refusing one outright is legal in nearly every state. A handful of states require disclosure instead, and the trigger is different in each. New York requires every retail establishment to post its refund policy, full stop. California only requires it if your policy is stricter than a full refund or equal exchange within seven days — refund freely for a week and you have nothing to post.
The stakes differ too. Skip the posting in New York and the customer gets 30 days to choose a cash refund or a credit — their choice, not yours, which erases the store-credit lever entirely. Both statutes accept proof of purchase, not just a paper receipt, and both require the goods unused and undamaged. California also exempts perishables, custom orders and anything marked final sale outright; New York doesn't exempt them, it just requires your sign to say whether you take them back. Read California's statute and New York's directly before you post anything. That's not the FTC's Cooling-Off Rule, which covers only sales made away from your regular place of business.
Track retention on returns, not return rate
Return rate is a number you can only lower with friction: more paperwork, more suspicion, a shorter window. Retailers estimated that 15.8% of retail sales, roughly 16 cents of every dollar, would be returned in 2025, according to NRF's returns report, and that figure tracks a store's product mix more than its strictness. Fighting it is a losing argument. The number worth fighting for is what happens to a dollar once it's back in your hands.
Call it retention on returns: the share of returned dollars that stay in the store as an exchange or store credit, instead of leaving as cash or a card reversal. Most POS systems already report refunds, exchanges and store credit as separate lines. Pull last month's totals and divide: retention on returns equals (exchanges + store credit issued) ÷ total returned value.
Two stores can post the identical return rate and be running different businesses. Store A takes back $9,200 in a month: $5,000 leaves as straight refunds, $4,200 converts to an exchange or a credit balance, 46 cents retained on the dollar. Store B takes back the same $9,200, same rate, same reason codes on the tickets, but only $2,300 converts, 25 cents retained. Nothing on either store's return-rate line tells you which is which. Only retention does.
Track it monthly, over a full season before drawing conclusions. A denim-heavy month retains worse than a jewelry-heavy one, so compare July to last July, not July to August.
The first sentence decides whether it's a refund or an exchange
"Do you have your receipt?" opens with an obstacle. Before you know anything about the problem, the customer already has to prove themselves, and people who feel accused defend a position instead of volunteering information. The fastest position is "give me my money back."
"What happened with it?" opens with a diagnosis. Wrong size gets a different size. Wrong color means a walk to the shelf. A gift that missed gets solved by asking what they'd have picked instead. None of that requires a dollar to leave the register — it requires an exchange, which your return-rate report counts identically to a refund and your bank account does not.
Ask about the item before the paperwork — the receipt question can wait.
Where the policy should hold, and where credit earns its keep
Your policy should be firm about its edges and flexible about everything inside them. The edges are what you post and enforce without exception: the day count, the condition standard, whether proof of purchase is required. Give the floor a rule they can apply alone at 6pm: bend for a genuine defect regardless of age; bend once for a lost receipt you can verify in the system; never bend the condition standard, tags off or visibly worn. "Policy says no" avoids the judgment instead of making it. The customer doesn't remember that policy was correctly applied. They remember being turned away, and that's the story they tell.
Inside those edges, store credit is where the real decision lives. Offered honestly, it solves the customer's problem without losing the sale a straight refund would erase, the right call whenever they aren't sure what they want instead. It stops being honest the moment you use it to dodge a refund someone is actually owed: inside the window, proof of purchase in hand, item defective. The posting statutes won't stop you doing it. Your posted policy already promised otherwise, which means you're now the store that doesn't mean what its own sign says. A credit balance tied to a customer profile, which VoVi does by default, beats a paper slip that gets lost — but it's not a substitute for asking first.
The item in the back room is dead stock you already paid for
A refund is a cost you can see. An item sitting in a bin for a week is a cost you haven't noticed: you already paid the vendor for it, and every day off the floor isn't earning that money back.
Inspect and restock the same day, or the next morning at the latest. Whoever handles returns needs authority to do it without waiting on a manager — the same logic that applies to clearing dead stock, in reverse.
Receipt-less returns, and the customer who returns everything
No proof of purchase doesn't have to mean no return. If the item is clearly yours (your tags, your SKU, in your system), look it up by phone number or account instead of demanding paper. Can't verify what was paid? Default to store credit at the lowest price that SKU sold for in the last 90 days, a number your POS can pull directly.
The dishonest case is real but smaller than it feels from the counter: retailers estimated that roughly 9% of returns were fraudulent in 2025 (wardrobing, receipt fraud, stolen goods), meaning the other 91% are genuine problems facing someone who's already made up their mind. Flag repeat no-receipt returns on the same customer profile, and route anyone past three in ninety days to a manager instead of a blanket no. Treat it the way you'd treat a short till: rule out the obvious explanation first.
Back to that Tuesday. Same code in the system, same $68 sweater, same wrong size — the only thing that changed was the first sentence a seller used. One got asked for a receipt and left with a refund. The other got asked what happened and left wearing a medium. Retention on returns is just that habit, counted.
Takeaways
- Stop grading the return desk on return rate. Calculate retention on returns instead: (exchanges + store credit) ÷ total returned value, tracked monthly.
- Open every return with "what happened with it?" not "do you have your receipt?" Diagnosis before paperwork turns refunds into exchanges.
- Hold the edges of your policy firm: time window, condition, proof of purchase. Post it conspicuously and keep everything inside those edges flexible.
- Restock same-day. A returned item in the back room is dead stock you already paid for.
- Treat receipt-less returns and repeat returners as an exception routed to a manager, not a reason to interrogate every customer.
Common questions
Can I charge a restocking fee?
Generally yes, if you disclose it. New York's statute requires the fee and its amount on the same sign as the rest of your policy; California's requires disclosing the conditions governing the refund. A fee sprung at the register afterward counts as no policy at all.
How long should my return window be?
Thirty days is the number worth defaulting to. It covers returns that are genuinely about the product — a gift opened late, a wash that didn't survive — without carrying liability into the next markdown cycle. It's also the remedy New York imposes on a store that posts nothing at all, and California on a store that should have posted and didn't — so a shorter window is fine, provided you actually post it.
Do I have to take back a clearance or final-sale item?
It depends on the state. California exempts goods marked "as is," "no returns accepted" or "all sales final" — the marking is what earns the exemption, not the clearance rack. Unmarked clearance stock is fully inside the statute. New York doesn't grant that exemption — without a sign saying so, the standard 30-day default still applies. Mark it final sale at the point of purchase, not after someone tries to return it.