A WhatsApp ordering platform comparison is easy to get wrong because the demos all look the same: a chat, a menu, a cart, a payment. The differences that matter show up later, in the bill, in who owns the number, in what happens on a busy Saturday, and in how hard it is to leave. These 20 questions pull those differences out before you sign up. Put them to every vendor on your shortlist and write the answers next to each other.
They are grouped into five areas: pricing, ownership, the ordering flow, operations, and marketing plus exit. If you want a shortlist to start from, the guide to the best WhatsApp ordering software for restaurants covers the main options in India.
Pricing: five questions that find the real cost
- What is the all-in cost at my volume? Give the vendor your real monthly order count and average bill, and ask for a single monthly figure including plan, per-order fees, payment charges and message charges.
- Is any charge a percentage of order value? A flat per-order fee stays the same whether the order is ₹200 or ₹2,000. A percentage grows with your ticket. Many "zero commission" platforms still take a percentage somewhere, often on payments. The breakdown of platform fees, commission and per-order fees shows how each model behaves as you grow.
- Is there an order cap on my plan? Some plans quietly limit orders and push you up a tier when you get busy. Ask for the cap in writing or confirm orders are unlimited.
- What do WhatsApp messages cost me? Meta charges for template conversations such as broadcasts. Ask whether the platform passes those charges through at cost, adds a markup, or bundles a fixed number into the plan.
- Is there a free trial on the plan I would actually use? A trial on a stripped-down tier tells you little. You want to test the plan you would pay for, with your real menu, for at least a week.
Ownership: four questions about your number and your customers
- Does the bot run on my own WhatsApp number? Some platforms run orders through a shared or platform-owned number. You want your number, connected to the WhatsApp Business API through Meta's embedded signup, so the customer relationship stays with you.
- If I leave, do I keep the number and the customer list? Ask how the number is released and whether you can export customers and order history.
- Who holds the payment relationship? Platforms that process payments on your behalf hold your money for a settlement period. Platforms that let you connect your own gateway account settle directly to you. Ask which it is and what the settlement cycle looks like.
- Do I get a store page and can it sit on my own domain? A web menu you can link from Instagram and Google matters as much as the chat. If it can live on your domain, the links you print stay valid even if you change platforms later.
The ordering flow: five questions that separate food platforms from chat tools
- Does the menu handle variants and add-ons natively? Half and full, sizes, extra toppings, choice of bread. If the answer involves a workaround, it is a chat tool with a catalog, and the post on why a generic chatbot is not enough for ordering explains what breaks next.
- How are delivery charges worked out? You want zones with distance-based charges and a free-delivery threshold per zone, set by you in a dashboard. A single flat charge for the whole city loses money on far orders and customers on near ones.
- Can customers pay inside the flow and choose cash on delivery? UPI and card through a gateway, with cash as an option, and the order marked paid automatically. Anything that relies on a customer sending a screenshot is a manual process with a fraud risk.
- Does it support pickup, scheduled orders and pre-orders? Pickup points with a collection time, a delivery slot the customer chooses, and pre-orders for tomorrow are standard needs for cafes, bakeries and tiffin services.
- Can the menu change by time and day on its own? Breakfast until 11, lunch until 3, a Tuesday-only special. If you have to switch menus by hand, you will forget at the worst moment.
Operations: three questions about the busy hour
- How does the kitchen find out about an order? A dashboard is not enough at peak. Ask about a staff app with alerts, a spoken announcement, and KOT printing on a thermal printer.
- Does it handle dine-in as well as delivery? QR codes on tables, a table number on the order, and a status that goes from preparing to served. If you have tables, you want one system for both.
- Can I give staff limited access? Roles and permissions so the person at the counter sees orders but not revenue, and a part-timer cannot change prices. Ask what the staff app shows to each role.
Marketing, support and exit: the last three questions
- Can I message my customers from the same number they order on? Broadcasts, coupons that auto-apply, and a post-delivery rating prompt, run from the same dashboard, so an offer and the orders it produces are in one place.
- What does support look like at 8pm on a Saturday? Ask for the support hours, the channel, and a realistic response time. Then message them once during your trial at a busy hour and see what happens.
- How long does setup take, and who does it? A platform that needs a two-week onboarding project is a different commitment from one you can set up in an afternoon. Ask for a number, and test it in the trial.
If a vendor's answers to questions 1, 6 and 7 are vague, stop there. Cost, number ownership and exit are the three that cost you the most to get wrong. The post on what free online ordering systems really cost is worth reading before you take any plan that is priced at zero.
What this looks like on Tezzu
For the record, here are Tezzu's answers to the questions that matter most. The all-in cost is the plan, ₹999, ₹1,999 or ₹3,999 a month, plus a flat ₹10 per order, with no commission and no order cap. Campaign messages are paid from a prepaid wallet at Meta's conversation charges. Every plan starts with a 7-day free trial on the plan itself.
The bot runs on your own number through Meta's embedded signup, and the number stays yours. Payments go through Razorpay, and you can connect your own Razorpay account for zero platform fee on online payments, with cash on delivery as an option. The store page is free and can sit on your own domain. The menu handles variants, add-ons and bundles, delivery zones are distance-based with per-zone free-delivery thresholds, and pickup points, scheduled orders, pre-orders and menu scheduling by weekday and time are built in. Orders reach the kitchen through the dashboard, the staff app with spoken announcements and KOT printing, dine-in gets QR tables and a served status, and staff roles control who sees what. Setup takes about 30 minutes. The pricing detail is in Tezzu pricing explained.
Put the 20 questions to Tezzu yourself
Connect your number, build your menu and test the full flow during the free 7-day trial. No commission, ₹10 per order.
Start your free 7-day trialFrequently asked questions
How do I compare WhatsApp ordering platforms on price?
Give every vendor the same inputs, your monthly order count and average bill, and ask for one all-in monthly figure that includes the plan, per-order fees, payment charges and message charges. Then check whether any part of it is a percentage of order value, because that part grows as your ticket size grows. Compare the totals, not the headline plan prices.
What is the most important question to ask?
Whether the bot runs on your own WhatsApp number and whether you keep that number and your customer list if you leave. Pricing can be renegotiated and features can be added, but a customer relationship that lives on a platform-owned number is not yours, and moving it later is painful.
Should I pick a chat tool or an ordering platform?
If your main need is support conversations and broadcasts across many kinds of business, a chat tool fits. If your main need is turning messages into paid, structured orders that print in the kitchen with delivery charges worked out, you want an ordering platform built for food. Questions 10 to 14 on this list separate the two quickly.
How long should a trial be?
Long enough to take real orders from real customers on the plan you would actually pay for, which means at least a week with your full menu loaded. Use the trial to test the busy hour, the delivery charges and the support response as well as the demo flow.