WhatsApp Business Catalog for restaurants India 2026 — complete setup guide

What is WhatsApp Business Catalog — 30-second answer

WhatsApp Business Catalog is Meta's native product-listing surface built into the WhatsApp Business app and the WhatsApp Business API. Each item is a card with a photo, a name, a price and a short description. Guests browse the catalog by tapping the shop icon inside a chat with the outlet, add items to a native cart, and send the cart back to the outlet as a single message — no menu PDF, no external link, no third-party app.

Items live on Meta's Commerce Catalog — the same schema that powers Facebook Shops and Instagram Shopping. That matters because a single catalog can be reused across WhatsApp, Facebook Page and Instagram Shop from one source of truth. For a restaurant, the practical effect is that the guest experience is closer to a lightweight food-ordering app than to reading a menu PDF over chat.

Why every Indian restaurant should have one in 2026

Three numbers make the case.

• 500 million+ Indian WhatsApp users. Meta's disclosed India MAU sits above half a billion — more than the combined install base of Swiggy and Zomato apps. Any guest who has ordered food online in the last year already has WhatsApp on their phone.
• Aggregator commissions of 25-32% all-in. Swiggy and Zomato's headline commission is 18-25% but the effective take once ads, packaging levy and promotional discounts stack in sits at 25-32%. Every direct order via WhatsApp catalog keeps that in the operator's pocket.
• Zero catalog hosting cost on the free tier. Meta charges nothing to host the catalog itself on the WhatsApp Business App. The only spend is optional — conversation fees on the API tier and photography if the operator hires it out.

The alternative — asking guests to open a website, sign in, add to cart and pay — introduces friction at every step. WhatsApp collapses discovery, ordering, payment confirmation and support into one thread the guest is already inside.

WhatsApp Business App vs API — which do you need?

The decision matrix is honest and short. Free app for small operators, API for anything that scales.

Setup on WhatsApp Business App — free, 30 minutes

The free WhatsApp Business App is available on Android and iOS. Full setup for a 60-item menu takes 30-45 minutes once photos are prepared. Below is the exact 8-step walkthrough — this is the same sequence used in the HowTo schema at the top of this page.

1. Install WhatsApp Business App. Download from Google Play or Apple App Store on the outlet's business phone — not the manager's personal phone. Register the outlet's dedicated number and verify by OTP. A number cannot be on personal WhatsApp and Business WhatsApp at the same time — the switch is one-way.
2. Complete the business profile. Open Settings, Business Tools, Business Profile. Add outlet name, category Restaurant, address, opening hours, email, website, FSSAI licence number and GSTIN in the description field. Guests read the profile before they order — a blank profile lowers conversion.
3. Open the Catalog tool. From Business Tools, tap Catalog then Add new item. Each item becomes a product card visible inside every chat via the shop icon at the top-right of the chat window.
4. Add the first item with a photo. Upload a 500x500 px photo minimum, enter dish name, price in INR, short description under 150 characters. Save. Repeat for every menu item up to the ~500 item limit. Data entry is the slow part — batch it in one sitting.
5. Group items into collections. Tap Manage Collections, create Starters, Mains, Beverages, Desserts. Assign each item to one collection. Collections show as tabs to the guest browsing the catalog — a menu without collections looks like a wall of images.
6. Toggle sold-out items to hidden. Long-press any item and pick Hide from catalog when the dish is 86-out. Unhide when it is back on the menu. Never leave sold-out items visible — the cost of a refund plus a 1-star review dwarfs the effort of the toggle.
7. Generate a wa.me short link. Use the format https://wa.me/91XXXXXXXXXX?text=Hi%20I%27d%20like%20to%20see%20your%20menu. Print on QR menus, add to Google Business Profile, Instagram bio, Facebook Page and every table QR sticker. The link opens WhatsApp with the outlet's chat pre-populated.
8. Send a test order end to end. From a second phone, tap the link, open the catalog, add 2 items, send the cart to the outlet. Confirm the message lands, price totals are correct, sold-out items are hidden, and the outlet phone can reply within 60 seconds. Fix any friction here before printing QRs at scale.

Setup on WhatsApp Business API — 2-3 days with a BSP

