Where: open your Advice flow → Translations.
You do not need to duplicate an Advice flow for every language. One flow can show the same routes and matching with different text.
What do you want to translate?
| Content | Where to configure it |
|---|---|
| Questions, answers, intro and buttons | Translations in the Advice flow |
| Product titles, links and product values | A locale feed in Product data |
| The language you use in the app | Your own account settings |
Translating a question does not automatically translate products from your webshop.
1. Add a language
- Check the Source language. This is the language of the text in Builder.
- Click Add language and choose the language you need.
- Select that language and enter its translations.
- Check public labels, intro and recommendation labels as well as questions and answers.
- Save your changes.
Edit source text in Builder. Edit translated text under the relevant language in Translations.
2. Use AI if your plan includes it
AI translations use your account's monthly AI budget. Choose the action that fits your task:
- Auto-generate fields: fills missing translations and keeps existing text.
- Regenerate translations: translates again from the current source text and replaces existing translated fields after confirmation.
Rewritten a question or duplicated a flow? Filling missing fields does not update an existing translation. Edit it manually or regenerate it. Then check product names, specialist terms and tone.
3. Add product data for the language if needed
Open the connected dataset in Product data and add the new language's feed under locale feeds. Validate it and map the detected fields.
Product IDs must match the source feed. This tells BerryPath which translated title, price or product link belongs to each product. For answers sourced from product data, also map the relevant fields; matching uses source values while visitors see localized values.
After import, check coverage and any notices. A locale feed with different Product IDs cannot correctly translate the source products.
Use market feeds only when available for your account and you need separate prices, links or availability per market. The market code must match the code in the widget settings.
4. Publish and choose the widget language
Publish the Advice flow. In Share & Publish, select the desired language and copy the corresponding code or settings for your webshop plugin.
Test on the actual webshop page: are questions, buttons and product titles in the intended language, and do product links open the correct webshop?
Change the source language
Use Use as source when you want to write in another language from now on. Existing translations in that language become the Builder text; the previous source text remains as a translation. Review the content before publishing again.
You are ready when: the entire path, including products, works in the intended language. Problems? See the troubleshooting checklist.