WhatsApp ordering for restaurants: how it works and when it fits dine-in

WhatsApp ordering works well when the guest isn’t in your dining room yet: takeaway, delivery, catering, next-day pre-orders, and regulars who already message you. It fits dine-in less well. A table order needs to know which table it came from, it needs a staff check before the first order is cooked, and it needs one bill that everyone at the table can see. Chat apps weren’t built around any of that.

We make WaiterPilot, an AI waiter by BroadNet.AI, and it is not a WhatsApp tool. Guests scan the QR code on their table and order by chat in the phone’s browser, with no app and no phone number. It doesn’t take WhatsApp orders, takeaway or delivery. If those are what you need, a WhatsApp ordering service is the better fit, and this guide explains how to choose one.

How does WhatsApp ordering work for restaurants?

Short answer: the guest sends the order in a WhatsApp chat, and either a person or a chatbot handles it.

There are three common set-ups, from simplest to most automated:

1. Replies by hand. The guest messages your WhatsApp Business number. A staff member answers questions, writes the order down and confirms the time and price. This needs no ordering software, but every message is staff time.
2. A menu link that sends the order into the chat. The guest taps a link, picks dishes from a web menu, and the finished order arrives in your chat as a message. Staff confirm and enter it.
3. A chatbot. The guest talks to a bot inside WhatsApp. It answers menu questions, takes the order and passes it to a dashboard, a kitchen screen or a POS. Staff step in when the bot can’t help.

Payment usually happens by a payment link, at pickup or on delivery. Which of these a vendor supports, and what it costs, varies widely, so ask each one directly.

When does WhatsApp ordering fit best?

Short answer: for orders placed before the guest arrives, by guests who already use WhatsApp every day.

• Takeaway and pickup. The guest orders from home or work and collects at a set time.
• Delivery you run yourself. You hold the guest’s number and address for the driver anyway.
• Pre-orders, catering and large groups. Back-and-forth messages (“can we swap the lamb for chicken?”) suit a chat.
• Regulars. Guests who message you already don’t need to learn anything new.
• Markets where WhatsApp is the default way to talk to a business. In many countries, guests expect to message a restaurant rather than call it.

In these cases the guest’s phone number isn’t a privacy cost; you need it to confirm, call back or deliver. If those orders arrive as phone calls rather than messages, our guide to whether AI can take restaurant orders covers phone AI.

Can you use WhatsApp for dine-in orders?

Short answer: you can, but a chat app makes table service harder than ordering in the browser.

Some vendors do offer it. According to its AWS Marketplace listing, ServAI lets guests start from a table QR code or NFC tag and order through WhatsApp, Messenger or a browser chat, with a merchant portal showing table layouts. We found no official ServAI site, so treat those details as unconfirmed by the vendor.

The trade-offs at the table:

• Which table? A QR code can pass the table number into the chat, but staff must trust it and match it to the floor.
• Everyone needs WhatsApp, and shares their number. A guest who doesn’t use WhatsApp, or doesn’t want a restaurant to have their number, can’t order.
• One chat per guest. Four guests at a table means four chats, and someone has to add them into one bill.
• Staff work from an inbox. Orders arrive between other messages instead of on a board sorted by status.
• Pranks and wrong tables. Anyone with the code can send an order to “table 6”. Ask whether staff confirm a table’s first order before it is cooked.
• The chat stays in the guest’s phone. Your restaurant’s thread sits next to their family chats after the meal, which some guests like and some don’t.

How does WhatsApp ordering compare with QR ordering at the table?

Short answer: WhatsApp suits orders from outside; browser ordering from the table suits guests already sitting down.

Guests at sit-down restaurants are open to ordering from a phone: 63% of full-service diners said they would place an order using a smartphone app, and 48% would order with a QR code (NRA, 2024). The question is which tool on the phone fits a guest who is already at the table.

WhatsApp ordering and table QR ordering compared, using WaiterPilot as the table example (as of 16 October 2026):

What does WhatsApp ordering cost?

Short answer: it depends on the set-up; ask for the full cost per order, not just the monthly fee.

We have not checked WhatsApp ordering vendors’ prices for this article, so we quote none. When you compare them, ask about each part of the cost:

1. Software: a monthly subscription, a per-order fee, or both?
2. Commission: is there a percentage on each order?
3. Messaging: are WhatsApp messaging fees included, or billed on top?
4. Payments: who processes card payments, at what rate?
5. Staff time: how many orders will still need a person to reply?

Here’s how staff time adds up when replies are done by hand.

Casa Olivo is a fictional restaurant (an example, not a customer). Assumptions, not measurements: 30 takeaway orders a night by WhatsApp, an average of 5 messages each way per order, and 30 seconds of staff time per message.

On those assumptions, manual WhatsApp ordering takes more than four 8-hour shifts a month. That’s the number to set against a chatbot vendor’s fee. It’s also why a free set-up isn’t free.

What should a restaurant chatbot be able to do?

Short answer: answer only from your menu, take a complete order, and hand guests to a person when it should.

The last point matters to guests. In a June 2026 survey by PAR Technology, which sells restaurant software, 44% said AI goes too far when they cannot easily reach a person (PAR, reported by QSR Web, 2026).

Use this checklist for any chatbot, on WhatsApp or at the table. The right-hand column shows WaiterPilot’s answer for dine-in.

Can you run WhatsApp ordering and table ordering together?

Short answer: yes, and many restaurants should: WhatsApp for orders from outside, table QR for guests in the room.

Keep the two separate, with one rule: when a dish sells out, mark it sold out in both. At Casa Olivo (our fictional example), takeaway orders arrive by WhatsApp at the bar and dine-in orders arrive on the WaiterPilot board. One person owns each channel on each shift.

WaiterPilot doesn’t connect to your POS or printer, so dine-in orders are rung into the till by staff, and so are WhatsApp orders unless your WhatsApp vendor connects to the till.

Where does WaiterPilot fit, and where doesn’t it?

Short answer: it covers dine-in tables only, and uses WhatsApp only for the owner’s summary.

WaiterPilot takes orders by chat at the table, with the table built into every order, staff confirming each table’s first order, and a live bill for the whole table. Guests don’t sign up or give a name, phone number or email to order. Its only link to WhatsApp is on the owner’s side: a “Tonight at” summary of the night that the owner can send by text or WhatsApp from their own phone.

It doesn’t take takeaway, delivery or WhatsApp orders, and it takes no payments. It costs $200 per location per month after 30 days free, with 0% commission and no contract. For other options at the table, see the best AI waiter software, which includes ServAI.

What to do next

Count last week’s orders by where they started: in the room, on the phone, or by message. If most started outside, look at WhatsApp ordering vendors and ask the five cost questions above. If your tables are the problem, read the AI waiter page and what QR table ordering is, check pricing, then try a sample order.