WhatsApp Business API is not a self-serve product. Meta provisions API access only through Business Solution Providers (BSPs) — the current active list of Indian BSPs includes Gupshup, AiSensy, Wati, Interakt, Doubletick, MessageBird and a handful of others. Each BSP wraps the raw Meta API with a dashboard, a chatbot builder and a catalog manager.

Full onboarding takes 2-3 working days end-to-end when documents are ready. Here is the standard sequence.

1. Choose a BSP. Compare on monthly platform fee, catalog sync depth, POS integrations available, WhatsApp Pay support and Green Tick assistance. A single-outlet plan sits in the ₹1,500-4,000/month band. Do not sign the annual contract on day one — most BSPs offer monthly billing.
2. Meta Business Verification. Meta requires the business to complete verification in Meta Business Manager — upload the shop licence, GST registration, FSSAI licence and a utility bill. Turnaround is 1-3 working days. This is a hard prerequisite for API access.
3. Provision the WhatsApp number. The number chosen for API must not be on personal WhatsApp or the WhatsApp Business App. If it is, migrate the chat history off, delete the account, then hand the number to the BSP for provisioning.
4. Set up the display name and business profile. Meta reviews the display name to make sure it matches the legal or trading name. A misalignment (using "Rahul's Kitchen" when the FSSAI licence says "Sharma Foods Pvt Ltd") triggers rejection.
5. Green Tick (optional). The blue-tick equivalent for verified business accounts. Requires the outlet to be a notable brand with press coverage. Most single-outlet operators skip it — the tick is nice-to-have, not conversion-critical.
6. Approve message templates. Utility and marketing message templates need Meta approval before they can be sent. Draft the order-confirmed template, the payment-received template, and the delivery-out-for-dispatch template in the BSP dashboard. Approval takes 24-48 hours per template.
7. Connect the POS to the Catalog API. If the POS supports Meta Commerce Catalog sync natively (Online eMenu Ordering Suite, Petpooja, Restroworks and a few others do), enable it in the BSP dashboard and paste the Catalog ID. Menu changes in the POS now push to WhatsApp within seconds.
8. Import the menu. First sync uploads every item, category, price and photo from the POS to the Meta Catalog. Manual verification: open WhatsApp Business Manager, confirm the item count matches, spot-check 10 items for price and photo accuracy.
9. Set up chatbot flows. Minimum viable set: welcome message with catalog button, order-confirmation auto-reply, out-of-hours message, contact-owner handoff. Every additional flow (loyalty enrolment, feedback request, reorder-past-item) adds measurable revenue but is not day-one critical.
10. First test order and cutover. Send a real order from a real customer number. Verify the flow: guest taps link → opens catalog → adds to cart → sends cart → outlet gets the message with structured items → payment link sent → payment received → order fired to KDS → confirmation sent. Cut over live traffic once all steps land clean.

Menu structure best practices

The menu structure inside the WhatsApp catalog is what the guest actually browses — it decides whether an order lands or an app gets closed. A few rules earn back the setup time within the first week.

Category grouping

Group into 4-6 collections maximum — Starters, Mains, Beverages, Desserts is the standard restaurant template. Cloud kitchens can use brand-based collections (Biryani House, Wraps Co, Sweet Corner) if one number services multiple virtual brands. More than 6 collections and the guest scrolls past them without reading.

Item naming conventions

Format: [Style] [Dish] [Portion if fixed]. Examples: "Punjabi Butter Chicken (Half)", "Andhra Chicken Biryani (Family)", "South Indian Filter Coffee". Skip decorative adjectives — "Delicious", "Authentic", "Homemade" waste the 30-character card headline that guests actually scan.

Description length

Aim for 60-150 characters. Anything under 60 looks lazy, anything over 150 gets truncated in the card preview. Content that works: 2-3 key ingredients, spice level, whether it comes with rice/roti, allergen flags. Content that wastes space: "our chef's special", "made with love", "you will love it".

Modifier handling

The free WhatsApp catalog does not support add-on modifiers natively. Handle it two ways: (1) create separate items for common variants — "Butter Chicken (Full)" and "Butter Chicken (Half)" as two catalog items, or (2) use the description field to prompt the guest — "Reply with spice level: mild / medium / spicy". On the API tier with a proper chatbot builder, modifiers flow inline as buttons.

