100% token protection
Every %1, %2 and %3 keeps its identity and occurrence count. Word order follows the target language, so a price never becomes an item count.
Adobe Commerce + Magento 2
Magento CSV translation for Adobe Commerce.
Translate the words. Protect the logic.
Translate Magento CSV dictionaries with human-level AI while keeping %1, %2 and %3 protected, CSV escaping valid, and module identifiers unchanged.
- 100% placeholder protection
- Strict CSV escaping
- Module-aware output
For Magento developers, enterprise agencies and multi-store teams.
A Magento_Checkout module exports en_US.csv. The file drops into Qopywriter.ai, where a translation stream runs alongside placeholder, CSV syntax and module-scope checks. The validated de_DE.csv moves into an Adobe Commerce deployment preview. A compilation warning changes to Dictionary Compiled - 0 Errors.
- 100%
- Positional placeholder protection
- 100+
- Target languages for your store views
- Same schema
- Original column count and order
The cost of a broken string
One missing %2.
A checkout nobody trusts.
Magento dictionaries are not plain copy. The source phrase is a lookup key; %1 and %2 stand in for live values, and scope fields tell a language-package workflow where a phrase belongs. Let a generic translator rewrite those and a simple locale update turns into a debugging ticket.
A dropped token breaks the message. A stray quote shifts the columns. A translated source key quietly sends the frontend back to English. Malformed rows bring language-package compilation exceptions and frontend rendering failures into the mix. Your team should be reviewing language, not rescuing a release.
For a scope-bearing row such as "Original text","Translated text",module, the rule is simple: translate the second field. Protect the contract around it.
What a generic text pass misses
Variable driftInvalid token
%1 → % 1
Unescaped quotesBroken syntax
"Click "Pay", now"
Translated module identifierWrong scope
Magento_Checkout → Magento_Kasse
Only the translation column gets new words.
Placeholders are data, not prose
Change the language.
Keep the contract.
Our Magento translation tool shields positional variables and scope before AI touches the text. The sentence gets new grammar. The file keeps its keys, token identities and column layout.
A scanner crosses a scope-bearing CSV row. Shields lock over %1, %2 and Magento_Checkout while the translation value changes from English to German. The German sentence places %2 before %1 without changing either token. The original phrase and module scope do not change.
English order:
%1 → %2
German order: %2 → %1
Same variables. Natural grammar.
CSV escaping, not guesswork
Fields are serialized as CSV, with embedded quotes escaped as "" and commas kept inside quoted values. Output remains headerless UTF-8, ready for your dictionary workflow.
Scope stays read-only
Original phrase keys, module identifiers and context-type columns are excluded from translation. A two-column dictionary or a scoped export keeps the structure you supplied.
Human-level commerce language
A valid dictionary should also sound right.
A credit memo is not store credit. Anyone who has worked on a Commerce implementation knows the difference. Our Adobe Commerce localization AI keeps that distinction in the target language, along with the vocabulary shoppers see in their cart, account and checkout.
E-commerce dictionary translation needs more than swapped words. The model writes natural sentences, moves protected variables to fit local grammar and maintains consistent customer-facing nomenclature across complex store views. “Wishlist” stays the same term from product page to account menu.
Small detail. Big difference. Customers should recognize your store in every language, not stop to decipher it.
Commerce terminology
en_US de_DE
| Source phrase / module | German translation |
|---|---|
Credit memoMagento_Sales |
Gutschrift |
Store creditMagento_CustomerBalance |
Kundenguthaben |
SubtotalMagento_Quote |
Zwischensumme |
WishlistMagento_Wishlist |
Wunschliste |
Your repository. Your release.
Translate Magento 2 language files
in three controlled steps.
Keep the workflow you already use. Qopywriter handles dictionary translation and integrity checks; your team owns the Magento deployment.
Collect and upload
Start with an existing module or theme dictionary, or collect phrases with the Magento CLI. Upload the CSV rather than pasting its rows into a chat window.
i18n/en_US.csvChoose the target language
Match the language to your store-view locale. AI translates the value fields, then integrity checks compare token identities, occurrence counts, CSV syntax and scope with the source.
en_US → de_DEDownload. Test. Commit.
Save the validated dictionary in the correct module or theme directory. Deploy the target locale in staging and check cart, account and checkout strings with real dynamic values.
i18n/de_DE.csvKeep the format your workflow expects.
Adobe’s dictionary reference (opens in a new tab)
Native module and theme dictionaries use two columns. Magento’s i18n:collect-phrases -m output adds separate context-type and context-value fields, such as module,Magento_Checkout. Qopywriter preserves the supplied layout instead of flattening scope metadata into translated text.
Native dictionary / de_DE.csv2 fields
"Click ""Continue"", then pay","Klicken Sie auf ""Weiter"" und bezahlen Sie anschließend."Scoped collection / -m4 fields
"Add %1 items to cart for %2","Legen Sie für %2 insgesamt %1 Artikel in den Warenkorb.",module,Magento_CheckoutPricing
Start with one dictionary.
Plan for every store view.
Test CSV translation for Adobe Commerce on the free trial. Choose a character allowance for your release cycle, with placeholder and CSV protection on every plan.
Monthly billing
Lite
$9/ month
400,000characters per month
- Advanced AI translation
- Placeholder and module protection
- CSV syntax validation
- 100+ languages
Monthly billing
Starter
$19/ month
1,000,000characters per month
- Advanced AI translation
- Placeholder and module protection
- CSV syntax validation
- 100+ languages
Monthly billing · For teams
Business
$49/ month
3,000,000characters per month
- Advanced AI translation
- All CSV integrity checks
- Unlimited team members
- Priority support
Annual billing
Yearly
$169/ year
12,000,000characters per year
- Advanced AI translation
- All CSV integrity checks
- Unlimited team collaboration
- Priority support
Developer questions
Answers for the people shipping the locale.
File structure, positional variables, store-view deployment. Get the details before your next language release.
Talk to supportWhat does this Magento translation tool change?
Qopywriter translates the value column of your CSV dictionary. Original source phrases remain lookup keys, positional placeholder identities and counts are protected, and module or context columns stay outside the editable text. The output is serialized as CSV, not returned as a block of chat text.
Will %1 and %2 stay correct if the sentence order changes?
Yes. Protection applies to the token’s identity and occurrence count, not its absolute position in the sentence. A German translation can place %2 before %1 when the grammar calls for it. Each token still refers to the same dynamic value. The same rule applies to %3 and repeated positional placeholders.
Which Magento CSV structures are supported?
Standard two-column module and theme dictionaries, plus scope-bearing translation exports. The input field count, column order and metadata are preserved. Magento’s i18n:collect-phrases -m format stores context type and context value in separate columns, such as module and Magento_Checkout; those fields remain read-only.
How are commas, double quotes and encoding handled?
CSV serialization keeps commas inside quoted fields and escapes literal double quotes by doubling them. The downloaded dictionary uses UTF-8, preserving accents and non-Latin scripts without adding a header row. Field boundaries are checked separately from linguistic translation.
Does this also translate product imports and CMS content?
This workflow handles Magento phrase dictionaries: module and theme labels, checkout strings, validation messages and other translatable interface phrases. Product-import CSVs, catalog descriptions and CMS blocks use different content workflows. Store-view locale settings are configured separately in Adobe Commerce.
How do I deploy the translated language file?
For a module dictionary, save the file under its i18n directory with the correct locale filename, for example app/code/Vendor/Module/i18n/de_DE.csv. Theme dictionaries belong in the theme’s i18n directory. Scoped language-package exports follow your Magento package-building workflow.
Commit the file, deploy the target locale in staging, refresh the translation cache and test the selected store view. Check dynamic values in cart totals and validation messages, not just static menu labels.
Why does a valid dictionary still show English on the storefront?
Check the exact source phrase first, including punctuation and spacing. Then confirm the dictionary’s locale, its module or theme location, and the store-view locale. Look for higher-priority translation overrides, clean the translate cache, and redeploy locale-specific static assets for JavaScript strings. Inspect js-translation.json if only browser-rendered phrases remain in English.
Can our team test a CSV before paying?
Yes. The free trial includes a limited character allowance for testing. Upload a representative dictionary with positional placeholders, embedded quotes and module context. Inspect the returned CSV, then run it through a staging store view before choosing a paid plan.
Build your next store view
Your next locale.
Not your next hotfix.
Bring a Magento CSV. Get back natural language with protected placeholders, valid escaping and the same module structure. Put your first dictionary through the pipeline.