Delivery Platform Refund Disputes: UK Restaurant Guide

Refund clawbacks are the payout deduction most restaurants notice but least understand. When a customer claims a missing item, a quality issue, or a late delivery, the platform deducts the refund amount from your next payout — sometimes without notification, and often without obvious evidence that the claim was valid.

For a restaurant doing 300 orders per week across three platforms, even a 2% refund rate means six deductions per week. At £15 per refund, that is £90 per week — over £4,500 per year in refund costs. Platforms acknowledge that a proportion of refund claims are disputed by operators, and operators commonly report that a meaningful share of the deductions they see are questionable — not evidenced by a clear customer fault or missing item.

This guide covers how refund clawbacks work on each platform, which categories you can dispute, and the practical process for tracking and challenging unjustified deductions.

How platform refund deductions work

When a customer reports a problem with an order — missing items, incorrect items, damaged packaging, unacceptable food quality, or very late arrival — the platform's support team assesses the claim. If the platform approves it, the refund is issued to the customer and the deduction appears in your next payout.

The key point: the deduction happens before you can respond. Unlike a traditional chargeback process, platforms deduct first and — in theory — allow disputes after. In practice, the dispute window is short and the burden of proof is on the restaurant.

Each platform handles this slightly differently:

Deliveroo: Refund deductions appear in the weekly statement. Deliveroo operates a dispute window (commonly around 1-2 weeks after the deduction, though the exact window varies and may change — check your current platform agreement), during which you can challenge the claim through the Restaurant Hub. Evidence required: POS records showing the item was included in the order, photos where available, preparation notes. Uber Eats: Refund deductions appear in the Payment Details CSV (the per-order report). Uber Eats allows disputes through the Uber Eats Manager portal. The dispute window and evidence requirements are similar to Deliveroo. Uber Eats has an "order accuracy" programme that tracks your restaurant's reported accuracy rate — a persistent pattern of refund claims affects your visibility and ratings. Just Eat: Refund deductions appear in the weekly invoice. Just Eat's dispute process goes through the Partner Centre or the support contact channel. Just Eat is generally considered the most difficult of the three to dispute effectively, partly because the weekly invoice format makes individual order tracking harder.

Categories of refund you can challenge

Not all refund types are created equal for dispute purposes. The refund categories where you have the strongest case:

Missing item claims: If your POS records show the item was included in the order confirmation, and you have the order printout or KDS record, you have evidence to challenge a missing-item claim. This is the most disputeable category. Incorrect item claims: Where your records show the correct item was on the ticket and the receipt, and the variation in the delivered item is not substantiated by a photo from the customer, this is challengeable. Quality complaints on sealed containers: If the product was sealed at the time of handover and no photo evidence shows the issue within the container, a quality claim is harder for the platform to substantiate. Late delivery attributable to the rider, not the kitchen: Platforms sometimes apply refunds for late arrival where the kitchen preparation time was within the quoted time and the delay was the rider's. This category is harder to dispute but worth tracking — a pattern of rider-attributable refunds is evidence for a broader complaint. Duplicate claims: Occasional cases where the same order generates more than one refund deduction. Identifiable by matching order IDs across your POS and the platform report.

Categories that are harder to dispute

Photo-evidenced quality issues: If the customer submitted a photo showing a clear quality problem (wrong item, visibly spoiled food, incorrect portioning), disputing without counter-evidence is difficult. Late delivery where kitchen time was the factor: If your own prep time exceeded the quoted time, this is likely not disputable. Customer preference complaints: "I didn't like it" or "not what I expected" — platforms generally absorb these rather than attributing to operator error, but when they do attribute, the evidence bar is low.

Building the evidence base

The practical constraint on disputes is evidence. The platform's assessment is based on the customer's report; your counter-evidence needs to be documentary. What you need in place:

POS order records. Every order should have a printout or KDS record that shows each item, timestamp, and order ID. This is your primary evidence for missing-item and incorrect-item disputes. If your POS does not produce a per-order record that you can retrieve after the fact, that is a gap to fix. Packaging confirmations. Some restaurants photograph sealed bags before handover, particularly for high-value or frequently disputed items. This is operationally demanding but provides the strongest evidence for sealed-container quality claims. Rider handover timestamps. If you can record the time each order was handed to the delivery rider (not the platform's time estimate, but the actual handover), you have evidence for rider-delay attributions. Most POS systems or KDS setups can capture this. Weekly refund log. Maintain a spreadsheet (or use your payout reconciliation data) that tracks every refund deduction by order ID, amount, date, and category. You cannot dispute what you do not track.

The dispute process in practice

Once you have identified a refund deduction you want to challenge:

1. Match the order. Cross-reference the refund deduction (from the payout report) to the original order in your POS. Note the timestamp, the items ordered, and any special instructions.

1. Retrieve your evidence. Print or export the POS record for that order. Attach any photos, KDS records, or preparation notes.

1. Submit through the platform's dispute channel. Each platform has a specific path:

- Deliveroo: Restaurant Hub → Orders → [specific order] → Report an issue - Uber Eats: Uber Eats Manager → Reports → Payments → dispute the specific line - Just Eat: Partner Centre support contact

1. Note the dispute reference number. For tracking and follow-up.

1. Follow up if no response within the stated window. Platforms do not always respond proactively; a follow-up contact often prompts resolution.

Tracking refunds in your payout reconciliation

Effective dispute management starts with good reconciliation. If you record each payout as a net lump sum, you cannot see the refund component — which means you cannot track, let alone dispute, individual refund deductions.

The correct reconciliation treatment is to book refunds as a separate line in your weekly journal:

• Gross food sales: £4,000
• Commission: -£960
• VAT on commission: -£192
• Refunds: -£120
• Net to bank: £2,728

With refunds on their own line, you can compare your refund rate week by week across each platform, spot unusual spikes, and maintain the order-level tracking needed for disputes.

For the full payout reconciliation workflow — including how to record refunds per platform — see our multi-platform delivery reconciliation guide. For the Xero-specific journal setup, see our Xero delivery accounting guide.

What to do when a dispute is rejected

Platform dispute decisions are not always final. If an initial dispute is rejected:

1. Request a review — most platforms have a second-level review process
2. Escalate to account management — if you have a dedicated account manager (typically available for higher-volume operators), they have more latitude than frontline support
3. Document the pattern — a series of rejected disputes on the same claim type (e.g. Deliveroo repeatedly upholding customer claims on sealed-container quality issues) is a pattern you can raise with the account team

Persistent patterns of questionable refund deductions, especially where your POS evidence is strong, are worth escalating. Platforms have an interest in not alienating restaurant partners — particularly those doing meaningful volume — and account teams can sometimes achieve what support desks cannot.

Key takeaways

• Refunds are deducted before dispute — the burden of proof is on the restaurant to challenge, not the platform to prove.
• Missing-item and incorrect-item claims are the most disputable — especially with POS evidence showing the item was included.
• You cannot dispute what you do not track — weekly refund recording, per order ID, is the foundation of any dispute process.
• Each platform has a limited dispute window — commonly around 1-2 weeks after the deduction appears in the payout report, though exact windows vary and change; missing the window closes the option.
• Good payout reconciliation makes refund tracking automatic — booking refunds as a separate journal line gives you the data without extra work.

---

This guide covers refund dispute processes for UK restaurants on delivery platforms and is for general guidance only. Platform policies and dispute windows change — check your current platform agreement for specific terms. This is not legal or financial advice.