Managing Store Languages and Translations

If your store is set up with multiple markets, you may need to manage translations separately for each market, including market-specific theme content and localized copy. 

This guide covers how to export and import market-specific translation data, and how to handle multi-market theme corpus translation for OS 3.0 themes.

Exporting and Importing Market-Specific Translation Data

When exporting translation data, SHOPLINE includes a Market filter option that lets you scope the export to a single market. This is useful when you want to focus on one market's content at a time.

To export translation data for a specific market:

1. From your SHOPLINE admin panel, go to Settings > Languages.
2. Configure the export options as needed: select Language range and Scope. To limit the export to a specific market, select from the Market filter (all markets included by default). Select Online store language, enter the destination email address in Export to Email, then click Export.
   
3. Fill the translated language materials in the form.

4. Click Import, and import the filled-in form.
   

   Notes:  The file size limit for importing translation data is 20 MB. If your file exceeds this limit, a File too large notification will appear in the top-right corner of the page. Split your data into smaller batches and try again. Please note that exported files are encrypted for security purposes, which may increase their overall size. For full details on the export/import workflow, including field descriptions, file size limits, and error handling, refer to "Managing Store Languages and Translations".

Translating Theme Corpus for Multi-Market Stores (for OS 3.0 Themes Only)

If your store uses a 3.0 theme with multiple markets, you may need to translate theme components (such as text blocks and headings) for each market. The correct approach depends on how your theme components are structured across markets.

Use the following scenarios to identify your situation and take the right action.

Scenario 1: The Same Component Exists in All Markets, Each with Different Default Text

Situation

Your store has a component, for example, a heading block, in all markets (US, UK, JP), and you have entered a different default text for each market.

What to do

• Translate the content separately for each market.
• In the exported CSV, locate the row for each market and fill in the Translated Content column for each one individually.

Scenario 2: The Same Component Exists in All Markets, but Only One Market Has Text

Situation

You have placed the same component (for example, a heading block) in all markets, but you only entered text in the JP market. The other markets have no text in that component.

What to do

• Only translate the content for the JP market.
• For all other markets, no translation is needed. The system will display the component as empty. This is expected behavior, and no action is required.

Scenario 3: A Component Was Added to One Specific Market Only

Situation

You added a component exclusively to the US market (for example, for a market-specific promotion). No other market has this component.

What to do

• Only translate the content for the US market.
• The exported file will only contain a row for the US market. This is correct and expected (what you see is what you get). You do not need to add rows for other markets.

Scenario 4: A Component Was Added to the Default Setup, but Only Some Markets Inherit It

Situation

You added a component to the Default setup. However, the US and JP markets were previously customized (privatized) and do not inherit changes from Default. Only the UK market inherits the new component.

What to do

• Translate the content for Default or the UK market (which inherits from Default).
• Do not fill in translations for the US or JP markets. Since they do not inherit this component, any translations you enter for them in the CSV will have no effect and will not be applied.

Recommended Practices for Multi-Market Theme Translation

• Use the UGC Multi-Language Visual Translator app for day-to-day edits: For most routine content changes, the UGC Multi-Language Visual Translator app gives you full control and accuracy over your translations. You can customize content for specific markets and languages directly within the app. This approach is the most straightforward and minimizes the risk of errors. 
• Key rules when using CSV export/import for bulk edits: If you need to make large-scale edits (for example, correcting British vs. American English spelling differences across your UK and US markets), using the CSV export/import feature is more efficient. However: 
  • Always update the Translated Content column for the specific market row you want to change.
  • Do not try to update the Default translation and expect it to apply across all markets automatically. This does not work.