WhatsApp Ordering · Cloud Kitchens · India · 2026

WhatsApp ordering for Indian cloud kitchens — zero commission, live in 48 hours, ₹199/month.

Cloud kitchens are 100% delivery-dependent, so every rupee lost to aggregator commission is a rupee off the bottom line. Online eMenu puts your menu on WhatsApp, auto-synced from your POS, with multi-brand routing, Swiggy/Zomato in the same live queue, and payment inside the chat via UPI. Repeat guests move from 27% commission to 0%.

Start 14-day free trial → WhatsApp See pricing

48-hour go-live · 0% commission · Swiggy + Zomato in one queue · ₹199/mo · India + GCC

Live · Cloud kitchen POS → WhatsApp → POS queue

MENU · Andheri Shared Kitchen Live

Biryani House Wok Bowl Burger Lab Filter Coffee Co.

Hyderabadi Chicken BiryaniMains · 620 kcal

₹380

Veg BiryaniMains · veg

₹260

Mutton BiryaniMains · slow-cooked

₹460

Raita & Salan comboSides · veg

₹60

PhirniDessert · seasonal

₹90

4 brands · one kitchen · Andheri West Auto-sync · 3 sec ago

Menu sync

Meta Catalog
API

Multi-brand collections

WhatsApp
Business

One number · all brands

Order returns · UPI paid

Andheri Kitchen · 4 brandsBusiness · typically replies instantly

Biryani House Wok Bowl Burger Lab

Biryani House · Live 18 items

Chicken Biryani

₹380

Add

Veg Biryani

₹260

Add

Mutton Biryani

₹460

Add

Raita + Salan

₹60

Add

2 items · ₹440UPI · pay in chat

Checkout

The unit economics

Why cloud kitchens are the highest-leverage users of WhatsApp direct

A dine-in restaurant that loses a rupee to Swiggy commission still has a walk-in crowd paying full price on the same night. A cloud kitchen has no walk-in crowd. Every rupee of revenue comes through a delivery channel, and today that means Swiggy and Zomato take the first 25% to 32% off every ticket before the operator sees a paisa. On a food-cost of 32% and rent-plus-labour of another 24%, aggregator commission is what turns a lot of Indian cloud kitchens from break-even into loss-making by month four.

WhatsApp direct changes the maths because WhatsApp is not an aggregator — it is a direct channel that happens to have 500 million daily users in India. The operator does not pay a commission per order. There is no bidding for search placement inside the WhatsApp catalog. The customer relationship, the phone number, and the order history belong to the outlet, not to a third party. The only variable cost is the Meta conversation fee on marketing-initiated messages — roughly ₹0.80 to ₹1.20 per conversation — versus 27% of the ticket on an aggregator order.

The ₹ maths on a real 30-order-per-day cloud kitchen. Average ticket ₹450, monthly revenue ₹4.05L. On 100% aggregator flow at a 27% blended take rate, ₹1.09L walks out the door in commission every month. Shift 30% of that volume — the repeat orders, the corporate lunches, the Saturday-night regulars — to WhatsApp direct within 90 days, and the aggregator bleed drops to roughly ₹0.76L. The recovered ₹33,000 to ₹37,000 a month is a real number: 3 to 4 months of a shared-kitchen bay in Andheri, Powai or Whitefield.

The lever gets bigger as ticket size grows. A cloud kitchen doing an average ₹600 ticket on 40 orders a day turns over ₹7.2L monthly and bleeds ₹1.94L in commission. The same 30% shift recovers ₹58,000 a month. Multiply across an operator running two or three cloud kitchens under different brands and the annual number is meaningful in ways that a one-line-item POS spend can never claim to be.

The flow

How WhatsApp ordering works for a cloud kitchen — step by step

Six stages between the customer opening WhatsApp and your rider reaching their door. No dashboard your team has to babysit.

Customer messages your outlet

The lead comes from one of four sources: an insert card printed in the aggregator delivery bag, a Click-to-WhatsApp button on your Google Business Profile, a Meta ad running on Facebook or Instagram, or a QR sticker on the packaging. Any of them opens WhatsApp with a pre-filled "see menu" message.

