A 37 year old tier 2 restaurant doing 100+ call orders a day proved that demand channels and ordering channels are two different decisions. Here is the playbook.
Previous article
Every restaurant chasing a lower commission rate is solving the wrong problem.
Next article
A 37 year old restaurant doing 100+ call orders a day showed us that the channel that drives demand and the channel that takes the order are two different decisions.
A WhatsApp broadcast to your own opted in list converts 5 to 8 times higher than a cold advertising channel, and each conversation costs around 0.88 rupees against 150 to 400 rupees for a single Instagram click (WA.Expert). So you would expect the story to end with "we moved everything to WhatsApp and won." It did not. The most useful thing we saw was stranger than that, and it rewired how we think about ordering channels entirely.
Nila Restaurants is a 37 year old institution in a tier 2 city. The kind of brand where the phone rings all day and the kitchen just knows the regulars. They were doing a minimum of 100 call in orders a day, entirely on voice, entirely on habit. When we set out to digitise that, we assumed the job was to pick the one right channel and move them onto it. The job turned out to be the opposite: separating two decisions that everyone treats as one.
Ask an operator which ordering channel they should use and they will name one thing: the app, or WhatsApp, or the website. That single question is actually two questions wearing one coat.
The first is a demand question. What is the cheapest, highest trust way to make a customer want to order right now? The second is a fulfilment question. Once they want to order, what is the least painful way for them to actually place it? Most restaurant tech pretends these have the same answer. Nila proved they do not.
We started where most digitisation projects start. We put Nila on the Play Store and the App Store to automate the ordering their staff were handling by phone. Customers did install it. Then we ran Meta ads to drive orders into it. The installs came, but the order volume from the ads was not significant. We were paying to rent cold attention and hoping it converted, which is the oldest and most expensive move in the book.
Then we switched on WhatsApp and started broadcasting content and promotional messages to their existing ordering numbers. These were people who already knew Nila, already had the number, already trusted the brand. The results were immediate and real. This is exactly what the data predicts: a broadcast is fundamentally a tool for reaching people who already know you, and owned warm audiences convert several times better than cold ad traffic (Qualimero, WA.Expert).
Here is the part that surprised us. Once WhatsApp broadcasting was clearly working, we introduced a full WhatsApp ordering system, assuming that if the demand lived on WhatsApp, the order should too. Nila's customers did not accept it. And during the exact same period, orders through the app climbed sharply. The same channel that was Nila's single best demand engine was its worst ordering channel, at the same time, for the same customers.
This looks like a contradiction until you separate the two decisions.
Receiving a broadcast requires zero behaviour change. The message lands in a thread the customer opens dozens of times a day, they see the food, they get tempted. WhatsApp is unbeatable for that job because the friction of receiving is essentially nil. That is a demand job, and low friction wins it.
Placing an order is a different test. The right question is not "how few steps is this," it is "is this actually better than what the customer does today." For a brand whose customers were used to calling a human who knew their order, typing a free text order into a chat, going back and forth, and never seeing a clean menu or a clear total, is not an upgrade. It is an awkward sideways move. The app, by contrast, was a genuine step up from the phone: the full menu visible, customisation, a clear total, saved details, repeat ordering, no waiting on hold. Higher setup cost, but a real improvement over calling. So it stuck.
The pattern underneath: for the demand channel, minimise the friction of receiving. For the fulfilment channel, maximise the upgrade over the customer's current habit. Those two rules point at different channels more often than anyone admits.
The first mistake is assuming the demand channel and the ordering channel must be the same. They are chosen on opposite criteria, so they frequently should not be.
The second is judging paid ads on clicks and installs instead of on orders. Nila's Meta ads produced installs. They did not produce meaningful order volume. If we had stopped at the install number, we would have called a failure a success.
The third is the assumption that a channel that works for one restaurant will work for the next. Nila's customers rejected WhatsApp ordering. We have other restaurants where WhatsApp ordering worked beautifully from the third day. Same country, same channel, opposite result, because the customer base and their existing habit were different. Copying another operator's fulfilment stack is how you inherit their mismatch.
Decide your demand channel and your fulfilment channel separately. Write them in two columns. The moment you stop assuming they are the same, better options appear in each.
Before you rent cold attention with ads, broadcast to the customers who already have your number. It is warmer, cheaper, and it converts several times better. Cold acquisition is a top up, not a starting point.
Installs, impressions, and open rates are diagnostics. Completed orders are the verdict. A channel that produces downloads but not orders has not earned its budget.
If your customers call today, your ordering channel has to be clearly better than calling, not just newer. Sometimes that is an app. Sometimes it is WhatsApp ordering. The customer's current behaviour decides, not the trend.
The reason operators get stuck is that demand and fulfilment usually live in separate tools that do not talk. A platform like Menuthere lets a restaurant run WhatsApp broadcasting, a branded app, a QR menu, and WhatsApp ordering from a single system, so the demand you create flows straight into whichever fulfilment channel your customers actually prefer, and you can shift that mix without rebuilding anything.
Broadcasting works until it is abused. Message only opted in customers, warm up a new number before scaling sends, segment instead of blasting, lead with value, and honour opt outs fast. Blast a cold list and Meta throttles then bans the number. A healthy list compounds. A burned one is gone.
Nila did not teach us that WhatsApp beats apps, or that apps beat WhatsApp. It taught us that "which ordering channel" is the wrong question, because it hides two different decisions that deserve two different answers. The channel that makes a customer want to order and the channel that lets them place it are chosen on opposite logic, and the best operators pick each on its own merits.
WhatsApp created the hunger. The app fed it. For the next restaurant, the answer flips. That is not a flaw in the strategy. It is the strategy.
See your demand and ordering channels working together. Menuthere runs WhatsApp broadcasting, your app, QR menu, and WhatsApp ordering from one place, so you can create demand and capture it wherever your customers actually prefer.
Sources: WA.Expert (owned list conversion, broadcast cost versus ad click cost), Qualimero (broadcast as an owned audience tool), Paytronix (app adoption and cart abandonment), SendWo (WhatsApp cost per lead), Meta and Sensor Tower (WhatsApp open rates and daily usage in India).
WhatsApp ordering
Most operators know this number. It gets quoted in every WhatsApp group in the industry. What gets discussed far less is the second cost, the one that never appears on the invoice.
WhatsApp ordering
You built a structured ordering flow. The customer thinks they are talking to a restaurant. They are not wrong, because it is a chat. Here is how to design for that.