All work
Restaurant ordering

W8ER

A QR ordering experience that helps guests decide what to order, then carries that choice through payment and pickup without turning staff into a FAQ desk.

React, TypeScript, Vite, Express, Gemini, Square, Firebase

Scan the table QR and land on a short welcome screen: presets, full menu, or ask Aria.
01

The ordering friction

A digital menu is usually a catalog. It lists categories and prices, but it does little when a guest is unsure what to order.

Those questions still land on staff: what is light, what pairs with coffee, what is vegan, what is ready quickly. W8ER sits between the QR menu and that human FAQ layer.

Guests get answers and can place an order without waiting for someone free. The floor spends less time repeating the same guidance, while the kitchen still receives an ordinary paid ticket.

02

Two ways in

Some guests want a recommendation. Others already know what they want. W8ER supports both, and moving between chat and the menu does not restart the order.

Ask Aria

Aria answers from the cafe's actual menu and current order. When something fits, it shows up as an item the guest can add — not a dead-end suggestion.

Ask Aria about the menu the way you would ask a host at the table.

Browse the menu

Categories and item details stay available for guests who prefer to scan first, or who already know the dish and just need to add it.

Browse categories and add items the usual way when the guest already knows what they want.
03

From preference to paid order

Whether the guest starts with Aria or the menu, the rest of the path is the same cafe order: customize, pay, then watch progress until pickup.

A short welcome path into lunch, desserts, or the full menu.
A recommendation that can become part of the order.
Selections land in the cart with the modifiers the guest chose.
04

Order path

One phone surface from the first tap to ready for pickup.

  1. 01

    Ask or browse

    The guest gets a recommendation or picks from the menu. Either path can add the same kind of item.

  2. 02

    Customize

    Size, milk, extras — whatever the dish allows — before it lands in the cart.

  3. 03

    Pay

    Checkout happens on the phone. The cafe still receives a normal paid order.

  4. 04

    Follow status

    Preparing and ready update on the same screen, so pickup does not require another trip to ask.

05

For the house

The menu they already run

Prices, modifiers, and locations stay tied to the cafe's existing Square catalog, so the guest app does not become a second storefront to maintain.

Kitchen stays in the loop

Once an order is paid, staff can mark it preparing or ready. Guests see that progress without a separate tracking app or another trip to the counter.

Table QR and look

Each location gets a printable QR. Colors, welcome line, and first-screen groupings keep the guest experience aligned with the cafe.

What to highlight today

Welcome presets can spotlight lunch, desserts, or chef picks so the first screen sells what the house wants to move — not only a flat category list.