The catalog opens inside the chat

The WhatsApp Business Catalog renders as a native product list — image tiles, category chips, prices in ₹, availability toggle. It is auto-synced from your POS in the last 5 seconds, so what the customer sees is exactly what the kitchen can cook right now. Sold-out biryani has already disappeared.

Customer builds the cart, chooses delivery

Items go into the cart. Delivery is the default fulfilment mode for a cloud kitchen; pickup can be switched on for outlets that offer it. Address is captured either via the pinned location in the chat or a saved delivery address from an earlier order.

Payment via UPI in-chat

A dynamically-generated Razorpay link lands inside the same WhatsApp thread. The customer taps to pay via PhonePe, GPay, Paytm, BHIM or a card. The confirmation returns to the chat automatically. Cash on delivery stays available for outlets that want it.

Order lands in the POS live queue

The paid order drops into the same live queue that already holds your Swiggy, Zomato and dine-in tickets, tagged with the correct brand and station. The KOT prints on the kitchen thermal, the KDS lights up the prep and pack stations, and rider allocation fires — either to your in-house fleet or to Porter, Dunzo or WeFast via the integration.

Status updates push back to the same thread

Cooking, ready, out for delivery, ETA, delivered — every status transition pushes an update to the same WhatsApp thread. No SMS, no email, no separate app. If the customer replies to the update, the reply lands in your live queue as a customer service ticket.

The wire-level detail — templates, the 24-hour session rule, webhook JSON, Green Tick verification — is covered in the WhatsApp ordering + POS integration deep-dive.

Four scenarios

The 4 cloud kitchen scenarios where WhatsApp direct is decisive

Not every cloud kitchen needs WhatsApp for the same reason. These are the four operator profiles where the ₹ shift lands hardest.

1. Multi-brand cloud kitchen — one WhatsApp number, all brands, cross-sell

A shared kitchen in Powai runs Biryani House, Wok Bowl, Burger Lab and a filter coffee brand out of the same prep line. On aggregators, each brand is a separate listing that competes for the customer's attention. On WhatsApp, one number holds all four catalogs — the customer who ordered biryani last Tuesday sees a Sunday burger promo from Burger Lab in the same thread. Cross-brand baskets happen naturally.

Cross-brand basket lift: 12-18% of second-brand carts include a first-brand item · Setup: one BSP number, four Meta catalog collections

2. Cloud kitchen with dedicated delivery fleet — WhatsApp becomes primary channel

If you already run two or three in-house riders on salary or per-drop pay, WhatsApp direct is the channel that makes those riders profitable. Every order that comes through WhatsApp routes to your own fleet instead of Swiggy Genie, meaning the delivery fee stays inside your P&L rather than leaking to the aggregator. Cloud kitchens with in-house fleets typically flip WhatsApp from a "nice to have" second channel to the primary revenue channel inside a quarter.

Fleet utilisation: 3-5 more drops per rider per day · Delivery fee retained: ₹40-70 per order

3. Corporate and office bulk orders — B2B repeat with no aggregator middleman

The Friday-lunch order for 40 people at a nearby tech office is the highest-margin ticket a cloud kitchen ever gets — but it is also the one where aggregator commission hurts most. WhatsApp handles corporate repeat with a saved-cart shortcut: the office admin sends one message on Friday, the same platter order fires automatically, invoice with GST is generated inside the chat, and payment lands via a corporate UPI or NEFT link. No aggregator commission on a ₹18,000 ticket.

B2B commission avoided: ₹4,800-5,600 per ₹18K corporate order · Repeat rate: 60-75% weekly on saved carts

4. Cloud kitchen scaling to 3+ outlets — WhatsApp broadcast + city routing

An operator with three cloud kitchens across a city — one in Andheri, one in Bandra, one in Powai — needs geography-aware routing. WhatsApp direct handles it: the customer's pinned location is matched to the nearest active kitchen, the catalog served is the one that kitchen can actually cook, and Wednesday-Thursday broadcast promos targeting the dead 3pm to 6pm daypart are sent per-outlet to the customers who ordered from that outlet before.

