You Already Get Blamed When the Rider Is Late

Every zero commission pitch makes the same assumption: that restaurant owners have not done the maths.

They have. Ask any operator what an aggregator takes and they will tell you to the percentage point, along with what they pay for ads and what the Gold subsidy costs them on a good weekend.

The commission is not why they stay.

Ask them properly and you get the real answer, usually in one sentence.

If the rider does not turn up, the customer blames me.

On the platform, the thinking goes, a late delivery is Swiggy's problem. On my own channel, it is mine. So the commission is insurance, and going direct means buying back a risk somebody else is currently carrying.

That reasoning is completely rational. It is also built on a premise that turns out to be false.

The customer already blames you

There is a peer reviewed study on exactly this question, published in the British Food Journal, examining where customers place blame when a third party delivery goes wrong.

The finding is unambiguous. <cite index="5-1">Customers typically perceive such mishaps to be the responsibility of the restaurant rather than the delivery platform itself</cite>, and <cite index="6-1">they attribute failures such as wrong items, missing items, cold food or leaking containers to restaurants over third party platforms</cite>. The scale of the problem is not small either: <cite index="6-1">surveys suggest nearly a quarter of deliveries suffer some service failure</cite>.

The researchers went further and deliberately tested the hardest case. <cite index="4-1">Late delivery was selected as the failure scenario precisely because late delivery is typically outside the restaurant's control when a third party platform is used, usually caused by a driver being assigned multiple deliveries at once</cite>.

In other words, they picked the failure that is most obviously not the restaurant's fault.

The customer still blamed the restaurant.

Other data points the same way. An eduMe study reported by Restaurant Dive found that <cite index="7-1">66 percent of consumers blame the restaurant for incorrect, late or missing delivery items, 24 percent have requested a refund over an inaccurate order, and 20 percent say they would not order from that restaurant again</cite>. A Circuit survey covered in January 2026 found that <cite index="9-1">for late orders specifically, more than half of respondents said they would blame the restaurant rather than the delivery service or the driver</cite>.

So the insurance you thought you were buying does not exist

This is the part worth sitting with, because it reverses the entire calculation.

The aggregator absorbs the operational work of delivery. It does not absorb the reputational cost of delivery failing. That stays with you, on your listing, in your reviews, in the mind of a customer who will simply not order again.

Which means the current arrangement is the worst available split of the two things that matter.

They hold the control. You hold the blame.

The rider allocation is theirs. The batching decision that made your order late is theirs. The routing is theirs. You cannot see any of it, cannot intervene in any of it, and are not told when it goes wrong.

And when it does go wrong, the one star review has your restaurant's name on it.

Going direct does not add blame to your account. The blame is already there. What going direct adds is control over something you are already being held responsible for.

That is a completely different proposition from the one most operators think they are being offered.

The research also found the fix

The same study tested something more useful than the diagnosis.

<cite index="6-1">Including an observable cue indicating preventative action, such as time stamp information showing when an order was received and packaged for delivery, increased customer re order intention through the underlying mechanism of blame attribution</cite>. The researchers described it as <cite index="6-1">a practical method to shift blame away from the restaurant</cite>.

Read that carefully, because it is the most actionable finding in this entire area.

Blame is not fixed. It moves, based on what the customer can see. A customer who has no visibility assumes the failure belongs to whoever they interacted with, which is you. A customer who can see that your kitchen confirmed the order at 8:12, had it packed at 8:31, and handed it to a rider at 8:34 understands where the forty minute gap actually happened.

Now ask what you can show a customer on an aggregator order.

Nothing. There is no channel. You have no way to reach them, no way to timestamp anything, no way to tell them the food was ready twenty five minutes ago. The platform owns the entire communication surface and has no particular interest in telling your customer that the delay was theirs.

On your own channel you can show all of it. Automated status updates going back to the same chat the customer ordered from: confirmed, preparing, out for delivery, delivered. That sequence is not a convenience feature. It is precisely the observable cue the research says shifts attribution away from you.

The channel that lets you take orders directly is the same channel that lets you defend yourself.

The honest part

None of this makes the original fear silly, and it would be dishonest to pretend otherwise.

Going direct genuinely does add operational responsibility. Somebody has to book the rider. Somebody has to notice when no rider gets allocated at 9:40 on a Saturday. Somebody has to make a decision about the customer whose food is sitting under the pass with nobody to carry it.

On an aggregator, that work happens somewhere else, and however badly it is done, it is not being done by your floor manager during service.

So the correct answer to "what if the rider does not show" is not that it will not happen. It will. The correct answer is a named person whose job is to handle it when it does.

That is the part most direct ordering vendors skip. They hand over an integration and leave. An integration does not phone anybody at 9:40 on a Saturday.

How we handle it

Menuthere connects Porter delivery directly into the order screen, so a rider is booked from the same place the order arrives, with live tracking shared to the customer.

Behind that, every restaurant gets a named account manager who oversees delivery allocation on your orders. If a rider is not allocated, we arrange an alternate delivery partner without waiting for you to notice. If the delivery genuinely cannot be completed, we refund the customer so the experience closes cleanly and your name is protected.

And no refund is ever processed without your permission. We recommend, you decide, because it is your restaurant's name on the bag.

It also works alongside your own riders. Nearby orders on your delivery boy, distance and peak overflow on Porter, whichever suits the order.

What to do before you decide

1. Read your own delivery reviews. Go through the last fifty and count how many complain about something that happened after the food left your kitchen. Those are already on your listing. You have been paying commission and carrying them anyway.

2. Separate the two objections. "I will lose money" and "I will get blamed" are different problems with different answers. Most owners have merged them into one vague reluctance. Once you separate them, the first is arithmetic and the second is an operational question about who handles exceptions.

3. Ask any direct ordering vendor what happens at 9:40 on a Saturday. If the answer is a dashboard, that is not an answer. Ask who calls, what they do first, and who decides on the refund.

4. Start with the orders where the risk is lowest. Short distance, repeat customers, off peak. Prove the delivery layer works before you move your Friday night volume onto it.

The bottom line

The commission argument has been made a thousand times and it has not moved the market, because it was never the real objection.

The real objection is that a restaurant owner's name is on every bag that leaves the kitchen, and handing that name to a rider they did not book, cannot see and cannot reach feels like a risk worth paying twenty five percent to avoid.

Except the research is clear that they are not avoiding it. The customer blames the restaurant for the late order, the missing item, the cold food, even when the platform caused it and even when the study was designed specifically to test the case where the restaurant plainly could not be at fault.

You are already carrying that risk. You are just carrying it with no control over the outcome, no visibility into what went wrong, and no way to tell the customer your side.

Take the control, not just the margin. Menuthere gives you WhatsApp ordering, Porter delivery from the same screen, and a named account manager watching allocation on every order.

Sources: Lefebvre, Orlowski and Boman, British Food Journal 2024 (blame attribution in third party delivery service failures, observable cue findings), eduMe via Restaurant Dive (consumer blame and reorder intent), Circuit survey via Restaurant Business Online, January 2026 (late order blame attribution).