Translation options

Deciding which languages to publish is a commercial decision with an operational cost. Every language is a second copy of every dish name and description that has to stay correct forever.

Which languages are available

The setup assistant offers a set of languages a restaurant is most often asked for:

Castellano · Catalán · Euskara · Galego · English · Deutsch · Français · Русский

The site's own language is set separately and is the source that everything else is translated from.

Enabling a language

During setup, in Step 1 — Your restaurant, the additional languages appear as checkboxes when a translation layer is installed. Tick a language to enable it, untick it to disable it.

The current site language is shown but cannot be changed there — it is the source of every translation, so choose it before building the menu.

Choose fewer languages than you are tempted to

The right question is not "which languages do our guests speak?" but "which languages can we keep correct?"

A menu in five languages where three are half-finished is worse than a menu in two that are complete. Guests notice an untranslated section immediately, and an out-of-date translated price is a real problem at the table.

Practical guidance:

• Two languages — the local language and one international one. This is right for most restaurants.
• Three — when a second local language is genuinely expected.
• More — only with someone responsible for keeping them current.

The ongoing cost

Every language multiplies:

• item titles and descriptions to write;
• category names to translate;
• tasting and set menu blocks to translate;
• languages to review before each launch;
• QR codes and PDFs to generate;
• checks after every menu change.

Prices, allergens, images and the menu order are shared, so those do not multiply. That is what keeps the cost manageable at all.

Add a language later

Nothing prevents adding a language once the menu is stable, and it is the recommended order:

1. Finish and publish the source menu.
2. Enable the new language.
3. Translate the categories.
4. Translate the items, section by section.
5. Review the whole language as a guest.
6. Generate its QR codes and PDF.

Removing a language

Unticking a language stops publishing it. Translated content is not deleted by that action, so a language can come back later without retranslating.

Before removing one, check what was printed: table material or a PDF pointing at that language will stop being useful.

What guests get in each language

• The full menu, in their language, at the same prices.
• The same allergen information.
• The same dishes, in the same order.
• A language switcher, if the toggle is enabled for that archive.

Before enabling a language

• [ ] The source menu is complete and stable.
• [ ] Someone is responsible for keeping this language current.
• [ ] There is a plan for translating new dishes as they are added.
• [ ] The translation quality bar is agreed — human, AI-assisted, or professional.
• [ ] The team knows that a change to a dish means a change in every language.