Broadcast open rate: 55-70% (versus 18-22% for email) · Dead-daypart lift: 8-14 extra orders per outlet per week

The ₹ comparison

Real cost comparison — cloud kitchen, 30 orders/day, ₹450 avg ticket

Same daily volume. Three channels. What the operator actually keeps at the end of the month.

Monthly maths on ₹4.05L gross revenue

30 orders/day · ₹450 avg ticket · Mumbai rates · Nov 2026

Channel	Take rate	Per-order cost	Monthly bleed	Net to operator
Swiggy (blended)	27-31%	₹122-140	₹1.09L-1.25L	₹2.80L-2.96L
Zomato (blended)	25-30%	₹113-135	₹1.01L-1.21L	₹2.84L-3.04L
WhatsApp direct	0%*	~₹1	₹120-180	₹4.05L

*WhatsApp direct: 0% commission, plus roughly ₹0.80-1.20 per marketing-initiated Meta conversation (service replies inside an open thread are free). On a realistic 30% shift from aggregators to WhatsApp direct over the first 90 days, a 30-order/day cloud kitchen recovers ₹33,000 to ₹37,000 a month — against a ₹199/month software cost. Full year-1 payback maths are broken down on the aggregator profit calculator.

Go-live plan

Setup in 48 hours — the real steps

Not a marketing timeline. This is the actual sequence Online eMenu runs for a cloud kitchen switching from aggregator-only to WhatsApp direct.

WhatsApp Business API

Provisioned on your outlet's registered phone number through our sister BSP Go4WhatsApp. Green Tick optional. Runs in parallel with Day 1 of onboarding — you do not wait for it.

Day 1 · 2-3 hours

Menu sync from POS to Meta Catalog

Your existing menu — including brand splits, images, prices, allergen tags — is imported into the Ordering Suite once and pushed to Meta Business Catalog automatically. Multi-brand cloud kitchens get one collection per brand.

Day 1 · 1 hour

Print WhatsApp insert cards

Every order leaving your kitchen in a Swiggy or Zomato bag gets an insert card offering 10% off the next WhatsApp order. Cards are generated in one click from the WhatsApp opt-in generator, printed at any local press for ₹0.40 per card.

Day 1-2 · print in parallel

Go live · first opt-in broadcast

Day 2, once BSP verification completes: switch on WhatsApp channel inside the Ordering Suite, run a smoke test with two internal orders, then send the first opt-in broadcast to the customers who scanned QRs in your dine-in phase or gave numbers to your loyalty programme.

Day 2 · afternoon

Weekly Wed-Thu daypart broadcast

The dead 3pm-6pm daypart on Wednesday and Thursday is where WhatsApp broadcasts earn the most incremental orders. Templates for the first four weeks — including festival flanks and rain-day promos — are loaded during onboarding.

Week 2 onwards · recurring

Read the weekly report

Every Monday the operator gets a one-page report: WhatsApp orders vs aggregator orders, commission saved, opt-in growth, catalog views, top-viewed items. The single number to watch in month one is the ratio of WhatsApp orders to total orders.

Weekly · Monday 9am

Why us — honestly

Why cloud kitchens choose Online eMenu (not a generic WhatsApp BSP)

A generic WhatsApp Business Service Provider — Interakt, WATI, Gallabox and a dozen others — will get you a working WhatsApp number and a catalog you can fill in by hand. That is fine for a boutique store. It falls apart for a cloud kitchen the moment you have four brands sharing one prep line, an 86-out at 8pm, and Swiggy plus Zomato firing tickets from another dashboard.

Menu sync from POS is automatic — no CSV re-uploads. This is the single biggest reason cloud kitchens end up abandoning generic BSPs within a quarter. Nobody has time to keep a Meta Business Suite catalog synced with a POS by hand, and the moment the two drift, refunds and Google reviews follow. Online eMenu writes the POS-to-catalog pipe as a first-class product: 2-5 second sync, retry on failure, hashed payloads so nothing gets missed. Edit the price in the POS, walk away, done.

