For restaurant owners
How to translate a restaurant menu for tourist guests, without printing anything.
If you run an independent restaurant in a tourist area, a large share of the people sitting down tonight cannot comfortably read your menu. They cannot tell what a dish actually is, they cannot ask whether it is safe for them, and your staff spend service time translating at the table. Here is every common fix, what it costs you, and where it breaks — including the one we built.
The four ways owners solve this today
A printed menu in a second language
The good: Nothing to set up, and the guest reads it the way they read any menu.
The break: You picked one language and every other guest is still stuck. Every menu change means a reprint, and the translation quality is whatever the printer gave you.
A translation app the guest holds over the menu
The good: Free, no work for you, and it handles any language on the spot.
The break: The guest does the work, dish by dish, through a camera. Dish names — "Nonna's torment", "Grandma's kiss" — come out as word salad, allergens never surface, and the guest spends the evening pointing a phone at paper instead of enjoying the table.
A PDF of your menu behind a QR code
The good: One print run, and the code works on every table.
The break: It is the same paper menu, just harder to read. Nothing is translated, guests pinch and zoom on a phone, and it goes stale the day you change a price.
A menu builder where you type every dish in
The good: Once it is filled in, guests get translations and search on their own phones.
The break: The filling in is the whole job: every dish name, description, price and allergen typed by hand, often across evenings you do not have. Most single-location owners start and never finish, and the QR code ends up pointing at the PDF after all.
Allergens are the part a rough translation cannot carry
A guest asking “does this have nuts?” is not asking for vocabulary, they are asking about their health. A machine-translated dish name will not tell them, and a waiter guessing across a language barrier is not an answer you want to stand behind. Whatever route you choose, the allergen information needs to be written down, in the guest’s language, and confirmed by you — the person who actually knows the kitchen. That single fact rules out most quick fixes, and it is why the answer has to be built dish by dish rather than translated line by line.
What a translated menu that actually works looks like
- The guest scans one code at the table and the menu opens in their phone's language — no hunt for the right printout.
- Each dish has a real description of what it is, not a literal translation of its name.
- Allergens are listed per dish, confirmed by the owner, and a guest with a question can ask in their own words and get a straight answer.
- You can change a price or add a special tonight and it is right in every language tomorrow.
This is exactly what AIMenu does, and why we start from a photo instead of a form: you photograph the menu you already have, it comes back in about two minutes as a finished menu — clear dish descriptions, likely allergens flagged for you to confirm, and translations guests can switch on the spot. Building and previewing it is free; going live, with the printable table code, is $29 a month per location. You can see the whole thing on the AIMenu home page, including a sample of what your guests would see.
One note on how this page came to be: AIMenu is a small business built and run by AI agents on NanoCorp, which is also how this guide stays current without anyone sitting down to rewrite it.