Why are Delhi-NCR restaurants moving repeat orders to WhatsApp?
Delhi NCR spans Delhi, Haryana and Uttar Pradesh, and a restaurant with regulars scattered from Connaught Place to the Noida Expressway still pays aggregator discovery fees on an order from a customer who already knows exactly which outlet they want. That fee is fair on a first-time diner the platform found, but a straight cost on a repeat customer who typed the outlet's name into a chat instead.
WhatsApp ordering does not replace Swiggy or Zomato — it adds a second lane for the customer who no longer needs discovering: the Cyber Hub office worker with a standing lunch order, the Hauz Khas regular messaging ahead of a booking. That lane runs through WhatsApp Ordering, so no commission applies.
How does the order flow work, catalog to KOT?
The flow is identical whether the outlet is a CP cafe or a Greater Noida cloud kitchen: catalog, cart, payment, queue, KOT.
- Customer opens the chat. A QR at the table, a wa.me link in a residents' or office group, or a saved number opens it.
- Catalog opens. The customer browses the menu as a WhatsApp Business catalog — photos, prices, collections — no app to install.
- Cart is built and sent. The customer adds items, notes an address or pickup time, and sends the cart as one message.
- Payment link or UPI. The outlet replies with a UPI ID or payment link for the total, paid inside the thread.
- Live order queue. The order lands in a unified queue alongside any Swiggy or Zomato orders in progress.
- KOT prints. The ticket prints at the right station automatically, no manual re-entry.
Higher-volume outlets provision the paid WhatsApp Business API through Go4WhatsApp, typically 24-48 hours; a single-counter operator starts on the free app.
Neighbourhood playbook: CP, Khan Market, Hauz Khas, Cyber Hub, Sector 18, Faridabad, Ghaziabad
Delhi NCR's neighbourhoods run on the same catalog and cart flow, but each rewards a different trigger point for the chat.
Connaught Place, Khan Market and Hauz Khas
Dine-in-heavy pockets. A table QR turns a wait for a table into a pre-order the kitchen can start before the guest sits, and a catalog link saved by regulars covers a pickup order timed to arrival — dine-in and pre-order on one catalog, not competing formats.
Cyber Hub, Udyog Vihar, Sector 18 and the Noida Expressway
Office corridors compress lunch into a narrow window, so the pre-order is the highest-value tactic: a catalog link shared in a floor or team group lets an admin send one cart shortly before the break, and food is ready on arrival rather than ordered on it.
Faridabad and Ghaziabad
These lean toward family delivery over office lunch. A catalog link circulated in a residents' WhatsApp group fits an evening or weekend household order, and a simple, low-friction catalog outperforms a heavy broadcast cadence here.
Wedding season and corporate bulk orders by chat
Delhi NCR's wedding season and steady corporate-event calendar both generate bulk orders suited to a chat thread rather than a phone call or spreadsheet. A planner or admin sends one cart for the full quantity, and the outlet confirms it against an agreed deposit policy in the same thread — quantities and timing sit in one written record. Broadcasting a bulk-order catalog should go only to a list that has already opted in, kept separate from the retail catalog.
Winter street food and late-night delivery windows
Delhi NCR's winter season shifts demand toward warm, quick street-food-style orders and later evening windows as people stay in rather than step out. A WhatsApp catalog fits that shift because a regular can reorder a familiar combination from a saved chat without browsing the full menu again, and a late-night order for pickup or self-delivery keeps the last call moving when aggregator rider availability is thinner than at the daytime peak — a seasonal shift in when the direct channel earns its keep, not a claim about specific delivery times or order volumes.
Cloud kitchens in Delhi NCR: multi-brand routing
Delhi NCR has a growing base of delivery-only kitchens running two or three virtual brands from one address, and WhatsApp fits that model because each brand carries its own catalog while the kitchen stays singular. Multi-brand routing sends every order into one queue, printing to the right station with the brand marked on the KOT. Revenue-by-channel reports show which brand earns its keep — see the cloud kitchen India cost, licence and setup guide for a launch plan.
Missed calls: auto-reply with the ordering link
A Delhi-NCR outlet fielding calls through a peak inevitably misses some, and a missed call from a hungry customer is often a lost order rather than a callback. Missed-call auto-reply sends the caller an automatic WhatsApp message carrying the ordering link the moment a call goes unanswered, so the customer can place the order themselves instead of trying a second number or giving up.
Running Swiggy, Zomato and WhatsApp in one queue
A busy Delhi-NCR kitchen typically runs at least two aggregator tablets plus a counter register, and a fourth disconnected screen for WhatsApp is how orders get missed at peak. Native Swiggy and Zomato sync into one live order queue solves that: every order appears in the same kanban-style queue and prints as a KOT, tagged by channel — a workflow fix, not a cost fix, since Online eMenu carries zero transaction fees regardless. The WhatsApp Ordering page covers this setup.
GST across Delhi, Haryana and UP outlets, plus FSSAI billing
GST is a central tax, so a Delhi-NCR restaurant follows the same rules as any Indian city: bill at the regular rate, or under the composition scheme where eligible, regardless of channel. A chain spanning Delhi, Gurgaon and Noida registers GST separately in each state the outlet sits in — Delhi, Haryana and Uttar Pradesh each carry their own state registration on the same central framework. FSSAI-compliant billing applies the same way, with the FSSAI number printed on every invoice.
Desktop POS at ₹4,999/year is built for this: Windows, automatic GST calculation, offline mode, multi-station KOT routing and cash, card and UPI at the counter — a WhatsApp order and a walk-in print an identical, compliant bill regardless of the outlet's state.
Opt-in broadcasts that don't get you blocked
Meta's WhatsApp Business commerce rules require a customer's explicit opt-in before a restaurant sends marketing or broadcast messages — a daily-specials note, a wedding-season catalog, a winter menu update. Replying to a customer who messaged directly needs no opt-in; broadcasting to a saved list does. The safest opt-in points sit in front of the customer already: a line on the bill ("reply YES for offers"), a checkbox at the counter QR, or a one-time confirmation after the first order. Keeping frequency low protects the number from being reported.
Setup in 48 hours, day by day
The timeline assumes a menu and business number are ready; a multi-brand kitchen repeats the catalog step per brand.
Day 1 — verify, import, sync
- Business verification. Meta verification runs through Online eMenu onboarding, alongside WhatsApp Business API provisioning through Go4WhatsApp, typically 24-48 hours.
- Menu import. The existing menu is built into the Ordering Suite POS with pricing and variants structured.
- Catalog sync. The POS menu pushes to WhatsApp as a catalog, mirroring the kitchen.
Day 2 — test, place, announce
- Test order. A staff phone scans the QR, builds a cart, pays a small UPI amount, and confirms the KOT prints correctly.
- QR and bag inserts. A counter or table QR, plus a bag insert pointing aggregator customers to the direct channel.
- First opt-in broadcast. A message to existing regulars, opt-in already collected at the counter or bill.
Cost: what you pay and what you don't
Ordering Suite is ₹199/month or ₹1,990/year for one outlet, no annual lock-in, and a 14-day free trial that needs no card. It includes the WhatsApp catalog and cart flow, native Swiggy and Zomato sync, QR menu, multi-brand routing and revenue-by-channel reports — zero transaction fees. Desktop POS, a Windows counter with GST calculation and UPI billing, is ₹4,999/year.
What you do not pay on WhatsApp is aggregator commission. As an example, take any order value you see at your counter: a typical 20-30% commission plus GST on commission is what an aggregator would keep on that ticket. The same order on WhatsApp costs only the UPI fee plus the flat subscription. Run your own ticket size on the commission calculator.
Who this is for
This guide is for single-outlet Delhi-NCR restaurants, cafes and cloud kitchens that already run Swiggy or Zomato and want a direct channel for customers who need no discovering — the office lunch group, the dine-in regular, the wedding-season planner, the household reordering through winter. It is not a call to leave the aggregators; WhatsApp is the retention channel alongside them. Founders planning a new kitchen should read the cloud kitchen India setup guide; operators elsewhere can compare notes with the Mumbai and Bengaluru guides.
Set up WhatsApp ordering for your Delhi-NCR restaurant
Online eMenu Ordering Suite at ₹199/month sets up your outlet with a WhatsApp catalog, cart and payment-link flow, unified Swiggy, Zomato and WhatsApp orders on one screen, and KOT auto-print. No lock-in, monthly billing, 14-day free trial, no card.
Start on WhatsApp See pricingFrequently asked questions
How do Delhi-NCR restaurants take WhatsApp orders without aggregator commission?
Delhi-NCR restaurants share a WhatsApp catalog and wa.me link — on a QR standee, in an office or residents' WhatsApp group, or as a saved contact. The customer builds a cart and pays by UPI or a payment link in the chat. The order lands in a live queue and prints as a KOT, with no aggregator commission on it.
What does WhatsApp ordering cost for a restaurant in Delhi NCR?
Online eMenu Ordering Suite is ₹199/month or ₹1,990/year, no annual lock-in, with a 14-day free trial and no card needed. It includes the WhatsApp catalog, cart and payment-link flow, Swiggy and Zomato sync, and QR menu, with zero transaction fees. Desktop POS is ₹4,999/year.
Do I need a separate POS for WhatsApp orders in a Gurgaon or Noida restaurant?
Not to start — a counter phone on the WhatsApp Business App can take orders, with staff keying the cart into the existing billing method. Once every channel competes for the same peak, a POS pulling all of them into one queue removes the re-typing. Desktop POS is ₹4,999/year, offline on Windows.
Can a Connaught Place or Hauz Khas restaurant use WhatsApp for pre-orders?
Yes. In Connaught Place, a table QR turns a dine-in wait into a pre-order the kitchen can start before the guest sits. In Hauz Khas, a catalog link shared with regulars covers both a reservation and a pickup order timed to arrival.
How do Delhi-NCR restaurants handle wedding season and corporate bulk orders on WhatsApp?
A bulk order runs through the same catalog, with the buyer sending a single cart for the full quantity and confirming against a deposit policy agreed in the chat. Broadcasting only goes to a list that has opted in, keeping quantities and timing on written record.
How does a Delhi-NCR cloud kitchen run several brands on one WhatsApp setup?
Multi-brand routing lets one kitchen run several virtual brands, each with its own WhatsApp catalog, while every order lands in one queue and prints to the correct station. Revenue-by-channel reports show which brand is earning its keep.
What GST rules apply across Delhi, Haryana and UP outlets?
GST is a central tax, so the same rules apply to a Delhi-NCR WhatsApp order as anywhere in India: bill at the regular rate or, where eligible, under the composition scheme. A chain with outlets in Delhi, Gurgaon and Noida registers GST in each state the outlet sits in, and FSSAI-compliant billing is required on every invoice.
How long does WhatsApp ordering setup take for a Delhi-NCR outlet?
Online eMenu Ordering Suite goes live in 48 hours once the menu and a business number are ready, with WhatsApp Business API provisioning through Go4WhatsApp running 24-48 hours in parallel. Day 1 covers verification and catalog sync; Day 2 covers the QR rollout and first opt-in broadcast.