Refunds, redeliveries and chargebacks solve different problems. A refund is a remedy arranged through the restaurant, marketplace or payment provider. A redelivery replaces the failed order. A chargeback is a card-scheme dispute raised through the customer’s card issuer. Treating them as one process creates duplicate compensation, poor records and avoidable losses.
Start with the customer outcome
| Situation | Possible operational response | What to verify |
|---|---|---|
| Missing low-value item | Partial refund, credit or controlled redelivery | Customer preference, delivery practicality and provider rules |
| Wrong or unusable main meal | Urgent replacement or full/partial refund | Food-safety risk, time and whether the customer still needs the meal |
| Order never delivered | Redelivery or refund | Driver evidence, address, contact attempts and marketplace process |
| Severe delay | Context-specific remedy | Promise shown, food condition and customer impact |
| Duplicate payment | Refund the duplicate after verifying both transactions | Order and payment references |
| Customer changes mind | Apply a fair stage-based cancellation policy | Whether preparation has started and applicable consumer law |
| Card dispute | Respond through the acquirer or provider | Deadline, reason code and evidence |
Refunds
A refund should have:
- one order reference;
- a clear reason;
- full or partial amount;
- authorised staff member;
- provider transaction reference;
- submitted date;
- status;
- customer communication;
- accounting record.
Do not mark a complaint resolved merely because a refund button was pressed. Confirm that the request was accepted by the provider and keep the customer informed without promising a bank-credit date outside the restaurant’s control.
Redelivery
A redelivery is appropriate only when:
- the customer still wants the food;
- the kitchen and delivery operation can complete it safely;
- the revised time is honest;
- the cause of the first failure is understood;
- the replacement will not repeat the same mistake;
- the marketplace or direct-order record is updated.
Do not send a second order automatically if the customer is no longer available or the delivery problem has not been fixed.
Chargebacks
A customer may ask their card issuer to dispute a transaction. The acquirer or payment provider then requests evidence from the restaurant under card-scheme rules. Time limits can be short.
Evidence may include:
- order and payment record;
- price and terms shown;
- authentication information available through the provider;
- acceptance and preparation timestamps;
- collection or delivery evidence;
- customer messages;
- refunds or replacements already provided;
- proof that the response matches the dispute reason.
Do not submit irrelevant personal information. Follow the provider’s evidence requirements and protect customer data.
Consumer rights and policy wording
Made-to-order and perishable food does not fit the ordinary change-of-mind return process used for durable online goods. However, this does not justify a blanket “no refunds under any circumstances” policy. Customers retain rights where goods are faulty, not as described or the business has not supplied what was agreed.
Use operational policy to explain how the restaurant will respond, but obtain qualified advice for legal wording and unusual disputes.
Prevent duplicate compensation
Before providing a remedy, check:
- whether the marketplace already refunded the customer;
- whether the restaurant already sent a replacement;
- whether a card dispute is open;
- whether a goodwill credit was issued;
- whether the complaint concerns one item or the entire order.
One central incident record should be visible to operations, customer service and finance.
Root-cause categories
- menu or modifier error;
- kitchen preparation error;
- packing or missing item;
- allergen or dietary-information issue;
- delay or capacity failure;
- driver or address problem;
- payment or duplicate charge;
- customer cancellation;
- suspected fraud;
- marketplace decision;
- system or integration failure.
Review the value and frequency by root cause. A high refund rate is an operational signal, not only a finance cost.
Staff authority
| Decision | Suggested control |
|---|---|
| Small partial refund | Trained shift lead within an approved limit |
| Full high-value refund | Manager review and documented reason |
| Redelivery | Kitchen and delivery capacity check |
| Chargeback evidence | Named owner with provider access and deadline tracking |
| Repeated claimant or suspected fraud | Escalation without public accusation |
Weekly review
- Total refunds, redeliveries and chargebacks separately.
- Identify duplicate remedies.
- Review response and resolution time.
- Find repeated causes by item, shift, driver or channel.
- Check unresolved provider cases.
- Update training or process controls.
Related guides
- Payments — the main guide for the wider topic.
- Chargeback Management for Restaurants — a detailed next step for putting this guidance into practice.
- Handling Refunds for Online Orders — a detailed next step for putting this guidance into practice.
- Receipts and Reconciliation — a closely related operational control to review alongside this page.
- Channel Profitability — a closely related operational control to review alongside this page.
- Failed Deliveries and Problem Handling — a connected decision that can change the recommended approach.
Official guidance checked
- GOV.UK: accepting returns and giving refunds
- GOV.UK: liability for disputed card payments
- Financial Ombudsman Service: chargeback as a card-scheme process
Guidance checked: 24 July 2026. Refund obligations, card-scheme procedures and marketplace allocation depend on the facts and current agreements. This operational guide is not legal advice.
