Delivery & Growth

Refunds and Cancellations on Delivery Apps: The Margin Leak You're Not Measuring

A refund on a delivery app is money returned to the customer that, in many cases, is deducted from your payout — and it's almost always a P&L line restaurants never measure. Who pays depends on the cause: the platform often absorbs courier or logistics issues, while the restaurant typically eats refunds tied to missing items, wrong orders or quality complaints. Most operators run a refund rate between 2% and 5% of delivery sales; anything consistently above that is a controllable leak that usually starts in the kitchen or packaging, not in the app.

By Pimentón · 2026-11-11 · 4 min read

35%typical from stock / 86s

28%from prep time

1location that drags the rest

Common causes

• Stock / 86 35%
• Prep time 28%
• Address / rider 22%
• Other 15%

Illustrative split. The first step is tagging every cancellation: no cause, no lever.

Every week your delivery payout arrives a little lighter than the gross sales you rang up, and the gap rarely gets a name. A big part of that difference is refunds, cancellations, error charges and quality disputes. It's not the app quietly taking money — it's a cost line that exists in every channel and that most restaurants simply don't track. Measure it, and you'll find a margin leak you can actually close.

What refunds and cancellations actually are

These are four different events that get lumped together and shouldn't be:

• Refund: the customer gets money back after the order — usually for a missing item, wrong item or quality complaint. Often charged back to the restaurant when the cause is on your side.
• Cancellation: the order is stopped before or during preparation. The cost depends on who cancelled and when.
• Error charge (adjustment): a platform deduction applied when something didn't match the order — a missing drink, wrong protein, incomplete combo. It shows up as an adjustment on your payout.
• Quality dispute / chargeback: a formal complaint (cold food, spill, wrong order) that the platform reviews and may charge to you.

The key distinction: customer cancellation, restaurant cancellation and courier cancellation are not the same cost. A customer who cancels in the first seconds usually costs you nothing. A restaurant that cancels after cooking eats the food cost and takes a rating hit. A courier issue is typically absorbed by the platform. Knowing which bucket each event falls into is step one.

Who pays what

There's no single rule across Rappi, Uber Eats, DoorDash, PedidosYa or DiDi Food, but the logic is consistent:

• Restaurant pays when the cause is controllable: missing items, wrong items, undercooked or poorly packed food, long prep times that trigger cancellations.
• Platform/courier side absorbs many logistics failures: courier no-show, order lost in transit, app technical errors — though you often still need to flag them.
• Shared/grey zone: "food arrived cold" or "late delivery" can land on either side depending on timestamps and prep data.

This is why framing refunds as "the app robbing you" is a mistake: most charged-back refunds trace to something that happened in your kitchen or at handoff. The problem isn't the platform — it's not measuring where the error was born.

How to calculate your refund rate and lost margin

You can't manage what you don't size. Run this monthly, per app:

1. Refund rate = total refunds + error charges ÷ gross delivery sales. If you refunded $1,200 on $30,000 of delivery sales, that's a 4% refund rate.
2. Lost margin: multiply refunds by your contribution margin impact. A refunded order doesn't just lose the sale — you already paid food cost, packaging, labor and sometimes commission on it. A cancelled-after-cooking order can cost you more than its menu price in real terms.
3. Controllable vs non-controllable split: tag each refund by cause. If 70% are missing/wrong items, that's your fixable share.

Most restaurants that start measuring discover their refunds sit at 2%–5% of delivery sales, and that half or more is controllable. On a store doing $40,000/month in delivery, trimming a 5% refund rate to 2.5% can recover over $1,000 in margin monthly — before any new marketing spend.

Common mistakes that feed the leak

• Never reading the adjustments line on the weekly payout — so the cost stays invisible.
• Not tagging causes, which makes it impossible to tell a packaging problem from a prep-time problem.
• Not disputing legitimate errors. You can and should dispute refunds on Rappi, Uber Eats, DoorDash and PedidosYa when the data backs you up — photos, timestamps, order checklists.
• Blaming the app instead of the process. Beligerance doesn't recover margin; a packaging checklist does.
• Ignoring the rating impact. Cancellations and repeated quality complaints lower your rating and visibility, which quietly costs you future orders too.

A playbook to reduce the leak

1. Install a handoff checklist: every bag gets item-counted against the ticket before it leaves. Missing items are the #1 controllable refund.
2. Fix packaging for travel: separate hot and cold, seal liquids, vent fried items. Most "quality" disputes are packaging, not cooking.
3. Tighten prep-time accuracy so couriers don't wait and customers don't cancel.
4. Tag and review weekly: sort refunds by cause and attack the top two.
5. Dispute with evidence: build a simple routine to contest error charges that aren't yours.

How to read it in the weekly payout

On every platform's statement, look past gross sales to the adjustments / deductions section. That's where refunds, error charges and quality disputes appear, usually itemized by order. Reconcile it against your own tickets: match each deduction to a cause, confirm which ones are legitimately yours, and flag the rest for dispute. Done weekly, this 20-minute habit turns an invisible leak into a managed number — measure before you blame the channel.

Frequently asked questions