Module · Digital Menu

Digital Menu & QR Ordering for Restaurants

Built for how guests actually order. Static PDFs and laminated cards can't filter by allergen, build a custom dish, read in Italian, or update the moment a price changes.

Why it matters

Most menu problems aren't design problems — they're update problems. A dish sells out, a price changes, an ingredient gets swapped, and the printed menu is wrong until the next reprint. Guests with allergies are stuck asking a server to read every ingredient list aloud.

Every guest-facing surface — the code on the table, the counter screen, the board on the wall, a terrace, a room — reads from the same live source, so one edit updates all of them at once. And in a town where half your covers arrive off a coach, the same menu meets them in a language they read and a currency they recognise, with no second printed version to keep in step.

Digital menu on a laptop showing dish photography, prices in euros, category filters and a featured carousel
One menu, read from every table. Edit a price once and every surface has it. Screenshots are of a demo venue. Dish photography from Unsplash.

Menus in 40 languages, prices in 35 currencies

This is the part that decides whether a tourist orders confidently or points at a photo and hopes. Two independent things, both live on the same menu.

01

Pick up to five languages per venue

From a list of 40. Choose the ones your guests actually speak — the menu itself is written once, in your own language, and everything else is generated from it.

02

The guest's phone decides

Someone arriving with a German phone gets the German menu on first scan, without touching anything — but only if you offer German. They can switch at any time, and every language is listed by its own name, not translated into yours.

03

Localised, not translated word for word

Ćevapi stays Ćevapi, with a line underneath explaining what it is. A dish with a name worth keeping keeps it — because a literal translation of a proper name is how a house speciality turns into something nobody orders.

04

Edit a dish and the old translation stops instantly

Translations are tied to the exact text they were made from. Change a description and the stale version stops being served the same second — the guest sees your original wording rather than a translation of something you've since changed. It refreshes itself within minutes.

05

Your words beat the machine's

Not happy with how a dish reads in Italian? Write it yourself and yours is what's served, until you edit the source text.

06

Prices in the guest's currency

35 currencies, converted at live rates refreshed twice a day. The guest taps the currency chip and every price on the menu re-reads. They still pay in your currency — this is so they know what they're agreeing to before they order.

07

Right-to-left, properly

Arabic, Hebrew and Persian flip the entire layout — not just the text direction.

Guests are always told the translation is automatic and can tap through to the original. That's a deliberate choice: a menu that quietly pretends a machine wrote it in perfect Italian is worse than one that says what it is.

The guest menu on a phone in English, showing the venue open until 2am and dish photography
English
The same guest menu on a phone in German, with category names and opening hours translated
Deutsch
The same guest menu on a phone in French, with category names and opening hours translated
Français
The same guest menu on a phone in Arabic, with the entire layout mirrored right to left
العربية · RTL
Language picker on the guest menu, each language listed under its own name
Every language listed under its own name, never translated into yours.

Allergens that survive the translation

Every other translated string on the menu is generated. The safety-critical ones are not. All fourteen EU allergens, every dietary filter, the spice levels and the nutrition labels are written by hand in all 40 languages and ship with the product.

That distinction matters more than it sounds. A machine mistranslating a dish description costs you an order; a machine mistranslating "contains nuts" costs you something else entirely. So allergens don't go through the translator at all — the system sends a code and each language has its own reviewed word for it.

On the guest's side, excluding an allergen narrows the whole menu at once rather than making them read every description. Allergens are held per ingredient, so a dish inherits them from what's actually in it.

Menu filter panel with checkboxes for each of the fourteen EU allergens and dietary options
Excluding an allergen narrows the whole menu at once, rather than making a guest read every description.

The rest of the menu

01

Search and filters that hold up on a long list

Search by dish or by ingredient; filter by category, diet, spice level or how long something takes.

02

Step-by-step item builder

Required choices, optional sides and add-ons, with the price updating as the guest builds — the same builder staff use to configure combos.

03

QR that knows where it is

Each table, room or counter carries its own context, so an order routes correctly without anyone typing a table number. No app, no tablet, no new hardware.

04

Installable and readable offline

The menu installs to the home screen and recently viewed menus stay readable when the signal drops.

05

Sold out means sold out

Optionally, a dish whose ingredients have run out stops being orderable — so the apology happens in the kitchen rather than at the table.

Item detail on the guest menu with required choices, optional extras and a price that updates as the guest builds the dish
Required choices, optional extras, and a price that moves as the guest builds it. Screenshots are of a demo venue. Dish photography from Unsplash.

Common questions

Do guests pay on their phone?

Not yet. Orders go to the kitchen and onto one running bill for the table, settled with your staff as today. Card payment on the phone is planned, and this line will change when it is live.

Do I have to write the translations?

No. You write the menu once in your own language and the translations are generated for the languages you've switched on, then kept current as you edit. You can override any dish's wording if you want to.

How many languages can I offer at once?

Five per venue, from a catalogue of 40. It's a deliberate limit — five languages your guests actually speak beats forty nobody reads.

Is my admin dashboard translated too?

No. Translation covers the guest-facing menu. The admin and staff screens are English only.

What happens if a translation is missing?

The guest reads your original text. Nothing ever comes out blank, and a field that hasn't been translated simply shows as written — a translated dish name can sit above an untranslated description rather than the whole item falling back.

Does the price convert automatically to the guest's currency?

The language does; the currency doesn't. Prices start in your currency and the guest picks another from the chip if they want one. Rates refresh twice a day.

Do guests pay in their own currency?

No — conversion is for reading. The bill is in your currency, which is also the currency every report is priced in.

Do I need new hardware for QR ordering?

No. Guests scan with their own phone camera.

Can I update prices instantly?

Yes. Edit once and every surface reflects it immediately — including, within a few minutes, the translated versions.

See it in action

See the Digital Menu running on your own items.

Book a demo