How a restaurant gets going

Four steps take a restaurant from a paper menu to live orders. Nothing is installed at the restaurant and there is no terminal to buy. Every screen below runs in a web browser on an ordinary phone, tablet or computer.

Step 1
We set up the menu
Categories, items, choices, prices and hours. They send a PDF or a photo of the menu and we do the typing.
Step 2
They get a link
One web address that works on any phone. It goes on their site, their posts, and a QR code on the table.
Step 3
Orders arrive
On the kitchen screen, in order, with the age of each ticket. One button moves it along.
Step 4
They keep the guest
Every order and booking builds a guest record they own, not a marketplace.

Step 1: the menu is set up for them

The restaurant sends the menu they already have, as a PDF or a photo, and we type it in. A menu can be split by daypart, with categories, items and photos. Each item can carry required and optional choices, and a choice can change the price, so a large size or an added topping is charged correctly without anyone doing the math at the counter.

Step 2: one link goes everywhere

The restaurant gets one web address for its menu, and it works on any phone. The same menu drops into the website they already have with a single script tag, so guests order without leaving the restaurant's own site. For dine in, a printable sheet of table QR codes sends each guest to the menu from their seat.

Guests can order for pickup, delivery, curbside, dine in at the table, or catering. Tax, fees, tips and promo codes are computed on the server, never in the guest's browser.

Step 3: orders reach the kitchen screen

Each order lands on the kitchen display in the order it came in, with the age of every ticket showing. Tickets move through a fixed sequence of statuses, one button at a time, so nothing skips a step. When the kitchen marks an item sold out, it disappears from the menu at once, including from carts that already hold it.

Reservations run in the same place. The host works from a service view for the day, and each booking moves from requested to confirmed, seated, completed or no show. Staff enter phone bookings in the same book, so there is one list of who is coming.

Step 4: the restaurant keeps the guest

Every order and every booking builds a guest record that belongs to the restaurant, not to a marketplace. A guest who orders can be pushed into AppWT CRM as a contact, so follow up works from the same names the kitchen served. Either product can be used on its own, and neither requires the other.

Guest information is held on the restaurant's instructions. The Privacy Policy explains who is responsible for what.

See it, then talk to us

We set the whole thing up, including typing in the menu.

See a live restaurant menu What it does Call (888) 565-0171