One Channel Sold the Food. Another Took the Order. What Nila Restaurants Taught Us.
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.

Not every channel works for every restaurant. An app will not work for all of them. WhatsApp ordering will not work for all of them either. The only honest way to find out is to test, and one of the clearest tests we have run was with a brand that had been doing things the old way for a very long time.
Nila Restaurants is a reputed 37 year old brand in a tier 2 city. The kind of place where the phone rings all day and the staff know the regulars by voice. They were taking at least 100 call orders a day, entirely by phone. Our job was to help them modernise that. What we learned changed how we think about ordering channels for everyone.
What we actually did
We started by putting Nila on the Play Store and the App Store, so their ordering could run through an app instead of the phone. Customers installed it. Then we ran Meta ads to push orders into the app. The installs came, but the order volume from the ads was not significant. We were paying to reach cold, new attention and hoping it converted.
Then we switched approaches. We started broadcasting content and promotional offers over WhatsApp, straight to the numbers Nila already took orders from. These were people who already knew the brand and already trusted it. This worked really well, and the reason is simple: a broadcast to your own opted in customers converts several times better than a cold ad, at a tiny fraction of the cost. A WhatsApp conversation costs under a rupee. A single ad click can cost a few hundred.
So far the story looks like WhatsApp beats everything. Then it got interesting.
The twist
Because WhatsApp was clearly working, we assumed the orders should live there too. We launched a full WhatsApp ordering system. Nila's customers did not take to it. And during the exact same period, orders through the app climbed sharply.
The same channel was Nila's best tool and its worst tool at the same time. WhatsApp was brilliant at making people want to order. It was poor at actually taking the order. Same channel, same customers, opposite results.
The lesson: two decisions, not one
When a restaurant asks which ordering channel it should use, it thinks it is asking one question. It is really asking two.
The first is about demand. What is the cheapest, most trusted way to make a customer want to order right now? The second is about fulfilment. Once they want to, what is the easiest way for them to actually place the order? Most operators treat these as the same decision with the same answer. Nila proved they are not.
Here is why the two split apart. Receiving a WhatsApp offer asks nothing of the customer. The message lands in an app they already open all day, they see the food, they want it. That is a demand job, and low effort wins it.
Placing an order is a different test. The real question is not how few taps it takes, it is whether this is actually better than what the customer already does. Nila's customers were used to calling a human who knew their order. Typing an order into a chat, going back and forth, never seeing a clean menu or a clear total, is not better than that. It is a sideways move. The app was genuinely better than the phone: the full menu in front of you, a clear total, saved details, reorder in a couple of taps, no waiting on hold. Higher effort to set up, but a real upgrade. So that is where the orders went.
Drive demand where the customer already is. Take the order wherever it clearly beats their current habit. Those two rules point at different channels more often than anyone expects.
What this means for your restaurant
A few things worth taking from it.
First, separate the two decisions before you spend anything. Decide your demand channel and your ordering channel on their own merits, not as one bundle.
Second, warm before you spend cold. Broadcast to the customers who already have your number before you pour money into ads for strangers. It is cheaper and it converts better.
Third, judge every channel on orders, not on installs or clicks. Nila's ads produced installs and very few orders. If you only look at downloads, you will call a miss a win.
Fourth, if your customers phone you today, your ordering channel has to clearly beat the phone, not just look newer. Sometimes that is an app. Sometimes it is WhatsApp. The customer decides, not the trend.
This is also where the right platform matters. Menuthere lets a restaurant run WhatsApp broadcasting, a branded app, a QR menu, and WhatsApp ordering from one place, so the demand you create can flow into whichever ordering channel your customers actually prefer, without rebuilding anything each time you learn something new.
And it is not the same for everyone
The most important caveat is that Nila's answer is not universal. We have seen restaurants where WhatsApp ordering worked brilliantly from day 3. Same country, same channel, completely different result, because the customers and their habits were different. Copy another restaurant's setup and you can easily inherit a mismatch.
That day 3 story, and why WhatsApp ordering won there when it lost at Nila, is the one we will tell next.
Want to find the right channel mix for your restaurant? Menuthere runs your broadcasting, app, QR menu, and WhatsApp ordering from a single place, so you can test what works and shift fast.
