WhatsApp food ordering for restaurants: build a direct-order channel your regulars will use

Gaurav Chhabra runs a 30-seat Punjabi restaurant in Mohali with a delivery kitchen behind it and three riders of his own (an invented example). Most of his delivery orders come through the food apps. About fifty families order from him every week, and a few already ring the restaurant to order directly because they know him. He wants WhatsApp food ordering for those families: a number they message, a menu they can see, a way to pay, and an update when the food leaves.

Our restaurant and cloud kitchen playbook covers running orders, table bookings, Instagram comments and the after-delivery feedback message from one inbox. This one is narrower: building the direct-order channel itself, step by step, and what it really costs. Terms such as “service message” are in the glossary.

What does “zero commission” actually save?

The commission, and only the commission. Marketplaces charge restaurants a commission on each order; look at your own invoice for the percentage you pay, because it varies by agreement and we won’t guess yours.

What a direct order costs instead:

• Meta’s message charges, worked out at the end of this article.
• Your payment gateway’s fee on online payments, from your gateway’s own rate card.
• Delivery: your riders’ time and fuel, or a delivery service.
• Your provider’s plan.
• The work the marketplace did: answering “where is my order”, issuing refunds, and being found by people who have never heard of you.

That last point decides the strategy. A direct channel keeps the customers you already have. It rarely finds new ones. So build it for regulars, and expect the apps to stay your shop window for strangers.

Step 1: get your regulars onto one number

Put one business number everywhere a regular already looks: the bill, the menu card, the table tent, the delivery bag sticker, the Google Business Profile chat button (our Google profile guide covers setting it up) and the Instagram bio.

Use a QR code that opens a chat with a message already typed, and make the message different for each placement: “Hi, I’d like to order (bag)” or “Hi, I’d like to order (table)”. The first message then tells you which one works. Our QR code guide shows how.

Read your marketplace partner agreement before putting stickers or inserts in bags that went out on the apps’ orders. Bills and table tents in your own restaurant are yours to use.

Step 2: share the menu in a form people can order from

There are four ways to put a menu in a chat, and they suit different kitchens.

Format	What the customer sees	Meta’s limits	What you need
Photo or PDF menu	Your printed menu	Images 5 MB, JPEG or PNG; PDFs 100 MB	Nothing extra; the customer types the order
List message	One button opening a list of rows	Up to 10 rows in all, titles of 24 characters, descriptions of 72	Nothing extra; good for today’s specials
Multi-product message	Up to 30 dishes in sections, with a cart	Text header required	A Meta catalog
Product carousel	2 to 10 dish cards to swipe	Body text required; no header, footer or buttons	A Meta catalog

A catalog is the closest thing to an app screen. The customer adds dishes to a cart inside the chat and sends it as one order, which arrives with each item’s ID, quantity and price. Meta’s own multi-product page gives a restaurant’s exact use: “a user can re-order their regular take-out order of less than 30 items.” The habits to know, from Meta’s catalog pages and our catalog guide: the cart lives on one device, can’t be edited once sent, and dish pages show images only. Mark a dish unavailable when it runs out and Meta shows it as unavailable in messages that carry it. Businesses based in India “must comply with all online selling laws”, Meta’s catalog overview adds.

Our view: if your menu changes daily or runs past 30 dishes, a clear photo menu plus a list message of today’s specials is less work and nearly as quick for a regular who knows what they want. A catalog earns its upkeep when the menu is stable and direct orders run to dozens a day.

Every one of these is a reply inside the customer’s window, so each is a service message.

Step 3: take the order in one confirmation

The order is only real when the customer has seen it written back. Send one message with everything in it: dishes and quantities, notes (“less spicy”, “no onion”), the address, delivery fee and packaging, total, payment method and a time. Then two buttons.

AR A regular customer talking to Chhabra Family Kitchen

1. A regular customer:
   Hi, I'd like to order (bag). 2 dal makhani, 4 butter naan, 1 jeera rice. Same address as last time 8:04 pm
2. Chhabra Family Kitchen:
   Got it: 2 dal makhani, 4 butter naan, 1 jeera rice to your Sector 70 address. Food ₹840, delivery ₹40, total ₹880. Ready in about 35 minutes. 8:05 pm
   • Confirm order
   • Change order
3. A regular customer:
   Confirm order 8:05 pm
4. Chhabra Family Kitchen:
   Thank you. Here is the payment link for ₹880, or pay the rider in cash if you prefer. 8:05 pm
5. Payment checked in the gateway dashboard · tagged Paid · ticket to kitchen

