WhatsApp ordering for cloud kitchens
A cloud kitchen has no walk-ins, no signage and no captive footfall. Every order arrives through a channel someone else controls, which makes commission your largest controllable cost and customer ownership your biggest structural weakness. A direct WhatsApp channel addresses both.
The commission problem is sharper without a dine-in floor
A restaurant with a dine-in floor can absorb aggregator commission because a portion of revenue never touches the platform. A cloud kitchen has no such buffer — if aggregators are the only channel, the commission applies to effectively everything you sell.
At 22–28% on every order, the platform frequently earns more from a given order than the kitchen does once food cost, packaging, rent and labour are subtracted. Moving even a third of orders to a direct channel changes the shape of the business.
You cannot build repeat business you cannot contact
Cloud kitchen economics depend on repeat orders, because there is no location advantage to win a customer the second time. The difficulty is that on an aggregator you generally do not receive the customer's contact details, so a customer who loved your biryani last month is reachable only by paying the platform to show them an ad.
Orders placed on WhatsApp arrive with a phone number and a conversation thread. Within the platform's messaging rules you can legitimately reach past customers about a new item or a slow Tuesday, and the conversation history is already there.
Running several brands from one kitchen
Multi-brand operation is normal in cloud kitchens — separate menus and identities out of a shared production line. This works cleanly on WhatsApp because each brand can run its own number and menu while orders converge on one kitchen display, so the line sees a single queue rather than several dashboards.
- Separate customer-facing identity per brand
- One kitchen display for the whole production line
- Per-brand revenue and item performance in reporting
- Shared inventory reality without shared customer confusion
A realistic transition
Turning off aggregators on day one is a bad idea — they are still your discovery engine. The transition that works is gradual and uses the aggregator order itself as the acquisition step.
- Put a QR code and a WhatsApp number on every delivery bag and flyer
- Include a card with a first-order incentive for ordering direct next time
- Keep aggregators for discovery by customers who have never tried you
- Track what share of revenue is direct, monthly, and grow it deliberately
- Expect the shift to take months rather than weeks
Frequently asked questions
Will aggregators penalise me for taking direct orders?
Platform agreements vary and some restrict promoting competing channels inside their packaging or on their listing. Read your specific contract. Putting your own number on your own delivery bag is generally normal practice, but the agreement you signed is what governs.
How do I handle delivery without the aggregator's fleet?
Options are your own riders for a tight radius, a third-party logistics provider, or customer pickup. Many cloud kitchens start with a small direct-delivery radius where margins are best and keep aggregators for the long tail.
Does this work with multiple brands on one number?
It works better with a number per brand, since the customer's chat thread is the brand experience. The kitchen side still consolidates.
See whether it fits your business
Tell us what you run and how many orders you handle a day. If ChatBite is the wrong tool for you, we will say so.