Connect Magento
Import Magento (Adobe Commerce) product copy into transglot and publish reviewed translations into each language's own store view.
| Direction | Two-way |
| Imported | Product name, description and short description, read from your source store view |
| Written back | The same fields in each target store view you map. The source store view is never written |
| Sync | Sync from CMS |
| Per sync | Up to 2,500 products |
| Plan | Starter and above |
Before you start
- Create a store view for each target language in your store configuration.
- Create an integration in Magento's integration settings and activate it to get an access token with catalog read and write access. An admin token also works.
- Your store must be reachable over https at a public address.
Connect
Open your project's settings, choose CMS, and pick Magento in the CMS list.
| Field | What to enter |
|---|---|
| Magento store URL | Your Magento host, for example https://shop.example.com. transglot adds /rest/{storeView}/V1/… itself |
| Source store-view code | The store view that holds your source-language content. Leave it as default for most stores |
| Access token | The integration access token |
| Content types | products |
| Translatable fields | Any of name, description, short_description |
| Locale → store view | For each target language in your project, its Magento store-view code, for example fr_fr |
| Publish these locales | The target languages to write back |
Select Connect, then Test connection. The test runs a minimal product search, which checks both the address and the token.
What gets imported
transglot reads every product from the source store view, by SKU, and imports the mapped fields. name is the product's own field; description and short_description are read from its custom attributes. A product whose SKU contains a colon (:) is skipped.
How translations are written back
For each target language, transglot writes the reviewed values to the product in that language's mapped store view. A store-view value overrides only that scope, so your source store view keeps its content.
- A language with no store view under Locale → store view is skipped.
- A language mapped to the source store view is skipped.
- The reserved scopes
allandadmincannot be used as targets.
Troubleshooting
That URL did not return a Magento store (the products search was missing).The address is not the Magento REST API root.... the credentials were rejected.The token is wrong, the integration is not active, or it lacks catalog access.... the store, store view or product was not found, check the URL and store-view codes.Check Source store-view code and the codes under Locale → store view.- A language never receives translations: check it has a store-view code mapped and is ticked under Publish these locales.