Translated QR codes

On a multilingual site the QR generator produces one code per language for every destination selected, grouped and labelled by language.

What you get

Select the wine list, and the results arrive as one group per published language. Every code in a group opens the wine list in that language, and the downloaded file names include the language.

The same applies to the home page, to every menu archive and to every category archive.

The risk, stated plainly

QR codes are visually identical. Nothing about a printed code reveals which language it opens until someone scans it.

Almost every multilingual QR problem is a file mix-up between download and print, not a generation failure.

Handle the files properly

  1. Download from the correctly labelled group.
  2. Rename immediately: wine-list-en-2026-03.svg.
  3. Keep one folder per language.
  4. Send the printer one language at a time, naming it in the message.
  5. Scan every printed proof and confirm which language opens.

Decide the strategy before printing

One code, guests switch language. Print the main-language code and rely on the language selector on the menu. One item to print, one file to manage, and guests are one tap from their language.

Requires the Language toggler to be enabled for that archive.

One code per language. Table tents with a flag, or a card per language. Guests land in their language with no step, and you maintain more printed material.

The first is right for most restaurants. Use the second where the clientele is strongly bilingual and the placement makes the distinction obvious.

Category codes are language-specific by nature

A translated category is its own record with its own address. A category code in one language is not interchangeable with the same category in another, even though the section is "the same".

That makes category codes the most error-prone to print in several languages — one more reason to point printed codes at menu archives or the home page.

Adding a language after printing

Existing codes keep working; they point at the languages they were generated for.

To serve the new language, either rely on the language selector, or generate and print its codes. Nothing already printed becomes invalid.

Before printing

  • [ ] Every language you will print is published and complete.
  • [ ] Codes were downloaded from the correctly labelled group.
  • [ ] Files were renamed with their language.
  • [ ] Each printed proof was scanned and its language confirmed.
  • [ ] If relying on one code plus the selector, the language toggle is enabled and reaches every language.
  • [ ] Printed material makes the language obvious to a guest, if you printed several.
Paid access
Previous
Translation options
Next