Skip to main content
Available languages and locale behavior. Language configuration controls which locales are available and how localized content is selected.

Localization concepts

Separate the language catalog from translated values. Confirm how the application identifies the requested locale (for example, request header, query parameter, or configured default) and how fallback works when a translation is missing.

Content coverage

Check products, categories, collections, CMS content, email templates, and validation messages independently. A language being enabled does not guarantee that every field is translated.

Developer guidance

Use stable locale identifiers, preserve the original/default language, and test fallback behavior. Avoid assuming that a translated label changes stored identifiers or business logic.

Verify

Inspect language entities, translation middleware, translatable fields, and database migrations for the actual v6 behavior.