How to Handle a Refund Request Your Policy Doesn't Allow

03 September 2026·6 min read

Quick answer: You don't need to choose between caving on every refund request and sounding like a robot reading terms and conditions. Acknowledge the request warmly, explain the policy clearly without over-apologising, and offer an alternative where you can — store credit, a partial gesture, or a fix. Saying no with warmth protects both the relationship and the policy. 🤍

Every business gets the email eventually: a customer asking for money back on something your policy clearly says isn't refundable. It's one of the most uncomfortable moments in running a business, because the two instinctive responses are both wrong. Cave every time and your policy means nothing — word gets around, and suddenly everyone expects the same exception. Go full corporate and quote the fine print, and you've turned a disappointed customer into a furious one who tells everyone about it. The businesses that handle this well have figured out you can hold a boundary and still lead with 💖 — the two aren't actually in conflict, even though it feels that way in the moment.

What most businesses get wrong

Caving immediately to avoid a difficult conversation, which trains your best-behaved customers to ask for the same treatment and quietly erodes your margin.
Replying with policy language — 'as per clause 4.2' — which is accurate and completely tone-deaf, because the customer doesn't feel heard before they feel declined.
Taking too long to respond because the reply feels awkward to write, which lets frustration build into a public review before you've said anything at all.
Treating every refund request as the same request, when a customer who's genuinely upset needs a different response than someone testing whether the policy is real.

Three response scripts to copy and adapt

1. The full no (policy stands, no exception):
'Hi [name], thanks for reaching out, and I'm sorry this hasn't worked out the way you'd hoped. I've had a look and, because [brief factual reason — e.g. this falls outside our 14-day window], we're not able to offer a refund on this one. I know that's not what you wanted to hear. Is there anything I can do to help make this right in another way?'

2. The goodwill gesture (partial or non-cash):
'Hi [name], I completely understand the frustration. While a refund isn't something we can do here, I'd like to offer [store credit / a discount on your next order / a complimentary add-on] as a gesture of goodwill — not because we have to, but because I want you to feel looked after. Let me know if that works for you.'

3. The alternative offer (fix instead of refund):
'Hi [name], thank you for the honesty — that's genuinely useful feedback. Rather than a refund, I'd love the chance to make this right properly: [redo the work / send a replacement / extend your access]. If that doesn't sit right with you, let's talk about what would.'

A high-ticket one-off purchase business: A customer bought a $3,000 item six weeks ago and now wants a full refund because it 'isn't quite right,' well outside your 14-day return window. Use script one, but pair it with a genuine alternative — offer to have it altered, serviced, or exchanged rather than just declining outright. The refusal lands softer when it comes with a real path forward.

A subscription or membership business: A member used the service heavily for three weeks, then asks for a full refund on the month, citing 'I just didn't get the value.' Because they've already had the benefit, a full refund rarely makes sense — script two works well here: offer a discount on next month or extended access instead, which costs you far less than cash and still feels generous.

A referral-driven business: Because so much of your new business comes from word-of-mouth, a badly handled refund conversation doesn't just cost one customer — it costs whoever they would have referred. When a longtime, referring customer asks for an out-of-policy refund, it's often worth stretching further than you would for a first-time customer, precisely because their opinion carries downstream weight. Script three, offering to genuinely fix the issue, tends to preserve the relationship best.

How to decide which response to use

Is this a first request or a pattern? A first-time, genuinely upset customer deserves more flexibility than someone who does this every few months.
What's the actual cost of saying yes? Store credit and discounts cost you far less than cash refunds — they're often the better middle ground.
Is there a real issue to fix? If the complaint points to something you can genuinely correct, offering the fix is usually more satisfying to the customer than money back anyway.
What's the relationship worth? A high-value, repeat, or referring customer is worth more flexibility than a one-off, first-time buyer — decide the tier before you reply, not while you're writing the email.
Always reply within 24 hours. Silence is what turns a private refund request into a public review.

💡 Put your policy where people see it before they need it, not after. A cancellation or refund policy that only appears in an email footer nobody reads will always feel like a surprise. Put it on your booking confirmation, your invoice, and your website — the same policy feels fair when it's expected and unfair when it's sprung on someone.

Mistakes to avoid

Responding with policy language before acknowledging how the customer feels.
Making an exception silently, without noting it anywhere — the next team member won't know it was a one-off.
Letting the request sit unanswered because the reply feels awkward to write.
Offering a cash refund as the default when store credit or a fix would satisfy the customer just as well.
Being inconsistent — the same situation getting a different answer depending on who happens to be replying.

Frequently asked questions

What if the customer threatens a bad review if I don't refund them?

Stay calm and don't let the threat change your answer — caving to threats teaches people that threats work, and word travels. Respond to the substance of their complaint, offer what you're genuinely willing to offer, and let the review land if it does. A single review from an unreasonable request rarely does the damage people fear, especially against a business with a solid review history.

Should I ever make a full exception, even when policy says no?

Sometimes, honestly — this isn't a system that says never bend. A genuine error on your side, a long-term customer with real lifetime value, or a situation that would clearly look bad if it became public are all fair reasons to make a considered exception. The key word is considered: decide it deliberately, not because the conversation felt uncomfortable.

How do I stop this becoming a habit across my team?

Write the three scripts above into your actual policy document or a shared internal note, with guidance on which situations call for which one. Without that, every team member ends up improvising differently, and customers compare notes.

Does a clearer refund policy actually reduce how often this happens?

It reduces it, but it won't eliminate it — some customers won't read the policy no matter how clearly it's written, and some will ask anyway hoping you'll bend. The value of a clear policy is less about stopping every request and more about giving you (and your team) a confident, consistent answer when one comes in.