How to Use DeepL Translation Service with Transcy
Unlock premium translation quality for your global store. DeepL is renowned for producing some of the most accurate and natural-sounding translations available, and you can integrate it directly into your Transcy workflow. Available for Continental, Cross-border, and Global plan subscribers, DeepL integration brings professional-grade translation quality to your multilingual store.
Table of Contents
I. Understanding DeepL Integration
II. Getting Your DeepL API Key
III. Setting Up DeepL in Transcy
IV. Using DeepL for Content Translation
VI. Comparing Translation Quality
VII. Troubleshooting and Support
I. Understanding DeepL Integration
DeepL is an AI translation service known for accuracy and natural language flow. By connecting DeepL to Transcy, you can translate your storefront with a service many merchants find produces more fluent output than general-purpose engines, particularly for European language pairs.
This integration expands Transcy's translation toolkit, which also includes Google Translate, OpenAI, Baidu, and Gemini. DeepL is especially strong at preserving context and tone, which helps product descriptions and marketing copy read as though they were written natively.
II. Getting Your DeepL API Key
1. Choosing the Right DeepL Plan
To use DeepL with Transcy, you need a DeepL API plan. DeepL currently offers three:
Plan | What you get | Best for |
|---|---|---|
API Developer | Up to 1,000,000 characters in total — this is a lifetime allowance, not monthly, and it does not reset. No speech-to-text. | Testing the integration before committing |
API Growth | Fixed monthly or yearly price with an included character allowance; usage above the allowance is billed on top. Monthly billing includes 1 million characters; yearly billing includes 12 million characters. Monthly ceiling of 50 million characters. | Most production stores |
API Enterprise | Custom character commitments arranged with DeepL's sales team. | High-volume catalogs and long-term projects |
You can register or compare plans at DeepL API pricing.
A note on the Developer plan: 1,000,000 characters sounds generous, but a full store translation consumes characters quickly — a mid-sized catalog with product descriptions, collections, and theme content can exhaust the entire allowance in a single translation run. If you intend to translate your whole store, start on Growth.

2. API Key Generation Process
Once your DeepL API subscription is active:
- Access Your DeepL Account: Log in to DeepL, then click the "Account" button at the bottom left
- Navigate to API Keys: Open the "API Keys & Limits" section at the top of the page
- Copy Your Key: Copy your API key — you'll need it for the Transcy setup below
Security Tip: Treat your API key like a password. Don't share it publicly, and don't include it in screenshots you send to support.

3. Setting a Cost Control Limit
Before you run your first large translation, set a spending cap in DeepL. All API plans let you define a maximum monthly cost limit and per-key usage limits in the same "API Keys & Limits" area.
This is worth doing on day one. Translating a large catalog is a single click in Transcy but can represent millions of characters at DeepL, and DeepL — not Transcy — bills you for that usage.
III. Setting Up DeepL in Transcy
1. Configuration Steps
Integrating your DeepL API key with Transcy:
- Access Account Settings: Navigate to Account & Settings in your Transcy
- Open Localization Settings: Select "Localization setting" from the menu options
- Enter API Key: Locate the DeepL Integration API key field and paste your copied key
- Configure Translation Preferences: Choose your preferred translation tone
- Save Configuration: Click "Save" to activate DeepL integration
Troubleshooting: If you run into issues during setup, Transcy support may ask for temporary access to your DeepL account to investigate the configuration.

2. Translation Tone Selection
DeepL can adjust how formal or casual the translated text sounds:
- Formal: Professional, business-appropriate language
- Casual: Conversational, friendly tone
- Creative: Expressive, engaging language style
Select the tone that best matches your brand personality and your target market's expectations.
IV. Using DeepL for Content Translation
Once configured, using DeepL for translation is seamless:
→ Go to the "Content translation" section in your Transcy app
→ Choose the "Markets" you want to control translation for first
→ Then choose the "Language" at the line "Translate to:"
→ Select the content sources you want to translate
→ Click "Translate with AI" to open the engine list
→ Choose the "DeepL" engine
→ You can control which market to translate by selecting "Select Market" and choosing your target language market
→ Press "Translate now"
Before you can translate into a language with DeepL, that language must be set as "editable" in your Transcy. If your target language is currently "non-editable", switch it first. Learn how to switch from non-editable to editable language here.

