Online ordering and reservations that need no special software.
A restaurant gets a menu that takes orders, a kitchen screen, and a reservation book. No terminal to buy, nothing to install, no tablet on the counter. It runs in a browser, and it drops into the website they already have.
Built and hosted by AppWT in Metro Detroit. American English by default.
Two products, honestly separated
Restaurant technology splits into ordering platforms and reservation platforms. They solve different problems, and treating them as one product is how features go missing. AppWT Relay covers both, and keeps them distinct.
Ordering
Menus with choices and photos, QR ordering at the table, and a kitchen display that works tickets in the order they arrived.
Reservations
Bookable time slots with real capacity limits, table fitting the host can override, and one book for web and phone bookings.
How a restaurant gets going
Four steps, and we do the first one for them: we set up the menu, they share one link, orders arrive on the kitchen screen, and they keep the guest.
Questions restaurants ask
Does a restaurant need to buy hardware or install software?
No. It runs in a web browser. There is no terminal to buy, nothing to install, and no tablet on the counter. The guest orders from their own phone.
Can it work on the website a restaurant already has?
Yes. The menu drops into an existing website with a single script tag, and it also has its own web address that works on any phone. A printable sheet of table QR codes covers dine in.
Which order types does it handle?
Pickup, delivery, curbside, dine in by QR code at the table, and catering.
Are online ordering and reservations the same product?
No. They solve different problems, so AppWT Relay covers both and keeps them distinct. Ordering routes food to the kitchen. Reservations allocate seats, with bookable time slots, real capacity limits and a service view for the host.
Who sets up the menu?
We do. The restaurant sends a PDF or a photo of the menu, and we type in the categories, items, choices, prices and hours.
Who owns the guest information?
The restaurant. Every order and booking builds a guest record the restaurant owns, not a marketplace. We hold guest information on the restaurant's instructions, as the Privacy Policy explains.
Does it require AppWT CRM?
No. Either can be used on its own and neither requires the other. A restaurant that uses both can push a guest who orders into the CRM as a contact.
Where it sits next to the rest of AppWT
Some restaurants want ordering. Some want the customer relationship tools in AppWT CRM. Plenty want both, because they do different jobs: this platform runs the service, the CRM runs the follow up. A guest who orders here can be pushed into the CRM as a contact, so marketing works from the same names the kitchen served.
Either can be used on its own. Neither requires the other.
Talk to us
We set the whole thing up, including typing in the menu.