Black Friday
Skip to documentation content

Multilingual Sites

Understand booking, email and invoice languages

The current visitor language, a saved booking language and the WordPress administrator's language are different contexts. Changing today's site language does not translate every historical booking or rewrite previously sent correspondence.

The current visitor language, a saved booking language and the WordPress administrator’s language are different contexts. Changing today’s site language does not translate every historical booking or rewrite previously sent correspondence.

Verify a new booking

Use a synthetic guest, select the intended frontend language and follow Search → Book Now → the applicable payment/result flow. Verify the booking stores the validated locale and retains the language through its supported URLs/forms. Currency and machine-readable dates remain canonical values, separate from translated display labels.

Inspect a newly generated booking message and, when entitled, the invoice in the booking’s saved language context. A translated theme heading does not prove that Core/Pro message catalogs or guest-facing content translations are available.

Customize email templates by language

With Free 3.30.0 and Pro 1.38.0 or later, open Hotel Booking → Email Settings → Templates, select Email language and edit the required email type. Each type and locale has its own template. A locale without custom wording uses its translated default; the applied shared design still supplies branding and the inherited footer. Custom wording is not automatically translated into other languages.

Choose Use default to inherit current defaults or Custom to enter language-specific text. Save, preview that language with sample data, optionally send a test and apply the draft. This does not change the booking’s saved locale. Check both left-to-right and right-to-left presentation where applicable. See Customize booking email content and branding for the complete workflow and supported placeholders.

Preserve historical terms and financial facts

Saved room-policy/cancellation terms and financial lines belong to the booking’s history. Current catalogue translations, tax rules or policy edits must not replace those snapshots. Room names/photos can use current public presentation and are not a universal historical media snapshot guarantee.

Existing queued/sent messages and issued invoices are not automatically rewritten by a new translation file. A resend or new document action must follow its owner workflow; do not mass-rewrite old records to change a CTA or language label.

Diagnose the correct layer

Check the saved booking locale, availability of the relevant Free/Pro language files, translatable entity content and the recipient/document context. Administrator locale alone is not the expected customer-message locale. An unsupported or invalid locale can fall back through the provider’s validated resolution.

Use a mail sink and synthetic paid booking for controlled document tests. A local capture proves generated content, not Internet inbox delivery. Actual PDF issuance still requires the invoice’s settled-payment and booking-state conditions.

Do not turn a language problem into a financial repair: keep totals, payment references and policy revisions unchanged. See software versus content translations and emails/invoices.

Was this article helpful?

Your feedback helps us improve the documentation.