Cloud kitchen WhatsApp ordering: take direct orders and keep your margin on repeat customers
Cloud kitchen WhatsApp ordering lets repeat customers order directly from you instead of through an aggregator. A bot shows the menu as lists and buttons, builds a cart, captures the address, takes payment by Razorpay link or COD, and sends confirmation and delivery status messages. On Convo360 you build this flow without code, and you keep the customer's number for opted-in repeat offers.
- Let aggregators handle discovery, and move repeat orders to your own WhatsApp number.
- Use List Menu, Buttons and Set Variable blocks so customers order with taps, not typing.
- Confirm prepaid orders only on the Razorpay payment event, and keep COD with a confirmation step.
- A QR code on your packaging is the cheapest way to bring aggregator customers to direct ordering.
- Send repeat-order nudges and festival offers only to customers who opted in, using approved templates.
Why repeat orders belong on your own WhatsApp number
A cloud kitchen has no dining room, no signboard and no walk-in traffic. Almost every new customer finds you inside an aggregator app, and for that first order the app earns its fee. The problem is the tenth order from the same customer. You still pay the commission your aggregator charges, you still do not get the customer's phone number, and you cannot tell them about the biryani combo you launched last week.
Direct ordering on WhatsApp fixes the repeat-order part of the business. There is no app to install, the chat thread doubles as order history, and the contact stays with you. The aim is not to quit aggregators. Let them handle discovery, and let WhatsApp handle the regulars.
| Point | Aggregator order | Direct WhatsApp order |
|---|---|---|
| Finding new customers | Strong | Weak, you bring the traffic |
| Cost per order | The commission your aggregator charges | Flat platform fee, Meta's per-message fees, payment gateway fee |
| Customer contact | Stays with the aggregator | Number and opt-in stay with you |
| Repeat offers | Paid ads and discounts inside the app | Opted-in WhatsApp messages |
| Delivery | Aggregator's fleet | Your riders or a delivery partner you book |
Be honest about the last row. Direct orders mean you arrange delivery, so fix a delivery radius and a rider arrangement you can actually honour before you promote the number.
The ordering flow: menu, cart and address
Customers should be able to order with taps, not typing. A flow that suits most cloud kitchens:
- Menu: a List Menu of categories (Biryani, Rolls, Thali, Desserts), then a second list of dishes with prices in ₹. A list holds a limited number of rows, so group by category instead of pasting the whole menu. Use a Carousel for photo-led bestsellers and combos.
- Cart: after each dish, ask the quantity with Buttons (1, 2, 3), store the item and running total with Set Variable, then offer 'Add more' or 'Checkout'.
- Address: use Ask a Question for flat and building, landmark and pincode. A Condition block checks the pincode against your delivery area and politely declines if it is outside.
- Returning customers: save the address to a contact custom field, so the next order simply asks 'Deliver to the same address?' with Yes and Change buttons.
Add one more Condition for kitchen hours. An order placed at 1 am should get a clear 'we open at 11 am' message and an option to pre-order, not silence.
Payment: Razorpay link or cash on delivery
At checkout, show the cart summary with the total and two Buttons: Pay online and Cash on delivery.
For online payment, the Razorpay payment link block creates a link for the exact cart amount. Use the payment event trigger so the order is confirmed only after the money actually arrives. Give unpaid links one reminder after a few minutes with a Wait / Delay step, since many people simply get distracted.
COD still matters in many neighbourhoods, so do not drop it. Reduce the risk instead. Ask the customer to confirm the COD order with a button, and send unusually large COD orders to a team member in the live-chat inbox for a quick check before the kitchen starts cooking.
The bot never asks for card numbers, OTPs or UPI PINs in chat. Payment happens only on the Razorpay page.
Order confirmation and delivery status messages
A customer on an aggregator app gets live status. Your direct channel should feel just as reassuring, with four short messages:
- Order confirmed, with items, total, payment mode and an estimated time.
- Being prepared.
- Out for delivery, with the rider's name and number.
- Delivered, with a one-tap rating.
On the kitchen side, push each confirmed order to a Google Sheets row your staff watch on a tablet, or to your POS through a Webhook or HTTP/API request. When staff change the order status, an API or inbound webhook trigger fires the matching customer message.
Because the customer messaged you first, these updates normally fall inside WhatsApp's 24-hour customer-service window. For anything later, such as a pre-order for the next day, use an approved utility template through Send Template. If a customer replies with a complaint, a human can take over the chat and the bot pauses.
Moving aggregator customers to direct with a QR code
Your packaging is the only thing of yours an aggregator customer ever touches. Print a QR code on the box sticker, the bill and a small insert card. The code opens a WhatsApp chat with a pre-filled word such as MENU, and a keyword trigger starts the ordering flow.
- Give a reason to scan: a direct-only combo, a free add-on with the first direct order, or simply 'reorder your usual in a few taps'.
- Ask for offer opt-in in the first chat with Yes and No buttons, and store the answer on the contact.
- Put the same link in your Instagram bio and on your Google Business Profile.
- Read your aggregator's partner terms before placing inserts in their orders, and follow them.
Repeat-order nudges and festival offers
Once a customer has opted in, WhatsApp becomes your loyalty programme. Tag contacts into groups by what they order and where they live, such as veg, biryani regulars or Andheri West. Then use two kinds of messages:
- Repeat-order nudge: a Wait / Delay drip that checks in some days after the last order with a 'Your usual?' button. Waits can run for days and are kept on the server.
- Festival and occasion offers: modak boxes for Ganesh Chaturthi, Eid biryani, Diwali party packs, match-night combos. These are marketing templates, so get them approved by Meta first and send them as a campaign to the right group only.
Marketing messages are charged by Meta, so send fewer, better-targeted offers, and honour STOP replies immediately. The Diwali campaign playbook covers timing and template wording in more detail.
Building it on Convo360, and what it costs
- Connect your WhatsApp number through Meta Cloud API embedded signup. With Coexistence you can keep the WhatsApp Business phone app on the same number.
- In the Flow Builder, create a chat flow with a keyword trigger (MENU, ORDER) and a new conversation trigger.
- Add List Menu, Carousel, Buttons, Set Variable, Ask a Question and Condition blocks for the menu, cart and address.
- Add the Razorpay payment link block and a payment event trigger, plus a COD branch.
- Send orders to Google Sheets or your POS by Webhook, and wire status updates to an API or inbound webhook trigger.
- Use Preview / Try-it for a dry run, fix any dead ends the health check flags, then publish.
A rule-based ordering bot can run as a guided (no-AI) bot with no AI key. Add an AI Reply block later if you want it to answer questions like 'is the paneer roll Jain-friendly?' from your knowledge base. If you run several brands from one kitchen, separate workspaces keep each brand's number and menu apart under one login.
The Starter plan is ₹999/month excluding GST and covers WhatsApp, web chat, the flow builder and CRM. Check pricing for the plan that includes the integrations you need. Convo360 adds zero markup on messages, so Meta's per-message fees and the payment gateway's fee are paid directly at their rates. For counter pickup instead of delivery, see the QSR takeaway ordering guide.
Step by step
- Connect your WhatsApp numberUse Meta Cloud API embedded signup in Convo360. Choose Coexistence if you want to keep the WhatsApp Business app on the same number.
- Build the menu and cartIn Flow Builder, add a keyword trigger such as MENU, then List Menu, Carousel and Buttons blocks. Store items and the running total with Set Variable.
- Capture and check the addressUse Ask a Question for building, landmark and pincode, and a Condition block to confirm the pincode is inside your delivery area.
- Add Razorpay and CODOffer Pay online and Cash on delivery buttons. Use the Razorpay payment link block and confirm prepaid orders on the payment event trigger.
- Send orders to the kitchenPush each confirmed order to Google Sheets or your POS by Webhook, and trigger status messages when staff update the order.
- Print the QR code on packagingCreate a WhatsApp link with the pre-filled word MENU, turn it into a QR code and print it on box stickers, bills and insert cards.
- Run opted-in nudges and offersCapture opt-in in the first chat, tag customers into groups, and send approved marketing templates as campaigns for repeat orders and festivals.
Example conversation
Industry guide: AI agents for Restaurants & QSR — Reservations, orders & feedback on autopilot.
Start taking direct WhatsApp orders
Start free in minutes — no code, no credit card. Bring your own AI keys and pay no per-message markup.
Frequently asked questions
Can a cloud kitchen take orders on WhatsApp without an aggregator?
Yes. A WhatsApp bot can show your menu as lists and buttons, build a cart, capture the delivery address and take payment by Razorpay link or COD. You arrange delivery yourself, so set a clear delivery radius and rider plan before promoting the number.
How do customers pay for a WhatsApp food order?
The bot sends a Razorpay payment link for the exact cart amount, and the order is confirmed once the payment event arrives. You can also keep cash on delivery as a button option, with a confirmation step to reduce fake orders.
How do I get aggregator customers to order from me directly?
Print a QR code on your packaging, bill and insert card that opens a WhatsApp chat with a pre-filled word like MENU. Offer a direct-only combo or add-on as the reason to scan, and check your aggregator's partner terms before adding inserts.
Can I send offers to customers on WhatsApp?
Only to customers who opted in. Offers are marketing messages, so they need a Meta-approved marketing template and are charged by Meta per delivered message. Capture opt-in with a button in the first chat, and honour STOP requests immediately.
Do I need a developer or an AI key to build a WhatsApp ordering bot?
No. On Convo360 the ordering flow is built in a drag-and-drop Flow Builder, and a rule-based menu bot can run as a guided bot without any AI key. You can add AI replies later for menu questions from your knowledge base.
What does WhatsApp ordering cost a cloud kitchen?
On Convo360 you pay a flat monthly plan, starting with Starter at ₹999/month excluding GST, plus Meta's per-message fees and the payment gateway's fee, both paid directly with zero platform markup. There is a 14-day free trial with no credit card.
Related reading
Available across India — see WhatsApp & AI calling automation by state and city.