This guide is for stores whose catalog lives outside WordPress: in a spreadsheet, a PIM, an ERP or a supplier feed. Products reach WooCommerce by an importer, the REST API or a scheduled job, and you rarely open the product editor.
You need WPML, WPML Multilingual & Multicurrency for WooCommerce and, for imports with translations, WPML Export and Import.
Part 1. How a Multilingual Store Managed from Outside Works
One Product per Language, Linked by a Translation Group
Each language has its own WooCommerce product, with its own ID. WPML links the languages in a translation group. The original is the product in your store's default language; the other languages are its translations.
In our example store, the Zip-Up Hoodie is product 14 in English, 121 in German and 122 in French. Every REST API answer for any of them carries the same map: "translations": {"de":"121","en":"14","fr":"122"}.
- The SKU is the same in every language. A variable product's variations keep the same variation SKUs too.
- The SKU is the key for your external system. WooCommerce's own lookup,
wc_get_product_id_by_sku(), returns the original product, not a translation. - Lists return one language at a time.
GET /wc/v3/products?sku=HP-HD-ZIPreturns the default language only. Add&lang=defor one language, or&lang=allfor every language.
What WPML Copies to Every Language and What It Translates
When the original product changes, through the product editor, a CSV import or the REST API, WPML copies these values to every translation:
- Regular price and sale price
- Stock quantity and stock status
- SKU, weight and dimensions
- Product image and gallery (each language gets its own copy of the image)
- Categories and tags (as the translated category or tag)
- Upsells and cross-sells (pointing to the product in the same language)
- Publishing status
- For variable products: each variation's price and stock, the price range, a new global attribute term (as its translation, for example Schwarz and Noir for Black) and a new variation
These stay different in each language, because they are translated:
- Name, description and short description
- Slug (the product's address, for example
/de/produkt/kapuzenjacke-mit-reissverschluss/) - Attribute terms, such as Blue, Blau and Bleu
- Values of product-specific attributes, such as a "Material" set only on this product
Stock is shared by all languages.
Write prices and attributes to the original. If your system writes a price or attributes to a translation, the translation keeps the original's values. Stock written to any language becomes the stock of every language, because it is shared.
Prices in a second currency also follow the original (see multicurrency for WooCommerce). Set them on the original, with custom_prices in the REST API ("custom_prices": {"USD": {"regular_price": "55.00", "sale_price": "49.00"}}) or with the CSV columns Meta: _wcml_custom_prices_status, Meta: _regular_price_USD, Meta: _sale_price_USD and Meta: _price_USD. Every language then shows those prices in that currency.
custom_prices is stored when multicurrency is on and the currency is one of your store's currencies. Send it as follows:
- Turn on multicurrency first. Go to WPMLSettingsMulticurrency, tick Enable the multicurrency mode and click Save changes. Under Show currencies based on, choose an option (for example Site Language) and click Save changes. Then add each currency with Add currency. With multicurrency off, WPML stores nothing from
custom_prices. - Use your store's currency codes. WPML stores the prices of the store's currencies only. A price in any other code is not stored.
- For a variable product, send
custom_priceson each variation, not on the parent. WPML stores it on the original variation, and every language shows it. Sent on the parent, it is not stored. - Read the stored prices from
meta_data(_regular_price_USD,_sale_price_USD,_price_USD). The answers to REST calls do not include acustom_pricesfield.
Duplicates or Independent Translations
WPML has two kinds of translated product. Which one you have decides what happens to text you import.
| Duplicate | Independent translation | |
|---|---|---|
| What it is | A copy that WPML maintains | A translation with its own text |
| Text after the next save of the original | Replaced by the original's text | Kept only with Translate Everything off or with Products set to None |
| Price and stock | Follow the original | Follow the original |
- Where you see it: a duplicate's Language box reads "This document is a duplicate of ... and it is maintained by WPML." with the button Translate independently.
- Turning duplicates into independent translations: click Translate independently in the duplicate's Language box, or, for many products, go to ProductsAll Products, switch to the translation's language, tick the products and choose Bulk actionsTranslate independently.
- What the processes in Part 2 create: Process A creates translations with Translate Everything. Process B imports independent translations. Neither needs duplicates.
Set Up the Store Before the First Product Arrives
- Run the WooCommerce Multilingual setup wizard. It opens when you activate WPML Multilingual & Multicurrency for WooCommerce. Its screens are Store Pages, Global Attributes and Multiple Currencies. The first creates Shop, Cart, Checkout and My account in every language.
- Make your global attributes translatable. On the wizard's screen "Which product attributes should be translatable?", tick each attribute, for example Color and Size. Later, the same setting is the Translatable? checkbox under ProductsAttributesEdit.
- Translate the attribute terms before the products. Go to WPMLTranslations, open the Taxonomy tab, choose the attribute under "Select the taxonomy to translate" and translate each term. With Translate Everything on (Process A), WPML translates new terms for you.
Part 2. Build It without Code
Choose Your Process: One Language or Every Language
| Process A: WPML translates | Process B: you import every language | |
|---|---|---|
| What your system holds | The store's default language only | Every language |
| What you import | Original products | Originals and their translations, linked by SKU |
| Who translates | Translate Everything, with Private Translation Cloud (PTC) (opens in a new tab) | Your translators, before the import |
| When an original's text changes | Translate Everything translates the change | WPML marks the translation as needing an update; your next file brings the new text |
| Prices and stock | Follow the original | Follow the original |
Process A suits a store that keeps one language and wants every other language without translation files. Process B suits a store whose PIM or translators already hold the texts in every language.
Process A with the WooCommerce CSV Importer or WP All Import
Turn on Translate Everything once:
- Go to WPMLTranslations and click Set up Translate Everything.
- Choose the content. Under "Content to Translate", keep All products and click Continue.
- Choose how translations publish. Under "Publishing method", keep Publish without review.
- Click Enable Translate Everything Automatically.
Import your products in the store's default language only. Use ProductsImport (WooCommerce's CSV importer) or All ImportNew Import (WP All Import with its WooCommerce add-on). Your file needs no WPML columns.
The import itself queues the translations. WPML then translates every product, variation, category and new attribute term into each language and publishes them. You start nothing by hand, and no WPML admin page needs to be open. You can follow the progress under WPMLTranslations.
When you edit an original, Translate Everything translates only what changed. The rest of the translation stays word for word.
Translate Everything translates published products, including external products. It does not translate private products. Drafts wait too: Translate drafts automatically (under WPMLSettingsAI Translation, in the Advanced Translation Editor box) is off by default, and when you turn it on, WPML translates a draft only when you save it again. To translate drafts and private products, send them from WPMLTranslations (see Troubleshooting).
If you want to change a translation, open it from the product's Language box (Edit the ... translation), edit it in the Advanced Translation Editor and click Save and Complete. When the original changes later, your edit of the unchanged sentences stays.
Process B with the WooCommerce CSV Importer
In Process B, your file carries every language.
Set Translate Everything for imported translations before the first import:
- Go to WPMLTranslations. If Translate Everything is off, leave it off and go on to the file.
- If you want WPML to translate your pages, posts and strings automatically, click Set up Translate Everything. Under "Content to Translate", set Products to None. Click Continue, keep Publish without review and click Enable Translate Everything Automatically.
- If Translate Everything is already on, click the three-dot menu in the "Translate Everything Automatically is enabled" box, choose Adjust content limits, set Products to None and click Save changes. Translations already in progress still finish.
With Products set to None, WPML keeps your imported product translations word for word. When an original changes, WPML marks its translations as needing an update, and your next file brings the new text.
Prepare one file with all languages. Use WooCommerce's normal columns and add four WPML columns:
| Column | What it holds | Example |
|---|---|---|
Meta: _wpml_import_translation_group | The value that links the languages. Use the SKU. | HP-JK-SHELL |
Meta: _wpml_import_language_code | The row's language | de |
Meta: _wpml_import_source_language_code | The original's language, which is the store's default language. Empty on original rows. | en |
Meta: _wpml_import_after_process_post_status | The status after WPML links the products | publish |
- Order the rows by language, originals first. In each language, products come before their variations.
- Import products as drafts:
Published=-1on products,1on variations. - Give each language its own texts: names, descriptions, categories (
Kleidung > Jacken) and attribute values (Blau, Grün). - Keep the store's attribute names (
Color,Size) in every language. Translate the attribute labels under WPMLTranslationsTaxonomy. - Give related products and parents by SKU, the same SKU in every language.
A German row of a variable product from our example file:
Type,SKU,Name,Published,...,Categories,...,Parent,Attribute 1 name,Attribute 1 value(s),...,Meta: _wpml_import_translation_group,Meta: _wpml_import_language_code,Meta: _wpml_import_source_language_code,Meta: _wpml_import_after_process_post_status
variable,HP-JK-SHELL,Verstaubare Regenjacke,-1,...,Kleidung > Jacken,...,,Color,"Blau, Grün",...,HP-JK-SHELL,de,en,publish
variation,HP-JK-SHELL-BLU-S,,1,...,,...,HP-JK-SHELL,Color,Blau,...,HP-JK-SHELL-BLU-S,de,en,publishImport it:
- Go to ProductsImport and choose the file under "Choose a CSV file from your computer:". Leave Update existing products unticked. Click Continue.
- Check the mapping. The four
Meta:columns map to Import as meta data. Click Run the importer. - Go to WPMLExport and Import. The screen reads "Good job. We see 33 posts that are imported and need language information." Click Run WPML Import.
- Wait for "Multilingual Import Complete".
Until step 3, every product is an English draft and every variation an English variation, none of them linked to its original. After it:
- Each product and each variation is linked across its languages.
- Everything is published.
- The translations are independent translations.
- Categories and attribute terms are linked across languages, and each language's variations use its own terms.
- Upsells point to the product in the same language, and each language has its own copy of the images.
Categories and attribute terms travel inside the product rows, so this importer needs no separate taxonomy import. If translated attribute terms already exist in the store, the importer uses them, and Run WPML Import connects them to their originals.
To have WPML translate chosen products automatically while Products is set to None:
- Keep Translate Everything on.
- Add the column
Meta: _wpml_import_teato the file, with the value1on each product to translate. - Keep
Meta: _wpml_import_translation_groupin the same file. - Import the file, then go to WPMLExport and Import and click Run WPML Import. The progress list shows "Sending Posts for Automatic Translation", and WPML translates and publishes those products.
Process B with WP All Import
You need WP All Import Pro and its WooCommerce add-on. The free edition does not import custom fields, and the WPML columns are custom fields.
The working order is: attribute terms first, with their translations connected, then the products. Translated product pages then offer each attribute value in their own language, for example Bleu marine and not Navy.
- Connect the translated terms the store already has. For each translated attribute term that already exists in the store, go to ProductsAttributes, click Configure terms for the attribute, switch the admin bar to the term's language and click the term's name. In the Language box, choose its original under This is a translation of and click Update. Each connected term then shows a pencil under its language on WPMLTranslationsTaxonomy.
- Set the admin language to the store's default language in the admin bar's language switcher before you run the imports.
- Import the categories. All ImportNew ImportUpload a file, choose TaxonomiesProduct categories. Under Term Meta, add three rows:
_wpml_import_language_code,_wpml_import_source_language_codeand_wpml_import_translation_group, each mapped to the file's column of the same name. Set the parent under Other Category OptionsParent Term. - Import the attribute terms the same way, for example TaxonomiesProduct Color, with the same three Term Meta rows.
- Connect the terms. Go to WPMLExport and Import and click Run WPML Import. Check under WPMLTranslationsTaxonomy (choose the taxonomy in "Select the taxonomy to translate") that each term has one row with a pencil under each language's flag. Hover a pencil to see the translated name. A "+" means that language has no translation. A translated term listed in its own row is not connected.
- Import the products. Choose WooCommerce Products. In the WooCommerce Add-On section, map SKU, prices, stock and attributes. Under Custom Fields, add the three
_wpml_import_*rows. - Run WPML Import again, and wait for Multilingual Import Complete.
Our example term file:
name,_wpml_import_language_code,_wpml_import_source_language_code,_wpml_import_translation_group
Navy,en,,color-navy
Marineblau,de,en,color-navyTwo settings for a product file that holds every language:
- Variation rows carry the type
variable, the same as their parent, in the column you map to Set Product Type With XPath. - Link variations to their parent with a per-language key. Under Variations, choose All my variable products have SKUs or some other unique identifier... and map SKU element for parent and Parent SKU element for variation to a key such as
HP-OW-RAIN-de. Map the real SKU, the same in every language, to GeneralSKU and to the translation group. The other way is one import per language file.
This order works whether you start the WP All Import imports from wp-admin, from WP-CLI or on a schedule.
Update Stock and Prices on a Schedule
Update the original products. WPML copies stock and prices to every language right away.
With the WooCommerce CSV importer:
- Send only the columns you change. A column with an empty cell writes an empty value. Our example file:
SKU,Stock,Regular price,Meta: _wpml_import_language_code HP-JK-FIELD,11,95,en HP-JK-SHELL-BLU-S,5,72,en - Add
Meta: _wpml_import_language_codewith the original's language on every row. Then each row updates the product in that language, the original. Without the column, a row updates the product in the admin's current language, so the result depends on the admin language switcher. - Set the admin language to the store's default language in the admin bar's language switcher.
- Go to ProductsImport, choose the file, tick Update existing products, click Continue and Run the importer.
Right after the import, every language shows the new stock, prices and price range.
With WP All Import, on a schedule:
- All ImportNew ImportDownload a fileFrom URL, with your supplier's feed URL. Choose WooCommerce Products.
- Map SKU, Regular Price and Stock Qty in the WooCommerce Add-On section.
- In Import Settings, tick Attempt to match to existing WooCommerce products before creating new ones and match by Custom field
_sku. Turn off Create new WooCommerce products from records newly present in this import file. Turn on Update existing WooCommerce products with the data in this import file. - Under Choose which data to update, turn off everything except Custom Fields, and choose Update only these Custom Fields, leave the rest alone:
_regular_price, _price, _stock, _manage_stock. - Schedule it. Under All ImportManage ImportsScheduling Options, Manual Scheduling shows a Trigger URL and a Processing URL for your server's cron job.
Each run matches the rows to the original products, and every language gets the new prices and stock of each product and variation.
If a full Process B file is imported again as an update, set Published to 1 on every row. Otherwise the live products go to Draft until Run WPML Import. Tick Update existing products, then click Run WPML Import. The products stay published, and the texts in the file replace the translations at once.
Add a Language to a Catalog You Already Have
Process A:
- Go to WPMLLanguages, click Manage and Hide Site Languages, use Search and add a language… and pick the language.
- Click Calculate Costs. The dialog "Cost to translate your content into ..." lists the items and words. Click Save.
Translate Everything starts the new language by itself, the next time a WPML admin page loads. WPML translates and publishes every product and variation in the new language. Your existing languages are not touched.
Process B:
- Prepare a file with the new language's rows only. Use the SKU as the translation group, the original's language as the source language,
Published=-1andpublishas the final status. - Go to ProductsImport. Leave Update existing products unticked. Run the importer.
- Go to WPMLExport and Import and click Run WPML Import.
Each new product and variation joins its original's translation group, matched by SKU. This works on any catalog, also one that was never imported. The new language gets its own categories and attribute terms from the file.
Update existing products does not add a language: the importer skips those rows. It lists each new-language product with "No matching product exists to update." and each new-language variation with "A new variation cannot be created without a parent product."
Import Large Catalogs
- Import one file per language, originals first.
- Run WPML Import once, after the last file.
- For long runs, use WP-CLI:
wp wpml import processruns the same step as the button and shows each step's count.
How long it takes, from our lab, with WooCommerce's importer and one Run WPML Import for a catalog in three languages:
| Products per language | Whole import | Of that, Run WPML Import |
|---|---|---|
| 500 | about half an hour | a few minutes |
| 1,000 | about one hour | about 10 minutes |
| 2,000 | about two hours | about half an hour |
Each size finished in one sitting, with every product and variation present and connected in every language. Each figure is one run on a shared lab server. Most of the time is the WooCommerce importer's, and it depends on your server. Read these numbers as an order of magnitude.
Export Products with Their Languages (WP All Export)
WP All Export adds the WPML columns _wpml_import_language_code, _wpml_import_source_language_code and _wpml_import_translation_group to a WooCommerce Products export by default. Its WPML section exports all languages or one. Exports run by hand and on a schedule both fill the columns. Read more in Export multilingual websites using WP All Export.
Sync from an ERP or PIM
An ERP (enterprise resource planning system) is the software where a business keeps stock, prices and orders. A PIM (product information management system) is where it keeps product texts and data.
A connector between such a system and WooCommerce typically:
- Holds the catalog keyed by SKU, in one language
- Finds each product by SKU (
GET /wc/v3/products?sku=...) - Updates stock and prices of existing products, and creates new products, through the WooCommerce REST API
- Runs on a schedule
This is the flow that works with WPML:
- The connector writes to the store's default language only.
- WPML copies stock and prices to every language in the same request.
- Translate Everything translates new products into every language (Process A).
- A product the connector sets to draft goes to draft in every language.
- A product the connector deletes follows WPMLSettingsDeleting content, row Products. Nobody is asked during a sync, so set Deleting an original to the behavior you want: Delete all languages removes the translations with it; Only that one keeps them published.
Ask your connector's vendor three questions:
- Does it write through WooCommerce, or straight to the database? Changes written straight to the database reach the original only. The translations keep the old stock and prices.
- Which language does it write to? It must write to the original. A price written to a translation is not stored: the translation keeps the original's price.
- Does it create one product per language? WooCommerce refuses a second product with the same SKU. Without the SKU, the copies are separate products that get no stock or price updates. Let the connector create the original only, and let WPML translate it.
Part 3. Build Custom Flows (Developers)
Create a Product and Its Translations with the WooCommerce REST API
Create the terms first, then the original, then each translation with lang and translation_of.
- Translate the category (and any attribute terms):
POST /wp-json/wc/v3/products/categoriesJSON{ "name": "Wohnen und Geschenke", "slug": "wohnen-und-geschenke", "lang": "de", "translation_of": 32 }For attribute terms, use
POST /wc/v3/products/attributes/<id>/terms/batchwith the same two fields on each term. - Create the original:
POST /wp-json/wc/v3/productsJSON{ "name": "Stoneware Coffee Mug", "type": "simple", "status": "publish", "sku": "HP-HG-MUG", "regular_price": "16.00", "manage_stock": true, "stock_quantity": 60, "categories": [ { "id": 32 } ], "lang": "en" } - Create each translation:
POST /wp-json/wc/v3/products, with the translated texts, the translated category,langandtranslation_of(the original's ID). Send no SKU, price or stock: WPML copies them from the original.JSON{ "name": "Steingut-Kaffeebecher", "slug": "steingut-kaffeebecher", "status": "publish", "categories": [ { "id": 38 } ], "lang": "de", "translation_of": 120 } - Read the result with a GET. The answer to the create call shows SKU, price and stock empty, because WPML copies them after the answer is built.
GET /wc/v3/products/121right after shows them.
For a variable product, create the original's variations on the original only (POST /wc/v3/products/<id>/variations/batch). Then create each translated parent with lang and translation_of. WPML creates the translated variations itself, links each to its original variation, and copies SKU, price, stock and the attribute terms in that language. Do not post variations on a translation.
Read a translation's variations with ?lang=: GET /wc/v3/products/137/variations?lang=fr. Each variation carries lang, its translations map and the option names in that language.
One product translation per language. A second product translation in a language that already has one is refused with HTTP 400 wcml_translation_exists, and nothing is created. The message names the existing translation's ID. Update the existing translation instead.
Full field reference: WooCommerce Multilingual REST API.
Update Products with the WooCommerce REST API
Update the original. WPML copies the change to every language in the same request.
PUT /wc/v3/products/123/variations/124with{"regular_price": "59.00", "stock_quantity": 3}changes that variation's price and stock in every language, and the price range follows.PUT /wc/v3/products/120with a new regular price, sale price or stock changes them in every language.- New attribute terms are created on the original's attribute and translated with
langandtranslation_of, as in step 1 above. - A new variation added to the original (
POST /wc/v3/products/123/variationsor.../variations/batch) reaches every language in the same request, linked, with its price and stock. The answer to the call lists only the original's language;GET /wc/v3/products/130/variations?lang=deright after lists the new translated variation. - A price or attributes sent to a translation are not stored: the translation keeps the original's values. A stock value sent to any language becomes every language's stock.
Delete through the API: DELETE /wc/v3/products/<id> follows WPMLSettingsDeleting content, row Products. The API never asks: under Ask me it deletes only the original. Set Deleting an original to the behavior your store wants. With Delete all languages, a delete moves every language to the Trash, and ?force=true deletes every language.
Write Your Own Importer or Connector
Use WooCommerce's product functions. WPML sees the change and copies it to every language.
$id = wc_get_product_id_by_sku( 'HP-HG-MUG' ); // returns the original
$product = wc_get_product( $id );
$product->set_regular_price( '19.00' );
$product->set_stock_quantity( 33 );
$product->save();After save(), the translations show the new price and stock.
Never write product data straight to the database (update_post_meta() or SQL). The original changes, and the translations keep the old values.
Run the WPML import step from code after an import with the WPML columns: wp wpml import process. It runs the same steps as the Run WPML Import button and prints each one with its count.
Scheduled Jobs
A scheduled job (WP-Cron) that changes the original with WooCommerce's product functions carries these changes to every language in the job's own request:
- Regular price, sale price and stock, with the stock status that follows from it
- A category added to the product (as the translated category)
- A new attribute term on a variable product (as its translation)
- The variable product's price range
Part 4. Troubleshooting
Imported Translations Show Up as Separate, Unlinked Products
What you see: the translated rows are missing, or they sit as English (default-language) products, often Private, with no link to the original.
Why it happens:
- The file has no WPML columns. WooCommerce then skips every row whose SKU already exists: "A product with this SKU already exists."
- The file has the WPML columns, but Run WPML Import was not run. Until then every row is a default-language product with no link to its original, with the status the file's
Publishedcolumn gives it (Private for0, Draft for-1). WPMLExport and Import shows "Good job. We see 12 posts that are imported and need language information."
How to fix it now:
- No WPML import step run: go to WPMLExport and Import and click Run WPML Import.
- No WPML columns: add the four WPML columns to the translation rows and import them again as a new import, with Update existing products unticked. Then click Run WPML Import. Each translation joins its original by SKU.
How to avoid it: always include the WPML columns, and run Run WPML Import after every import.
Imported Translations Are Replaced by the Original's Text
What you see: you imported translated names and descriptions, and after the next save of the original they are back in the original language.
Why it happens: the translations were duplicates. WPML rewrites a duplicate on every save of its original.
How to fix it now:
- Make them independent. Go to ProductsAll Products, switch to the translation's language, tick the products and choose Bulk actionsTranslate independently.
- If Translate Everything is on, set Products to None. On WPMLTranslations, click the three-dot menu in the "Translate Everything Automatically is enabled" box, choose Adjust content limits, set Products to None and click Save changes.
- Import your translations again.
After that, saving the original keeps the imported text.
How to avoid it: before importing text into existing translations, set them to Translate independently. Or import translations as new products with the WPML columns (Process B).
Translated Products Show Attribute Values in the Original Language
What you see: the translated product page offers "Blue", "Green" instead of the translated terms.
Why it happens: the products were translated before their attribute terms were translated.
How to fix it now:
- Go to WPMLTranslations and open the Taxonomy tab.
- Under "Select the taxonomy to translate", choose the attribute, for example Product Color.
- Translate each term in each language and click Save. Translate the attribute's label on the same screen.
Existing translated products pick up each term as you save it. No product needs saving again. If a term was first created as a copy with the original's name, its slug keeps the original's text; change it in the same dialog.
How to avoid it: translate attribute terms before you translate or import products.
Translated Categories or Terms Carry the Original's Names After an Import
What you see: a translated product sits in a category called "Sunglasses" or offers "Blue" in the translated shop.
Why it happens: the translation rows were copied from the original's export and kept its category, tag and attribute-term names. WPML creates translated terms with those names and links them correctly, but it does not rename them. Upsells, cross-sells, images, galleries and variation parents given by the original's IDs are re-mapped to the right language.
How to fix it now: rename the terms under WPMLTranslationsTaxonomy, as in the section above. Breadcrumbs, term links, archive headings and attribute options show the new names at once, and no product needs saving again. The slugs keep the original's text unless you change them in the same dialog.
How to avoid it: in translation rows, write translated category, tag and attribute-term names, in the same order as the original. Give related products and parents by SKU.
Stock or Prices in Other Languages Are Behind the Original
What you see: the original shows the new stock or price, and the translations show the old one.
Why it happens: the change bypassed WooCommerce or WPML:
- A connector wrote straight to the database.
- An import ran while WPML was deactivated.
How to tell: open the original in the product editor. Below the description editor it reads "Last edited on" with a date and time. If that time is older than the new price or stock in the Product data box, or the change was made while WPML was inactive, the update bypassed the sync.
How to fix it now:
For variable products:
- Go to WPMLSupportFix WCML translations. Fix WCML translations is part of WPML Troubleshooting, a separate plugin.
- Tick Synchronize product variations and click Run the selected tools.
Every language then shows the original's variation prices and stock, and the product's price range.
For simple products, use one of these routes. Each one carries the original's price and stock to every language:
- One product at a time: open each changed original and click Update.
- Many products by import: with the admin language set to the default language, import the products again with ProductsImport and Update existing products ticked. The file can carry the values the originals already have. This also realigns variable products.
- Many products by REST: send
PUT /wc/v3/products/<id>with the price for each product, for example{"regular_price": "19.50"}. - Many products with one price: in ProductsAll Products, tick the products, choose Bulk actionsBulk edit and click Apply. Under Price choose Change to:, enter the price and click Update. Every ticked product gets that one price.
Running wp wc product update with the value the original already has does not carry it to the translations.
How to avoid it: let the connector write through WooCommerce (the REST API or the product functions), and keep WPML active during imports.
Products Created Through the REST API Land in the Wrong Language or Group
What you see: a translation appears in the wrong language, or as a separate product with no SKU and no link to the original.
Why it happens:
- An unknown language code is refused with HTTP 422
Invalid language parameter: "ge", and nothing is created. - A valid but wrong code, such as German text sent with
"lang": "fr", creates a translation in that language. - A missing
translation_ofcreates a product in its own group, with no SKU and no copied price or stock.
How to fix it now: send the product again with the right language and the link, with PUT /wc/v3/products/<id>:
{
"lang": "de",
"translation_of": 38
}The product moves into the original's group and gets its SKU, price and stock. For a variable product, WPML replaces the variations created without a link with new, linked ones. Read the new variation IDs back.
How to avoid it: send lang and translation_of on every translation, create the terms first, and let WPML create the translations' variations.
New Imported Products Are Not Translated Automatically
What you see: imported products stay in the original language only.
Why it happens: Translate Everything was off during the import, or the products are private, which Translate Everything never translates, or drafts, which it translates only when Translate drafts automatically is on and the draft is saved again.
How to fix it now:
- Send the products: go to WPMLTranslations, open the Products section, tick the products, choose Translate automatically for each language, choose Publish without review under "What would you like to do when WPML finishes translating your content automatically?" and click Translate content. This also works for drafts and private products; their translations get the original's status.
- Or turn on Translate Everything. It translates every published product not yet translated. WPML sends them while WPML admin pages load.
- Go to WPMLTranslationsSet up Translate EverythingContinueEnable Translate Everything Automatically.
- Stay on WPMLTranslations until it reads "Finished translating your content".
How to avoid it: turn on Translate Everything before the import (Process A), and import products as published.