Locale fallback chain for localized resources
Key Takeaway
Resource bundles are found in this order: locale (en_US), then language (en), then default. A language-level version serves every country locale of that language that has no version of its own. A country-locale version serves only that one locale.
When B2C Commerce needs localized text, data, or a file, it starts with the locale of the current request. If nothing is found there, it falls back to broader versions, so you translate only what actually differs for a locale. Business object data, such as product attributes, follows a fallback chain you can configure. Cartridge files, such as templates, properties files, forms, and static files, follow their own folder lookup instead.
Locales and where lookup starts
The locale of the current request, such as en_US in a storefront URL, sets where the lookup starts. The lookup works this way for files in the file system and for data in the database.
Language locales such as en, de, and es are treated like any other locale. They relate to their country locales, such as en_US and en_GB, only through the shared language code. Like any locale, they must be activated before the storefront can use them.