WhatsApp ordering for restaurants, with the cart already written
Ramlyon lets a guest browse a real digital menu, choose variants and add-ons, build a cart and then open WhatsApp with a structured order message ready to send. The guest stays in tools already familiar to them: a browser for choosing food and WhatsApp for the conversation with the restaurant.
How the WhatsApp ordering flow actually works
The restaurant publishes a WhatsApp ordering number and chooses a message template. A guest opens the menu, selects dishes, quantities, variants and add-ons, and provides the checkout details the restaurant has enabled. When the guest taps the WhatsApp order button, Ramlyon builds the message in the browser and opens the restaurant's wa.me conversation with that text filled in.
The restaurant controls which supported details appear in the message, including items, table number, customer name and total. A table-aware QR can bring the scanned table into the cart, while a normally shared menu link drops that table reference. The resulting message gives the restaurant one readable summary instead of a chain of separate messages about sizes, extras and quantities.
This path is deliberately a WhatsApp hand-off. It does not create an order in the Ramlyon database, and it does not include online diner payment. The restaurant receives the message and handles confirmation and payment in its normal WhatsApp workflow. That distinction keeps the Menu plan simple and matches what the product records.
Let guests configure a complete order before the chat
The public menu shows current categories, dish descriptions, photos and prices. Item details can include required or optional variant groups, single or multiple choices, minimum and maximum selections, and add-ons with their own price differences. The cart calculates the displayed total from those choices, and the WhatsApp message carries the configured summary.
The checkout always uses a phone number as the customer identity. The restaurant can decide whether a customer name is required and whether a notes field appears. It can also publish dine-in and takeaway choices that match its enabled setup. The menu has no diner account wall and needs no dedicated app.
Availability remains under restaurant control. Hidden items disappear; unavailable items remain visible but cannot be added. Working hours and timezone data let the menu present an honest live status. Busy mode can show a custom message, and the restaurant can pause ordering or turn the whole experience into browse-only mode. WhatsApp itself remains the place where the owner can triage a message that arrives outside normal service.
Keep your message and your brand under your control
The menu uses the restaurant's subdomain, logo, cover, colours and published contact details. Guests can search dishes, jump between categories and switch among the languages the restaurant enabled. Photos uploaded from a phone are compressed for the web, and a menu edit invalidates the cache immediately.
The message template belongs to the restaurant. This makes it possible to set a consistent opening line and include only the supported order sections useful to the team. Ramlyon does not pretend to be the WhatsApp inbox, send messages on the restaurant's behalf, or read the later conversation. It prepares the cart summary and redirects the guest to the correct chat.
WhatsApp ordering versus real web orders
WhatsApp ordering is part of the Menu plan and remains available with Operations. When an Operations restaurant enables real web ordering, the primary web channel creates a server-validated order that appears in the Ramlyon dashboard and kitchen display. The server rebuilds pricing from the live menu, and the guest receives a private status tracker. That is a different workflow from the WhatsApp redirect.
If neither channel is enabled, Ramlyon presents a browse-only menu with no cart, checkout or add buttons. Compare the Menu and Operations workflows on the pricing page before choosing which hand-off fits the restaurant.
A fast menu before the message
Ordinary menu browsing is served as static, cacheable HTML and sets no cookies. Anonymous visit measurement uses a restaurant-specific random identifier in browser storage, can be reset, and can be turned off from the menu privacy sheet. The WhatsApp path itself makes no order API call and creates no Ramlyon order record.
That means a guest can inspect the full food list without waiting for a staff member to reply “What would you like?”, and the staff member receives a clearer starting message when the guest is ready.
<!-- FAQ -->WhatsApp ordering questions
Does Ramlyon send the WhatsApp message automatically?
No. Ramlyon opens the restaurant chat with the order text prepared. The guest reviews and sends it from WhatsApp.
Does a WhatsApp order appear on the Ramlyon kitchen screen?
No. The WhatsApp route is a client-side hand-off and creates no database order. Real web orders that enter the dashboard and kitchen display are an Operations workflow.
Can the restaurant choose what the message contains?
Yes. The supported template and include controls cover the order items, table number, customer name and total.
Can guests pay online in this flow?
No online diner payment is built into the WhatsApp hand-off. The restaurant handles confirmation and payment through its own established process.
Turn menu choices into one useful message
Create your Ramlyon account to configure the menu and WhatsApp hand-off, or try the live menu before you start.