Why are Bengaluru restaurants moving repeat orders to WhatsApp?
Bengaluru is one of India's most aggregator-dense food delivery markets — Swiggy itself is headquartered in the city — so restaurants compete for visibility inside a crowded platform before they compete on food. That discovery is worth paying for on a first-time customer, but not on a regular who already knows the outlet, because the operator still pays commission on an order the aggregator did nothing to generate.
WhatsApp ordering does not replace Swiggy or Zomato in the channel mix — it adds a second lane for the customer who already has the number saved: the Koramangala office worker who orders the same thali every Tuesday, the Indiranagar regular who messages before brunch. That lane runs through WhatsApp Ordering instead of an aggregator listing, so no commission applies.
How does the order flow work, catalog to KOT?
The flow is the same whether the outlet is a Jayanagar restaurant or a Whitefield cloud kitchen: catalog, cart, payment, queue, KOT.
- Customer opens the chat. A QR at the table or counter, a wa.me link in an office WhatsApp group, or a saved number opens the chat.
- Catalog opens. The customer browses the menu as a WhatsApp Business catalog — photos, prices, collections — inside the chat, no app to install.
- Cart is built and sent. The customer adds items, notes a delivery address or pickup time, and sends the cart as one structured message.
- Payment link or UPI. The outlet replies with a UPI ID or a payment link for the exact total, paid inside the same thread.
- Live order queue. The order lands in a unified queue alongside any Swiggy or Zomato orders in progress.
- KOT prints. The kitchen ticket prints at the right station automatically on Online eMenu WhatsApp Ordering, no manual re-entry.
Higher-volume outlets provision the paid WhatsApp Business API through the Go4WhatsApp BSP, typically 24-48 hours. A single-counter operator can start on the free WhatsApp Business App.
Neighbourhood playbook: Koramangala, Indiranagar, HSR, Whitefield, Jayanagar
Bengaluru's neighbourhoods do not need different technology, but they reward different tactics — where the WhatsApp trigger sits and when the catalog gets shared.
Koramangala
Offices, PGs and apartments mean the catalog link travels fastest through existing WhatsApp groups. Tech-park style lunch pre-orders work well: the cart goes in 20-30 minutes before the break, so food is ready rather than ordered on arrival.
Indiranagar
Weekend brunch queues are the opportunity. A table tent with a WhatsApp QR lets a waiting group order before a table is free, giving the kitchen a head start. Late-night crowds near the pub strip respond well to a saved-number reorder as a last call.
HSR Layout
A mixed residential and tech-park catchment runs two rhythms: daytime lunch pre-orders from nearby offices, and evening household reorders once the number is saved. Keep the catalog structured so both order types build equally fast.
Whitefield
Large tech campuses make bulk lunch pre-orders the highest-value case — one admin sends a cart with a dozen items, the kitchen batches it as one ticket, and delivery lands at a fixed gate time. A short daily-specials broadcast to a saved office list beats a general announcement.
Jayanagar
An older, traditional customer base is often more comfortable with a phone call or a plain WhatsApp text than an app. Keep the catalog simple, allow free-text orders alongside the cart, and lean on festival and weekend-family repeat orders over a heavy broadcast cadence.
Cloud kitchens in Bengaluru: multi-brand routing from one kitchen
Bengaluru has no shortage 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 — whichever brand or channel it arrived through — into one kitchen queue, printing to the right station with the brand marked on the KOT.
Revenue-by-channel reports show which brand earns its keep on WhatsApp versus Swiggy versus Zomato — the reliable way to decide whether a third brand is worth the complexity it adds. The WhatsApp for cloud kitchens guide covers the full playbook, launch checklist and unit economics.
Running Swiggy, Zomato and WhatsApp in one queue
A Bengaluru kitchen at peak usually manages at least two aggregator tablets plus a counter register, and a fourth disconnected screen for WhatsApp is how orders get missed. Native Swiggy and Zomato sync into one live order queue solves that: every order, whichever channel it came through, appears in the same kanban-style queue and prints as a KOT, with the channel tagged for reporting.
This is a workflow fix, not a cost fix — Online eMenu carries zero transaction fees on any order. What changes is whether the kitchen reads three screens or one during the rush. The Bangalore Restaurant POS page covers the counter and kitchen-display setup this queue runs on.
Karnataka GST and FSSAI billing on Desktop POS
GST is a central tax, so a Bengaluru restaurant follows the same rules as any Indian city: bill at the regular rate, or under the composition scheme where eligible, and the bill must be GST-ready no matter which channel — WhatsApp, Swiggy, Zomato or walk-in. 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 that syncs when the connection returns, multi-station KOT routing, multi-printer support, and cash, card and UPI at the counter — a WhatsApp order and a walk-in print an identical, compliant bill.
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 festival offer, a reminder the channel exists. Replying to a customer who messaged directly needs no separate opt-in; broadcasting to a saved list does.
The safest opt-in points sit in front of the customer already: a line on the printed bill ("reply YES for weekly offers"), a checkbox at the counter QR, or a one-time confirmation after the first order. Keeping broadcast frequency low and relevant — a weekly lunch special, not a daily push — protects the number from being reported.
Setup in 48 hours, day by day
The 48-hour timeline assumes a menu and business number are ready; a multi-brand cloud kitchen repeats the catalog step per brand.
Day 1 — verify, import, sync
- Business verification. Meta Business verification runs through Online eMenu onboarding, in parallel with WhatsApp Business API provisioning through the Go4WhatsApp BSP, 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, organised to mirror the counter or 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, with the opt-in already collected at the counter or on the 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-channel menu push, multi-brand routing, and revenue-by-channel reports — zero transaction fees. Desktop POS, for a Windows counter with offline mode, GST calculation, multi-station KOT routing and cash, card and UPI billing, is ₹4,999/year.
What you do not pay on WhatsApp is aggregator commission. As an example — a round ₹600 order — a typical 20-30% commission plus GST on commission works out to roughly ₹140-190 kept by the platform. The same order on WhatsApp costs only the UPI fee plus a flat subscription that does not change with volume. Run your own ticket size on the commission calculator.
Who this is for
This guide is for single-outlet Bengaluru restaurants, cafes and cloud kitchens across Koramangala, Indiranagar, HSR Layout, Whitefield and Jayanagar that already run Swiggy or Zomato and want a direct channel for customers who need no discovering — the office lunch group, the weekend regular, the household that reorders weekly. It is not a call to leave the aggregators; they remain the discovery channel, and WhatsApp becomes the retention channel with no commission line.
Counter-format operators should read the WhatsApp ordering for QSRs and dhabas guide. Multi-brand kitchens should read WhatsApp for cloud kitchens.
Set up WhatsApp ordering for your Bengaluru 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 Bengaluru restaurants take orders on WhatsApp without paying aggregator commission?
A Bengaluru restaurant shares a WhatsApp catalog and wa.me link — on a QR standee, in WhatsApp groups, 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 Bengaluru?
Online eMenu Ordering Suite is ₹199/month or ₹1,990/year, no annual lock-in, and a 14-day free trial that needs no card. It includes the WhatsApp catalog, cart and payment-link flow, Swiggy and Zomato sync, and QR menu, with zero transaction fees. Operators who also want a Windows billing counter can add Desktop POS at ₹4,999/year.
Do I need a separate POS for WhatsApp orders in a Bengaluru restaurant?
Not to start — a counter phone running the WhatsApp Business App can take orders, and staff key the cart into the existing billing method. Once WhatsApp, Swiggy, Zomato and walk-in orders compete for the same peak, a POS pulling every channel into one live queue removes the re-typing. Desktop POS at ₹4,999/year runs offline on Windows with GST auto-calculation and multi-station KOT routing.
Can a Koramangala or Indiranagar restaurant use WhatsApp for pre-orders?
Yes. In Koramangala, a catalog link pinned in office and apartment WhatsApp groups turns lunch regulars into a saved-number habit. In Indiranagar, table tents with a WhatsApp QR let a weekend brunch queue send its order before a table opens, so the kitchen starts before the guest is seated. Both run off the same catalog, cart and payment-link flow — only the trigger point changes.
How does a Bengaluru cloud kitchen run several brands on one WhatsApp setup?
Multi-brand routing lets one kitchen operate several virtual brands, each with its own WhatsApp catalog, while every order lands in one kitchen queue and prints to the correct station. Revenue-by-channel reports show which brand and channel — WhatsApp, Swiggy or Zomato — is earning its keep, so an operator can retire a weak brand without touching the ones that work.
Can I run Swiggy, Zomato and WhatsApp orders from one screen in Bengaluru?
Yes — Online eMenu natively syncs Swiggy and Zomato into the same live order queue as WhatsApp, so the counter or kitchen display shows every channel on one screen instead of three tablets. Each order still carries its own channel tag for reporting, but nothing needs retyping, and a busy Bengaluru peak collapses into one queue with one KOT stream.
What GST and FSSAI rules apply to WhatsApp billing in Karnataka?
GST is a central tax, so the same rules apply to a Bengaluru WhatsApp order as anywhere in India: bill at the regular rate or, where eligible, under the composition scheme, and keep the bill GST-ready regardless of channel. FSSAI-compliant billing is required on every invoice, with the FSSAI number printed. Desktop POS applies GST automatically whether the order started on WhatsApp, Swiggy, Zomato or a walk-in.
How long does WhatsApp ordering setup take for a Bengaluru outlet?
Online eMenu Ordering Suite goes live in 48 hours once the menu and a business phone number are ready. WhatsApp Business API provisioning through the Go4WhatsApp BSP takes 24-48 hours in parallel. Day 1 covers business verification, menu import and catalog sync; Day 2 covers the QR rollout and the first opt-in broadcast. A cloud kitchen adding a second brand follows the same path per brand.