Translation Cache
Every newly translated text is stored with target and source language in a local database table. If a later job contains the same text, the stored translation is used without consuming the DeepL quota.
Benefits
Section titled “Benefits”- Saves DeepL quota for recurring texts (e.g. identical descriptions across variants)
- Faster job runs, since repeated texts do not run through the API again
Management
Section titled “Management”- View and manage under Content > Translation with DeepL > Translation Cache
- The cache can be disabled per job using the “Ignore cache” option to force re-translation
- On complete uninstall the cache is removed; with “keep data” it is preserved
- The cache is bound to the target language, not the source field position: the same original is stored separately per target language.
- A glossary change does not alter already cached texts, see FAQ: Glossaries.
- The cache stores only text content that you translate via the plugin. No customer or order data is stored.