From setup to apply: store the provider, create a job, collect and translate, maintain the glossary, review and approve - and know what an error message means.
Shopware 6.7, PHP 8.2 or newer and your own API key with the AI provider of your choice. Scheduled runs need the Shopware message consumer; manual runs work without it.
Upload the ZIP in the admin under Extensions, install and activate it. Then enter the licence key; the check needs a shop domain configured in the sales channel.
All settings live in the admin module under the Plugin Suite. There is deliberately no config file.
Choose provider and model and store the API key. The connection test verifies both before the first run starts.
Available are OpenAI, Anthropic, Mistral and Google Gemini. Which model makes sense depends on volume and expectation - for catalogue text the faster models are usually enough.
First choose the sales channel. It deliberately comes first, because it determines which languages and which stock are available at all.
Then come scope and fields, followed by source and target languages as well as provider and model.
Collecting reads the source texts and creates them as individual items. Only then is it clear how many texts actually need translating.
Texts unchanged since the last run are identified by a checksum and not sent again. That saves cost and keeps already reviewed translations stable.
On start the items go to the model in batches. A window shows the progress with percentage, processed out of total items and the remaining count.
Manual runs are processed in short segments in the admin and need no running message consumer. Scheduled runs still use the queue because they have to work without an open admin.
A running job can be stopped with the cancel button in the progress window. The progress achieved so far is kept.
"Resume" continues the run later. This also applies to runs with the status Running, Ready or Translated that got stuck in an earlier version.
In the glossary you store terms that should stay identical in every language or be translated in a particular way - brand names, product designations, technical terms.
The entries are passed to the model with every request. That keeps the language consistent across all runs, even when the model changes in between.
Translated text first exists as a draft. You see source and translation side by side and can adjust individual texts before approving them.
Only applying writes the approved text into the Shopware translation tables. Until then nothing in the shop has changed.
Recurring runs can be scheduled, weekly for newly added articles for example. These runs go through the message queue and need a configured consumer.
Since version 1.8.0 the messages are phrased in understandable language, in German and English. Instead of a technical raw response it states what went wrong and where to check.
Recognised and named are, among others: missing or rejected API key, rate limit reached, provider fault, provider unreachable, unreadable model response and a mismatching number of returned texts.
Unknown messages are normalised to a single line and truncated after 120 characters so the view does not scroll horizontally.
Questions and requests come straight to us - support is from the developer. You can also request a feature through the Plugin Suite in the admin.
Every setting of the plugin with its default value and explanation, in the same order as in the administration. The texts come straight from the plugin (version 1.9.3).
Choose scope and languages. The translation runs in the background and is applied directly.
Limits the translation to one sales channel. For products, only products visible there are considered and the target languages are limited to the channel's languages. Without a selection all languages are available and the entire stock is considered.
What is translated: products, categories, manufacturers, properties or property values. For manufacturers only the description is translated; the name stays unchanged as a proper name.
The language translated from. Its texts serve as the source for all target languages.
One or more languages to translate into. The translations are saved directly under the respective language.
Which text fields of the chosen scope are translated, such as name, description or meta data. The choice depends on the scope.
Translate variants with their own texts in addition to the main products. Increases the volume considerably.
By default only texts that changed since the last translation are processed. Enable this when everything should really be translated again after a model or tone change. This costs the full amount.
Applies to this run only and takes precedence over the general rules. It also affects the preview so the result can be checked beforehand.
The service that translates the texts: OpenAI, Anthropic, Mistral or Google. The texts are sent to this provider. Test connection checks the access.
Access key for the chosen provider. Each provider has its own field; the key is kept when switching.
The model of the chosen provider. Without a selection the plugin uses the provider's default model.
Tone of the translation. Request bundling adapts automatically to the type of field.
Appended to the system prompt. Describes style and form of address, such as factual or informal.
Translate automatically at a fixed interval. Only changed texts are processed.
Requires a running Shopware scheduled task. Manual runs remain possible at any time.
How many hours pass between two automatic runs. Allowed range: 1 to 720.
The source language for the automatic runs.
Which scopes the automatic runs cover: products, categories, manufacturers, properties or property values.
All fields of the respective scope are processed.
Binding terms. Brand names can be excluded from translation.
The term in the source language that should get a fixed translation.
The binding translation of the term. Stays locked if the term should not be translated.
Which target language the entry applies to, or all languages.
For brand names and product lines that should stay identical in every language.
All prices net, plus VAT.
You buy the licence directly from us and receive an invoice from us. Installation by upload in the admin without SSH, updates through our licence platform, support straight from the developer.
The plugin will be listed in the official Shopware Community Store. Installation and automatic updates then run through the plugin manager in the backend, billing through your Shopware account. We will link it here as soon as it is available.