In this article
A notification comes in: a guest got a refund because last night's order "never arrived". Except it did — the kitchen made it, someone packed it, and the courier picked it up. The money is simply gone from your payout, without anyone in the building ever getting the chance to push back. This article is about that claim: how often it happens, why the platform almost always sides with the guest, what it really costs you, and whether fighting it is worth it.
Every fraud article on this site so far has covered someone impersonating your restaurant, or a guest who leaves before paying. This is the third, different kind: an order that went perfectly right — correctly made, correctly packed, handed off on time — and still costs you money afterwards, because a delivery platform believes the guest's complaint by default.
"Item not received" fraud (INR, for short) is the formal term: a customer claims an order never arrived, even though the app itself shows it as delivered, and gets the full amount refunded. Sometimes it's an honest mistake by the courier. Often enough, it isn't a mistake at all — it's someone who knows a platform will refund almost automatically without demanding proof, and uses that pattern deliberately.
What sets this apart from every other fraud pattern on this site: there is no criminal swapping a sticker or hacking a system here. The platform itself decides, on the basis of a policy built to keep the customer happy — and the bill lands on the kitchen that did nothing wrong.
Seven numbers, in this order: how much of your revenue is already tied up in this, why it hits harder than the percentage suggests, why delivery is riskier than a table bill to begin with, what one dispute really costs you, the flat fee stacked on top, how big the problem is across the whole delivery industry, and the clock that starts ticking the moment a claim lands.
Why most kitchens never add this up
A single €25 or €30 refund doesn't feel like a problem — it's the cost of doing business, most owners think, and move on. That's exactly why the pattern never gets totalled: every refund gets written off on its own, never summed into what it actually is over a year.
Platforms make it easy to ignore, too. A dispute shows up as one line in a payout statement, buried among dozens of others, with no clear flag that there's something to contest — and even when it is noticed, responding takes time most kitchens don't have mid-service.
The rest of this article adds up what most kitchens never do: what share of your delivery revenue is tied up in this, what that actually means for your delivery profit, and — the part that sets this apart from every other fraud topic on this site — whether it's worth your time to fight every dispute, or better spent elsewhere.
Free guide Everything digital in your restaurant, in one guide From QR ordering to cybersecurity — the complete guide to the digital side of your restaurant. Read the guide7 numbers most restaurants have never looked up
Every number below comes from a published source — an industry data provider, a fraud-prevention study, or a platform's own policy — never an estimate from this site. Together they explain why a "small" refund here and there isn't an incident; it's a structural leak in your delivery channel.
1. How much of your delivery revenue is already tied up in this
Industry data from Voosh, a company that specialises in resolving platform disputes, shows that on average 2.5 to 3% of the total revenue restaurants run through delivery platforms is tied up in some form of dispute — a missing item, a wrong order, or exactly the claim this article is about: "never arrived".
That number sounds modest next to a food-cost percentage or a labour-cost percentage, and that's precisely the problem: nobody puts it next to those other percentages. No one keeps a running line for "money lost to disputes", even though that same discipline exists for every other cost line in the business.
It's also not a fixed amount — it scales with your delivery volume. A restaurant that doubles its delivery revenue without ever checking this percentage doubles the euros disappearing into disputes at the same time, without anyone seeing it grow as its own line item.
Each from a separate, published source — together the reason "it's just one refund" hides the problem instead of explaining it.
Sources: Voosh data via Restaurant Business Online ("Restaurants say they're bearing the brunt of delivery chargebacks"); Appriss Retail / Deloitte 2025 fraud study; Merchant Risk Council 2026 Global Payments and Fraud Report.
2. Why it hits harder than the percentage suggests
2.5 to 3% of your delivery revenue sounds too small to act on — until you set it against your delivery profit instead of your delivery revenue. Delivery margins are already thin after platform commission, packaging and the extra labour minutes, and against that backdrop, Restaurant Business Online reports the same disputes represent roughly 20% of restaurants' already slim delivery profits.
In other words: of every five euros of delivery profit a restaurant keeps, roughly one disappears directly into disputes — not into labour, not into ingredients, but into refunds for orders the kitchen made correctly.
That's why this article measures the percentage against profit rather than revenue: a cost dismissed as "small" on revenue is exactly the percentage that decides whether a delivery channel contributes something or merely breaks even.
3. The risk that's already built into every online order
A bill a guest pays by card at the table carries a chargeback rate of roughly 0.5% — the card is physically present, the payment happens in view, and a dispute afterwards is rare. Online orders, delivery included, run structurally higher: between 0.6 and 1.0%, close to double.
That gap isn't about who your guests are — it's about the channel itself. A card-not-present transaction (the card is never physically shown or swiped) is by definition easier to dispute than a payment that happened at a table in full view, and platforms design their dispute policies with exactly that difference in mind.
For a restaurant that treats delivery as a second or third channel next to the dining room, this means every euro that arrives through an app carries a higher risk profile from the start than the same euro settled at a table — before a single complaint ever lands.
4. What an upheld dispute really costs you
The naive maths says one refund costs you the price of that order. The real maths adds more: the ingredients already spent that never come back, the staff time it took to make it, and — see the next number — a flat fee many platforms stack on top.
Analyses from chargeback-specialist firms put the true cost of a single upheld dispute at 2 to 3 times the original order value once all of that is counted — not because the platform punishes you extra, but because a "€32 refund" on paper is a different amount from €80 of margin actually lost in practice.
That difference is exactly why this article doesn't treat one dispute as equal to one lost order. It counts, like every number here, what a dispute really costs — not what it looks like it costs on the payout statement.
5. The flat fee stacked on top of the refund
On top of the refunded amount itself, many platforms and payment processors charge a flat dispute-handling fee — an amount unrelated to the order's value that applies the moment a complaint is formally processed as a dispute, regardless of the outcome. Data from chargeback-specialist firms puts that flat fee between $20 and $100 per dispute.
For your restaurant, converted, that works out to roughly €45 per dispute — an amount that, on a €32 refund, sharply increases the real damage, and one that weighs the same on a cheap order as on an expensive one.
That's also why this cost is sneakier than a percentage of revenue: it's fixed, it stacks on top of the refund itself, and it's rarely called out on its own — usually one line buried in a payout statement nobody fully reads during a busy week.
What a refund looks like it costs, what stacks on top of it, and what a dispute really costs once everything is counted.
The first amount is an illustrative average order value. The second is the flat dispute fee (source: chargebacks911.com, $20–$100 per dispute). The third is 2 to 3 times the order value (source: delivery-sector chargeback cost analyses) — converted into your own currency.
6. The claim that costs more than the meal
Fraud-prevention firms Appriss Retail and Deloitte estimate that "refund abuse" — a false claim that an order never arrived, made to get the money back without returning anything — accounts for nearly half of all fraud on delivery apps, inside a reported $103 billion loss across online retail and delivery in 2025.
That $103 billion figure covers far more than restaurants — it spans all of online retail and delivery. It's cited here not as a restaurant-specific loss but to show the scale your business operates inside: "never arrived" claims aren't a rare misunderstanding, they're the single largest fraud category inside a multi-billion-euro problem.
What that means for a kitchen in practice: the odds that any given refund claim is deliberate rather than an honest mistake are real enough to build a policy around — not to distrust every guest, but to understand the platform you work with already knows this pattern exists and hasn't fully closed it.
7. The clock that's already ticking — and the trend making it worse
When a dispute lands, you typically get a limited window to respond before it becomes final — Uber Eats, for example, gives merchants 30 days to contest an adjustment on their payout. After that, the decision stands, whether or not you could still have supplied proof.
That window matters more, not less: the Merchant Risk Council's 2026 Global Payments and Fraud Report finds 64% of merchants report a meaningful rise in exactly this kind of refund and policy abuse — it's the single biggest concern merchants name today, ahead of stolen card details.
For a kitchen with no routine to track disputes, that means the window to respond isn't getting any wider while the problem grows — it stays exactly as short, while more claims have to fit through it.
Is it worth fighting, or better to just eat it?
This isn't the classic "risk versus prevention" calculator you'll find elsewhere on this site. The question here is sharper and comes up more often: when a dispute lands, is it worth gathering proof and contesting it — or does that cost more time than it recovers?
Enter your own numbers. The tool weighs two scenarios against each other: what it costs if you eat every single dispute, versus what it costs if you fight every single one — including the time that takes, against what your time is worth.
Eat it or fight it: which is cheaper for your restaurant?
Enter your own numbers — the rest does the math.
—
Default dispute rate: 3% of orders — the midpoint of Voosh's 2.5–3%-of-revenue range. Replace it with your own estimate.
This is a thinking exercise with your own numbers, not an accounting guarantee — the assumptions (12 minutes per dispute, a 55% win rate when you contest) are explained below and are illustrative.
The tool assumes an average of 12 minutes to gather proof (a photo of the packed order, a timestamp, a courier handoff confirmation) and file it, and a win rate of roughly 55% once you supply that proof consistently — both illustrative assumptions, not measured figures for your specific platform.
What the tool doesn't measure: spotting the pattern. The same guest claiming "never arrived" three times in a month isn't a coincidence anymore — and you only see that pattern if you track disputes, regardless of what the maths above says about whether fighting is worth it.
How to fix this tomorrow, without a new system
Three steps, in the order they pay off — from before the order leaves the kitchen to what you do once a dispute actually lands.
1. Build proof before the courier leaves
- Photograph every packed delivery order right before handoff — most apps or POS systems timestamp it automatically.
- Have the courier sign or scan at pickup if your platform offers that option, and keep the confirmation.
- Use sealed or tamper-evident packaging where possible — it's proof, and it also discourages some false claims before they happen.
2. Respond inside the window, every time
- Assign one person or a fixed weekly moment to check the payout statement for disputes — don't wait for one to happen to be noticed.
- Submit proof the moment a dispute appears, not right before the 30-day window (or your platform's own window) closes.
- Keep a short log of which guest, which amount and which outcome — that's what makes a pattern visible.
3. Work out whether fighting is worth it, and act on it
- Use the calculator above with your own volumes, average order and what your time is worth.
- If the result is low, put that time into the prevention step above instead of contesting every dispute individually.
- Redo the maths whenever your delivery volume changes noticeably — the answer shifts with order count.
The short answer
A "never arrived" claim isn't a rare misunderstanding — it's the single largest fraud category on delivery apps, and most platforms' policies are built to side with the guest by default, not with the kitchen that made the order correctly.
The damage runs deeper than the refund alone: add the flat dispute fee, the sunk ingredients and labour time, and the share this represents of an already-thin delivery profit, and "it's just one refund" stops holding up.
The fix doesn't need a new system — a photo before the courier leaves, a fixed moment to track disputes, and the maths in this article to know whether fighting is worth it at your volume.