Delivery-App Commissions vs Your Own Ordering Channel: The Payments Cost Trade-off

Published: 20 October 2026

Category: how-to-guides | cardbuzz

Tags: food delivery, commissions, cloud kitchen, payment gateway, ordering channel, food business, customer acquisition

Every cloud kitchen in India faces the same fork in the road: sell through the big delivery aggregators and pay their commissions, or build your own ordering channel — a website, a WhatsApp ordering flow, a simple app — and keep the margin. The debate usually centres on commissions, but the payments layer underneath changes the maths in ways founders underestimate. How customers pay, what that payment costs you, and who funds the discounts all interact. This is a guide to thinking through the trade-off mechanically, without the usual slogans from either side.

What aggregator commissions really buy you

An aggregator commission is not just a fee; it is a bundled purchase. For that cut of each order, you get discovery (customers finding you while browsing), logistics (the delivery fleet), payments infrastructure (cards, UPI, wallets handled for you), and a degree of trust (customers order from unknown kitchens because the platform guarantees the transaction). For a new cloud kitchen with no brand, that bundle is genuinely valuable — it replaces a marketing budget, a delivery team, and a payment setup you would otherwise have to build.

The mistake is treating the commission as pure cost. The right question is what it would cost you to replicate each component independently. Discovery through your own ads, delivery through your own riders or a third-party logistics partner, payments through your own gateway — each has a price. The commission looks expensive until you price the alternative stack honestly. It looks like a bad deal precisely when you have already built brand and repeat demand, because at that point you are paying for discovery you no longer need.

The true cost stack of a marketplace order

To compare fairly, break a marketplace order into its cost layers. The headline commission is the largest, but it sits alongside discount funding (who pays for the coupon the customer applied — often partly or fully you), packaging extras demanded by delivery (leak-proof, tamper-evident, which costs more than dine-in packaging), and the operational cost of platform-driven unpredictability (surge-hour staffing, rating anxiety, menu compliance).

There is also a subtler cost: customer ownership. The aggregator owns the relationship. You cannot easily remarket to the customer who loved your biryani, you cannot see their full order history, and you cannot control the experience beyond the food. That data gap has a compounding cost — every order through the platform is an order that does not build your own customer base. Founders who ignore this end up permanently renting demand instead of owning it.

Your own ordering channel: the payment mechanics

Running your own channel flips the cost structure. You keep the commission, but you now pay for payments directly. A payment gateway charges per transaction — a proportion of the order value plus sometimes a fixed component — and that charge applies to every card payment you accept. UPI, by contrast, typically carries no merchant charge for the small-ticket person-to-merchant flows most food orders fall into, which makes UPI-heavy customer bases cheaper to serve on your own channel.

This creates a real strategic variable: your payment mix. If your direct-channel customers mostly pay by UPI, your payment costs are negligible and the channel is dramatically cheaper than the aggregator. If they mostly pay by card, gateway charges eat part of the saving — though still far less than a full commission. Encouraging UPI on your own channel, through small nudges at checkout or UPI-first payment ordering, is one of the highest-leverage optimisations a cloud kitchen can make.

Beyond gateway charges, the own-channel stack includes the cost of driving traffic (ads, influencer seeding, locality marketing), delivery fulfilment (your riders or a logistics partner's per-order fee), and the technology itself (website, ordering system, or even a managed WhatsApp commerce tool). None of these is free; the honest comparison is the full own-channel stack against the full aggregator stack.

Repeat customers change the maths

The single most important variable in this decision is your repeat rate. Aggregators are efficient for acquisition and expensive for retention. Paying a full commission on a customer's twentieth order — a customer who would have ordered directly if you had a channel and a reason to use it — is pure margin leakage.

The mechanical way to think about it: acquisition orders can justify the commission, because the alternative is spending on ads with uncertain returns. Repeat orders rarely justify it, because the customer is already yours. This is why the standard mature playbook is a hybrid — stay on aggregators for discovery and new-customer flow, while systematically converting repeat customers to your direct channel with packaging inserts, loyalty incentives, and a genuinely smoother direct ordering experience.

Measure this, don't guess. If you can estimate what share of your aggregator orders come from repeat customers, you can estimate the margin you are donating. Even a rough number reframes the decision from ideology to arithmetic.

Discount funding: who really pays

Discounts deserve their own analysis because they distort the comparison. On aggregators, platform-wide sales and coupon campaigns are often co-funded — the platform funds part, you fund part, and the split is buried in settlement reports. Founders frequently discover that their "commission" understates the true platform cost once discount contributions are included. Read your settlement statements line by line; the real platform cost is commission plus your discount contribution plus any marketing or visibility fees.

On your own channel, you control discounting completely. That control is powerful — you can run tight, targeted offers (a free dessert on the third direct order, a birthday coupon) instead of blanket discounts. But it also means every rupee of discount comes from your pocket. The discipline is to discount for behaviour change (first direct order, repeat purchase) rather than for volume vanity.

The credit card angle for founders

Where do credit cards enter this picture? On the cost side, your gateway charges for card payments on the direct channel are a business expense — put the gateway settlement account's fee payments on a card where the biller accepts it, and route any ad spend for driving direct traffic through a card that rewards online advertising categories. On the revenue side, accepting cards on your own channel is non-negotiable for ticket sizes above impulse levels; customers ordering a family dinner expect card options, and the gateway fee is simply the cost of capturing that order.

One more founder-level use: the float. Ad spend and gateway fees paid by card ride the interest-free period, which smooths the lumpy cash flow of running your own acquisition. Just as with procurement, the rule is absolute — pay in full, every cycle.

The hybrid playbook most kitchens run

In practice, successful cloud kitchens converge on a similar structure. Aggregators handle discovery and fill off-peak capacity. The direct channel — website plus WhatsApp — serves repeat customers with better margins. Packaging carries a direct-order incentive. A simple loyalty mechanic (every Nth order free, or a standing direct-channel discount) gives customers a reason to switch. And the payments mix on the direct channel is nudged toward UPI to keep transaction costs minimal.

The transition is gradual and measurable. Track the share of revenue from your direct channel monthly. When it crosses the point where direct-channel fixed costs are covered and growing, you have optionality — you can negotiate harder with aggregators, be selective about which platforms you stay on, and ultimately treat them as one acquisition channel among several rather than your landlord.

Key takeaways

  • Price the full stacks, not the headlines: aggregator cost is commission plus discount contributions plus platform fees; own-channel cost is gateway charges plus traffic plus delivery fulfilment.
  • Your repeat rate decides the strategy: aggregators for acquisition, your own channel for retention — convert repeat customers systematically.
  • Read settlement statements line by line to find your true platform cost, including co-funded discounts.
  • Nudge direct-channel payments toward UPI to minimise gateway charges; accept cards for higher ticket sizes regardless.
  • Run discounting for behaviour change on your channel, not volume vanity — targeted beats blanket.
  • Track direct-channel revenue share monthly; optionality over aggregators is earned gradually, not declared.