...
Do you only want to use different languages within one market, but your product assortment remains identical (= Prices and Product Outlinks outlinks stay the same)?
- Yes → continue with B) Localize Display Attributes
Do you want to use different channels/markets, but you require also multiple languages for some markets?
...
To provide different URLs of the workbench in each market, you can add a column "channelid" and add the corresponding market name for each product. For a multi-country setup we suggest the common two-letter-abbreviations (e.g. us, de, fr). All products must therefore be represented multiple-teams in the product data (once for market). This allows you to have different e.g. different outlinks, prices, product names etc. for each market/channel.
1. Add a column "channelid" in your product data
2. Duplicate the Product Data which has market-specific product assortments and outlinks
3. Add in the column "channelid" the language shortcut e.g us, de
If you upload the Product Data in the Workbench in the Preview you can see a new field for the Channel:
...
| Info | ||
|---|---|---|
| ||
If you cannot prepare a combined multi-channel Product Data export yourself or if maintaining such a file manually is not feasible (e.g. due to too many products that change too often), please contact your excentos Project Manager to develop a suitable solution together (e.g. excentos can setup set up jobs to automatically download and combine multiple country Product Data feeds). |
...
If a Display Attribute (attributes that are shown on the Product Card in the Recommendations e.g. the product description) needs to be localized you can add an additional a corresponding column in the Product Data with the original name followed by the language ("ATTRIBUTE" → "ATTRIBUTE_LANGUAGESUFFIX"). If the original column is called "description", then the column for the additional language must be called "description_frde_FRDE". The Workbench automatically uses the right column, when the corresponding language is selected (e.g. in the Preview or for Integration Codes).
| Info | ||
|---|---|---|
| ||
Note, that if you are running your Product Guide, which you have not created yet localized columns for, the Product Guide will automatically fall back to the original default column. Example:
|
Localizing Values that are also used for Data Binding
...
However, if you want to use a Product Data Attribute for Data Binding as well as displaying it in the Product Cards, you may want to use approach B) Localize Display Attributes, so your Data Binding can be done on the original column (based on the same original values for all market in the original concept lanaguagelanguage) and for usage in the Display Attributes, the system can use the localized attributes.
...