WPML WooCommerce Product Attributes Not Translated: Global vs. Local Attribute Fixes

Your product title, description, and price may be perfectly translated—yet the “Color,” “Size,” or “Material” fields stubbornly remain in the original language. If you’re searching for wpml woocommerce product attributes not translated, the issue is often not a broken translation job at all. It’s that WooCommerce can store attributes in two fundamentally different ways, and WPML does not treat them the same.

A global attribute is a reusable taxonomy: its terms live beyond a single product and need their own translation path. A local attribute, however, belongs only to that product, making it part of the product-level translation workflow. Miss that distinction, and it is easy to translate everything that looks important while the attributes customers actually see stay behind.

The frustrating part is that both can appear side by side on the same product page, creating the impression that WPML is translating some fields at random. Once you know where each attribute truly lives, the fix becomes far more straightforward—and you can stop chasing the wrong settings.

First, Identify Whether Your Product Attributes Are Global or Local

Many cases of wpml woocommerce product attributes not translated come down to one easily missed detail: WooCommerce stores global and local attributes in different ways. They may look similar on a product page, but WPML does not translate them through the same workflow. Diagnose the attribute type before changing translation settings.

What are global product attributes in WooCommerce?

Global attributes are catalog-wide attributes created under Products > Attributes. Common examples include Color, Size, Material, Brand, or Capacity. Once created, an attribute can be assigned to many products, and its values become reusable terms: “Red,” “Blue,” “Small,” and “Large,” for example.

This matters because WooCommerce treats a global attribute like a taxonomy. WPML therefore sees both the attribute label and each value as taxonomy content to translate, rather than as text belonging solely to one product. Global attributes are also commonly used for variations, such as a T-shirt available in several sizes and colors.

What are local (custom) product attributes?

Local attributes are created inside one product’s Attributes tab. They are manually entered for that product and are not available elsewhere in the catalog. A one-off dimension, a compatibility note such as “Fits 2021–2023 model,” or a bundle detail such as “Includes two mounting brackets” may all be local attributes.

They are product-level data, not shared taxonomy terms. That distinction is why a fix intended for translated global terms may do nothing for a custom attribute entered directly on a single product.

How to tell which type you are using

Start with a quick check in Products > Attributes. If the attribute appears there, it is global. If it exists only in an individual product editor and its name and values were typed manually, it is local.

Do not convert attributes casually. Changing a global attribute or rebuilding it as a local one can disrupt product variations, filters, and existing term assignments. Identify the structure first; then use the WPML translation path that matches it.

How to Translate Global WooCommerce Attributes and Their Terms in WPML

Make the attribute taxonomy translatable in WPML

A translated product can look complete until its “Color” field quietly shows Blue in the source language. That is because global WooCommerce attributes are taxonomies, not ordinary product text. In WPML’s taxonomy translation settings, find the specific product attribute taxonomy—typically named with a pa_ prefix, such as pa_color—and set it to translatable.

Do not assume that enabling translation for Products handles this step. Product settings govern the post type; reusable attributes have their own taxonomy rules. This is the first setting to inspect when wpml woocommerce product attributes not translated is the symptom.

Translate every attribute term, not just the attribute label

Translating “Color” to “Farbe” does not translate “Blue,” “Black,” and “Green.” The attribute name is the taxonomy label, while those selectable values are individual terms inside that taxonomy. They require separate, linked translations.

Open WPML’s taxonomy or term translation screen, select the relevant attribute, and translate every term currently assigned to products. A store may have only three visible colors today, but missing one legacy term can still produce mixed-language filters, product summaries, or dropdown choices. Check spelling, slugs, and term relationships as you go; consistency matters when the same attribute is reused across dozens of products.

Check translated product assignments and variations

After translating the taxonomy and its terms, open the translated product and confirm that it is assigned to the corresponding translated terms. WPML should maintain those links, but imports, manual edits, and older products can leave gaps.

Be especially careful with variable products. Each variation depends on valid attribute-term data in the target language. If a translated term is missing or no longer matches the variation configuration, customers may see an untranslated dropdown, no selectable option, or an “unavailable” variation. Test the translated product on the front end before publishing.

