Skip to content
Accueil » Quickstart – Tutorial » Translate values

Translate values

OpenAI GPT-3x & more, Google Gemini Pro, trained on a massive dataset of text from the internet, is capable of generating text in a variety of languages, including English, Spanish, French, Chinese, Russian, and many more. Nevertheless, it is important to bear in mind that the model’s performance will vary depending on the language and the complexity of the text to be generated.

List of locales available with OpenAI.

NumberLanguageCountryLocal Translation
1AlbanianAlbaniaShqip
2ArabicArab Worldالعربية
3ArmenianArmeniaՀայերեն
4AwadhiIndiaअवधी
5AzerbaijaniAzerbaijanAzərbaycanca
6BashkirRussiaБашҡорт
7BasqueSpainEuskara
8BelarusianBelarusБеларуская
9BengaliBangladeshবাংলা
10BhojpuriIndiaभोजपुरी
11BosnianBosnia and HerzegovinaBosanski
12Brazilian PortugueseBrazilportuguês brasileiro
13BulgarianBulgariaбългарски
14Cantonese (Yue)China粵語
15CatalanSpainCatalà
16ChhattisgarhiIndiaछत्तीसगढ़ी
18ChineseChina中文
19CroatianCroatiaHrvatski
20CzechCzech RepublicČeština
21DanishDenmarkDansk
22DogriIndiaडोगरी
23DutchNetherlandsNederlands
24EnglishUnited KingdomEnglish
25EstonianEstoniaEesti
26FaroeseFaroe IslandsFøroyskt
27FinnishFinlandSuomi
28FrenchFranceFrançais
29GalicianSpainGalego
30GeorgianGeorgiaქართული
31GermanGermanyDeutsch
32GreekGreeceΕλληνικά
33GujaratiIndiaગુજરાતી
34HaryanviIndiaहरियाणवी
35HindiIndiaहिंदी
36HungarianHungaryMagyar
37IndonesianIndonesiaBahasa Indonesia
37IrishIrelandGaeilge
38ItalianItalyItaliano
39JapaneseJapan日本語
40JavaneseIndonesiaBasa Jawa
41KannadaIndiaಕನ್ನಡ
42KashmiriIndiaकश्मीरी
43KazakhKazakhstanҚазақша
44KonkaniIndiaकोंकणी
45KoreanSouth Korea한국어
46KyrgyzKyrgyzstanКыргызча
47LatvianLatviaLatviešu
48LithuanianLithuaniaLietuvių
49MacedonianNorth MacedoniaМакедонски
50MaithiliIndiaमैथिली
51MalayMalaysiaBahasa Melayu
52MalteseMaltaMalti
53MandarinChina普通话
54Mandarin ChineseChina中文
55MarathiIndiaमराठी
56MarwariIndiaमारवाड़ी
57Min NanChina閩南語
58MoldovanMoldovaMoldovenească
59MongolianMongoliaМонгол
60MontenegrinMontenegroCrnogorski
61NepaliNepalनेपाली
62NorwegianNorwayNorsk
63OriyaIndiaଓଡ଼ିଆ
64PashtoAfghanistanپښتو
65Persian (Farsi)Iranفارسی
66PolishPolandPolski
67PortuguesePortugalPortuguês
68PunjabiIndiaਪੰਜਾਬੀ
69RajasthaniIndiaराजस्थानी
70RomanianRomaniaRomână
71RussianRussiaРусский
72SanskritIndiaसंस्कृतम्
73SantaliIndiaसंताली
74SerbianSerbiaСрпски
75SindhiPakistanسنڌي
76SinhalaSri Lankaසිංහල
77SlovakSlovakiaSlovenčina
78SloveneSloveniaSlovenščina
79SlovenianSloveniaSlovenščina
90UkrainianUkraineУкраїнська
91UrduPakistanاردو
92UzbekUzbekistanЎзбек
93VietnameseVietnamViệt Nam
94WelshWalesCymraeg
95WuChina吴语

Step 0 : Click on the “Translate values” pattern

Step 1 : Select the Akeneo instance to connect to

With your subscription, you can connect 1 production instance and as many staging instances as you need. Test your prompts before feeding your production !

Step 2 : Choose the right AI model you want to use

We regularly update our range of models, introducing new ones as well as enhanced versions.

Each model is unique and can be suited to different contexts. For instance, older models like GPT-3.5 Turbo, which are much more cost-effective, are particularly suitable for generating internal or low-visibility content (e.g., meta descriptions). In contrast, the latest models are recommended for creating high-quality content or handling a larger volume of data.

It’s important to note that models from GPT-4 Turbo and Google Gemini Pro onwards are clearly better in translation.

The choice of AI model to use is made directly by clicking on the model. It can be adapted for each pattern, making BeeApp highly flexible in terms of cost optimization and data quality.

Step 3 : Select the products to be enriched

This step is crucial because it allows you to choose the products you want to work on using static or dynamic filters.

  • Static Filters: You can select one or more specific products (product model and variant) by using their identifier.
  • Dynamic Filters: You can select products using various filters available in Akeneo, such as families, categories, and any text, number, date, or boolean attribute configured in your instance. If these attributes are localized or scoped, you can precise the locale & channels to use.

This feature is powerful because it lets you schedule regular executions. Therefore, any new product meeting these criteria will be included in the process defined in Step 4.

To use the filters, enter the attribute codes. An autocomplete feature is available: simply type the first few letters of the family, category, or attribute code to see the available options.

By combining different attribute values with families and categories, you can identify parts of your catalog and contextualize your new content more efficiently.

Example : I want to translate all my products of the family “Led TVs” (code : led_tvs) whose description (code of the attribute : description) is empty (for the locale fr_FR and the ecommerce channel)

After entering the code of the attribute, if the attribute does not exist in your Akeneo instance, an error message will be displayed under the input field.

💡The more precise you are, the better the content generated will be. That’s why we advise you to make small selections of products and to adapt specific content in step 3.

💡To avoid overwriting an existing value, remember to add a filter for the value to be enriched that is not empty.

Step 4 : Configure the content to translate

Enter the attribute code to translate.

💡 Only attributes of type “text” and “textarea” can be translated through this pattern.

Select the initial locale of the content to be translated. The list displayed corresponds to the locales configured in Akeneo.

Select the locales in which to translate the content. The list displayed corresponds to the locales configured in Akeneo. It is possible to select several locales if you want simultaneous translations.

In order to improve the quality of the translation (especially in the case of certain terms that may have several meanings), we recommend that you add the lexical field of the product or selection of products to be translated.

Example : Personal Protective Equipment, haberdashery, food, electronic, wheel and gear…

Custom instructions can be used to improve translation quality through additional instructions. For example, when translating from English into French, it may be appropriate to add a custom instruction indicating whether to translate “you” as “tutoie” or “vouvoie”.

In some cases, it may also be necessary to force the translation of certain terms into a specific locale.

It is now possible to force these translations by creating a glossary (To find out how to create a glossary, click here). Once a glossary has been created, you can select it directly from the drop-down list.

Loading a glossary increases the cost of input tokens. To limit this cost, don’t hesitate to create glossaries by product category, by locale… there’s no limit to the number of glossaries you can create with Bee.

Step 4 : Save and run

Before finalizing and executing your prompt, Bee specifies the number of products corresponding to your selection of products by separating the number of products and the number of product models.

You can save the pattern you have just configured in order to be able to program, in a second time, a recurrence of execution or a manual launch. All your saved patterns are accessible from the “Patterns” tab in the left menu.

This newly created prompt can be accessed from the “Patterns” link located in the left menu.