Multi-brand routing built in. The industry pattern in India is one shared kitchen running 3 to 8 brands. Online eMenu's Ordering Suite treats each brand as a first-class object — its own catalog, its own KOT format, its own delivery ETA, its own reports — while pooling into one WhatsApp number, one live queue, one kitchen station map. Generic BSPs treat brands as tags on a single catalog, which stops scaling the moment you pass three.

Aggregators and WhatsApp on the same live queue. No tab-switching between the Swiggy dashboard, the Zomato dashboard and a WhatsApp inbox. Every ticket — Swiggy, Zomato, WhatsApp, dine-in — hits one screen in one order. The KOT prints once. The KDS lights up once. Menu edits and 86-toggles sync to all channels in the same cycle.

Cloud-kitchen-friendly pricing, no per-outlet lock-in. ₹199 a month, all-in, includes WhatsApp Catalog sync at zero extra cost. No per-outlet minimum, no annual contract, no setup fee. If you shut down a brand or a kitchen next quarter, you cancel that outlet's subscription and stop paying. This matters for cloud kitchens because brand churn is the norm, not the exception — you launch four brands, you kill two, you launch two more. Your software should not punish you for it. Full pricing detail is on the pricing page.

Where competitors are stronger: Petpooja has broader out-of-the-box hardware integrations (billing printers, weighing scales, thermal roll suppliers) if you are running a large multi-outlet operation with legacy hardware. Foodics wins on ZATCA depth in Saudi. Restroworks (Posist) has stronger enterprise reporting for chains above 20 outlets. We are the honest choice for an Indian cloud kitchen operator between 1 and 8 outlets who wants WhatsApp direct as the primary long-term channel and needs it to work without a dedicated ops person to babysit the sync.

Cloud kitchen pricing — one line item, one subscription

Ordering Suite is the whole thing: WhatsApp ordering, catalog sync, Swiggy and Zomato sync, multi-brand routing, KDS, GST invoicing, reports. No add-ons. No per-outlet lock-in.

Ordering Suite · Cloud Kitchen · India

₹199/month

All-in monthly · cancel anytime · 0% transaction fees on WhatsApp orders · no per-outlet lock-in

WhatsApp Business Catalog auto-sync from your POS
Multi-brand routing — one number, up to 30 brand collections
Swiggy + Zomato in the same live queue
UPI (PhonePe, GPay, Paytm, BHIM), Razorpay cards, cash on delivery
KOT printer + KDS + rider dispatch to Porter, Dunzo, WeFast or in-house
GST e-invoice + FSSAI compliant bill format
Weekly Wed-Thu broadcast templates loaded in onboarding
Hindi & English support 24×7

Start 14-day free trial → WhatsApp

14-day free trial, no card required. Full regional pricing (GCC $9, UK £8, EU €8) on the pricing page.

Frequently asked

The ten questions cloud kitchen operators ask next

Does WhatsApp ordering work for cloud kitchens without dine-in? +

Yes — and cloud kitchens are the exact use case WhatsApp ordering was made for. A cloud kitchen has no walk-in traffic and no dine-in tables, so 100% of revenue rides on delivery. Every order that stays on Swiggy or Zomato loses 25-32% to commission. Every order that moves to WhatsApp direct keeps the full ticket. Online eMenu's WhatsApp ordering treats delivery as the default fulfilment mode, prints straight to the kitchen thermal, and hands off to your rider fleet — Porter, Dunzo, WeFast or in-house — without any dine-in workflow in the way.

Do I need a separate WhatsApp Business number for each cloud kitchen brand? +

No. Online eMenu supports multi-brand routing on a single WhatsApp Business API number. The customer messages one number; the bot detects which brand they are asking about — from the pre-filled greeting, a menu chip, or the ad they came from — and serves the correct catalog. Orders land in the POS live queue tagged with the correct brand, kitchen station and printer. This matches how most Indian cloud kitchens run: one physical kitchen serving 3 to 8 brands from a shared prep line.

How do WhatsApp orders integrate with my Swiggy and Zomato setup? +

