WhatsApp for restaurants in India
WhatsApp for restaurants means taking the order directly instead of renting the customer from an aggregator: a QR opens your live menu inside the chat, the cart is built in the thread with modifiers, the payment is UPI at zero MDR, and the ticket lands in the same kitchen queue as the dine-in tables. For an Indian outlet the reason is arithmetic — aggregators commonly take 24–30% all-in, which on a typical order is more than the gross margin on the food — and the reason it works is that a regular does not need to be discovered twice.
Plans from ₹1,999/month · 0% markup on WhatsApp messages · guided onboarding included
How a repeat customer orders without the aggregator
A regular reorders from a WhatsApp menu, pays by UPI at zero MDR, and the ticket lands in the same kitchen queue as a dine-in order — so the outlet keeps the 24-30% an aggregator would have taken, and keeps the customer’s phone number.
- 1
Menu shared
A QR on the table, the bill and the shopfront opens today’s menu — items 86’d in the kitchen grey out across every open chat within seconds.
Runs on: OneMenu + live stock sync
- 2
Order in chat
The customer builds a cart in the thread with modifiers and portion sizes, no app install and no third-party account.
Runs on: In-chat cart + modifiers
- 3
UPI payment
Paid in the conversation at 0% MDR, or COD confirmed explicitly before the kitchen fires the ticket.
Runs on: UPI checkout (Razorpay / PhonePe / Paytm)
- 4
Kitchen ticket
The KOT routes to Petpooja or Dotpe so the chef sees it in the same queue as the floor, not on a second tablet.
Runs on: POS integrations
- 5
Reorder nudge
The number is yours, so the Friday-night regular gets a utility nudge on Friday — an aggregator never hands you that list.
Runs on: Segments + scheduled campaigns
Six things Indian outlets actually use it for
The jobs that come up on every restaurant call, and the surface that does each one.
A menu QR that is always current
One QR on the table, the bill and the shopfront opens today's live menu — no reprinting when a price moves, and no PDF from three months ago floating around a WhatsApp group.
In-chat cart with real modifiers
Portion sizes, spice levels, add-ons and combos build in the thread, so the order that reaches the kitchen is unambiguous and the customer never installs anything.
UPI at 0% MDR, or an explicit COD confirm
Paid in the conversation through Razorpay, PhonePe or Paytm with no card page, or a COD order confirmed in writing before the kitchen fires it — which is where most COD losses actually start.
Tickets in the same kitchen queue
KOTs route into Petpooja or Dotpe so the chef reads WhatsApp orders on the same screen as the floor, instead of a second tablet nobody watches at 8pm.
The regulars list is yours
Friday-night regulars get a Friday nudge, because the number belongs to the outlet. An aggregator will never hand you that list, which is the whole argument for a direct channel.
FSSAI number where it belongs
The licence number sits on the menu header and on every invoice automatically, and licence-gated items stay hidden for outlets that cannot serve them.
Direct order vs aggregator: the arithmetic
A single-outlet QSR doing 1,200 delivery orders a month, currently almost all through Swiggy and Zomato. Every input below is visible and adjustable — change the ones you disagree with and the arithmetic still holds. We publish the workings because a number you cannot check is worth nothing.
The assumptions
- Delivery orders per month1,200
- Your own figure — substitute it.
- Average order value₹420
- Your own figure — substitute it.
- Orders placed through an aggregator90%
- Your aggregator-sourced share of delivery. Take it from last month’s settlement statements.
- Share of that loss recovered in chat12%
- Share of aggregator orders that shift to your own WhatsApp channel once regulars have a direct route. Conservative; repeat-heavy menus do better.
- Aggregator commission avoided on a direct order25%
- Base commission plus payment and packing fees, commonly 24-30% all-in for Indian outlets. Use your own settlement rate.
- Cost per utility message (Meta, India)₹0.115
- Meta's published India rate, verified 2026-08-25. GST of 18% applies on top.
The arithmetic, per month
| Line | How it is calculated | Amount |
|---|---|---|
| Revenue recovered | 1,200 × 90% × 12% × ₹420 | ₹54,432 |
| Aggregator commission avoided on a direct order | 130 × ₹420 × 25% | ₹13,608 |
| WhatsApp message cost | 1,200 × 3 messages × ₹0.115 | −₹414 |
| WatEase plan (Growth) | Flat monthly fee, 0% markup on the messages above | −₹1,999 |
| Net monthly impact | Under these assumptions, at this volume | ₹65,627 |
This is an illustrative model built from the assumptions above, not a measured outcome from a named customer, and nothing here is a guarantee of results. Message costs are Meta’s published India rates (verified 2026-08-25) and exclude 18% GST; WatEase adds 0% markup to them. Run your own volumes through the conversation cost calculator and the ROI calculator.
FSSAI and GST on a WhatsApp menu
A menu a customer can order from is a published menu, whichever surface it appears on. Under the FSS Act and the licensing regulations, your FSSAI licence or registration number belongs on the menu and on the invoice, and items requiring a separate licence should be gated by outlet rather than shown to every customer and declined afterwards. WatEase carries the number on the menu header and on each order invoice, so the requirement is not something a staff member has to remember.
GST treatment then has to be category-correct on the document, not just on the total. Restaurants under the composition scheme and cloud kitchens on regular GSTR are treated differently, and a buyer claiming the meal as an expense needs an invoice that matches. Getting this wrong is invisible until someone’s reimbursement is rejected, which is exactly the sort of thing a direct channel is supposed to eliminate.
Not legal or tax advice. Licence categories, display requirements and GST rates change. Confirm the current position for your registration before you rely on it. Reflects the position as of June 2026.
Four ways restaurants get this wrong
Running the menu off a Google Sheet
Items sold out during service stay orderable for another twenty minutes, and the refund conversation that follows damages both the relationship and your Meta quality rating. Live stock has to be wired to the kitchen, not to a spreadsheet someone updates between rushes.
Accepting orders past the kitchen cutoff
A late order accepted is a delivery SLA broken and a review lost. Per-outlet capacity limits should refuse the order at the point of sale, in the thread, before the customer has paid.
Blasting offers to the whole list every weekend
Marketing templates to an unsegmented list drops your quality rating to Yellow, which caps your daily messaging tier. Segment by order history and route order updates as Utility, which is both cheaper and unaffected by promotional limits.
Expecting WhatsApp to replace discovery
Nobody finds a new restaurant on WhatsApp. Treat the direct channel as where regulars are retained at full margin and the aggregators as paid discovery, and the two stop competing in your head.
The numbers, with their sources
Every WhatsApp vendor quotes the same unsourced open-rate figure. These are the ones we build the arithmetic on, each linking its primary source.
500M+
WhatsApp users in India — Meta has cited India as WhatsApp’s largest market worldwide.
Source: Meta Newsroom~₹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 pricingFrequently asked questions
How do restaurants use WhatsApp for orders in India?
A customer scans a QR on the table, the bill or the shopfront, which opens the outlet's live menu inside WhatsApp. They build a cart in the thread with modifiers and portion sizes, pay by UPI at zero MDR or confirm a COD order explicitly, and the kitchen ticket routes into the same queue as the dine-in tables through a POS integration such as Petpooja or Dotpe. Items marked unavailable in the kitchen grey out across every open chat within seconds, so the outlet does not sell what it cannot cook. Because the order is direct, the outlet keeps the customer's phone number and the aggregator commission.
Is WhatsApp ordering cheaper than Swiggy and Zomato?
On the unit economics, yes, and by a wide margin — but it does not replace the aggregators' discovery. Indian aggregators typically take 24–30% all-in once base commission, payment fees and packaging charges are counted; verify your own rate from a settlement statement. A direct WhatsApp order costs Meta's utility conversation rate of roughly ₹0.115 plus GST for each update you send, and UPI carries 0% MDR. On a ₹420 order that is the difference between roughly ₹105 of commission and well under a rupee of messaging. The realistic strategy is to keep the aggregators for new-customer discovery and move repeat customers to the direct channel, where the margin actually is.
Do I need FSSAI details on a WhatsApp menu?
Yes. Under the FSS Act and the Food Safety and Standards (Licensing and Registration) Regulations, the FSSAI licence or registration number must be displayed on the menu and on invoices, and a menu a customer can order from is a published menu regardless of the surface it appears on. Items requiring a separate licence should be gated by outlet rather than shown to everyone. WatEase carries the licence number on the menu header and on the order invoice automatically. Rules change — confirm the current position for your licence category.
Can WhatsApp handle a Friday-night rush?
The failure mode is not message throughput, it is the kitchen. Two controls matter: live stock, so an item 86'd during service disappears from every open chat within seconds instead of being sold for another twenty minutes; and per-outlet capacity limits, so new orders are refused past the kitchen's cutoff rather than accepted and then apologised for. WatEase enforces both, and pushes accepted orders straight into the KOT queue so the pass sees them in the same place as the floor.
What does WhatsApp ordering cost a restaurant in India?
The platform is WatEase Growth at ₹1,999/month, month-to-month, with guided onboarding and no setup fee. On top sit Meta's conversation charges: about ₹0.115 for a utility message such as an order confirmation or a delivery update, ₹0.8631 for a marketing message such as a weekend offer, plus 18% GST, with replies inside the 24-hour service window free. WatEase adds 0% markup to those rates. For a 1,200-order month sending three updates per order, the Meta side is a few hundred rupees.
Will customers actually order on WhatsApp instead of an app?
For repeat customers, the friction argument is on your side: no install, no account, no password, and the reorder is one tap on last week's order. For first-time discovery it is not — nobody finds a new restaurant on WhatsApp. That is the honest split, and it is why the direct channel is a retention play rather than an acquisition one. Move the regulars, keep the aggregators for reach, and measure the mix rather than assuming it.