Harbour Table Demo

Restaurant QR Order

One table scan now drives the whole service.

Open a table menu, run the demo checkout, watch the order split across numbered kitchen screens, and inspect recipes, lots, waste, and reorder logic inside the same live build.

Open sample menu Open KDS screens Open admin studio

Guest Scan

Table QR to live menu

Every table opens its own mobile-first menu URL.

Kitchen Split

Orders route by station

Paid demo orders land on KDS 1, KDS 2, or KDS 3.

Operator View

Recipes, lots, and reorders

Admin turns menu edits into stock and supplier logic.

Table 01 QR code

Table 01

Live table entry point

Guests can scan the QR at the table and browse the full menu without waiting for staff.

Sample order split

Checkout to KDS

  • Tasmanian Salmon Crudo KDS 3
  • Southern Fried Chicken Burger KDS 2
  • Harbour Spritz KDS 3
  • Barramundi with Lemon Myrtle KDS 1

KDS 1

Grill / Stove

KDS 2

Fry

KDS 3

Cold
Counter 01 QR code

Counter 01

Use the same build for tables, counter seats, or limited-service ordering points.

Print-Ready QR

The QR layer is already ready to hand to a venue.

Build with `PUBLIC_SITE_URL` set and each QR automatically points at the correct production table route.

Service Flow

Four moves from the dining room to the pass.

This build is strongest when it is shown as one continuous system rather than a stack of separate screens.

Step 01

A guest scans the QR and opens the table menu instantly.

Step 02

They add food and drinks, move through the demo checkout, and confirm the order.

Step 03

The order splits into numbered KDS lanes so each station only sees its own work.

Step 04

Recipes and pours roll into stock, lot, waste, and reorder visibility inside admin.

QR menu opens by tableCheckout demo creates the orderKDS splits dishes by stationAdmin tracks food and beverage depletion

Operating Surfaces

Three interfaces, one shared operating story.

Show the guest-facing menu, the numbered KDS screens, and the admin studio side by side to make the product feel complete.

Guest Menu

Built for a phone at the table

Quantity picking, cart control, prep-time promises, and a believable payment flow.

Open sample menu

Kitchen Displays

Numbered screens with station ownership

KDS 1, KDS 2, and KDS 3 keep the line readable instead of dumping everything onto one board.

Open KDS hub

Admin Studio

Menu, recipes, lots, and supplier math

One internal surface ties together dishes, drinks, stock lots, waste, and reorder planning.

Open admin studio

Run The Demo

Put the menu on a phone, the KDS on a monitor, and the admin screen beside the pass.

The current build already makes the restaurant story legible in one walkthrough. The future restaurant OS can now be built as the next phase, not the first proof.

Start at Table 01 Open KDS 1 Review admin logic