Multi-language documents

The platform can render editable documents in multiple languages. The right language is picked automatically from the customer record, with a manual override at generation time.

How it's configured

Each editable doc type can have language variants. In the Designer, top-bar → Language dropdown.

• Default: the tenant's base language (usually English).
• Add a variant: click + Language → pick one of the supported languages. Creates a parallel template, initially a copy of the base.
• Edit each variant's text blocks independently. Layout stays synchronised — structural changes propagate across variants; text does not.

Supported languages

English, Spanish, French, German, Portuguese, Italian, Dutch, Arabic, Hindi, Simplified Chinese, Japanese, Vietnamese, Indonesian, Thai, Turkish, Polish.

RTL (Arabic) renders right-to-left automatically; tables mirror column order.

Picking a language at render

1. If the source record has an override (e.g. quote.documentLanguage), that wins.
2. Else, the customer's preferredLanguage field is used.
3. Else, the tenant default.

The manual override is available on the quote / booking / invoice UI as a "Language" dropdown in the document generation modal.

Data-bound content

Merge variables render in the source data's language — a customer name in Arabic stays in Arabic even on an English template. Numeric / date formatting follows the template's language locale (e.g. 1.234,56 € on German, $1,234.56 on English).

Regulated docs

MAWB, HAWB, MBL, HBL are English-only by international convention. Customs declarations follow each authority's required language.

Fallback

If a language variant doesn't exist for a doc type, the tenant default variant is used. No error.