SKU strategy for common items

Give every item a short SKU in the description tag — "BC-FULL", "BC-HALF" — so KDS printouts and POS reconciliation stay clean. For a 60-item menu this is 15 minutes of upfront work that saves hours of debugging when a guest reports the wrong dish arrived.

Photos — image spec and what actually works

Meta's technical requirements are the floor, not the ceiling.

When phone photos work

A modern Android or iPhone camera in daylight, dish on a white plate, table near a window: this stack produces a catalog-usable photo in 15 seconds per dish. For a menu of 60 items, one operator with an evening off can shoot the entire catalog. Consistency of background and lighting matters more than any single hero shot.

When to hire a photographer

Three cases justify the ₹15,000-40,000 spend on a food photographer: (1) hero photos for Google Business Profile and Instagram that double as catalog images, (2) fine-dining or premium-brand outlets where menu presentation is a positioning cue, (3) launching a new outlet where every touchpoint is being built out at once. For a mid-priced neighbourhood restaurant, phone photos beat delayed listings every time — a live catalog with imperfect photos out-earns a perfect catalog that never ships.

Pricing display — tax, variants, combos

GST-inclusive or GST-exclusive?

Show GST-inclusive prices in the catalog. Two reasons: (1) it matches the price the guest actually pays, which reduces cart abandonment when the invoice arrives with a bigger number, (2) most restaurants under composition scheme cannot show GST separately anyway. If the outlet is on the regular GST scheme and issues tax invoices, footnote the description with "prices incl. 5% GST" — but the headline price stays inclusive.

Variants — small, medium, large

The free app does not support variants inside a single card. Best practice: create one card per variant with the size in the item name — "Cappuccino (Regular)", "Cappuccino (Large)". Cluttered? Yes. Clear? Yes. Guests would rather see 3 clear line items than 1 ambiguous one.

Combo pricing

Combos are a separate catalog item with the combo composition in the description — "Thali Combo: 2 sabzi + dal + rice + 4 roti + salad + sweet, ₹249". Never assume the guest will figure out that "Half Butter Chicken + Naan + Rice = ₹399" — spell it out.

Discount handling

Meta's catalog supports a Sale Price field that shows the discounted price with a strikethrough on the original. Use it for temporary promotions only — never leave a permanent 20% strikethrough live, guests learn to ignore it and it eventually reads as dishonest. For loyalty discounts and coupon codes, apply the discount at the payment step, not in the catalog card.

Availability toggles — the 86-out discipline

Restaurant staff know "86-out" as the shorthand for a dish that has run out of ingredients mid-service. In an in-restaurant context the server tells the guest at the table. In a WhatsApp catalog, if the item is not toggled hidden, the guest orders it, pays for it, waits 40 minutes, then finds out. The cost of that failure mode is asymmetric:

• Refund of ₹250-500 order value
• 1-star Google review that stays visible for years
• Loss of a repeat customer with a ₹15,000+ lifetime value

The fix is a 5-second toggle. On the free app: long-press the item, pick Hide from catalog. On Online eMenu Ordering Suite (or any POS with catalog sync): toggle the item to unavailable in the POS, and the WhatsApp catalog reflects it within seconds. Build this into the shift-open checklist — before opening WhatsApp orders, the shift manager runs through the 86-list and hides every item that will not be available today.

Customer ordering flow — what the guest sees

The end-to-end guest experience for a WhatsApp catalog order in India, on the free app tier:

