What a guest sees on the first scan
In a city of visitors, the first scan decides whether a guest explores the menu or orders the one dish they recognise. Screens from the demo restaurant.
The first scan in a city of visitors
The menu opens in the phone browser at the right table, with a confirmation such as Table 12 · Terrace. One tap switches the language and another the currency, and the choice is remembered for next time.
Allergens and dietary filters on every dish
Each dish carries its dietary tags and allergens, from nine allergen options, and guests can filter by dietary need, spice level and allergen. Allergen information is a guide and a prompt for your team, not a guarantee.
From QR menu to ordering in one step
The same menu takes the order and the payment. The ticket goes to your kitchen display, and the guest follows its status from Received to Served.
What would a small uplift be worth to you?
Move the sliders to your own numbers. The point is not our figures — it is how little the uplift has to be before the subscription pays for itself.
5% is a deliberately conservative default. Your own number is the one that matters, and you can change it.
An estimate based on the figures you entered, not a forecast or a guarantee. Actual results depend on your menu, your guests and how the platform is set up.
Frequently asked questions
You can switch on 27 menu languages. Arabic is laid out right to left, and Auto-translate fills each language for you to review.
Yes. Guests can switch the display currency, from the 11 you can accept, while you invoice in AED.
Yes, and by dietary need and spice level. Staff should still confirm allergens with the guest.
No. The menu opens in the phone browser from the table QR code.