This content is archived. See latest version here

Last updated: Oct 21 2014

This document provides an introduction to globalization in EPiServer Commerce. By globalization we mean the possibility to create and display website content in different languages, as well as the possibility to 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 formating, sort order etc.
  • 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 for instance a page or a block, as well as a product from the product catalog.

Conceptually, globalization in Commerce works the same way as in CMS. Refer to the Globalization section of the EPiServer CMS Developer Guide for a more detailed explanation of the language management concept in EPiServer.

Not all globalization features described for the EPiServer platform and CMS apply to Commerce. Some features may work differently, for instance in the legacy parts of Commerce Manager.

By default the EPiServer Commerce user interface comes in a number of languages, and can be further localized 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 as for CMS. Refer to the Localization service section in the EPiServer Framework SDK for more information.

Commerce Manager user interface

Do the following to add additional 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.
  • The recommended approach is to make a copy of existing resx files and rename them, in order to keep existing resx files and allow for multiple languages. This is not necessary, but you can rebuild your solution if you wish to do so. Open each resx file using Visual Studio, and edit each key/value pair to match your language.

See also


Do you have feedback on this documentation? Send an email to documentation@episerver.com. For development-related questions and discussions, refer to our Forums on https://world.episerver.com/forum/