Documentation

Multilingual passports

How a passport is translated into the languages of the markets it is sold on, typed by you or by AI, how the market suggestions work, and how the public page serves each language.

Under the ESPR, the language of a passport is the language of the market where the product is made available, and each member state sets its own rule. A shop that sells in three countries therefore needs its passports in several languages. The Pro add-on adds the writing of those translations; the free plugin stores and serves them.

The Translations box

With the add-on active, the passport editor gains a Translations box. Fill and save the passport in its own language first: a translation is an overlay on the source, and there is nothing to translate until the source exists.

The box works one language at a time. Pick a language from the list of the 24 official languages of the European Union, and a panel opens with the source text of each field beside an editable translation field. Type the translation, or click Translate to (language) with AI to have every filled prose field rendered in that language at once, then adjust what needs adjusting and save. Repeat for the next language.

The source is never touched by a translation. Correcting the source later does not rewrite the translations, so a corrected source means re-reading its translations too.

What gets translated

Every prose field of the template: care instructions, recycling, repair information, certifications and so on. Each material of the composition is a line of its own, so "organic cotton" can become "coton biologique" while the percentages stay.

The product name is offered as a translation too, and it is optional: left empty, the page shows the WooCommerce name, which is what a merchant wants when the page should match the printed label. The brand name is never translated; it is a proper noun.

Numbers and countries are the same in every language and need no translation.

Market suggestions

Above the language list, Your recent markets suggests languages drawn from your own orders: the add-on reads the shipping countries of your recent WooCommerce orders, keeps the EU ones, and lists their languages. The reading is local, refreshed twice a day, and nothing leaves the site for it.

It is a suggestion, not a rule: a country is not a language one to one, and each member state decides which languages it requires. The box says so.

AI translation

AI translation runs on the same service as the autofill and is described with it on the AI autofill page: the text of the fields is sent when you click, and only then. Unlike the autofill, there is no review state: the source was already written and checked by you, so the AI writes straight into the translation fields, where you adjust and save.

Pro includes a monthly reserve of AI translations, separate from the autofill credits. Beyond the reserve, a full translation of a passport into one language costs one AI credit. Typing a translation yourself is always free.

On the public page

A passport with translations gets a language switcher at the top of its public page. The source language keeps the clean address the QR code encodes; each other language has its own address, and the page declares them all as alternates so that search engines pair them. The labels of the page, "Country of origin" and the others, follow the chosen language in all 23 languages the free plugin ships, whatever the language of your WordPress.

One QR code is enough: the customer scans it, lands on the source language and switches. A corrected translation is visible at the next scan, like any edit.

Without the add-on

Translations are stored and rendered by the free plugin. If the add-on is removed or the licence lapses, every translation already written keeps being served, with its switcher and its alternates. What leaves is the box that writes them.