Email Localization

What this covers

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

Language selection

When DJUST sends an email to a customer user, the locale of the email is determined by:

1. The customer user's locale (set on their profile).
2. If not set, the store's default locale.
3. If not set, the tenant's default locale (platform-wide fallback).

✅

This applies to all platform emails: order confirmations, shipping notifications, account emails, etc.

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 locales configured on the store. There is no requirement to create templates for locales that the store does not support.
• If a customer user's locale matches a store locale, the template for that locale is used.
• If the customer user's locale is not available on the store, the system falls back to the store's default locale.

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.