The Tourist Restaurant Playbook: Menus, Wi-Fi, and Payments for International Guests (2026)
A tourist decides where to eat in under a minute, on a street where twelve places want the same table filled. They aren't comparing your food to the place next door. They can't. They're comparing how easy you look.
Short answer: three things decide whether an international guest sits down, spends well, and leaves happy — a menu they can read, Wi-Fi that connects without a conversation, and a payment they understand before it happens. Publish one QR menu in two or three languages with clear allergens and photos. Put a Wi-Fi QR code on every table. Take contactless, never push currency conversion at the terminal, print your service charge on the menu, and split bills without sighing. That's the whole playbook. Everything below is the detail.
Tourists are the easiest guests to win and the easiest to lose. They have no loyalty to break, no history with you, and no way to judge you except by the friction they hit in the first five minutes. Remove the friction and they spend more than locals do — because they're on holiday, and holiday money spends differently.
The five moments where you win or lose a tourist
Every international guest passes through the same five moments. Most restaurants nail one or two and quietly leak covers at the rest.
| Moment | What the guest is thinking | What loses them |
|---|---|---|
| The street | "Can I even read this?" | A chalkboard in one language only |
| Sitting down | "How does this work here?" | No menu, no Wi-Fi, no eye contact |
| Ordering | "What is this and will I like it?" | No photos, no portion sizes, no allergens |
| Paying | "Wait — what's this extra charge?" | A surprise on the bill, cash-only, no split |
| After | "Was that worth it?" | Nobody asked them for a review |
Fix them in order. The street costs you the most covers, and the bill costs you the most goodwill.
Moment 1: the street
Your window is doing more selling than your Instagram.
A guest standing outside has already narrowed it to three places. What tips them your way isn't ambience — it's the feeling that eating here won't be embarrassing.
Put a QR code in the window at eye level. Not on the door, not below the sill. Eye level, big enough to scan from three feet back. This is the highest-value scan you get all day, because that person hasn't sat down anywhere yet. Our QR code print size guide has the actual measurements, and a clear "scan me" frame lifts scan rates more than most people expect.
Show prices outside. Every study of tourist behaviour says the same thing, and every traveller will tell you the same story: an unpriced menu in a tourist district reads as a trap. Hiding the price doesn't make people walk in — it makes them walk on.
Photograph the three hardest dishes. The traditional ones. The ones with names that don't translate. Those are exactly the dishes tourists skip and exactly the ones with your best margin. A phone by a window, on a clean plate, in daylight is enough — shooting menu photos cheaply covers the basics.
Be findable before they arrive. Roughly two-thirds of travellers pick restaurants on a map app before they leave the hotel. A Google Business Profile with correct hours, real photos, and a menu link is not marketing — it's opening the door. If you're not appearing, here's why your restaurant doesn't show up on maps.
Moment 2: the menu
This is the pillar everyone half-does. Dishes get translated, everything around them doesn't.
One QR code. Every language. Never one code per language.
The most common mistake in tourist restaurants is a table tent with five stickers on it — one per language. Guests scan the wrong one. Staff can't tell them apart. You update three of the five and forget the rest.
One code. The menu opens in the phone's language if you publish it, falls back to English if you don't, and a language switch sits at the top where a guest can actually see it. Written in each language's own script — English · Español · Deutsch · Français · العربية · Türkçe — never flags. There's no single flag for Arabic, English or Spanish, and picking one can genuinely annoy people.
The full version of this argument, including which languages to publish first and how to handle right-to-left Arabic properly, is in our guide to multilingual QR menus for tourists.
What a tourist needs that a local doesn't
Locals skim. Tourists read every word in a slightly nervous state — spending holiday money in a place they don't know, in front of people they'd rather not look silly in front of.
Give them these five things and the guessing stops:
- Portion size in grams and ounces. "8 oz" is meaningless to most of the world. "225 g (8 oz)" works everywhere.
- A spice marker. One chilli icon prevents a lot of untouched plates.
- Allergens attached to the dish, not in a footnote in size-8 text at the bottom.
- A one-line explanation under untranslatable dish names. Keep the original name — that's the thing they came for — and explain it underneath.
- Photos on the ten hardest dishes. A photo answers what nobody asks out loud: how big is it, is that a whole fish, is it soup or stew.
Allergens are not a detail for travellers
For a guest with an allergy in a country whose language they can't read, allergen info isn't information — it's the entire decision. Without it they eat somewhere safe and boring, tonight and tomorrow night.
And allergy guests rarely eat alone. They choose the venue for the whole table. Translate your allergens properly and you're not winning one cover, you're winning the booking for six.
Two rules that don't bend. Your local official language is the legally required one — extra languages are an addition, never a replacement. And never machine-translate allergen text, because negation flips: "contains no nuts" is one word away from the opposite in most languages, and nobody on your staff can proofread six of them. Our guides to declaring allergens on a digital menu and allergen menu requirements across Europe cover what each market expects.
Say what's included, on the menu
Tourists don't know your country's norms. They don't know if bread is free, if water costs $5, if service is added, or if the "market price" fish will be $30 or $90.
Put it in writing, in every language you publish:
- Whether prices include tax
- Whether a service charge is added, and the percentage
- Whether bread, olives, or the cover charge is billable
- What "market price" actually means on the day
This single change removes more bad reviews than anything else on this page. People don't resent a charge. They resent finding out about it after they've eaten.
Moment 3: Wi-Fi
Here's the failure nobody plans for: the QR code is perfect and the guest still can't open it.
Roaming inside the EU is free for EU travellers, and that's where the good news ends. Visitors from the US, UK, Gulf, and Asia land on expensive roaming or a prepaid eSIM they're rationing carefully. A guest with no data is staring at a QR code they physically cannot use.
Then comes the worst thirty seconds in hospitality: your waiter spelling Br@sserie2019! letter by letter across a language barrier, twice, to a table of four.
Fix it with a Wi-Fi QR code. The phone camera reads it, taps once, connects. No typing, no spelling, no shared password on a chalkboard that's been wrong since March. It's a normal QR code holding one line of text, it takes about three minutes to make, and it never expires — here's the exact setup, including the encryption settings people get wrong.
Four things that make guest Wi-Fi actually work for international visitors:
- Two codes on one card. Wi-Fi on top, menu below it. Wi-Fi comes first because without it the menu doesn't load.
- Name the network after the restaurant.
Casa-Marina-Guest, notTP-LINK_5G_EXT2. A guest shouldn't have to guess which of eleven networks is yours. - Skip the captive portal if you can. Login pages that demand an email address fail constantly on foreign phones and roaming SIMs, and they annoy everyone else. If local law requires guest registration, keep it to one screen.
- Test on a cheap Android on 3G. Tourists browse on older phones and weaker connections than you'd think. Your new iPhone on the office fibre proves nothing.
One more thing worth saying plainly: guests on your Wi-Fi upload photos of your food while they're still eating it. Free advertising you're paying for anyway with the router.
Moment 4: payments — where the goodwill dies
You can do everything right for ninety minutes and undo it in the last four. Payment is where tourists feel most exposed, because it's the one moment they can't fix by pointing.
Take cards. Take contactless. Take phones.
Cash-only in a tourist district in 2026 is a choice to serve fewer people. A traveller with $40 in local cash and a card in their pocket will order to the cash, not the appetite.
- Contactless is the default, not the fallback. Tap limits vary by country, and a foreign card sometimes asks for a PIN — that's normal, not a fault.
- Apple Pay and Google Pay matter more for tourists than locals. Many travellers leave the physical card in the hotel safe on purpose.
- Bring the terminal to the table. Walking off with someone's card reads as normal to you and alarming to a visitor from a country where it never happens.
- Drop card minimums, or state them at the door. A $15 minimum discovered at the till, after two coffees, is a one-star review with a photo of your sign.
Say no to dynamic currency conversion
This is the one that quietly costs you reviews, and most owners have never heard of it.
Dynamic currency conversion is when the card terminal offers to charge a foreign guest in their home currency instead of yours. The screen says something friendly like "Pay in USD?" It sounds helpful. It isn't. The exchange rate is set by the processor, and the markup usually runs several percent above the real rate — sometimes far more.
The guest doesn't notice at the terminal. They notice a week later on their statement, and they blame you, because your name is on the line. Experienced travellers know exactly what it is and are irritated it was offered at all.
What to do: ask your payment provider to switch DCC off, or tell staff to always choose the local currency. If you're in the EU, card networks are required to show the markup against the reference rate — read what your own terminal displays and decide whether you'd be comfortable if a guest read it too. Rules and defaults differ by provider and country, so confirm with yours directly.
Your job is to charge in your currency, at the honest amount, and let the guest's own bank do the conversion. Their bank is cheaper than your terminal, every time.
Cash, change, and small notes
Cash is still a third of tourist spend in plenty of markets, and it comes with its own friction.
- Keep small change. A visitor from an ATM with two $50 notes at 9pm is not being difficult.
- Never accept foreign currency at a made-up rate. It feels generous and reads as a rip-off the moment they check.
- Say the total clearly and show it. Point at the number on the bill. Spoken numbers are the hardest thing to catch in a second language, especially in a noisy room.
Split the bill without the sigh
Tourist tables split. Four friends from three countries, one paying by card, one in cash, one who only had the salad. It isn't awkwardness — it's how travel money works, and refusing costs you far more than the thirty seconds it saves.
Splitting by item, in partial quantities, across mixed payment methods should be a non-event at your till. If it isn't, that's a system problem, not a guest problem — handling split bills cleanly covers the mechanics.
Tipping: kill the guessing
Tipping is the single most stressful thirty seconds of a tourist's meal. They genuinely don't know your norm, and getting it wrong feels rude in both directions.
The norms are wildly different, and travellers know that much:
| Where they're from | What they expect | What they'll do abroad |
|---|---|---|
| United States | 18–20% standard | Often over-tips, or panics |
| Most of Europe | Round up, 5–10% for good service | Under-tips by US standards |
| Japan, South Korea | No tipping at all | May be confused it's expected |
| Gulf states | Service charge common, small tip on top | Looks for the charge on the bill |
| Australia, New Zealand | Rare, service included in wages | Rarely tips unless prompted |
Print your norm on the menu. One line: "Service is not included — tips are welcome but never expected." Or: "A 10% service charge is added to every bill." Both are fine. Silence is not.
Then make the number easy at the terminal. Preset percentages, an obvious skip option, and no guilt-tripping screens. Aggressive tip prompts are the fastest-growing complaint in travel forums, and a guest who feels squeezed at the last moment forgets the meal entirely. If you're curious how service-included markets do it, European restaurants pay staff without tipping explains the model — and our tipping etiquette guide covers the guest side.
Give them a receipt they can actually use
A bill is what's owed. A receipt is proof they paid. Tourists need the second one more than locals do — for expense claims, tax-free shopping schemes, insurance, or just to prove a charge on a card statement in a currency they don't recognise.
Offer it digitally. Emailing or messaging a receipt saves the guest a wet paper slip in a beach bag and saves you a printer roll. Business travellers in particular will remember you for it.
Moment 5: after they leave
Tourists write reviews at a much higher rate than locals. They're documenting a trip, and your dinner is part of the story.
Ask while they're still at the table, not in an email that arrives after they've flown home. A card on the bill tray with a QR code to your review page is the whole tactic. Getting more Google reviews covers the timing that works.
And reply to the bad ones. A traveller reading reviews from 2,000 miles away is not counting your stars — they're reading how you handle a complaint. Our guide to replying to bad restaurant reviews has templates that don't sound like a corporate apology.
What your staff needs when the menu speaks and they don't
The menu solves reading. It doesn't solve the table.
Four things that cost nothing:
- Ten words in your top three visitor languages. Welcome, thank you, enjoy, the bill. Guests remember the effort far longer than they remember the risotto.
- A pointing sheet behind the bar. The ten most-asked questions with answers, printed once. "Is this spicy?" "Does it contain pork?" "Can I pay by card?"
- Teach the language switch. Every waiter should be able to say "you can change the language here" and point. Most guests never find it alone.
- A phone at the pass for the hard conversations. A serious allergy, a complicated dietary request — a translation app is the right tool. Just never for the printed allergen text itself.
The seasonal trap
Tourist restaurants have two businesses: the peak and the rest of the year. Most run both with the same setup, and that's a mistake in both directions.
- In season, your bottleneck is table turn. Faster ordering means an extra turn — and a tourist table with an unreadable menu takes four to six extra minutes to order, every single time.
- Out of season, your bottleneck is locals. The menu, the languages, the tone all need to shift back — a venue that treats its own neighbours like tourists in November doesn't survive to see May. Filling empty tables on slow weekdays is a different playbook entirely.
Digital menus make this switchable. You can add Polish for four months and drop it, change your header text for the season, and hide the tasting menu in January without reprinting a thing.
Let the scan data pick your next move
This is the part almost nobody uses, and it's free.
Every scan of a QR menu can tell you which country the guest is browsing from. Not a tourism board average — your actual guests, this month.
- Top five countries answers "which language next?" outright. If 18% of your scans come from Poland and you have no Polish menu, that's your answer.
- Seasonality shows up clearly. Gulf visitors in July, Nordic visitors in February.
- What gets viewed but never ordered is usually a description problem, not a food problem.
- Devices and connection quality tell you whether your menu is too heavy for the phones actually loading it.
Five minutes a month removes all the guesswork.
The 30-minute tourist audit
Do this today, with a phone, as if you'd never been to your own restaurant.
- Stand outside. Can you read anything? Are prices visible? Is there a code in the window? (5 min)
- Scan your own menu on mobile data. How long does it load? Does the language switch work? (5 min)
- Turn mobile data off and try the Wi-Fi. Time it. Anything over 20 seconds is broken. (5 min)
- Read one dish description out loud as if you'd never heard of it. Does it tell you what arrives? (3 min)
- Check three dishes for allergens and portion size. Both present? (3 min)
- Look at yesterday's bill. Is every line explainable to someone who doesn't speak your language? (4 min)
- Ask a waiter to split a bill four ways, by item, mixed cash and card. Watch their face. (5 min)
Whatever made you wince is your first job tomorrow.
Seven mistakes that cost tourist covers
- One QR code per language. Fix: one code, one switcher.
- No prices in the window. Fix: show them. Hiding prices loses more guests than high prices do.
- The Wi-Fi password spelled out loud. Fix: a Wi-Fi QR code on every table.
- Dynamic currency conversion left switched on. Fix: charge in your own currency, always.
- Service charge revealed at the bill. Fix: print it on the menu, in every language.
- Allergens machine-translated. Fix: human translation, checked twice, or don't publish that language.
- Never asking for the review. Fix: a QR card on the bill tray, while they're still glowing.
A note on tools
For what it's worth: Tabres does most of this in one place and it's free — a QR menu in as many languages as you want with per-language dish names, allergens and header text, full right-to-left support for Arabic, Wi-Fi QR codes with your logo and colours, table-specific codes, bill splitting by item with mixed payment methods, and the scan-country analytics that tell you which language to add next. Our reasoning for it being free is public.
Use whatever tool suits you. The playbook above works on any of them — and if you're starting from a PDF menu, turning it into a digital QR menu is the fastest way in.
Frequently asked questions
How do I attract more tourists to my restaurant? Be readable and be findable. A QR menu in two or three languages, prices visible from the street, photos on the dishes that don't translate, and a complete Google Business Profile with correct hours. Most tourists choose on a map app before leaving the hotel, so the profile does the work of a front-of-house team you don't have.
How many languages should a tourist restaurant offer? Two or three to start: your local language, English, and your biggest visitor group. Add more when your scan data supports it. Two languages done properly beat six done carelessly — a bad translation reads as carelessness about everything, including the kitchen.
Should restaurants offer free Wi-Fi to tourists? Yes. Many international visitors are on expensive roaming or a rationed eSIM, and without data they can't open your QR menu at all. Give them a Wi-Fi QR code that connects in one tap, name the network after the restaurant, and avoid login portals unless local law requires them.
What is dynamic currency conversion and should I allow it? It's when your card terminal offers to charge a foreign guest in their home currency. The exchange rate is set by the processor and usually carries a markup of several percent. Guests spot it later on their statement and blame the restaurant. Charge in your local currency and let their bank convert — it's cheaper for them and cleaner for you.
Do tourists spend more than local customers? Usually yes, when they can read the menu. Holiday spending is looser and tables are larger. But a tourist who can't read the menu orders the cheapest thing they recognise, which is why an unreadable menu costs far more than a translation does.
Should I add a service charge for tourists? You can, but never apply a different rate to foreign guests — that's the fastest route to a viral review. Whatever you charge, print it on the menu in every language you publish, and show it as its own line on the bill.
What payment methods should a tourist restaurant accept? Cards and contactless at minimum, including Apple Pay and Google Pay. Keep cash and small change too. Bring the terminal to the table, drop card minimums, and be able to split a bill by item across mixed payment methods without fuss.
How do I handle allergies when we don't share a language? Put allergens on every dish in every published language, translated by a human. Keep a printed allergen chart behind the pass. For the difficult conversations, a translation app on a staff phone is fine — but never rely on machine translation for the printed allergen text, because it can flip negation.
Do I need to reprint my QR codes when I add a language? No. A QR code points at your menu, not at a file, so anything you change behind it updates instantly. Add a language, change a price, hide a dish — the printed code stays the same.
How do I know which language to add next? Look at which countries scanned your menu last month. A digital menu can show you country, device, and traffic source for every visit. Your top five countries answer the question with your real guests instead of a tourism average.
Here's the honest summary. Tourists aren't difficult guests. They're guests who've been handed a menu they can't read, a Wi-Fi password they can't hear, and a bill they didn't expect — then judged for ordering the safe thing.
Take those three away and something changes. They browse. They ask fewer questions. They order the dish with the interesting description, they add a dessert, and they leave a review that brings you four more tables next week.
None of it needs a renovation. It needs a code in the window, a code on the table, and a bill with no surprises on it.