For a new customer, ask for the address with Meta’s address message, which is “only available for businesses based in India and their India customers”, or ask them to share a location pin with a location request message. Riders find a building from a pin faster than from “near the gurdwara”. Check the distance before you confirm. A promised delivery you can’t make is worse than a polite no.

Step 4: send a payment link, and check it yourself

Most restaurants should send their gateway’s payment link or a UPI request in the chat, or take cash on delivery from regulars they know. Meta does have a Payments API for India that puts the bill and a pay button inside the chat; it needs a gateway and a provider that supports it, and our WhatsApp payments guide explains which modes are open and which are still gated.

Two rules from the counter. Mark an order paid from the gateway dashboard or the bank app, never from a screenshot, because a screenshot is a picture of a payment. And save any screenshot a customer sends: Meta’s media page says a file received in a webhook can be downloaded for only 7 days.

Step 5: order-ready and delivery updates

A food order is cooked and delivered within an hour or two of the customer’s message, so their 24-hour window is nearly always open. That means updates can go as ordinary service messages, which draw on the 1,000 free a month first.

Approve them as utility templates anyway. A template gives every update the same wording whoever sends it, and it still goes out when the window has closed: a party order booked three days ahead, or tomorrow’s lunch ordered tonight.

Hi {{1}}, your order {{2}} has left the kitchen and should reach you by {{3}}. Message us here if you need anything before then.

Hi {{1}}, your order {{2}} is packed and ready at the counter. Please show this message when you collect it.

Both are utility at ₹0.1150 per delivered message to an Indian number, before GST. Since 1 October 2026 a utility template is charged at that rate inside the window too. Give the restaurant’s number for questions, not the rider’s own phone.

Keep offers out. “Try our new kulfi” in a delivery update makes the template marketing, because Meta bills mixed content at the marketing rate.

Step 6: regulars and the weekly special

A weekly special is a marketing message: ₹0.8631 per delivered message, an approved marketing template, and a separate opt-in. Ask after the first direct order arrives, not before: “Can we send you our Thursday special on WhatsApp? Once a week, and you can stop anytime.” Record the date and the wording, as our opt-in guide describes.

Hi {{1}}, this Thursday at {{2}}: {{3}}, cooked fresh from 6 pm until it runs out. Reply here to order.

Add a dish photo as the header, a quick-reply Order now button, and Meta’s marketing opt-out button.

Pick one day and keep to it. WhatsApp may limit how many marketing messages one person receives from all businesses combined, based on their recent reading, so a special sent three times a week mostly teaches people to ignore it. When it’s held back, the send fails with error 131049. A customer who replies “Order now” opens the window, and the rest of that conversation is service messages again.

Step 7: complaints, now that you are the refund desk

On the apps, the marketplace handled the angry customer. On your own channel, the counter does. Write the rules down so the person on shift can act without ringing the owner:

Problem	What the counter does
Missing item	Ask for a photo of the bag, then send the item or refund it the same evening
Cold or spilt food	Replace it if the rider can return within the hour; otherwise refund
Late delivery	Apologise and give the real time, once
Wrong order	Replace it, and let the customer keep the wrong one

Handle it in the chat while the window is open, and tag it Complaint with a note of what was given. Don’t send a “sorry, here is a credit for next time” template later. Meta’s categorization page lists that exact kind of message, an apology for a delay with a credit, as marketing.

What a month costs

An illustrative restaurant taking 40 direct orders a day for 30 days: 1,200 orders.

Messages	Category	Count	Cost before GST
Menu, confirmation, payment link, paid and on-the-way, 5 per order	Service	6,000
Questions, changes and complaints	Service	400
All service messages	Service	6,400, less 1,000 free	5,400 × ₹0.1150 = ₹621
Thursday special to 600 opted-in regulars, 4 weeks	Marketing	2,400	₹2,071.44

That’s about ₹2,692 a month, or about ₹2.24 an order, plus the provider’s plan and the gateway’s charges. Conecxt’s Basic plan caps 5,000 contacts and 10,000 messages a month, so check a cap like that against your own volume. Then put your marketplace invoice for the same month beside these numbers and do the sum for your kitchen.

Before the first direct order

• One number on the bill, menu card, table tents, Google profile and Instagram bio
• A different pre-filled message for each placement
• Marketplace partner agreement read before anything goes in their bags
• Menu ready as a photo or PDF, or a catalog if the menu is stable
• One confirmation message format with Confirm and Change buttons
• Payments marked from the gateway, never from screenshots
• Two utility templates approved: on the way and ready for pickup
• Weekly special opt-in asked after the first order, one fixed day
• Complaint rules written down where the counter can see them

Do the first one this week: a number on the bill costs nothing, and next month’s first direct order will start there.