Site preferences versus global preferences
Key Takeaway
Global preferences apply to the whole organization, while site preferences apply to one site. Locales and their regional settings, including number and currency formats, are global and set per locale. Each site then chooses its allowed locales, default locale, and allowed currencies.
B2C Commerce is set up as one organization that contains one or more sites, which are storefronts. Settings therefore live at two levels. Global preferences hold organization-wide settings, such as which locales are active and how each locale formats dates, numbers, and currency. Site preferences control how one site behaves, such as its allowed locales and currencies. Knowing which level owns a setting tells you where to configure it and what to set up first.
Organization and sites
Global preferences apply to the whole organization or instance. They live in Business Manager under Administration > Global Preferences. Site preferences control the behavior of one individual site. They live under Merchant Tools > (site) > Site Preferences.
| Setting | Level | Where you set it |
|---|---|---|
| Add, activate, and deactivate locales | Organization | Administration > Global Preferences |
| Regional settings, per locale | Organization | Administration > Global Preferences > Locales, "Regional Settings" tab |
| Locale fallback, per locale | Organization | Administration > Global Preferences > Locales, "General" tab |
| Default UI language and default data language | Organization | Administration > Organization > Organization Profile |
| Allowed locales and default locale | Site | Merchant Tools > (site) > Site Preferences > Locales |
| Allowed currencies | Site | Merchant Tools > (site) > Site Preferences > Currencies |
Configure organization settings first, then site settings. Locales show why the order matters. Only activated locales can be used in the storefront and appear in Business Manager language select boxes. A site can therefore only allow locales that are already active at the organization level.
Site preferences also cover site behavior beyond localization. Examples include:
- Product and content locking time, which is how many minutes a record stays locked while someone edits it
- A/B test preferences
- Commerce Intelligence IP filtering for reports
- Gift certificate email and export settings