REVENUE PROTECTION 8 September 2026 4 min read

A wrongful refund costs more than the order

The refunded amount is the part you can see. Three costs land with it that never show on the statement.

A customer reports a missing item. The channel refunds them, charges it back to you, and the case is closed before anyone in your branch hears about it. On the statement it shows up as one line, at order value. That line is the cheapest part of what just happened.

Short on time

The cost extends beyond the order

A refund may follow food preparation and delivery costs already incurred.

Separate the losses

Separate the refund, remake and delivery-app charges before judging the impact.

Return to the order

The order reference and preparation record explain more than a weekly total.

Start with one branch

Compare real claims with available evidence before expanding a process.

Four costs, one line item

The refund is a reversal of revenue you had already earned. Everything that produced the order stays spent.

WHAT ONE FORCED REFUND TAKES
The order valueReversed in full, even when the fault is disputed.
Food and packagingAlready consumed. The margin on that order is gone, not deferred.
The delivery feeUsually charged on the original order and not returned with the refund.
Your team’s timeSomebody checks the ticket, calls the branch, and writes back. On a busy channel this is an hour a day.

Take your own refund rate from finance and apply it to delivery revenue rather than total revenue. The number is normally larger than the operations team expects, because the loss is calculated after cost of goods rather than before it.

Why the same branches keep getting hit

Channels do not target restaurants. They respond to friction. A claim that goes unanswered is cheap for them to grant; a claim that comes back with a record is expensive to process. Over a few months, the branches that never answer accumulate more claims than the branches that do.

A branch that cannot answer a claim is teaching the channel that claims land.

This is not a theory about intent. It is what happens when a dispute process is built to resolve quickly and one side always concedes.

The window closes faster than the evidence arrives

Most aggregator claims have to be answered within a few days. That is usually enough time, if the evidence already exists. It is never enough time if somebody has to find the right branch, pull the right hour of footage from a recorder, and match it to an order number by hand. By the time that is done the case has closed and the amount is settled.

So the problem is not that restaurants lack evidence. Cameras have been in these branches for years. The problem is that the evidence is not attached to the order, and a claim can only be answered order by order.

What an answer actually needs

An answer that settles a claim is short. It names the order, fixes the time, and shows the items going into the bag. If the bag was sealed, the seal has a timestamp of its own. That is the whole case.

Anything less than that becomes an argument about process, and process arguments are lost by whoever has less documentation.

Three things worth doing this week

01
Ask finance for the refund rate by channel
Not the blended figure. One channel is usually much worse than the others, and that is where to start.
02
Time one claim end to end
From the notification to the reply you were able to send. That duration is the real constraint, not the refund rate.
03
Pick one branch and one channel
Answer every claim there for two weeks with whatever evidence you can assemble. The claim volume tends to tell you something on its own.

None of that needs a vendor. It gives you the two numbers you would need to judge one.

PUT YOUR OWN NUMBERS IN

ROI calculator

Four inputs, and the workings stay on screen.

Open the calculator

Read next.

Or just send us a week of orders.

Two weeks on one branch settles the question faster than any article.

Get a demo