WhatsApp menu ordering for restaurants and cloud kitchens in India
WhatsApp menu ordering lets an Indian restaurant or cloud kitchen publish a live menu inside the chat, take the order in the conversation, and collect payment by UPI at 0% merchant discount rate. Because the order never passes through Swiggy or Zomato, the roughly 18–30% aggregator commission stays with the kitchen instead of leaving it.
Built for Indian businesses 🇮🇳 · Plans from ₹1,999/month · 0% markup on WhatsApp messages
What the customer actually sees
Not a mock-up of a feature — the real message shape for a food & beverage business, in the price band and language this vertical works in.
WhatsApp Business
WhatsApp Business API
- Customer: Menu?
- Business: Here’s tonight’s menu at Anna Kitchen — tap to browse. Kitchen open till 10:45 PM, delivery in Koramangala and HSR.View menu (32 items) ↗
Live catalog · sold-out items hidden automatically
- Customer: 2 Paneer Butter Masala, 4 butter roti, 1 jeera rice
- Business: 2× Paneer Butter Masala ₹580, 4× Butter Roti ₹120, 1× Jeera Rice ₹160. Subtotal ₹860 + 5% GST ₹43 + delivery ₹30 = ₹933.Pay ₹933 via UPI ↗
Cart built in-chat · GST at 5% restaurant rate · 0% MDR on UPI
- Business: Paid. Order #AK-2214 is in the kitchen — KOT printed. Ready in about 25 minutes, rider assigned after that.
Pushed to Petpooja KOT queue · no aggregator commission deducted
How it works
Publish the menu
Import your menu with prices, categories, veg and non-veg markers and item photos. Your FSSAI licence number is carried on the published menu and on every invoice, as the FSS Act requires.
Take the order in the chat
The customer browses the catalog or simply types what they want. WatEase builds the cart in the conversation, applies the correct GST rate, adds the delivery charge for their zone, and returns a UPI payment link.
Fire it to the kitchen
On payment the order lands in your KOT queue — Petpooja, Dotpe or the WatEase kitchen view — alongside dine-in tickets. Sold-out items grey out across all open chats, and orders past your per-outlet capacity are refused rather than accepted and disappointed.
What one direct order is worth against one aggregator order
No invented ROI percentages — these are the mechanisms and the market facts behind them. Your numbers depend on your volume, and the dashboard measures each one.
~₹0.115
Meta’s published India price for a utility-category WhatsApp conversation (order/payment/delivery updates) — what a recovery or reminder nudge actually costs to send.
Source: Meta for Developers — WhatsApp pricingOver 16 billion
UPI transactions processed in a single month in India, per NPCI’s published product statistics for 2025–26.
Source: NPCI UPI product statistics500M+
WhatsApp users in India — Meta has cited India as WhatsApp’s largest market worldwide.
Source: Meta NewsroomCommission that stays in the kitchen
Aggregators take a base commission plus payment-gateway and packaging deductions. A direct WhatsApp order carries none of that — only the conversation fee and, if the customer pays by UPI, zero MDR.
On a ₹500 order, aggregator deductions in the roughly 18–30% all-in band come to about ₹90–₹150. The same order taken directly on WhatsApp costs a fraction of a rupee in conversation fee and ₹0 in MDR on UPI. At 20 direct orders a day, that gap compounds fast.
The customer relationship itself
An aggregator order gives you a masked number and no ability to message the customer again. A direct order gives you a real contact with recorded consent, which is what makes repeat ordering possible.
A regular who orders twice a month through an aggregator is worth the food margin minus commission, twice. The same regular reachable directly can be nudged, offered a combo, and retained — and every subsequent order keeps the full margin.
Fewer refunds from selling what you do not have
Live item-level stock tied to KOT acceptance means a dish that runs out disappears from the menu across every open chat immediately, instead of being ordered, paid for and then refunded.
Every avoided sold-out refund is one fewer payment reversal, one fewer angry customer, and — because Meta scores your number on user feedback — one fewer hit to the quality rating that governs your daily messaging limit.
A ₹500 order, aggregator versus direct
| Without WatEase | With WatEase | |
|---|---|---|
| Commission and deductions | Roughly 18–30% all-in, before packaging | None |
| Payment cost | Gateway fee deducted by the aggregator | 0% MDR when the customer pays by UPI |
| Who owns the customer | The aggregator — you get a masked number | You, with recorded consent to message again |
| When you find out an item is sold out | When the aggregator pushes an order you cannot make | Never — it greys out across all chats within seconds |
| Where the order appears | A separate tablet, in a separate queue | Your KOT queue, beside dine-in tickets |
The 18–30% commission band reflects publicly discussed aggregator rate cards and varies by city, cuisine and contract; the ₹500 order value is an illustrative figure, not a claim about your outlet or an average across WatEase customers. Verify your own rate card and your own average order value before relying on the arithmetic.
Set this up in WatEase
Five steps, each pointing at the actual screen you do it on. Most teams have this running the same day.
- 1
Import the menu
Bulk-import items with prices, categories, veg or non-veg markers and photos. Set your FSSAI licence number so it prints on the published menu and every invoice.
Catalog → Menu
- 2
Set delivery zones and cutoffs
Define pincode or distance-based zones with minimum order values and per-zone delivery charges, plus a kitchen cutoff time so late orders are refused rather than accepted and missed.
Orders → Delivery zones
- 3
Connect payments
Link Razorpay, PhonePe or Paytm so the in-chat cart returns a UPI link at 0% MDR with the correct 5% restaurant GST already applied.
Settings → Payments
- 4
Wire the kitchen
Connect Petpooja or Dotpe so paid WhatsApp orders enter the same KOT queue as dine-in, or use the built-in kitchen view if you have no POS.
Settings → Integrations → POS
- 5
Turn on live stock
Enable item-level availability so 86’ing a dish from the kitchen view removes it from every open chat, and set per-outlet order capacity so a viral broadcast cannot oversell the kitchen.
Catalog → Availability
The unit economics of Indian food delivery, and what the law requires
For a single-outlet restaurant or a cloud kitchen, aggregator commission is frequently larger than the gross margin on the food. That is the whole commercial case for direct ordering — and it comes with specific Indian compliance obligations.
- FSSAI registration or licence number must be visible on every published menu and every invoice. The FSS Act treats a WhatsApp menu as a published menu the moment a customer can order from it.
- GST is 5% without input tax credit for most restaurant supply under the current regime, and 18% for certain cloud-kitchen and packaged arrangements. The invoice must be category-correct or the buyer’s expense claim breaks.
- UPI carries 0% MDR, so a direct order collected on UPI avoids both the aggregator commission and the payment-gateway deduction the aggregator takes on top of it.
- Menu names in Hindi-Roman and regional transliteration consistently outperform anglicised names on Indian threads — “Paneer Tikka”, not “Cottage Cheese Tikka”.
- Order confirmations and kitchen updates are utility-category conversations about the customer’s own order, so they neither require marketing consent nor carry marketing pricing.
Frequently asked questions
Can customers really order food without leaving WhatsApp?
Yes. The menu opens as a browsable catalog inside the chat, the cart is built in the conversation, and the UPI payment link opens the customer’s own payment app. There is no website to visit and no app to install.
How much commission does WatEase take on an order?
None. WatEase charges a monthly platform fee and passes Meta’s per-conversation cost through at 0% markup. There is no per-order commission, which is the entire point against an aggregator.
Does it connect to my POS?
Yes — Petpooja and Dotpe are supported, so paid WhatsApp orders join the same KOT queue as dine-in tickets. If you have no POS, the built-in kitchen view handles the queue.
What happens when a dish runs out mid-service?
Mark it unavailable from the kitchen view and it greys out across every open chat within seconds, so it cannot be ordered. This is the single biggest source of avoidable refunds in direct food ordering.
Should I stop using Swiggy and Zomato?
Most kitchens should not. Aggregators supply discovery you cannot replicate; WhatsApp supplies margin and the customer relationship you cannot get from them. The realistic goal is to move your existing regulars to direct ordering and leave discovery on the aggregators.
Can I run daily specials and thali sets?
Yes. Update the menu and broadcast the special to consented regulars. Set a quantity cap per outlet so a broadcast that performs well does not oversell the kitchen by two hundred trays.
Is the FSSAI number handled automatically?
Yes, once configured. It appears on the published menu and on every generated invoice, which is what the FSS Act requires of a menu customers can order from.
What return can a food & beverage business expect from whatsapp menu & direct ordering on WhatsApp?
Through specific mechanisms rather than a single ROI number: commission that stays in the kitchen; the customer relationship itself; fewer refunds from selling what you do not have. On a ₹500 order, aggregator deductions in the roughly 18–30% all-in band come to about ₹90–₹150. The same order taken directly on WhatsApp costs a fraction of a rupee in conversation fee and ₹0 in MDR on UPI. At 20 direct orders a day, that gap compounds fast. WatEase publishes no invented ROI percentages — your numbers depend on your volume, and the dashboard measures each mechanism.
Go deeper
Other jobs food & beverage businesses run on WhatsApp
WhatsApp menu & direct ordering in other industries
The capabilities behind this
Zoom out to WhatsApp commerce for food & beverage, or read catalog & discovery across every industry.
Capabilities and competitor comparisons reflect what we could verify as of June 2026. Worked examples on this page are illustrative scenarios, not averages across WatEase customers.