Each one traceable
Create the job, collect the source texts, send them to the model, review and approve the translations, write the approved text into the Shopware translations. You can stop between every step.
Translate Shopware automatically with AI Catalogue text in every language.
Choose the scope, set the languages, have it translated - and review every text before applying. With a glossary for fixed terms, a progress display for pausing and resuming, and a choice of four AI providers using your own access.
01
Videos
AI Translation Manager on video.
A short tour, recorded right in the Shopware admin and the shop.
02
What the plugin does
Translate catalogue text, under control.
A job defines what gets translated: scope, fields, source language, target languages, provider and model. From there it runs in five traceable steps - collect, translate, review, approve, apply. Nothing reaches the shop unchecked.
Nothing goes live unchecked
Translated text first exists as a draft. You see source and translation side by side, can correct it and then approve. Only applying writes to the shop.
Your own access, your choice
OpenAI, Anthropic, Mistral or Google Gemini, each with your own API key. You settle the cost directly with the provider; nothing is routed through our servers.
Terms stay as they should
Brand names, technical terms and fixed phrases can be stored in the glossary. They are passed to the model so they stay consistent across every language.
No translating twice
Source texts are identified by a checksum. Unchanged text is not sent again - that saves cost and keeps already reviewed translations stable.
Runs without the queue
Manually started runs are processed in short segments in the admin and need no running message consumer. Only scheduled runs use the queue, because they have to work without an open admin.
Pick fieldsper run
- Pick sales channel, scope and languages
- Tick fields like name, description and meta
- Check the preview, then translate
- Every run can be undone
New countriesLarge cataloguesGlossary for brandsRegular new items
Read the manual03
What it is for
Sell in several languages, without an agency.
A second language channel rarely fails on intent but on the text. With thousands of articles, manual work is not an option, and an agency bills per word.
The catalogue stands in days
Instead of translation projects running for months, a complete catalogue in another language comes together in manageable time - and you keep control over every text.
New articles follow along
When articles are added or texts change, the next run covers only those. The rest stays untouched.
Several shops, one tool
If you look after several channels or clients, you can define languages and stock per channel without building a separate process for each shop.
04
Settings
You define scope and tone.
The channel comes first because it determines which languages and which stock are available at all. Everything else builds on that.
What gets translated
Sales channel, stock and the fields to translate can each be set individually. That keeps a run manageable instead of moving the whole catalogue at once.
A bar instead of guesswork
A window shows the percentage, processed out of total entries and the remaining count. The list of runs is not reloaded continuously meanwhile, so the view does not jump.
Progress is kept
A run can be cancelled at any time. What has been achieved stays and can be continued later via "Resume" - including runs that got stuck in an earlier version.
Regularly without action
Recurring runs can be scheduled. They use the message queue because they have to work without an open admin.
Instead of raw responses
Error messages are phrased in understandable language, in German and English. Instead of a technical raw response it states that the API key was rejected, for example, and where to check it.
The common stumbling blocks
Missing or rejected key, rate limit reached, provider fault, provider unreachable, unreadable model response and a mismatching number of returned texts are all named explicitly.
05
Technical details
Clean Shopware integration.
Dedicated entities for jobs, items and glossary. Writing happens exclusively into the Shopware translation tables.
Compatibility
Your own AI access
You store your own API key for OpenAI, Anthropic, Mistral or Google Gemini. Nothing is routed through our servers, and the connection can be tested before the first run.
Large runs asynchronously
Extensive jobs are processed through the message queue. Manual runs work without it, so installations with no consumer configured can still use the plugin.
Licence check with grace period
The check is designed strictly. If the licence server is unreachable, a grace period applies so an outage on our side does not stop your operation.
No config file
All settings live in the admin module under the Plugin Suite. There is deliberately no config.xml, so nothing has to be maintained in two places.
06
Frequently asked
Frequently asked questions about the AI Translation Manager
Workflow, cost and translation quality.
How do I translate my Shopware catalogue automatically?
You create a job defining scope, fields, source and target languages. From there it runs in five steps: collect, translate, review, approve, apply. Only applying writes into the Shopware translation tables.
Does anything go live unchecked?
No. Translated text first exists as a draft. You see source and translation side by side, can correct it and then approve. Only approved items are applied.
Which AI providers can I use?
OpenAI, Anthropic, Mistral or Google Gemini, each with your own API key. You settle the translation cost directly with the provider; nothing is routed through our servers.
What does the AI Translation Manager cost?
Buying directly costs 9.99 euros net per month or 101.90 euros net per year. On top come your AI provider costs, which depend on text volume. All prices are net and exclude VAT.
Are brand names and technical terms preserved?
That is what the glossary is for. You store terms that should stay unchanged or be translated in a particular way. They are passed to the model with every request, keeping the language consistent across all runs.
Will texts be translated twice if I restart the job?
No. Source texts are identified by a checksum. Unchanged text is not sent to the model again, which saves cost and keeps already reviewed translations stable.
07
Availability
Through the store or directly from us.
Two routes, the same feature set - pick whichever suits your setup.
Available now
Monthly9,99 €
Best valueYearly101,90 €15 % cheaper
All prices net, plus VAT.
Download the free Plugin Suite and upload it in the admin, no SSH needed. It installs and updates the plugin with one click. You buy the licence directly from us, with an invoice from us and support straight from the developer.
In preparation
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.