1. Discovery. Guest sees the outlet on Google Maps, Instagram, a table QR or a Google Business Profile. Taps the wa.me link (or scans the QR).
2. WhatsApp opens. The chat with the outlet opens with a pre-populated intro message ("Hi I'd like to see your menu"). Guest hits send.
3. Catalog opens. The outlet sends back a message with a Catalog button, or the guest taps the shop icon at the top of the chat. The catalog slides up as a native panel.
4. Browsing. Guest scrolls through collections — Starters, Mains, Beverages, Desserts. Taps into individual items to see the full photo, description, price. Adds to cart from inside the item view.
5. Cart review. Guest opens View Cart, adjusts quantities, adds a note ("less spicy please"). Total is calculated live.
6. Send order. Guest taps Send Order. The cart lands in the outlet chat as a structured message: item names, quantities, subtotal, note.
7. Confirmation and payment. Outlet staff replies with delivery time and a UPI ID or dynamic QR (₹350 to yesbank@upi for example). Guest pays via any UPI app.
8. Payment confirmation. Guest sends the payment screenshot or UPI reference number. Outlet marks paid, fires the order to KDS.
9. Order updates. Outlet sends "Order confirmed, preparing now" and "Out for delivery" as text messages. On the API tier these can be structured template messages with tracking links.
10. Delivery and feedback. Rider delivers, guest confirms receipt. Outlet sends a feedback prompt — "Rate your order 1-5" — 30 minutes later.

On the WhatsApp Business API tier, steps 6-9 are automated by the chatbot: cart lands → payment link sent → payment webhook fires → KDS ticket prints → status updates go out on state changes. The guest experience is faster and the operator's per-order labour drops from 3-4 minutes to under 30 seconds.

Compliance — FSSAI, GST, DPDP, Meta policy

FSSAI display

The FSSAI licence number must be visible to the guest at the point of sale. For a WhatsApp catalog, that means the 14-digit FSSAI number goes in the business profile description field, on every dispatched invoice or bill, and on the outer packaging of every delivered order. Section 31(10) of the FSS Act treats non-display as an offence — the fine is ₹2 lakh. See our FSSAI licence fee guide for the complete compliance walkthrough.

GST invoicing

Every WhatsApp catalog order is a supply of restaurant service and attracts 5% GST without ITC (composition-scheme outlets) or 5% GST on food supply plus applicable rates on beverages (regular scheme). A tax invoice must be issued for every order and stored for 6 years. The invoice can be a text message, a PDF or an image — the format is not prescribed, the content is. Required fields: outlet name and GSTIN, invoice number, date, guest phone number, item-wise breakdown, GST amount, total. See our GST composition scheme guide for the full field list.

DPDP consent

India's Digital Personal Data Protection Act 2023 governs how an operator collects, stores and uses guest phone numbers. Three concrete requirements for a WhatsApp catalog operation:

• Purpose disclosure. On first order, send a one-line message: "We store your phone number to send order updates. Reply STOP to opt out of marketing."
• Opt-in for marketing. Send marketing messages (broadcasts, offers, festive campaigns) only to guests who explicitly opted in. Unsolicited marketing is a DPDP violation regardless of platform.
• Retention limit. Retain order data only as long as GST audit requires (6 years). Marketing consent lapses if unused for 2 years — refresh or delete.

Meta's Business Messaging Policy

Meta enforces its own rules on top of Indian law. Key ones for restaurants: no unsolicited messages to numbers that did not initiate contact, no misleading business names, no catalog items outside the approved commerce categories, no illegal or restricted goods (this covers alcohol home delivery in states that prohibit it). Violations trigger tier restrictions, catalog removal, or in repeated cases, permanent account termination. The policy is at business.whatsapp.com/policy — read it once during onboarding, keep a link handy.

Frequently Asked Questions

What is a WhatsApp Business Catalog?

A WhatsApp Business Catalog is Meta's native product-listing feature inside WhatsApp Business. It lets a restaurant publish its menu as a browsable set of item cards — each with a photo, name, price and description — that guests view directly inside a WhatsApp chat by tapping the shop icon. It is distinct from a menu PDF or a website link. Items live on Meta's Commerce Catalog and are stored, moderated and served by Meta infrastructure at no cost on the free WhatsApp Business App tier.

Do I need WhatsApp Business API or does the free app work?

The free WhatsApp Business App is enough for a single outlet doing under 30 orders/day, one phone, one staff member replying manually and a menu under ~500 items. WhatsApp Business API is required when the operator wants multi-agent chat, catalog auto-sync from POS, in-chat UPI payment, order routing to KDS, chatbot flows or WhatsApp broadcasts to more than 250 contacts. API is delivered by a Meta-approved Business Solution Provider (BSP) — the messaging conversation fee is Meta's, and the BSP adds a monthly platform fee.

