Connect WooCommerce
Import WooCommerce product and category copy into transglot and publish reviewed product translations back to your store.
| Direction | Two-way for products. Categories are imported but not written back |
| Imported | Name, description and short description of products; name and description of categories |
| Written back | One translation bundle per product, in the _transglot_translations product meta. The product's own fields are never written |
| Sync | Sync from CMS |
| Plan | Starter and above |
Before you start
- In WooCommerce's advanced settings, create a REST API key with Read/Write permission and copy the consumer key and consumer secret.
- Your store must be reachable over https at a public address.
Connect
Open your project's settings, choose CMS, and pick WooCommerce in the CMS list.
| Field | What to enter |
|---|---|
| WooCommerce store URL | Your store root, for example https://store.example.com. transglot adds /wp-json/wc/v3/… itself |
| Consumer key & secret | The key and secret joined by a colon: ck_…:cs_… |
| Content types | products, categories, or both |
| Translatable fields | Any of name, description, short_description |
| Publish these locales | The target languages to write back |
Select Connect, then Test connection. The test checks that the address is a WooCommerce store and names it.
What gets imported
transglot reads the store's own (native) fields for each product and category. Categories have no short description, so that field is skipped for them.
How translations are written back
WooCommerce has no built-in place for per-language product text, so transglot writes every reviewed target language into one meta key it owns on each product, _transglot_translations, shaped as language, then field, then value. It writes only that key, so the name, description and short description you wrote are never changed.
Your theme or headless front end reads the bundle from product meta (for example with get_post_meta()). The leading underscore keeps the key out of the product's Custom Fields panel.
Product categories have no meta channel in the WooCommerce REST API, so category translations are skipped at publish time with WooCommerce categories require a term-meta capable endpoint; the translation was skipped. This is expected and does not stop the rest of the publish.
Troubleshooting
That URL did not return a WooCommerce store (the wc/v3 system status was missing).The address is not a WooCommerce store, or its REST API is blocked.... the credentials were rejected.The key or secret is wrong, or the key is read-only.... the endpoint was not found, check the store URL.Check WooCommerce store URL is the store root.... the store is rate-limited, retry.Wait and run the sync or publish again.