This content is archived. See latest version here

Last updated: Oct 12 2015

This topic describes globalization in Episerver Commerce, by which you can create and display website content in different languages, and make the user interface appear in different languages through the localization of user-facing texts.

Globalization in Commerce

When describing the language concept in Episerver, the following language setting types are mentioned:

  • System language. Used to control date/time formatting, sort order, and so on.
  • User interface language. Controls the localized (translated) resources to display; determines the language of the user interface.
  • Content language. The preferred language when displaying content. Content can be a page, a block, or a product from the product catalog.

Conceptually, globalization in Commerce works the same way as in CMS. See the Globalization section of the Episerver CMS Developer Guide about the language management concept in Episerver.

Note: Not all globalization features described for the Episerver platform and CMS apply to Commerce. Some features may work differently, such as in the legacy parts of Commerce Manager. (Legacy refers to before Commerce 8.6.0.)

By default, the Episerver Commerce user interface is available in a number of languages. You can localize it further with additional languages. The localization procedure differs somewhat between the Commerce user interface and the legacy Commerce Manager back-end system.

Commerce user interface

The Commerce plugable add-on user interface is localized using the Episerver localization services in the same way that the CMS is. See also the Localization service section in the Episerver Framework SDK.

Commerce Manager user interface

To add languages for localization of the user interface in the Commerce Manager back-end system:

  • Change the associated key values of those files of your resx files under App_GlobalResources. Each key/value pair corresponds to a particular function in the Episerver Commerce administration interface.
  • You should make a copy of existing resx files and rename them, to keep existing resx files and allow for multiple languages. This is not necessary, but you can rebuild your solution. Open each resx file using Visual Studio, and edit each key/value pair to match your language.

Related topic

Do you have feedback on this documentation? Send an email to For development-related questions and discussions, refer to our Forums on