Restaurant WhatsApp Orders: Take Orders in the Chat, No App Needed
A menu, a cart, and a payment link, all inside the chat a customer already has open.
A customer messages your restaurant's WhatsApp number to ask if you're open late. That's the moment to take their order right there, instead of pointing them to a delivery app where your menu sits next to five competitors and a 20%+ commission gets taken off the top before you see a cent.
Restaurant WhatsApp orders work because the entire flow — menu, cart, payment, delivery updates — happens inside a chat the customer already has open. There's no app to download and no account to create, which removes most of the friction that makes a first-time customer give up halfway through an order.
Why restaurant WhatsApp orders beat delivery apps
Delivery apps solved discovery — they got restaurants in front of new customers. But for a repeat customer who already knows your restaurant, an app is pure friction: open it, search for your name, scroll past ads for other restaurants, then place an order that a third party takes a cut of. WhatsApp skips all of that. The customer messages you directly, and the order goes straight to your kitchen with no commission taken anywhere in between.
This doesn't replace delivery apps for new customer discovery — it's the better channel for the customers who already know you, which over time is most of your order volume for any restaurant with regulars.
Menu setup
Build your menu as a product catalog inside WaSMS — categories (starters, mains, drinks), each item with a photo, price, and short description. A customer browses the catalog inside the chat itself, the same way they'd browse a delivery app, without ever leaving the conversation.
Keep item names exactly as customers already say them. If regulars call something "the spicy chicken wrap" and your official menu name is different, use the name customers actually use — that's what they'll type when they message you directly instead of browsing the catalog.
Keeping the menu current
A catalog that shows an item you're out of is worse than no catalog at all — it generates an order the kitchen has to cancel and apologize for. Whoever's on shift needs a simple way to mark an item unavailable for the day, ideally from a phone rather than needing a computer, so the catalog reflects reality by the time the lunch rush starts rather than by the time someone remembers to update it that evening.
Cart and order flow
Once a customer adds items, WaSMS builds a running cart summary automatically and shows it back to them before checkout — no chance of a wrong order reaching the kitchen because someone misread a text message. Quick-reply buttons handle the common decisions: delivery or pickup, any substitutions, spice level.
curl -X POST https://api.wasms.net/v1/messages/send \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"to": "+15551234567",
"type": "buttons",
"body": "Your order: 2x Spicy Chicken Wrap, 1x Iced Tea — $24.50. Delivery or pickup?",
"buttons": ["Delivery", "Pickup"]
}'
Handling special requests and allergies
Free-text notes still matter even inside a structured cart flow — "no onions," "nut allergy, please confirm the sauce," or "ring the bell, don't call" are the kind of details a rigid button-only flow can't capture. Let a customer add a note to any item or to the whole order before it's sent to the kitchen, and make sure that note prints or displays clearly wherever your kitchen staff actually looks, not buried at the bottom of an order ticket where it's easy to miss during a rush.
Payment options
Send a payment link directly in the chat once the order is confirmed — the customer pays without leaving WhatsApp, and you get confirmation the moment it clears. For regulars who prefer cash or card on delivery, keep that option available too; forcing prepayment on every order can cost you customers who've ordered from you for years without ever needing to pay up front.
Running more than one location
If your restaurant has multiple locations, route each customer's order to the nearest one automatically based on their delivery address, rather than making them specify which branch they mean. Each location can run its own catalog with local pricing and item availability, while sharing the same overall WhatsApp setup and order-flow logic — a customer messaging your main number shouldn't need to know which branch is fulfilling their order at all.
Delivery updates
Once an order is placed, automated status updates — order confirmed, in the kitchen, out for delivery — cut down the "where's my order" messages that otherwise interrupt your front-of-house staff during a dinner rush. A customer who can see their order is five minutes out doesn't need to call and ask.
The restaurants getting the most out of this aren't replacing their delivery app presence — they're capturing the orders that were always going to come from repeat customers anyway, without giving up a commission on every one of them.
Repeat customer reactivation
A customer who ordered three times last month and hasn't messaged in three weeks is worth a light nudge — a short message about a new item or a slow-night offer, sent through the same thread they already order from. This is the same follow-up automation logic used across other industries, applied to a restaurant's own repeat-order pattern instead of a generic broadcast list.
Handling peak-hour volume
During a genuine rush, even a fast ordering flow can get overwhelmed if every confirmation needs a person to type a reply. Set an automatic acknowledgment ("Got your order — confirming within 5 minutes") so customers know the message landed even if staff can't confirm the specifics instantly, then have the kitchen or front-of-house team batch-confirm orders as they're able to. This keeps the chat responsive without requiring a dedicated person glued to WhatsApp during your busiest hour.
Loyalty without a separate app
You don't need a dedicated loyalty app to reward regulars — a simple rule like "every 10th order gets a free drink," tracked against the customer's order history in WaSMS, works the same way inside the same chat they already order through. Mention the reward automatically once it's earned rather than making a customer ask about it or keep their own count; that small touch is often what turns an occasional customer into someone who orders from you every week instead of rotating between three restaurants.
Handling refunds and order mistakes
Mistakes happen — a missing item, a wrong dish, a delivery that took too long. Keeping the complaint in the same WhatsApp thread the order was placed in means whoever handles it can see exactly what was ordered and when, without asking the customer to repeat details they already gave once. A quick, direct response — acknowledging the mistake and offering a fix, whether that's a partial refund or a replacement item on the next order — tends to matter more to how a customer feels about your restaurant than the original mistake ever did.