A returns policy that pays for itself

Nobody opens a shop looking forward to returns. The money goes backwards, the stock comes back in a state you did not choose, and the conversation is usually the least pleasant one of the day.

Which is exactly why most small shops handle them badly. There is no written policy, so the answer depends on who is behind the counter and what kind of morning they have had. The customer who gets a cheerful refund tells nobody. The one who gets a grudging no tells everyone.

A returns policy is not generosity. It is a decision made once, calmly, so it does not have to be made twenty times under pressure.

Write it down, then put it where people can see it

The policy needs to answer four questions and fit on a postcard.

• How long? Fourteen days, thirty days, whatever suits what you sell. Longer than you are comfortable with is usually the right answer, because the number of people who exploit it is far smaller than the number who are reassured by it.
• In what condition? Unused and in the original packaging is the normal bar. Say it plainly.
• With what proof? A receipt is the clean case. Decide now what you do without one, because it will come up.
• Money back, or credit, or exchange? This is the important one, and it deserves its own section.

Print it, put it at the counter, and put it on the receipt. Half the difficult conversations disappear the moment the policy is something the customer could have read before they got to the counter.

Refund, credit, or exchange

These are three genuinely different outcomes, and treating them as one thing is where shops lose money they did not need to lose.

A refund returns the money to the customer. It is the cleanest outcome for them and the most expensive for you: the sale is undone and the cash is gone.

Store credit keeps the money in the shop. The customer has been made whole, they will be back to spend it, and in the meantime you are holding the cash rather than your bank.

An exchange is the best outcome for everyone when it is genuinely available. The customer leaves with something they want, the money never moves, and you have swapped one item of stock for another.

Offer them in that order, from the back: exchange first, then credit, then a refund. Not as a wall, and not with the enthusiasm drained out of it. “We can swap it for the next size, or put it on your account as credit, or refund it if you would rather” is a sentence that costs nothing to say and changes the outcome a large share of the time.

Where the law in your country requires a cash refund for a faulty item, that overrides all of the above. Know that line and stay well on the right side of it. Being generous about the things you choose costs far less than being caught being mean about the things you do not.

Faulty is not the same as changed their mind

Two different situations, two different postures.

If the item is faulty, the shop is at fault whether or not the shop made the item. Take it back, apologise once without grovelling, and sort it out. Then go and look at whether it is the third one of those this month, because that is a supplier conversation, not a customer one.

If the customer simply changed their mind, that is a favour rather than an obligation. Grant it more often than you feel like granting it. The cost of a returned item you can put back on the shelf is the sale you have to make again. The cost of a regular who now shops elsewhere is every sale after that.

Keep the record, always

Even when you say yes without hesitating, write it down properly. A return that is handled as “just give them the money out of the till” creates three problems at once.

The till does not balance at the end of the day, so nobody can tell a return from a mistake or from theft. The stock figure is wrong, so the item is on your shelf and not in your system, which quietly breaks your reorder points and your next stock take. And you have no way of knowing, six months later, that a particular line comes back twice as often as everything else.

That last one is worth real money. A high return rate on one product is information: the sizing is wrong, or the description oversells it, or the batch was bad. You cannot see any of that without the record.

Decide who is allowed to say yes

Refund authority is the classic internal theft route in retail, and it is uncomfortable but necessary to design around. The pattern is not complicated: a sale is rung up, cash goes in the till, a refund is processed later, and the cash comes back out with no customer involved.

You do not solve that with suspicion. You solve it by separating two permissions that look similar and are not. Everyone behind the counter needs to be able to sell, and to look up what a customer bought. Not everyone needs to be able to issue a refund.

In a shop with one owner and two part timers, that usually means the owner and one trusted person can refund, and everyone can sell. It is not an accusation. It is the same reason two people count the safe.

What good looks like on the system

A return should be its own record, not an edit of the original sale. The sale genuinely happened, and rewriting it makes every sales report from that week wrong. The return is a second document that points at the first.

Once that is true, some useful things follow. You can settle a return later, or partly, or as credit rather than cash. You can see what was returned without hunting through voided sales. Your revenue figures stay honest, because the two documents net out against each other rather than one of them quietly vanishing.

StoreWave works this way: returns are separate documents linked to the sale, refunds are recorded against the return, and store credit sits on the customer’s record with a full history of how it got there. Selling and refunding are separate permissions, so a cashier can take a return and look it up without being the one who decides the money goes back.