Taking Orders on WhatsApp Without Losing Track of Them
2 September 2026 · MidaOne
Nobody plans to run an ordering channel on WhatsApp. It arrives on its own: an office manager asks for a number instead of using the app, a regular sends a message on the way over, a neighbour asks whether you can do twenty sandwiches for Thursday. Within a year a real share of your trade is coming through a chat thread, and none of it is in the till until somebody remembers to put it there. This is a good channel — it costs nothing, the customer is yours rather than a platform's, and it converts far better than anything you post. It just needs a small amount of structure, because the failure mode is not losing money on the order. It is losing the order.
Why WhatsApp orders go missing
A chat is a conversation, not a queue. It has no unread state that survives someone opening it, no way to mark an order as accepted rather than merely seen, and no distinction between the message that matters and the sixteen after it. Add three people who all reply from their own handsets and you have a system where an order can be read by everyone and prepared by nobody.
Almost every WhatsApp failure a café has is one of four: the message was opened during a rush and never came back; the order was agreed in the thread but never written anywhere the kitchen looks; two people answered and each assumed the other had it; or the person who took it was off on the day it was due. None of these are attention problems. They are all the same missing step — the order never left the chat.
Get the order out of the chat and into the till
This is the whole discipline, and it is one sentence: a WhatsApp order is not accepted until it exists somewhere other than WhatsApp. For a small order that means ringing it into the till as an open ticket the moment you confirm it, so it sits with everything else and gets picked up on the next look at the screen. For anything with a date on it, it also means a line on whatever the kitchen actually reads in the morning — a prep sheet, a whiteboard, a diary. The chat is where the customer talks to you. It is not where the order lives.
Doing it that way fixes several problems at once. The order is visible to whoever is on shift rather than to whoever owns the phone. It reduces stock as you sell it rather than being discovered as a gap at stocktake. It carries the same 5% VAT and lands in the same sales record as a counter sale, so your reports do not quietly understate a channel. And when you later ask whether WhatsApp is worth the effort, there is something to count.
Reply with a confirmation the customer can reread, too — items, total, and the time it will be ready. It takes fifteen seconds and it removes the most common argument at handover, which is not about price but about when.
What to pin down before you say yes
Most disputes over a chat order trace back to something that was never actually stated. These are the ones worth typing every time, even when it feels excessive:
| What to confirm | Why it matters |
|---|---|
| The exact items and quantities, typed back | "The usual, times twenty" means something different to the person making it than to the person who asked |
| Collection or delivery, and by whom | Assumed delivery is the single most common cause of a large order sitting on your counter |
| The time — ready by, not ordered for | A nine o'clock meeting means the coffee leaves you at half past eight, not at nine |
| How it is being paid, and when | Deciding this at handover, in front of the customer, is how discounts get invented |
| A name and number for the person collecting | Often not the person messaging you, and the only way to reach anyone when they are late |
Once an order is big enough to need special buying, it is not really a WhatsApp order any more — it is catering, and it deserves the quote, the deposit and the written terms that go with it. Taking catering orders without losing money on them covers where to draw that line and what to ask for up front. The important thing is that the line exists, and that you decided where it sits in a quiet hour rather than at eleven at night.
A phone number is not a customer list
A year of orders leaves you with a contacts list full of people who have bought from you, and the temptation to send all of them your new menu is obvious. Resist it. A number somebody gave you so you could tell them their coffee was ready is not permission to market to them, and those are two genuinely separate consents in the UAE. Promotional messages need consent you can actually produce later, and a chat thread about a sandwich order is not it.
Build the list deliberately instead — ask at a moment when you are giving something rather than taking, record what the person agreed to and when, and give them an easy way out of it. Building a café customer list without annoying anyone works through what to collect, how to ask and where the consent line sits. The upside of doing it properly is that the resulting list is worth something; a list of people who never agreed to be on it mostly generates blocks.
Keep it off one person's personal phone
The most expensive version of this channel is the one that lives on a manager's handset. When they leave, so does every corporate contact, every standing Thursday order and every conversation you would need to reconstruct one. It is also the version where nobody else can cover a day off. Use a number that belongs to the business, on a device that stays in the café, and make answering it part of a shift rather than part of a person. If more than one person needs to reply, agree who owns the thread during which shift — two people answering is worse than one person answering slowly.
It is worth noticing what this channel actually is: a direct line to the customers who like you most, with nobody taking a percentage of it. That makes it the cheapest counterweight you have to the commission a delivery platform takes on the same order. A café with a working direct channel is negotiating from a different position than one whose entire order flow belongs to somebody else.
Where MidaOne fits — and where it doesn't
Straight answer first: MidaOne does not connect to WhatsApp. Orders do not arrive in the system from a chat, and nothing about that is automated. What it does is give the order somewhere to go the moment you confirm it — rung into the till on whatever device is nearest, held as an open ticket until it is collected and paid, with stock deducted and 5% VAT applied like any other sale, so the channel shows up in your sales by item and by hour instead of being invisible. If you would rather customers browsed before they messaged, each café also gets its own public QR menu page you can send as a link, which cuts down the back-and-forth about what is available.
Put every chat order in the same sales record as the counter. Free for 14 days, no card.
Start your free trialFrequently asked questions
Is it a good idea to take restaurant orders on WhatsApp?
For a small café in the UAE, usually yes — it costs nothing, the customer relationship stays yours, and it is where a lot of people already prefer to order. The risk is operational rather than commercial: chat has no queue and no accepted state, so orders need to be transferred into your till or prep list immediately rather than left in the thread.
How do I stop losing WhatsApp orders during a rush?
Make the rule that an order is not accepted until it has been rung into the till or written on the prep sheet, and confirm it back to the customer with items, total and ready time. If the order only exists in the chat, it will eventually be missed, and it will be missed on your busiest day.
Should I take a deposit for a large WhatsApp order?
Once an order requires you to buy in stock specially or blocks a chunk of production time, taking something up front is normal and reasonable. Decide your own threshold in advance and apply it consistently, so it reads as policy rather than as distrust of the person asking.
Can I send offers to customers who ordered from me on WhatsApp?
Not on the strength of the order alone. A number given so you could deliver an order is not consent to receive marketing, and promotional messages in the UAE need consent you can evidence later. Ask separately, record what was agreed, and always include an easy way to opt out.
Should the café's WhatsApp be on a staff member's own phone?
No. Use a number owned by the business on a device that stays in the café. Otherwise your order history and your corporate contacts leave with whoever was carrying the handset, and nobody can cover the channel on their day off.
The cafés that handle this well are not the ones with a clever tool. They are the ones where everybody knows the same rule, applies it to every message, and treats the chat as the doorway rather than the record. Write the rule down, put it where the phone lives, and the channel stops being the thing you dread opening after a rush.