A guest who cannot read your menu does one of two things: orders the one dish they recognise, or leaves. In a tourist area that is not a small loss — it is the difference between a full table and a table that spends nothing.
Why translation pays for itself
Descriptions are where a menu sells. If a guest cannot read yours, every dish is reduced to a name and a price, and unfamiliar dishes never get ordered. Put the description in their language and the expensive plate becomes explicable.
- Unfamiliar dishes become orderable
- Fewer questions for your floor staff
- Guests spend longer on the menu, which raises the basket
Automatic fallback: no empty spaces
You will rarely have every item translated into every language. When a translation is missing, the menu falls back to your default language rather than showing a blank — so a half-finished translation never breaks the page.
Ordering without a shared language
Reading is only half the problem. The guest still has to communicate the order. The 'Show to server' card puts the basket on screen in both languages at once: theirs and yours. They hold up the phone, your server reads it, and nobody mimes anything.
Getting there without a translator
Translating a large menu by hand takes a week nobody has. The AI Assistant proposes translations in bulk and you approve them — so the work becomes review rather than authorship.
- Bulk proposals across the whole menu
- Nothing publishes without your approval
- Right-to-left languages such as Arabic are laid out properly, not mirrored
Which languages to add
Start with where your guests actually come from, not where you wish they came from. Two well-finished languages beat eight half-finished ones.