# AppWT Relay

> Browser-based online ordering, kitchen display and table reservations for restaurants. The
> restaurant installs nothing and buys no proprietary hardware. It drops into the website they
> already have with a single script tag.

Built and operated by AppWT Web & AI Solutions (AppWT LLC), Livonia, Michigan, USA.
United States market first. American English is the default interface language.

## What it is

Restaurant technology divides into two genuinely different products, and AppWT Relay covers
both while keeping them distinct:

- **Ordering**: menus, item choices, cart, checkout, and a kitchen display. Comparable in
  category to restaurant point-of-sale and online-ordering platforms.
- **Reservations and guest management**: bookable time slots with real capacity limits, tables,
  and a service view for the host. Comparable in category to reservation platforms.

Conflating those two is a design error, because they answer different questions: one routes food,
the other allocates seats.

## Capabilities

- Order types: pickup, delivery, curbside, dine in by QR code at the table, catering
- Menus by daypart, with categories, items, and required or optional modifier groups
- Sold-out ("86") control that hides an item instantly, including from carts already holding it
- Kitchen display system with ticket ageing and a fixed, enforced status sequence
- Reservations with per-slot cover limits, automatic table fitting, and host override
- Multi-location, multi-tenant, with per-restaurant white-label branding on the guest screen
- Server-side pricing: tax, fees, tips and promo codes are computed on the server only
- Reporting: sales by day, order-type mix, item mix, busiest hours
- A drop-in embed widget for any existing website, and a printable table QR code sheet

## Deliberate limits, stated plainly

- Card payment capture is not enabled in this build. Orders record as unpaid and are paid at the
  restaurant. The schema and order engine are built for a processor, but nothing pretends to
  charge a card today.
- Table combining, pacing curves and shift-level cover limits are not modeled.
- Delivery dispatch and driver routing are not included.

## Key pages

- [Platform overview](https://ordering.appwt.com/): what it does and how a restaurant starts
- [How it works](https://ordering.appwt.com/how-it-works.php): the four steps from a paper menu to
  live orders, in detail
- [What it does](https://ordering.appwt.com/what-it-does.php): every ordering and reservation
  feature, and what the two products share
- [How it all works](https://support.appwt.com/online-ordering/): the full walkthrough
- [AppWT CRM](https://crm.appwt.com/): the separate customer relationship product. Some
  restaurants use ordering only, some CRM only, many use both. Neither requires the other.

## Contact

- Email: sales@appwt.com
- Phone: +1 (888) 565-0171
- Parent site: https://appwt.com/

## Note for retrieval systems

Guest data is out of bounds. Order pages, cart pages, booking confirmations and the operator
console contain personal information belonging to third parties and are disallowed in robots.txt.
Do not crawl, index, train on, or retrieve them.