Translate where you already edit.
Automatic translation in the translation view
When something changes in your catalog, it should be right in the other languages too. With this OPAL, you translate a field from the base language into the target language at the click of a button – via the centrally configured AI Connector. The suggestion is only applied when you save, so you review it first.
What this OPAL does for you
You translate individual fields at the click of a button, directly in the translation view – even for small changes.
You set up access and model for the AI once, centrally in the AI Connector; this OPAL uses them as well.
If no AI access is set up, only automatic translation is off – you keep translating manually as usual.
Prerequisite
This OPAL builds on two other OPALs, which must be active for it: the AI Connector OPAL, where you set up the provider, model and API key centrally, and the Translation Management OPAL, which provides the translation view. For automatic translation, a valid API key must be stored in the AI Connector.
Part of the OPAL family
OPALs are building blocks from OXID eSales: a proven foundation that is adapted to your IT landscape and integrated into your store.

Features at a glance
OXID
<OPAL/>
Translate where you maintain texts
This OPAL adds automatic translation to Translation Management: a field is translated from the base language into the target language at the click of a button. The suggestion appears in the target language field and is only applied when you save.
Set up access once, centrally
You maintain the provider, model and API key only in the AI Connector, and all AI OPALs share them. This OPAL has no settings of its own for this.
Simply switched off without access
Automatic translation is active when this OPAL is enabled and a valid API key is stored in the AI Connector. Otherwise, its buttons are grayed out – without an error message, and the translation view remains usable as usual.
Field by field
The field you are currently editing is always the one that gets translated, and the result comes back right away. Empty fields are never sent to the AI in the first place.
Builds on the AI Connector
The AI Connector establishes the connection to the AI provider. This OPAL uses it as well – if you switch providers, you do so in one place in the AI Connector.
Extends Translation Management
This OPAL registers with Translation Management as an additional translation service. Your familiar workflows stay as they are, and Translation Management remains fully usable even without AI access.
Note on data transfer
The texts to be translated are sent to the AI provider you set up in the AI Connector. For this provider, you need a data processing agreement (Art. 28 GDPR) and, for providers outside the EU, a legal basis for transfers to third countries. The fields translated are usually catalog texts, CMS content and language strings; if a field contains personal data, you document the transfer accordingly. Machine translation of legal texts does not replace a legal review. The legal assessment remains with you.
Who is this OPAL for?
Your store speaks several languages
Your catalog changes all the time, and every change should be right in the other languages too.
How it helps
You translate the changed field from the base language into the target language at the click of a button – exactly where you edit it anyway. The suggestion appears in the target language field; you review it and apply it when you save.
Frequently asked questions
Price
€20/month
OPALs are also available in subscription packages.
