Multilingual Restaurant Menu
A tourist sits down, opens your menu, and understands about a third of it.
They will not ask for help. Most people do not. They will order the one dish they recognise, or point at whatever the next table has, and you will have sold a margherita to somebody who came in wanting the thing you are actually known for.
A multilingual restaurant menu fixes a problem that never shows up in your figures, because the order still happened. It was just the wrong order, at the wrong price, and nobody complained.
The Cost You Cannot See
Language barriers do not produce complaints. They produce quiet, cheap orders.
- The guest orders the safest item rather than the best one
- They skip starters and desserts entirely, because reading three sections is too much work
- They do not order the wine, because the list is impenetrable
- They do not ask about the special, because asking requires a conversation
- They eat once and do not come back, and you never find out why
Every one of those is a smaller bill than it should have been, and none of them appears anywhere you would look.
In a city where a substantial share of covers are visitors, that adds up to a real number over a year. It is simply a number nobody has ever put on a report, because the alternative version of each evening was never recorded.
Why Printing More Versions Does Not Work
The obvious answer is to print an English menu and an Arabic menu, and maybe a Russian one if you are near the right hotel.
Then you have three print runs, three sets of proofs, and three documents that fall out of sync the first time a price changes. Most restaurants that try this end up with a current English menu and two increasingly historical translations.
There is also a physical limit. Nobody is keeping fifteen printed versions behind the host stand, and nobody is asking a guest which language they read before handing them a menu.
How Does One QR Code Serve Fifteen Languages?
The language lives on the menu page, not on the code.
A guest scans, and switches language themselves with a tap. Same code, same table, four people reading four different versions of the same menu at once.
You choose which languages each outlet offers, so a hotel restaurant on a tourist strip can run a long list while a neighbourhood place runs three. English plus fourteen others is the full range, fifteen selectable in total.
Nothing is printed twice, and a price change updates every language simultaneously because the price is not part of the translation.
That separation is the part worth understanding. Numbers, photographs and availability are shared across every language. Only the words differ, which means the maintenance burden of the fifteenth language is the same as the second.
Which Languages Should You Actually Offer?
Not all fifteen, and this is where restaurants tend to go wrong by being generous.
Offering a language you have not translated properly is worse than not offering it. A guest switches to their language, finds half the dish names still in English, and now knows exactly how much thought went into it.
Pick based on who actually sits down:
- Look at your own booking or delivery data before guessing
- Ask your floor staff which languages they are asked to explain the menu in
- Consider the hotels and attractions within walking distance
- Start with three or four done properly, and add more when you can do them well
What Has to Be Translated?
More than most restaurants expect, and the gaps are what make a menu feel unfinished.
- Dish names. Obviously, and this is usually the only part that gets done.
- The part that actually sells the dish, and the part most often skipped.
- Category headings. A menu with Arabic dishes under English section titles reads as half-built.
- Option names. “Choose your sauce” is not much use in English to someone reading Japanese.
- Allergen and calorie labels. These matter more than the rest and get forgotten more often.
- The cart and checkout. A menu that reads beautifully and hands the guest an English checkout has failed at the last step.
Do Not Let a Machine Write It
Machine translation is fine for understanding a menu. It is not fine for writing one.
A dish description is twelve words that have to be accurate, appetising and specific. Run that through a translator and you get something accurate and flat, which on a menu is a failure. “Slow-cooked lamb shoulder with pomegranate” becomes a list of ingredients.
Write the English first and tighten it until you are happy, then translate. Translating a weak description gives you a weak description in two languages.
If nobody in the business writes menu copy, it is worth paying someone who does. Proper content writing costs less than one print run and lasts a great deal longer.
Right-to-Left Is Not a Font Change
Arabic deserves its own note, because it is the language most often claimed and least often done properly.
True right-to-left means the page direction flips, including where the item name sits relative to its price and photograph. If prices end up on the wrong side, an Arabic reader notices before they have read a single dish.
Check it yourself on a phone rather than a laptop, and check the checkout as well as the menu. The narrow layout is where these implementations break.
Allergens in the Language Being Read
This is where multilingual menus stop being about revenue.
Calories, allergens and item details live on the dish itself, so they follow whichever language the guest selected rather than sitting in an English footnote.
A guest with a nut allergy reading a menu they only partly understand is a risk nobody should be carrying. Get the allergen vocabulary checked by someone who knows it, rather than translating those particular words yourself.
Tourist Areas Get the Most From This
Some rooms benefit far more than others, and it is worth knowing which side you are on.
- Hotel restaurants, where the occupancy list changes every week
- Anything near an airport, a beach or a major attraction
- Old town and heritage districts, where visitors arrive specifically to eat something unfamiliar
- Malls with heavy tourist footfall
The unfamiliar-food point is the interesting one. A guest who cannot read a description of a dish they have never heard of will not order it, and that dish is usually the reason they came.
The QR layer runs on QRHUB, which builds QR solutions for hospitality across the region.
One Catalogue Behind Every Language
The structural point that makes this maintainable.
Each dish is one record carrying all its translations, its photos, its allergens and its options. Assign it to whichever outlets serve it, and every language updates together when you correct something.
Prices remain per outlet. You can set a different price for the same dish at each branch without duplicating the item or re-entering a single translation.
Translations drift faster than prices do, precisely because nobody is checking them. Keeping them in one place is what stops that.
Does a Multilingual Menu Help You Get Found?
A menu page is a web page, and web pages get indexed.
People search for food in their own language, and a menu that exists only in English is invisible to every one of those searches. That is a smaller effect than the in-room benefit, but it costs nothing extra once the translations exist.
The bigger discovery effect is simpler. A guest who had a good meal and could read the menu is a guest who can tell someone else exactly what they ate, by name, which is how a dish becomes the thing your restaurant is known for.
What About Staff Who Do Not Share a Language With the Guest?
This is the half of the problem nobody markets at.
A multilingual menu does not only help the guest. It helps the waiter who is being asked, in a language they do not speak, whether the lamb is spicy. Both parties can look at the same item on a phone, in two different languages, and point at it.
The order arriving as a structured message helps here too. Nobody is transcribing a dish name they cannot pronounce or spell, and nothing is lost between the table and the kitchen.
Floor staff tend to notice this before management does. Ask them after a week.
What Does It Cost?
Languages are included rather than sold as an add-on, which is worth saying because they often are not.
- $29 per month, or $290 for the year, per outlet
- All fifteen languages included, with no per-language charge
- 0% commission on every order, permanently
- Every feature on every plan. No premium tier.
- 30 days free, no credit card
You can check the current plan and what it includes before deciding.
Prices are current at the time of writing and are billed in USD.
How Do You Set It Up?
- Build your menu in English and get the descriptions right first
- Choose three or four languages you can genuinely do well
- Have the names, descriptions and option labels written rather than machine-translated
- Select which languages this outlet offers
- Open the live menu on a phone in each language and read the whole thing, checkout included
Step five finds every problem. Skipping it is why so many multilingual menus are only multilingual on the first screen.
30-day free trial. No credit card. 0% commission.
The Guest Will Not Tell You
Nobody sends back a menu they could not read. They order something safe, pay a smaller bill, and leave.
A multilingual restaurant menu is one of the few improvements where the return is invisible in the complaint book and obvious in the average order value.
Let people read what you are actually good at.