What AppWT Relay does
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: one routes food, the other allocates seats.
Ordering
- Menus by daypart, with categories and photos
- Required and optional choices, with price changes
- Pickup, delivery, curbside, and dine in by QR code
- Sold-out items hidden the second the kitchen says so
- A kitchen display that bumps tickets in order
- Tax, fees, tips and promo codes computed on the server
Reservations
- Bookable time slots with real capacity limits
- Tables, areas and party-size fitting
- Automatic table assignment, overridable by the host
- Requested, confirmed, seated, completed, no show
- A service view for the host, by the day
- Phone bookings entered by staff in the same book
Across both products
- Every order type a restaurant runs: pickup, delivery, curbside, dine in by QR code at the table, and catering.
- More than one location: one account can run several locations, and each restaurant's guest screen carries that restaurant's own brand color, not ours.
- Sold out means sold out: an item marked unavailable is hidden at once, including from carts that already hold it.
- Prices the guest cannot change: tax, fees, tips and promo codes are computed on the server only.
- Reports the owner can read: sales by day, the mix of order types, the mix of items, and the busiest hours.
- It fits the website they already have: a drop-in widget adds the menu to an existing site, and a printable sheet of table QR codes covers dine in.
Nothing to install
There is no terminal to buy and no tablet to mount on the counter. The menu, the kitchen display and the reservation book all run in a web browser, and the guest orders from their own phone. The four setup steps show how a restaurant goes from a paper menu to live orders.
Guest information stays private
Order pages, cart pages, booking confirmations and the operator console hold personal information that belongs to the restaurant's guests. This site's robots.txt asks search engines and answer engines to stay out of them, and the operator console requires a sign in. The Privacy Policy sets out who holds what.