FAQ

Short answers about the behaviour of the AI Translation Suite. If something does not operate correctly, start at Troubleshooting.

Does an uninstall delete my translations?

No. The extension stores everything that it writes as a native Shopware translation, and an uninstall never changes those records. Its own data is jobs, error rows, translation history, glossary, usage figures, change fingerprints and settings. The extension deletes that data only when you do not keep the user data during the uninstall.

What data leaves my shop?

Three things go to the provider that you selected for that run: the content that you selected for translation, the translation instructions, and the source locale and the target locale. The extension never selects order entities or customer entities for translation. Catalogue, CMS, mail-template, snippet and custom-field content can still contain personal or confidential data, therefore examine what you send. Data protection lists each destination, its operator and the condition under which the extension sends data.

Which languages are supported?

That depends on your provider and on your account with it. The extension has no language list of its own. It maps Shopware locales onto the language codes of each provider, which include pt-PT and pt-BR, Simplified Chinese and Traditional Chinese, and Norwegian Bokmål. Before a manual run, it warns you when it cannot map a locale for the selected provider. LLM providers receive the language as a name, which usually makes them the more flexible option for less common locales.

Can I control which fields the extension translates?

Yes, at two levels. For each job you select the content types in the wizard. For each content type you then set the scope, either All items or Only items without translation. You also decide whether the run includes the custom fields. The wizard has no field-by-field selector, therefore the run translates each eligible field of a selected content type. Globally, you keep a permanent list under Settings → Advanced → Excluded fields, and no job can override that list. To select a subset of individual fields, use options.fields on the job endpoint of the Admin API. The extension translates a custom field only when its definition is text or HTML and marks the field as translatable. See Supported content and the Settings reference.

Are my Shopping Experiences layouts safe?

The extension writes the translated text into the target language layer of the layout. It does not change the media references, the URLs, the colours, the CSS classes and the configuration keys. It never writes the locked system layouts of Shopware. This is still a bulk write. Test representative pages on a staging shop before a large run, and keep the translation history on as your rollback path.

Can I use modernice All-in-One and my own API keys together?

Yes. modernice All-in-One appears as one more provider in the list, and your own keys continue to operate beside it. Under Settings → Providers → Providers by target language you can route one target language through modernice All-in-One and another language through DeepL. You can also select a different provider for each individual job.

How accurate is the cost estimate?

The estimate is advisory, and a note in the wizard gives this warning: The estimate is based on sampling and may differ from the final result. For large sets, the extension measures a sample of your real content and extrapolates. In fill-missing mode, the run skips the fields that already have a translation, therefore the actual cost is frequently below the estimate. The authoritative number is the provider invoice, or the quota check of modernice All-in-One at request time. See Cost & usage.

Must I operate anything on my server?

Yes. The message queue workers and the scheduled-task runner are a hard requirement, because each translation goes through the background queue. Managed hosting usually has both of them already. On a self-hosted shop you set them up once, under a process manager. Nothing else is necessary: there is no separate service to host, and no cron job specific to this extension. See Requirements and Automation.

What happens if I edit a translation by hand?

The extension stores a fingerprint of everything that it writes. A current translation that no longer agrees with that fingerprint is a hand edit. The extension then skips the field, for as long as Protect manual edits is on. That protection is the default in each job, and it is always active for automation. For one manual run you can switch it off in the wizard.

Can I undo a translation run?

Yes, if the history recording was on during the run. You can revert a finished job as a whole from its detail page with Revert all translations. You can revert or re-apply individual fields from History. A guard protects the reverts: the extension skips a field that somebody changed after the translation. It keeps the history for the retention period that you configured, and the default is 30 days. See Translation history.

Does the extension operate with third-party CMS elements?

Usually, yes. The CMS walker recognises text by key names and value shapes. It therefore translates the text in compatible third-party elements together with the elements of Shopware. It does not detect an element that stores its text under an unusual key. Test such elements on a staging shop first.

How do I translate storefront snippets?

Select Storefront snippets as a content type in the wizard, exactly like products or categories. A snippet set must exist for the source locale and for the target locale. The extension reads from one set and writes into the other set, and it creates no set itself. If a set is missing, you get a pre-flight warning and the extension skips the snippets. The snippets that the extension writes carry NiceTranslate as their author. In the snippet administration of Shopware you can therefore separate them from your own snippets.