V. DeepL Language Support
There are two lists to be aware of, and they are not the same:
- What DeepL supports: more than 120 languages and language variants, with nearly all of them usable in both directions. The authoritative, searchable list is on DeepL's documentation.
- What Transcy supports with the DeepL engine: the subset below. If a language is missing here, that's a Transcy limitation, not a DeepL one.
Source languages (translate from): Arabic, Bulgarian, Chinese (simplified), Czech, Danish, Dutch, English, Estonian, Finnish, French, German, Greek, Hungarian, Indonesian, Italian, Japanese, Korean, Latvian, Lithuanian, Norwegian (Bokmål), Polish, Portuguese, Romanian, Russian, Slovak, Slovenian, Spanish, Swedish, Turkish, Ukrainian
Target languages (translate to): Arabic, Bulgarian, Chinese (simplified), Czech, Danish, Dutch, English (American), English (British), Estonian, Finnish, French, German, Greek, Hungarian, Indonesian, Italian, Japanese, Korean, Latvian, Lithuanian, Norwegian (Bokmål), Polish, Portuguese (Brazilian), Portuguese (European), Romanian, Russian, Slovak, Slovenian, Spanish, Swedish, Turkish, Ukrainian
Target-only language variants
These 11 codes can only be used as a target language, not as a source. Use the base language as your source — for example, source EN with target EN-GB.
Code | Language |
|---|---|
ZH-HANS | Chinese (simplified) |
ZH-HANT | Chinese (traditional) |
EN-US | English (American) |
EN-GB | English (British) |
FR-CA | French (Canadian) |
FR-FR | French (France) |
DE-DE | German (Germany) |
DE-CH | German (Swiss) |
PT-BR | Portuguese (Brazilian) |
PT-PT | Portuguese (European) |
ES-419 | Spanish (Latin American) |
Not every language supports every feature
Translation itself is available for all supported languages, but DeepL's customization features cover a narrower set. This matters if you rely on brand-term consistency:
- Full-feature languages (glossaries, translation memory, and style rules): Arabic, Bulgarian, Chinese, Czech, Danish, Dutch, English, Estonian, Finnish, French, German, Greek, Hebrew, Hungarian, Indonesian, Italian, Japanese, Korean, Latvian, Lithuanian, Norwegian (Bokmål), Polish, Portuguese, Romanian, Russian, Slovak, Slovenian, Spanish, Swedish, Thai, Turkish, Ukrainian, and Vietnamese — plus the target-only variants listed above. Thai is the one exception in this group: it supports translation memory and style rules but not glossaries.
- All other supported languages: translation only, with no glossary, formality, or style rule support.
VI. Comparing Translation Quality
If you want to get a feel for DeepL's output before translating your whole store:
- Access DeepL Directly: Visit DeepL Translator and log in
- Test Sample Content: Paste in a representative product description
- Select Matching Settings: Choose the same source and target languages, and the same tone
- Review the Output: Read it as a native speaker of that market would
Report a problem to support when you see an actual failure, not merely different phrasing:
- Text that came back untranslated, or in the wrong language
- Broken HTML, missing formatting, or mangled Shopify placeholders and variables
- Translation that reverses or clearly distorts the meaning of the source

VII. Troubleshooting and Support
Common Issues and Solutions
Invalid API key: Make sure your key comes from a DeepL API plan — Developer, Growth, or Enterprise. Keys from a DeepL Translator or Translator + Write subscription will not work, because those plans don't include API access.
Translation stops partway, or returns a quota error: Check your remaining allowance in your DeepL account under "API Keys & Limits". On the API Developer plan, the 1,000,000-character allowance is a lifetime total that does not reset — once it's used up, translation stops until you upgrade to API Growth. Also check whether you've hit a cost control limit you set earlier.
Tone setting has no effect: DeepL's formality control only applies to certain target languages. See Translation Tone Selection above.
Target language not available: Confirm the language is set to "editable" in Transcy, and check DeepL's supported languages list. If DeepL doesn't cover the language or variant you need, you can use one of the other translation engines available in Transcy.
Getting Help
DeepL-specific issues: For DeepL account registration, billing, API plan questions, quota, or language availability, contact DeepL support directly.
Transcy integration issues: For problems with the DeepL integration inside Transcy — setup difficulties, engine errors, or unexpected translation behavior — reach out through LiveChat in your Transcy app or email support@transcy.io.
Conclusion
DeepL gives your store access to a translation engine trusted for its fluency, and pairing it with Transcy's localization tools lets you apply that quality across your entire storefront. Set a cost control limit before your first large translation run, confirm your target languages are supported and editable, and you're ready to go.
If you need further assistance, contact us via live chat or email support@transcy.io.
Updated on: 29/07/2026
Thank you!