WhatsApp Order Refunds and Cancellations: Policy & Scripts
Here's the short version for WhatsApp order refunds and cancellations: decide your cancellation cut-off before you start prepping, refund the same way the customer paid, and always say something rather than going quiet. Most disputes aren't really about the money — they're about a customer not knowing what happens next. Fix that and the maths sorts itself out.
If you're selling through a delivery app, all of this is handled for you (badly, and at a cost). On WhatsApp, you're the policy, the support desk and the person who has to actually say "sorry, no." That's more work, but it also means you get to set rules that fit a one-person kitchen instead of a call-centre script.
Why "no refunds" doesn't survive contact with WhatsApp
A rigid no-refunds line reads fine on a laminated menu nobody actually reads. On WhatsApp, it falls apart the first time a customer messages "this isn't what I ordered" with a photo attached, in real time, while you're mid-shift. You can't hide behind small print in a chat thread — you either answer well or the conversation (and the review) writes itself without you.
The businesses that handle this best don't have a longer policy. They have a shorter, clearer one, sent before the order is even confirmed, so nobody's negotiating the rules after something's already gone wrong.
The one-line policy, sent upfront
Drop this into your order confirmation message once, so it's never a surprise later:
Once we start prepping, orders can't be cancelled — but if anything's wrong with what arrives, message me and I'll sort it. 🙏
That single sentence does three jobs. It sets a cut-off. It removes any "well nobody told me" excuse. And it signals you'll actually fix mistakes, which is the part that keeps people ordering again. A policy that only says no trains customers to argue with you. A policy that says here's the line, and here's what happens if we mess up trains them to trust you.
Cancellations and refunds: before prep vs after
The line that matters isn't "was it silly of them to cancel" — it's whether food or ingredients are already committed.
Before you've started prepping — cancel cleanly, refund in full, no interrogation:
No problem, {name} — order's cancelled and nothing's been charged/refunded in full. Come back any time!
After prepping has started — this is where a lot of sellers either cave completely (and eat the cost every time) or dig in and lose the customer. A middle path holds up better:
We're already cooking this one, {name}, so a full refund isn't possible. I can do a partial refund for the ingredients we haven't used yet, or hold the order for you to collect later today — which works better?
Giving a genuine choice, instead of a flat "no," turns a confrontation into a decision the customer makes with you. Say a £22 order gets cancelled after £6 of ingredients are already committed. A £16 partial refund covers the customer fairly and covers your cost, instead of you eating the full £22 or losing them by refusing outright. Run that math with your own food costs once, and the "how much do I actually give back" question stops being a guess every time it comes up.
Wrong or missing items: refund fast, ask questions never
This is the one category where hesitation costs you more than the item itself. A customer sending a photo of the wrong order at 8pm on a Friday isn't looking for a debate — they're checking whether you're the kind of business that owns a mistake.
That's on us, {name} — genuinely sorry. I'll refund the {item} right now, or remake it and get it to you within {20 min}, your call. Thanks for flagging it rather than just not coming back.
Notice what's missing: no "are you sure," no asking for proof beyond what they've already sent, no making them re-explain themselves. Save the questions for patterns (the same customer disputing every third order is a different conversation), not for a one-off mistake.
No-shows: protect the slot, not the ego
A no-show isn't a refund problem — it's a wasted-ingredients problem, and the fix happens before the order, not after. If you're pre-cooking to a pickup time, send a hold-time line at confirmation. It does more good than any policy you write after the fact. Save it as a WhatsApp Business quick reply so it fires in one tap instead of being retyped every time:
Your order's confirmed for {7:15pm}. We'll hold it for 15 minutes past that time — after that we may need to release the slot to the next order. See you soon!
If someone does no-show, there's rarely anything to refund. The loss is usually ingredients, not a payment already taken. But if they did prepay, treat it exactly like a late cancellation: partial refund for what wasn't used, full charge for what was.
Refunding the same way they paid
The mechanics differ by payment method, and matching them matters more than customers expect:
| They paid by | How to refund | What to say |
|---|---|---|
| Bank transfer | Manual transfer back, same account | "Refunding £X to the same account now — give it a day or two to land." |
| Payment link (Stripe, PayPal, Razorpay, etc.) | Refund through the processor dashboard, not a new bank transfer | "Refunded through the same payment link — you'll see it back on your card in a few days." |
| UPI / local e-wallet | Refund via the app to the same handle | "Sent back to your UPI ID — should show up almost instantly." |
| Cash | Hand back on the spot, or hold as credit for next order if they've already left | "Since you've already left, I've saved £X as credit for your next order — or let me know if you'd rather I bring cash by." |
Refunding to a different method than they paid with (cash back for a card payment, say) is where a fair refund starts to feel like a hassle. It adds a step for the customer and a paper-trail gap for you. Keep it on the same rail wherever you can.
For payment links, refund through the processor rather than sending a fresh bank transfer. Most platforms let you reverse a charge from the same dashboard where you took it, keeping your records matching without extra manual tracking. UPI refunds are the cheapest to get right. As our payments guide covers, standard bank-to-bank UPI transactions have carried zero merchant discount rate since January 2020 — so sending money back costs exactly what sending it out does: nothing.
When to say no
A generous policy isn't the same as a policy with no edges. It's fair — and necessary — to decline a refund when:
- The order's already been collected or delivered and eaten, with no fault on your side.
- The same customer disputes orders repeatedly (a pattern worth tracking, not assuming from one bad night).
- The complaint arrives days later with no photo, no timestamp, nothing to check it against.
Saying no clearly and kindly, once, is better for the relationship than a vague stall that never actually resolves:
I hear you, but I can't refund this one — it was collected and there's no way for me to verify what happened after that. Happy to make it right on your next order if you'd like to try again.
Holding a line occasionally is what makes the yes mean something the rest of the time.
For the fast version, here's the whole policy in one table — pin it near your phone for the nights you don't have time to think it through:
| Situation | Refund? | Script tone |
|---|---|---|
| Cancelled before prep started | Full refund | Clean, no questions |
| Cancelled after prep started | Partial refund or hold order | Offer a choice |
| Wrong or missing item | Full refund or fast remake | Apologise, act immediately |
| No-show, prepaid | Partial refund for unused ingredients | Same as late cancellation |
| No-show, unpaid | Nothing to refund | Note the pattern, move on |
| Collected/delivered, disputed later with no evidence | Case-by-case, can decline | Polite, firm |
Put it where customers see it before they need it
None of this works if the policy only exists in your head. Say the cancellation cut-off in your order confirmation message — the same place you confirm the price and time — so it's never news to anyone. And if you're still tracking who paid what by scrolling back through chat history, a structured WhatsApp ordering setup keeps the order, total and payment status in one place. That's half the battle when you actually need to work out what to refund.
Keep the refunds and cancellations policy short, say it upfront, and handle the bad moments fast. That's what turns a mistake into a customer who orders again, rather than a one-star review you didn't see coming.