Translated menu or a chat in the guest's language? The options compared

A translated menu helps guests read your dishes; a chat in the guest’s own language helps them ask about them. Printed translations and translated QR menus are cheap and fast to scan, but they go out of date with every change and can’t answer “is this spicy?” or “what comes with it?”. A chat answers those questions from your menu in the guest’s words, but it needs a phone and a connection, and allergy questions still end with your staff. Most restaurants get the best result from a printed menu, photos, and one of the two.

This guide compares five approaches on cost, upkeep and where each one breaks, then works through one month of menu changes at Casa Olivo to show the upkeep in numbers.

Who needs this?

Short answer: any restaurant where some guests read the menu in their second or third language, and that’s more of them than you’d guess.

UN Tourism estimates 1.52 billion international tourist arrivals in 2025, “almost 60 million more than in 2024” (UN Tourism, 20 Jan 2026). Locals count too. In the US, 22% of people aged 5 and older spoke a language other than English at home, and about 61% of them spoke Spanish (US Census Bureau, 2025). Of the people who spoke another language at home in 2024, 60.9% said they speak English “very well” (USAFacts, from Census data, 2026). The other four in ten are reading your menu more slowly and less surely than you think.

What are the options?

Short answer: five, and they solve different problems. Translations help guests read. Staff and chat help guests ask.

None of these is “best”. A guest who wants to browse quietly is better served by a translated menu than by a chat. A guest with three questions about one dish is better served by a person or a chat than by any translation.

What do the tools cost?

Short answer: menu translation tools are cheaper than chat tools, and both cost less than a reprint run in several languages if your menu changes often.

These are vendors’ own published figures, as published on 15 Oct 2026:

If your main need is a menu guests can read in many languages, MENU TIGER or Menutech will do that for less than we charge. WaiterPilot makes sense when the problem is the questions, not the reading.

Where does each approach break?

Short answer: at the follow-up question, at the menu change, and at the allergy. Here is each approach against five situations a server sees every week.

Two lines in that table matter most.

The note. With WaiterPilot, a special request such as “no onions” goes on the ticket as the request was taken, not translated. So a note can reach your kitchen in Spanish or Japanese. Decide before service who reads those: usually the server who confirms the table’s first order.

The allergy. No translation and no chat should be the last word. WaiterPilot gives what your menu says and asks the guest to confirm with a member of staff; your staff always have the final word. Our allergies and dietary questions page covers the details.

A worked example: one month of menu changes at Casa Olivo

Casa Olivo is a fictional restaurant (an example, not a customer). The numbers below are assumptions chosen to show the arithmetic, not measurements.

Casa Olivo has 48 dishes on an English menu. Its servers hear Spanish, French and Japanese most weeks. In a normal month:

• 4 menu changes: one new special, one price change, two seasonal swaps.
• 6 evenings when a dish sells out mid-service.

Here is the upkeep for that month under three set-ups.

The arithmetic is simple, and it scales badly for paper: each extra printed language adds one more translation per change. With a chat that answers from your menu, a change is made once, in your menu’s language, and the next answer uses it.

The honest catch sits in the second row. With a chat, nobody checks each reply in Japanese before the guest reads it. That is why WaiterPilot answers only from your menu, tells the guest to ask a staff member when the menu doesn’t say, and keeps your staff in charge of allergies. It’s also why we name only the languages we’ve tested: English, Arabic (several dialects) and Spanish. In our 15 Oct 2026 test, a Spanish question was answered in Spanish, with dish names kept as written on the menu.

What doesn’t a multilingual chat fix?

Short answer: anything a guest needs to read without asking, and the parts of the screen that aren’t the chat.

Be exact about the scope before you buy:

So a Japanese guest sees English buttons and English dish names, and asks in Japanese what they are. If that guest wanted to scroll a fully Japanese menu, a translation tool would serve them better. In the chat, a dish name opens the dish photo, which covers part of the “what is it?” job that photos do on paper.

For Arabic, you can see how much of your menu an Arabic-speaking guest reads in Arabic: the owner’s menu editor shows Arabic coverage for sections, dish names and descriptions, and anything without Arabic text shows in English.

How do you choose? A decision guide

Work down the list and stop at the first line that describes you.

1. Most of your non-local guests come in groups on set menus. Print the set menu in the group’s language. Nothing else is worth it.
2. Guests mainly need to read and browse, and your menu changes rarely. A printed second language for your top language, plus photos.
3. Guests come from many countries, and you want every word on screen in their language. A translated QR menu (MENU TIGER, Menutech or similar). Check the translations in any language someone on staff reads.
4. Guests ask a lot of questions, your servers spend the rush explaining dishes, and the menu changes often. A chat that answers in the guest’s language, such as WaiterPilot’s AI waiter, alongside your printed menu.
5. You need guests to pay on their phone, or orders to print in the kitchen. Neither translations nor WaiterPilot solves that; see AI waiter vs QR menu vs POS ordering.

Can you combine them?

Yes, and most restaurants should. A good combination for a tourist area:

• The printed menu stays, with your top guest language added or as an insert.
• Photos of the 10 to 15 dishes that sell most.
• Plain ingredient lists under each dish, because they translate better than poetic descriptions and they’re what a chat answers from.
• A chat or translated QR menu for everyone else.
• One rule for allergies in any language: a member of staff at the table.

Our 12-point checklist for serving tourists goes through each of these, and the tourist restaurants page shows how the chat handles a visitor’s question.

What to do next

Write down the five questions your servers answer most often, in the languages they’re asked in. Then try each approach against that list. To test WaiterPilot, try a sample order, or read our multilingual ordering test to see the same question answered in English, Spanish and Gulf Arabic. It costs $200 per location per month after 30 days free, with 0% commission, whatever languages your guests use.