How many items can I have in my WhatsApp catalog?

The free WhatsApp Business App supports up to approximately 500 items per catalog — Meta has not published a hard cap but the practical limit sits between 450 and 500 before the app slows down. WhatsApp Business API supports Meta's Commerce Catalog which handles up to 30,000 items per business. For a typical restaurant with 60-180 dishes across categories, the free app is more than enough. For a multi-outlet chain sharing one master menu with variants and add-ons expanded, the API-backed catalog is the right tier.

Can I sync my POS menu to WhatsApp catalog automatically?

Yes — but only via the WhatsApp Business API tier, not the free app. Auto-sync means a menu change in the POS (new dish, price update, item marked sold-out) pushes to the WhatsApp catalog within seconds using Meta's Commerce Catalog API. Online eMenu Ordering Suite at ₹199/month includes this sync — one master menu in the POS updates the WhatsApp catalog, the QR menu, Swiggy and Zomato in one action. Manual re-entry into each channel is the failure mode that keeps most operators on the free app.

How much does WhatsApp Business API cost for restaurants in India?

Two costs stack. First, Meta's conversation fee — as of 2026 in India, service conversations initiated by the guest are free within a 24-hour window, utility conversations cost roughly ₹0.115 each, and marketing conversations cost roughly ₹0.78 each. Second, the BSP platform fee — typical Indian BSPs charge ₹1,500-4,000/month for a single-outlet plan with catalog sync, chatbot flows and unlimited service conversations. Total run cost for a mid-size restaurant sits between ₹2,000 and ₹5,000/month all-in.

What image size does WhatsApp Business Catalog require?

Meta requires each catalog image to be at least 500x500 pixels, in PNG or JPG format, and under 5 MB per file. Recommended: 1024x1024 px square photos, sRGB colour space, under 300 KB after compression so the catalog loads fast on mid-range Android devices on 4G. A single dish should have a single primary photo — carousel-style multiple images are supported on API but not on the free app. Photos with heavy text overlay get rejected by Meta's automated moderation — keep the dish clean and let the item name do the labelling.

Can customers pay directly inside WhatsApp?

Yes in India — WhatsApp Pay uses UPI and settles directly into a UPI-linked bank account. WhatsApp Business API accounts can also send a payment link inside the chat that opens PhonePe, Google Pay or Paytm as fallback. The free WhatsApp Business App does not natively invoice — the operator sends a UPI ID or dynamic QR as a text message after receiving the cart, and the guest pays outside the app. For a fully in-chat checkout with automatic payment reconciliation, an API plan with an integrated PSP is required.

Is WhatsApp Business Catalog GDPR / DPDP compliant?

WhatsApp Business Catalog itself is compliant infrastructure — Meta signs a Data Processing Addendum and hosts data on standard-contract-clause servers. The operator's obligation under India's Digital Personal Data Protection Act 2023 (DPDP) is separate: capture explicit consent before sending marketing messages, disclose the purpose of collecting the guest's phone number, provide an opt-out on every marketing conversation, and retain order data only as long as GST audit requirements demand. Marketing broadcasts without prior opt-in are a DPDP violation regardless of the platform.

Do WhatsApp catalog orders integrate with Swiggy and Zomato?

WhatsApp catalog orders are direct-channel orders — they do not go through Swiggy or Zomato and pay zero commission. However, a POS that unifies all channels lets a single menu update push to WhatsApp catalog, Swiggy menu and Zomato menu simultaneously, and pushes every order — direct or aggregator — into one KDS queue. Online eMenu Ordering Suite handles this unification: the operator maintains one master menu, orders from all sources land in one screen, and end-of-day reports show revenue and margin by channel.

How long does it take to set up WhatsApp Business Catalog for a restaurant?

On the free WhatsApp Business App: 30-45 minutes for a menu of 60 items if photos are ready. Uploading item by item is the slow part. On the WhatsApp Business API tier with a BSP: 2-3 working days end-to-end — Day 1 is Meta Business Verification, Day 2 is number provisioning and template approval, Day 3 is catalog sync from POS and first test order. Green Tick (official business badge) is optional and takes another 2-4 weeks of Meta review after the account is live.