{"_id":"595747b2f3c7c3002b095d70","project":"55a6e72e8cc73e0d00096635","version":{"_id":"55a6e72f8cc73e0d00096638","project":"55a6e72e8cc73e0d00096635","hasReference":false,"__v":29,"hasDoc":true,"createdAt":"2015-07-15T23:05:19.125Z","releaseDate":"2015-07-15T23:05:19.125Z","categories":["55a6e7308cc73e0d00096639","55b7ed07aea7c8190058badb","5604567c0c78b00d0039b191","5605e6f23a93940d002b3e4a","5605f2bba4574a0d00811365","5605f309a4574a0d00811366","5608e3b98aedf50d0004cf8f","5608e4318aedf50d0004cf90","5608e6b5a7cc2f0d00d9754d","5608e6d331beb60d001b6560","5608f879a7cc2f0d00d97580","560b097887b71d0d000d3bd9","560b13cbafa0990d00979545","560b5cbec341310d00de2a01","560b5cd0c341310d00de2a02","566a35b81e08750d00a0c49b","566a3e8503b4b20d00d02a4a","567889d307bf6a0d0083edc8","569c8b7c15bb390d00db6f9d","56b254dc65ddf50d0076ba8f","57a8ebc4cdeea20e001d2a63","57e48a4000c8680e00fae6e7","5808216773557d0f00a1e428","58105ad54a8aa50f00aa4cba","58105bf298aea40f00afa3ba","58105f548a4aed0f00d67536","581061b898aea40f00afa3be","584b3de7e5f3a42300df6ef7","596839a75965d400155bb750"],"is_deprecated":false,"is_hidden":false,"is_beta":false,"is_stable":true,"codename":"","version_clean":"1.0.0","version":"1.0"},"category":{"_id":"560b5cd0c341310d00de2a02","project":"55a6e72e8cc73e0d00096635","version":"55a6e72f8cc73e0d00096638","__v":9,"pages":["560b629c3616ac17004f1ca3","560b63343bcbd80d0077d10a","560b637e5148ba0d009bd0d0","560b63c53616ac17004f1ca8","560b63dd5148ba0d009bd0d3","560b63f42d00ca0d00a1fdbf","560b64ee5148ba0d009bd0d5","5617054c7f74330d00dfd73c","561705cbbd70650d00977851"],"sync":{"url":"","isSync":false},"reference":false,"createdAt":"2015-09-30T03:53:52.522Z","from_sync":false,"order":15,"slug":"internationalizationlocalization","title":"Internationalization/Localization"},"user":"55a6caa022cfa321008e01d6","__v":0,"parentDoc":null,"updates":[],"next":{"pages":[],"description":""},"createdAt":"2017-07-01T06:56:50.291Z","link_external":false,"link_url":"","githubsync":"","sync_unique":"","hidden":false,"api":{"results":{"codes":[]},"settings":"","auth":"required","params":[],"url":""},"isReference":false,"order":1,"body":"This page explains how to adapt a BigCommerce store for a different language and/or region. It covers:\n\n* [Overview: Localization Touchpoints](#ovw)\n* [Translating Theme Files via Stencil CLI ](#cli)\n* [Localizing Checkout](#checkout)\n* [Localizing Non-Theme Content](#nontheme)\n\t* [Localizing the Product Catalog](#catalog)\n\t* [Localizing Currency](#currency)\n\t* [Localizing Date Format](#date)\n\t* [Localizing Order Statuses](#status)\n\t* [Managing Transactional Emails](#email)\n\t* [Localizing the Blog](#blog)\n\t* [Managing Gift Certificates](#gift)\n\t* [Localizing Static Web Pages](#pages) </p>\n[block:html]\n{\n  \"html\": \"<!--\\n* [Beyond Language and Currency](#gestalt)\\n-->\"\n}\n[/block]\n## <a name=\"ovw\"></a> Overview: Localization Touchpoints\n\nYou can run a BigCommerce store in any single language of your choice. If you want to support multiple languages, we recommend setting up a separate store for each language. To fully localize a store into a language/region other than U.S. English, you will need to customize three areas:\n\n* [Storefront theme pages](#cli): Translate static strings. This requires adding translation files for your chosen non-English languages, via Stencil CLI.\n\n* [Checkout](#checkout): Localizing checkout requires modifications both to theme files (in Stencil CLI) and to settings in the BigCommerce control panel.\n\n* [Outside your theme](#nontheme): Adjust other localization details via the BigCommerce control panel.\n\nThe following sections provide a linked summary of all the steps involved.\n\n\n## <a name=\"cli\"></a> Translating Theme Files via Stencil CLI\n\nThe core of localizing a store is to translate content on your theme's page templates into each language that you choose to support. You will need to abstract these templates' literal text strings into `{{lang}}` variables, then provide per-language JSON files that define these variables in corresponding key/value pairs.\n\nFor details on this process, please see this section's remaining pages, starting with [Basis for Internationalization](/docs/basis-for-i18n).\n\n[block:html]\n{\n  \"html\": \"<!--\\nhttps://files.readme.io/539c63e-it-carousel-pg.png\\nA translated storefront\\n\\n### <a name=\\\"how\\\"></a> Translation Resources\\n\\nIdeally, your content will be translated by a native speaker of each target language. A backup alternative is to rely on an automatic translation app or third-party integration.\\n-->\"\n}\n[/block]\n## <a name=\"checkout\"></a> Localizing Checkout\n\nLocalizing your theme's checkout and order confirmation pages requires specific steps in their corresponding templates, and in each of your JSON translation files, and in the BigCommerce control panel.\n[block:callout]\n{\n  \"type\": \"warning\",\n  \"body\": \"To localize your theme's checkout and/or order confirmation page, you must first [enable Optimized One-Page Checkout](/docs/optimized-checkout-prereqs).\",\n  \"title\": \"Optimized One-Page Checkout Required\"\n}\n[/block]\nFor details, please see the following pages:\n\n* [Preparing Stencil Themes for Optimized One-Page Checkout](/docs/optimized-checkout-prereqs) <br> (a prerequisite for the remaining checkout internationalization options below)\n* [Currency-Conversion Options](/docs/multi-currency-checkout) <br> (displaying prices in alternate currencies)\n* [Multi-Language Checkout](/docs/multi-language-checkout) <br> (translating your checkout and/or order confirmation templates)\n\n\n## <a name=\"nontheme\"></a> Localizing Non-Theme Content\n\nThese remaining localization options reside outside your theme, and are accessible primarily through the BigCommerce control panel:\n\n* [Product catalog](#catalog)\n* [Currency](#currency)\n* [Checkout type](#checkout)\n* [Date format](#date)\n* [Order statuses](#status)\n* [Transactional emails](#email)\n* [Gift certificates](#gift)\n* [Blog](#blog)\n* [Static web pages](#pages)\n\n\n### <a name=\"catalog\"></a> Localizing the Product Catalog\n\nYou must localize the store's product catalog separately from its theme. Each entry within a catalog can be set up in only one language, so you will want to localize a separate version of your catalog for each single-language store. \n\nFor an overview of populating the store catalog – including options for bulk-importing content that you can localize outside the BigCommerce platform – please see our support article on [Adding and Managing Your Product Catalog](https://support.bigcommerce.com/articles/Public/Importing-Products/).\n\n[block:html]\n{\n  \"html\": \"<!--\\n### <a name=\\\"catalog\\\"></a> Localizing the Product Catalog\\n\\nYou must localize the store's product catalog separately from its theme. Your options include the same human, automated, or combined translation alternatives listed above under [Translation Resources](#how).\\n-->\"\n}\n[/block]\n### <a name=\"currency\"></a> Localizing Currency\n\nEach store's default currency is configured in the BigCommerce control panel. For details, please see our support article on [Changing Your Default Currency](https://support.bigcommerce.com/articles/Public/Managing-Currencies#default).\n[block:html]\n{\n  \"html\": \"<!--\\nNormally, all store transactions will be processed in this selected currency. If you want to accept payments in a currency other than the store's settlement currency, you can consider integrating a [third-party gateway](https://www.bigcommerce.com/features/sell-internationally/).\\n-->\"\n}\n[/block]\n### <a name=\"date\"></a> Localizing Date Format\n\nYou can set the appropriate date format for your store's language/region in the BigCommerce control panel (under `Store Setup` > `Store Settings` > `Date & Timezone`). For details, please see [this support article](https://support.bigcommerce.com/articles/Public/Date-Timezone-Settings).\n\n\n### <a name=\"status\"></a> Localizing Order Statuses\n\nThe order-status labels displayed on a BigCommerce storefront are configured outside your theme. You can translate each of these strings via the BigCommerce control panel's `Orders` > `Order Statuses` option. For instructions, please see the [Customizing an Order Status Label](https://support.bigcommerce.com/articles/Public/Understanding-Order-Statuses#customize) support topic.\n\n\n### <a name=\"email\"></a> Managing Transactional Emails\n\nBigCommerce does not currently provide native support for localizing transactional emails. To fully localize a store into a language other than English, the simplest solution is to disable the sending of BigCommerce native emails. You can access this option from the BigCommerce control panel's left nav in one of two locations (depending on your store's control-panel version):\n\n* `Storefront` > `Emails`\n* `Storefront Design` > `My Themes` > `Design Options` > `More` [drop-down list] > `Emails`\n\nNext, in the `Enable` column, uncheck the check box for each email type that you want to disable. (These toggles require no confirmation step.) For further details about managing BigCommerce transactional emails, please see [this support article](https://support.bigcommerce.com/articles/Public/Customizing-Email-Templates/).\n[block:html]\n{\n  \"html\": \"<!-- ### <a name=\\\"email\\\"></a> Managing Transactional Emails\\n\\nBigCommerce does not currently provide native support for localizing transactional emails' subject lines. You can modify emails' body text, although doing so on a Stencil theme currently requires a [workaround](/docs/customizing-email-templates) to access additional templates.\\n\\nGiven the constraint on subject lines: To fully localize a store into a language other than English, the simplest solution is to disable the sending of BigCommerce native emails. You can access this option from the BigCommerce control panel's left nav in one of two locations (depending on your store's control-panel version):\\n\\n* `Storefront` > `Emails`\\n* `Storefront Design` > `My Themes` > `Design Options` > `More` [drop-down list] > `Emails`\\n\\nNext, in the `Enable` column, uncheck the check box for each email type that you want to disable. (These toggles require no confirmation step.) For further details about managing BigCommerce transactional emails, please see this [support article](https://support.bigcommerce.com/articles/Public/Customizing-Email-Templates/).\\n\\nOnce you have disabled BigCommerce native emails, you have the option of sending localized emails using a third-party integration, such as [Mailgun](https://www.mailgun.com/). -->\"\n}\n[/block]\n### <a name=\"gift\"></a> Managing Gift Certificates\n\nThe BigCommerce platform does not currently support translation of gift certificates into languages other than English. To&#160;fully localize your store, you can choose to [disable gift certificates](https://support.bigcommerce.com/articles/Public/Using-Gift-Certificates#enable) via the BigCommerce control panel.\n\n### <a name=\"blog\"></a> Localizing the Blog\n\nYou manage blog entries through the BigCommerce control panel (under `Storefront Content` > `Blog`). You are free to add blog content in any language you choose. For details, please see [this support article](https://support.bigcommerce.com/articles/Public/Using-the-Built-In-Blog/).\n[block:html]\n{\n  \"html\": \"<!--\\nhttps://files.readme.io/539c63e-it-carousel-pg.png\\nA localized blog page\\n-->\"\n}\n[/block]\n### <a name=\"pages\"></a> Localizing Static Web Pages\n\nIf you create static pages as Stencil [custom templates](/docs/custom-layout-templates), you can localize their content just like [other theme pages'](#cli) content. However, if you create custom pages via the BigCommerce control panel (under `Storefront Content` > `Web Pages`), you must also enter their localized content via the control panel; for details, please see [this support article](https://support.bigcommerce.com/articles/Public/Web-Pages/).\n[block:html]\n{\n  \"html\": \"<!--\\n## <a name=\\\"gestalt\\\"></a> Beyond Language and Currency\\n\\nBy following all the steps on this page, you will create a localized version of your storefront. However, fully localizing a storefront to be \\\"at home\\\" in regions outside your base country involves modifications beyond language and currency. For an overview, please see [this article](https://www.bigcommerce.com/ecommerce-answers/how-translate-your-website-foreign-language/). \\n\\nConsiderations include include: layout and typography, reading direction, color choices and their connotations, measurement units, payment methods, locally prominent brands and categories, locally prominent competitors, locally popular search engines (with corresponding SEO guidelines), available omni-channel integrations, available apps, preferred shipping providers, tax calculation, and government regulations regarding privacy and other issues. \\n\\nYou can address several of these considerations by making changes in your theme's design, or in the store's BigCommerce control panel. You can use [BigCommerce Marketplace Apps](https://www.bigcommerce.com/apps/) to facilitate shipping and tax localization.\\n-->\"\n}\n[/block]","excerpt":"","slug":"localizing-stores","type":"basic","title":"Localizing Stores"}
This page explains how to adapt a BigCommerce store for a different language and/or region. It covers: * [Overview: Localization Touchpoints](#ovw) * [Translating Theme Files via Stencil CLI ](#cli) * [Localizing Checkout](#checkout) * [Localizing Non-Theme Content](#nontheme) * [Localizing the Product Catalog](#catalog) * [Localizing Currency](#currency) * [Localizing Date Format](#date) * [Localizing Order Statuses](#status) * [Managing Transactional Emails](#email) * [Localizing the Blog](#blog) * [Managing Gift Certificates](#gift) * [Localizing Static Web Pages](#pages) </p> [block:html] { "html": "<!--\n* [Beyond Language and Currency](#gestalt)\n-->" } [/block] ## <a name="ovw"></a> Overview: Localization Touchpoints You can run a BigCommerce store in any single language of your choice. If you want to support multiple languages, we recommend setting up a separate store for each language. To fully localize a store into a language/region other than U.S. English, you will need to customize three areas: * [Storefront theme pages](#cli): Translate static strings. This requires adding translation files for your chosen non-English languages, via Stencil CLI. * [Checkout](#checkout): Localizing checkout requires modifications both to theme files (in Stencil CLI) and to settings in the BigCommerce control panel. * [Outside your theme](#nontheme): Adjust other localization details via the BigCommerce control panel. The following sections provide a linked summary of all the steps involved. ## <a name="cli"></a> Translating Theme Files via Stencil CLI The core of localizing a store is to translate content on your theme's page templates into each language that you choose to support. You will need to abstract these templates' literal text strings into `{{lang}}` variables, then provide per-language JSON files that define these variables in corresponding key/value pairs. For details on this process, please see this section's remaining pages, starting with [Basis for Internationalization](/docs/basis-for-i18n). [block:html] { "html": "<!--\nhttps://files.readme.io/539c63e-it-carousel-pg.png\nA translated storefront\n\n### <a name=\"how\"></a> Translation Resources\n\nIdeally, your content will be translated by a native speaker of each target language. A backup alternative is to rely on an automatic translation app or third-party integration.\n-->" } [/block] ## <a name="checkout"></a> Localizing Checkout Localizing your theme's checkout and order confirmation pages requires specific steps in their corresponding templates, and in each of your JSON translation files, and in the BigCommerce control panel. [block:callout] { "type": "warning", "body": "To localize your theme's checkout and/or order confirmation page, you must first [enable Optimized One-Page Checkout](/docs/optimized-checkout-prereqs).", "title": "Optimized One-Page Checkout Required" } [/block] For details, please see the following pages: * [Preparing Stencil Themes for Optimized One-Page Checkout](/docs/optimized-checkout-prereqs) <br> (a prerequisite for the remaining checkout internationalization options below) * [Currency-Conversion Options](/docs/multi-currency-checkout) <br> (displaying prices in alternate currencies) * [Multi-Language Checkout](/docs/multi-language-checkout) <br> (translating your checkout and/or order confirmation templates) ## <a name="nontheme"></a> Localizing Non-Theme Content These remaining localization options reside outside your theme, and are accessible primarily through the BigCommerce control panel: * [Product catalog](#catalog) * [Currency](#currency) * [Checkout type](#checkout) * [Date format](#date) * [Order statuses](#status) * [Transactional emails](#email) * [Gift certificates](#gift) * [Blog](#blog) * [Static web pages](#pages) ### <a name="catalog"></a> Localizing the Product Catalog You must localize the store's product catalog separately from its theme. Each entry within a catalog can be set up in only one language, so you will want to localize a separate version of your catalog for each single-language store. For an overview of populating the store catalog – including options for bulk-importing content that you can localize outside the BigCommerce platform – please see our support article on [Adding and Managing Your Product Catalog](https://support.bigcommerce.com/articles/Public/Importing-Products/). [block:html] { "html": "<!--\n### <a name=\"catalog\"></a> Localizing the Product Catalog\n\nYou must localize the store's product catalog separately from its theme. Your options include the same human, automated, or combined translation alternatives listed above under [Translation Resources](#how).\n-->" } [/block] ### <a name="currency"></a> Localizing Currency Each store's default currency is configured in the BigCommerce control panel. For details, please see our support article on [Changing Your Default Currency](https://support.bigcommerce.com/articles/Public/Managing-Currencies#default). [block:html] { "html": "<!--\nNormally, all store transactions will be processed in this selected currency. If you want to accept payments in a currency other than the store's settlement currency, you can consider integrating a [third-party gateway](https://www.bigcommerce.com/features/sell-internationally/).\n-->" } [/block] ### <a name="date"></a> Localizing Date Format You can set the appropriate date format for your store's language/region in the BigCommerce control panel (under `Store Setup` > `Store Settings` > `Date & Timezone`). For details, please see [this support article](https://support.bigcommerce.com/articles/Public/Date-Timezone-Settings). ### <a name="status"></a> Localizing Order Statuses The order-status labels displayed on a BigCommerce storefront are configured outside your theme. You can translate each of these strings via the BigCommerce control panel's `Orders` > `Order Statuses` option. For instructions, please see the [Customizing an Order Status Label](https://support.bigcommerce.com/articles/Public/Understanding-Order-Statuses#customize) support topic. ### <a name="email"></a> Managing Transactional Emails BigCommerce does not currently provide native support for localizing transactional emails. To fully localize a store into a language other than English, the simplest solution is to disable the sending of BigCommerce native emails. You can access this option from the BigCommerce control panel's left nav in one of two locations (depending on your store's control-panel version): * `Storefront` > `Emails` * `Storefront Design` > `My Themes` > `Design Options` > `More` [drop-down list] > `Emails` Next, in the `Enable` column, uncheck the check box for each email type that you want to disable. (These toggles require no confirmation step.) For further details about managing BigCommerce transactional emails, please see [this support article](https://support.bigcommerce.com/articles/Public/Customizing-Email-Templates/). [block:html] { "html": "<!-- ### <a name=\"email\"></a> Managing Transactional Emails\n\nBigCommerce does not currently provide native support for localizing transactional emails' subject lines. You can modify emails' body text, although doing so on a Stencil theme currently requires a [workaround](/docs/customizing-email-templates) to access additional templates.\n\nGiven the constraint on subject lines: To fully localize a store into a language other than English, the simplest solution is to disable the sending of BigCommerce native emails. You can access this option from the BigCommerce control panel's left nav in one of two locations (depending on your store's control-panel version):\n\n* `Storefront` > `Emails`\n* `Storefront Design` > `My Themes` > `Design Options` > `More` [drop-down list] > `Emails`\n\nNext, in the `Enable` column, uncheck the check box for each email type that you want to disable. (These toggles require no confirmation step.) For further details about managing BigCommerce transactional emails, please see this [support article](https://support.bigcommerce.com/articles/Public/Customizing-Email-Templates/).\n\nOnce you have disabled BigCommerce native emails, you have the option of sending localized emails using a third-party integration, such as [Mailgun](https://www.mailgun.com/). -->" } [/block] ### <a name="gift"></a> Managing Gift Certificates The BigCommerce platform does not currently support translation of gift certificates into languages other than English. To&#160;fully localize your store, you can choose to [disable gift certificates](https://support.bigcommerce.com/articles/Public/Using-Gift-Certificates#enable) via the BigCommerce control panel. ### <a name="blog"></a> Localizing the Blog You manage blog entries through the BigCommerce control panel (under `Storefront Content` > `Blog`). You are free to add blog content in any language you choose. For details, please see [this support article](https://support.bigcommerce.com/articles/Public/Using-the-Built-In-Blog/). [block:html] { "html": "<!--\nhttps://files.readme.io/539c63e-it-carousel-pg.png\nA localized blog page\n-->" } [/block] ### <a name="pages"></a> Localizing Static Web Pages If you create static pages as Stencil [custom templates](/docs/custom-layout-templates), you can localize their content just like [other theme pages'](#cli) content. However, if you create custom pages via the BigCommerce control panel (under `Storefront Content` > `Web Pages`), you must also enter their localized content via the control panel; for details, please see [this support article](https://support.bigcommerce.com/articles/Public/Web-Pages/). [block:html] { "html": "<!--\n## <a name=\"gestalt\"></a> Beyond Language and Currency\n\nBy following all the steps on this page, you will create a localized version of your storefront. However, fully localizing a storefront to be \"at home\" in regions outside your base country involves modifications beyond language and currency. For an overview, please see [this article](https://www.bigcommerce.com/ecommerce-answers/how-translate-your-website-foreign-language/). \n\nConsiderations include include: layout and typography, reading direction, color choices and their connotations, measurement units, payment methods, locally prominent brands and categories, locally prominent competitors, locally popular search engines (with corresponding SEO guidelines), available omni-channel integrations, available apps, preferred shipping providers, tax calculation, and government regulations regarding privacy and other issues. \n\nYou can address several of these considerations by making changes in your theme's design, or in the store's BigCommerce control panel. You can use [BigCommerce Marketplace Apps](https://www.bigcommerce.com/apps/) to facilitate shipping and tax localization.\n-->" } [/block]