WhatsApp Business API for cloud kitchens: setup, rules and real costs

The app is fine until these start happening to a cloud kitchen:

• Zomato/Swiggy commissions eat your margin.
• Customers order once, platforms own them. Zomato knows your customers. You don't. They can recommend competitors on your next order.
• Repeat orders leak to the aggregator. A customer who ordered direct last week orders through Zomato this week, because nothing reminded them you exist.

The app cannot send on a trigger, share one number across staff, or read your records. The API can. And customers keep asking the same things: customers ask where their order is, whether an item is available today, whether you deliver to their area, and why the order they got differs from the one they placed.

• A verified Meta Business account in the cloud kitchen's legal name, backed by a registration, GST or utility document.
• A number not active on the WhatsApp app — your current one works once it is removed from the app.
• A display name matching the business, and a website or public page Meta can check.
• Opt-in from every customer you message first. Direct orders — through your own link or WhatsApp catalogue rather than a delivery app — are where you finally get the customer's number and consent.

1. Connect the number through Meta's embedded signup inside Reputoo, and submit business verification — you can start sending within Meta's starting limit while it is reviewed.
2. Get your first templates approved for the 2 routine messages listed below; anything outside a customer's 24-hour reply window must be a template.
3. Wire the triggers to your records. What to connect: aggregator dashboards plus a kitchen display or POS; direct WhatsApp orders should land in the same queue as everything else.
4. Put staff on one shared inbox, with conversations assigned so two people never answer the same customer.

A kitchen taking 150 direct orders a day with three updates each sends about 13,500 utility messages a month — roughly ₹1,553 in Meta fees on the July 1, 2026 India rate card, before GST. That is usually small next to the commission those orders would have cost through an aggregator. Promotions cost ₹0.8631 each.

Aggregators bring discovery; direct orders bring margin. The customers worth moving are the regulars — the ones who order the same thing twice a week. A card in every aggregator order ("Order direct on WhatsApp for our full menu"), a QR code on the packaging, and a direct-order benefit that is real — a free item, faster confirmation, a loyalty stamp — move some of them. Aggregators' own rules on contacting their customers vary; collect consent directly from the customer, not from aggregator data.

Meta charges per delivered template message, and the price depends on the category. For cloud kitchens, the day-to-day messages sort like this:

• Customer orders directly on WhatsApp — service reply
• Live delivery updates sent automatically — utility
• Post-delivery re-order prompt — utility
• Win-back for 7-day inactive customers — marketing

Timing matters as much as category. Order and dispatch updates in real time; promotions just before lunch and dinner decision windows, when people open food apps.

A service reply answers a customer who wrote first; from 1 October 2026 Meta charges those at the utility rate. Utility messages (confirmations, reminders, status updates) cost a fraction of marketing messages, so keep them strictly transactional — a discount line inside a reminder makes Meta classify the whole template as marketing.

Meta list rates, July 1, 2026. India in INR, plus 18% GST.

"Where is my food?" is the message cloud kitchens get most. Four short utility messages — confirmed, preparing, out for delivery with the rider's name, delivered — answer it before it is asked. When the kitchen is running late, say so with a new time; hungry customers forgive a delay they were told about.

Many cloud kitchens run several virtual brands — biryani, pizza, healthy bowls — from one kitchen. Each brand can have its own WhatsApp number, display name and menu under one business account, with orders landing on the same kitchen screen. Customers see the brand they chose; the kitchen sees one queue.

Meta rates every number on how customers react. For cloud kitchens, the risk is usually messaging the whole contact list about something only some of them asked for. Send reminders only to people with a booking or order, promotions only to people who opted in to them, and never use a bulk-sender tool on the ordinary app — that is the route to a banned number. The full list of what Meta checks is in our WhatsApp Business API guide.

Direct orders can come from a WhatsApp catalogue with dishes and prices, a link to your ordering page, or a chat where customers type their order. The catalogue suits a stable menu; the link suits complex customisation; the chat suits regulars with a usual order. Payment by link at order, or cash on delivery if you offer it.

Direct delivery only works within your riders' reach. Confirm the address is in your area before accepting the order, give an honest time, and if you use third-party delivery partners, pass the order to them with the customer's instructions.

Wrong or missing items and cold food need a fast, fair response. Customers report in the chat with a photo; staff decide the remedy — replacement, refund or credit — from the shared inbox. Speed matters more than the size of the remedy.

Put allergen and dietary information on the menu — vegetarian, vegan, Jain, contains nuts, gluten — and confirm allergy notes on the order. Severe allergies should be confirmed by a person; a shared kitchen cannot always guarantee against cross-contamination, and saying so honestly is better than an automated yes.

1. Week 1: set up the number, catalogue or order link, and order-status templates; connect the kitchen screen.
2. Week 2: QR codes and cards in aggregator packaging; direct orders open.
3. Week 3: order-status messages for every direct order; loyalty for direct customers.
4. Week 4: the first lunch-deal message to customers who opted in.

• Direct orders appear on the kitchen screen with the rest.
• Delivery area and times are defined.
• Order-status messages fire from order events.
• Allergen tags are on the menu.
• Marketing goes only to customers who opted in directly.

Office lunches, diet meal plans and tiffin subscriptions are steady revenue for a kitchen. WhatsApp handles the rhythm: the week's menu on Sunday, a daily "your lunch is on the way", skip-a-day requests, and renewal reminders with a payment link before the plan ends. These are utility messages as long as they describe the plan the customer already has.

Kitchens with their own riders can send the rider's name and number with the out-for-delivery message, so customers call the rider rather than the kitchen for directions. With third-party delivery partners, pass the tracking link instead. Either way, the customer knows who is coming.

Kitchens that take direct orders on a phone lose orders during the rush, when nobody can type. The API puts orders on a screen the kitchen already watches and sends every status message automatically, so direct orders scale without adding staff at a phone.

Customers who cannot see your kitchen ask how food is prepared and packed. A short, factual answer — your FSSAI licence number, how you pack for delivery, how you handle vegetarian and non-vegetarian items — builds trust. Keep it in your knowledge base so any staff member or your chatbot gives the same answer.

Keep templates short and factual: order number, items, total, time, rider. Keep offers out of order-status templates so they stay utility, and put combos and deals in separate marketing templates sent only to opted-in customers.

Direct orders can be paid by link at order or cash on delivery. A payment link in the order confirmation settles most orders before the rider leaves, which speeds handover at the door. Refunds for missing items can be sent back the same way once a person approves them.

Late-night kitchens serve customers when everything else is shut. An automatic reply outside hours should say when orders reopen, and a kitchen that runs until 3 am should say so clearly — it is a reason customers save your number.

Office customers need GST invoices in the company's name. Collect the details once, and send the invoice as a PDF with every office order or monthly for accounts on credit.