Swiggy, Zomato and WhatsApp orders all land in the same POS live queue on the same screen. Your team does not tab-switch between three dashboards. Menu edits and 86-out toggles pushed to Swiggy and Zomato also push to the WhatsApp catalog in the same sync cycle, so a sold-out biryani disappears from every channel at once. Reports at the end of the day break down by channel so you can see the exact ₹ split — aggregators versus WhatsApp direct — and decide where to spend marketing next month.

Can WhatsApp handle bulk / corporate orders for cloud kitchens? +

Yes. Corporate and office bulk is where WhatsApp direct pays for itself fastest. The admin team messages your one number, browses a bulk-order catalog with pre-priced platters and party trays, and pays by UPI or corporate card. Repeat weekly orders are handled by a saved-cart shortcut — the admin sends one message on Friday and the same lunch order for 40 people fires automatically. No aggregator commission on any of it, no per-order haggling, no missed calls.

What is the setup cost for WhatsApp ordering in a cloud kitchen? +

₹199 per month for the Ordering Suite subscription — the WhatsApp Business Catalog sync is included at no extra charge. There is no setup fee, no per-outlet lock-in, no per-order transaction fee on WhatsApp orders. The WhatsApp Business API itself is provisioned through our BSP partner Go4WhatsApp; conversation-based charges from Meta on marketing-initiated messages are passed through unchanged, at roughly ₹0.80-1.20 per marketing conversation. Service replies inside an open thread are free.

How much can a Mumbai cloud kitchen realistically save shifting to WhatsApp direct? +

A representative Mumbai cloud kitchen doing 30 delivery orders a day at an average ticket of ₹450 turns over roughly ₹4.05L a month. Aggregator commission on 100% of that volume at 27-31% blended is ₹1.09-1.25L a month gone. If 30% of orders move to WhatsApp direct over 90 days, the aggregator bleed drops to ₹0.76-0.88L, freeing ₹33,000-37,000 a month. Over 12 months that is ₹4-4.5L back to the operator — 3 to 4 months of rent for a typical Andheri or Powai shared-kitchen bay.

Does WhatsApp Catalog sync work with multi-brand cloud kitchens? +

Yes. Each brand keeps its own catalog inside the POS — its own items, prices, images and 86-toggle state — and each syncs independently to a separate WhatsApp Business Catalog collection. Meta allows up to 30 collections per catalog and up to 500 items in total, which covers all but the largest multi-brand kitchens comfortably. The customer sees a single branded catalog for the brand they messaged; the operator sees one live queue with brand tags on every ticket.

What payment methods work inside WhatsApp for Indian cloud kitchens? +

UPI on every major app — PhonePe, GPay, Paytm, BHIM — plus credit and debit cards via Razorpay. Cash on delivery is available for outlets that want it and can be toggled on or off per brand, per day-part, or by minimum ticket value. The pay-link is generated per order and lands in the same WhatsApp thread — the customer never leaves the chat. Refunds route back through the original payment method and confirm in WhatsApp automatically.

Do I need an FSSAI licence for WhatsApp orders? +

Yes. Every cloud kitchen selling food in India needs a valid FSSAI licence regardless of the ordering channel — WhatsApp, Swiggy, Zomato or walk-in. The specific licence category depends on turnover: FSSAI Registration for under ₹12L/year, State Licence for ₹12L-₹20Cr, Central Licence above that. The FSSAI number must be printed on every dispatch bill including WhatsApp orders. Full costs, timelines and paperwork are covered in our FSSAI licence guide.

What is the go-live time for a cloud kitchen switching from aggregator-only to WhatsApp direct? +

48 hours from signed order to first live WhatsApp order, assuming the kitchen already has a Meta Business account (most do — it is linked to the Facebook or Instagram page). Day 1 is WhatsApp Business API provisioning through Go4WhatsApp and POS menu import. Day 2 is catalog sync, payment gateway connect, opt-in insert card print and a live smoke test. From that point every insert card that leaves the kitchen in an aggregator bag is a WhatsApp lead for the next repeat order.

Ready when you are

Ship WhatsApp ordering for your cloud kitchen — ₹199/month, live in 48 hours.

14-day free trial. No credit card. WhatsApp Catalog sync included. Zero commission on WhatsApp orders. Multi-brand routing built in. We handle the WhatsApp Business API verification so you do not have to.