Email Localization

What this covers

How DJUST handles localized email templates: language selection for customer users, template storage structure, and store-level scoping.

📘

Note: This page applies to storefront email templates (scope: STOREFRONT), which are contextualized per store and locale. Back Office email templates (scope: BACK_OFFICE — export notifications, job failure alerts, etc.) are global to the platform and are not segmented by store or locale.

Language selection

The language of a transactional email is resolved from the store the event originates from, not from the tenant:

1. The main locale of the store at the origin of the event (the store the order was placed on, the store the password reset was requested from, etc.).
2. If no template is configured for that locale, the send is retried on the main locale of the tenant.
3. If no template is configured for that locale either, the email is not sent and the usual failure log is recorded.

✅

This applies to all transactional emails: order confirmations, shipping notifications, password resets, account emails, etc.

✅

Tip: No additional configuration is required. Templates already configured per locale are used as they are.

⚠️

Warning: A store exposing several active locales sends the same language to all of its customer users — the main locale of that store. The language actually selected by the buyer on the storefront is not taken into account. If you need per-buyer languages, split the audiences across stores whose main locale matches.

Template management

Email templates are managed per locale in the Back Office:

• Each template can be created in any of the active locales.
• The main locale template is the reference: if it is enabled, the workflow notification is considered active.
• Templates for other locales can be added independently.

⚠️

Make sure at least the main locale template is configured and enabled for each email workflow you want to activate.

Store-level scoping

In a multi-store setup with store-level locales:

• Email templates only need to exist for the main locale of each store, plus the main locale of the tenant as a safety net. There is no requirement to create templates for every locale a store supports.
• Two stores whose main locales differ send their transactional emails in two different languages, without any extra setup.
• A store whose main locale has no template falls back to the tenant main locale — configure that one to avoid silent non-sends.

Translated email subjects

Both the subject line and the body of the email can be localized. The subject is stored alongside the template and resolved using the same locale selection logic.