Café and restaurant automation

Menu and ordering, on the guest's phone

A café keeps one device per table: a printed menu, a pager, a card reader. Each one is both a cost and one more thing that breaks.

All of it is replaced by something the guest already has in their pocket: a QR code on the table, menu and ordering on their own phone.

What isn't confirmed yet

We don't claim an integration with a specific till or payment gateway until it is confirmed. We name the provider only once it is certain.

Scope of work

What this service includes

Each item is an independent job, chosen and priced separately — not a bundle you have to buy whole.

Menu and ordering by QR

The guest scans the code on the table and orders from their own phone. Changing the menu is editing one page.

Ready alert

When the order is ready, the guest's phone tells them — instead of a pager that has to be charged and handed out.

Payment in the same flow

Payment is part of the ordering flow, not a separate stop at the till.

Staff view

One status screen: new, being prepared, delivered. Everyone sees the same picture.

Fewer devices on the table

Menu, pager and payment collapse onto the guest's phone, so you buy fewer devices.

Recorded orders

Every order is stored with its time and items, so “what did we sell today” is a report.

Outcomes

What changes once it is running

Instead of percentages we've written the mechanism. What is guaranteed is that the work and the cost stay clear.

Fewer devices

Every device removed from the table is one purchase and one possible failure less.

An up-to-date menu

When a price changes it changes on everyone's menu instantly; no stale printed menu survives.

Shorter queue at the till

When ordering and payment happen at the table, the till stops being the bottleneck.

Fewer mistakes in orders

The guest places the order themselves, so nothing is lost between the table and the kitchen.

From inside the panel

How the service gets going

Each stage produces something you can review before the next one begins, and nothing runs without your approval.

  1. 01

    Scan the table code

    The guest opens the QR with their phone camera. Nothing to install, no device to hand out.

  2. 02

    Choose from the menu

    The menu opens with current prices and availability, and the guest completes their order.

  3. 03

    Payment

    Payment happens in the same flow and the order goes through to the kitchen.

  4. 04

    Preparation

    The order appears on the staff view and its status updates as the work progresses.

  5. 05

    Ready alert

    Instead of a shout or a pager, the guest's phone tells them the order is ready.

Requirements

What the venue needs to provide

The list is deliberately short: the more prerequisites there are, the likelier the project is abandoned halfway.

Reliable internet in the room

Guests can use their own connection, but a dead spot ruins the experience.

One screen for staff

A tablet or monitor in the kitchen or by the till is enough.

A current menu and table numbers

The item list with prices, and the number of each table — because each QR is tied to its own table.

One person responsible

Someone who keeps the menu current; the only ongoing job that stays on your side.

Cost

Set up once, pay for what you use

The cost comes out of the wallet and you see the estimate before anything runs.

Initial setup

Building the menu, generating the table QR codes and preparing the staff view — once.

Ongoing use

Usage is deducted from the wallet and stays visible in the history.

Payment fees

The gateway fee is separate from this service and goes to the bank, not to us.

Technology

Standards and technologies

What stays constant is open standards — something any other developer could pick up and continue.

  • QR Code
  • PWA
  • Web Push
  • Responsive Web
  • Digital Menu
  • Realtime Order Board

Questions

The most common questions, answered directly

No. The QR opens in the phone's browser and the job is done there. Installing an app for a ten-minute order drives guests away.

The second route is always open: staff take the order, exactly as before. This system reduces devices, not people.

Until an integration with a specific system is confirmed, we don't claim it. Tell us your till and we'll answer honestly.

Online ordering stops and staff take orders as before. That is exactly why reliable internet is listed as a requirement.

For a place where the number of tables and orders makes doing it by hand expensive. For a two-table kiosk it is added complexity.

Nothing beyond what the order itself needs is collected, and the venue owns the data.

A question about Café and restaurant automation?

Start from inside the panel, or talk to a person first — whichever is easier.