For stores already running WPML, LATW AI Translator for WPML can help translate WooCommerce products, attributes, and variations in its Pro workflow, while WPML remains the required multilingual foundation.

How to Handle Local Attributes That Do Not Translate

Open the product translation and review custom fields

Local attributes are easy to miss because they do not behave like global WooCommerce attributes. A global attribute is a reusable taxonomy term; a local attribute belongs only to one product. That distinction is often the real cause of wpml woocommerce product attributes not translated reports.

Open the product in the default language, then enter its translation through your configured WPML translation workflow. In the translation editor, inspect the fields and sections associated with the product’s custom data, attributes, and variations. The local attribute name and its values may appear as product-level fields rather than as terms in the WooCommerce Attributes screen. If the values are visible in the job, translate them there and complete the translation.

Check whether the attribute is set to copy, translate, or copy once

Before translating again, review WPML’s custom-field translation preferences and the relevant WooCommerce Multilingual settings. A field set to Copy carries the original value into every language, which is correct for codes, dimensions, or technical identifiers but wrong for customer-facing text. Translate exposes a separate value for each language. Copy once copies the initial value but allows later edits in the translated product.

For example, “Material: Hand-finished oak” should usually be translatable, while an internal SKU attribute should normally be copied. Changing this preference after a translation already exists may require a refreshed translation job.

Re-save and update the translated product

First, update the original product if its local attributes have changed. Next, refresh or reopen the WPML translation job, translate the attribute values, and save the completed translation. Visit the translated front-end product page to confirm the attribute table reflects the new text.

If the old value persists, clear page, object, and CDN caches before assuming WPML failed. For stores using WPML’s workflow with AI assistance, LATW AI Translator for WPML can translate eligible product content more efficiently, but it still requires WPML and a final review of product-specific fields.

Common Reasons Attributes Still Appear in the Original Language

The product is translated, but its terms are not

The most frequent cause of wpml woocommerce product attributes not translated is deceptively simple: the product translation exists, but its global attribute terms do not. A translated “T-Shirt” can still show “Blue” or “Large” in the source language if those taxonomy terms have no translated counterpart, or if the translated term is not connected to the original one in WPML. Check every affected value, not just the attribute label. One missing term is enough to make a product look only partly translated.

A cached page or stale translation job is being shown

A correct change does not always appear immediately. Page-cache plugins, persistent object caches, and CDN caches can all serve an older product page; an unfinished or outdated WPML translation job can do the same inside the dashboard. Clear the relevant WordPress, server, and CDN caches after updating attributes, then test the translated product URL in an incognito window. This avoids mistaking a cached response for a translation failure.

The attribute should be global for your catalog

Repeated local attributes create repeated translation work. If “Color,” “Size,” or “Material” appears across 50 products, making each instance local means maintaining dozens of separate values rather than one shared taxonomy. Use global attributes for values reused across the catalog, product filtering, layered navigation, and variations. Reserve local attributes for genuinely one-off details, such as “Includes a hand-finished oak stand.”

Speed up WPML product translations with LATW AI Translator for WPML

For stores already running WPML, LATW AI Translator for WPML can reduce the manual workload for WooCommerce products, attributes, and variations. It is an add-on, not a standalone multilingual plugin, so an active WPML installation is required. Its Pro plan includes WooCommerce support and uses a bring-your-own-key model with supported AI and machine-translation engines. Content is sent directly from WordPress to the selected provider, rather than through intermediary plugin servers.

Apply the Right Translation Path to Each Attribute

When WPML WooCommerce product attributes are not translated, the decisive question is not which setting to toggle—it is whether the attribute is global or local. Treat global attributes as WooCommerce taxonomies and translate their terms through WPML; handle local attributes within the translation workflow for the individual product. That distinction prevents a great deal of wasted troubleshooting.

After updating the translation, inspect both the translated product editor and the live product page. For variable products, also check the variation labels, dropdown values, and purchasable combinations in each language. A product is only truly localized when the option a customer sees is the option WooCommerce can sell.