Translate product attributes and terms
WooCommerce global attributes have two public layers: the attribute label, such as “Color,” and taxonomy terms, such as “Blue.” Translate both to keep filters, product selectors, carts, and emails consistent.
Translate attribute terms
- Make sure the attribute taxonomy is enabled in POM Translate.
- Go to Translations → Translate contents.
- Choose the target locale.
- Find the term in its
pa_...taxonomy. - Translate its name and description.
- Save the translation.
- Add or update its localized slug under Translations → Translate URLs when the public archive needs one.
Term translations are reused in variation selectors, attribute archives, breadcrumbs, Store API term payloads, and order/cart metadata when WooCommerce supplies enough context.
Translate the attribute label
The label naming the taxonomy is not the same record as one of its terms. POM Translate resolves public attribute labels as registered strings. Find the source label under Translations → Other translations, choose the locale, translate it, and save.
The same registered-string route is used for freeform option labels that do not map to a global term.
Verify every surface
Test:
- the product's Additional information area;
- variation dropdowns or swatches;
- layered navigation and product filters;
- attribute archive headings and URLs;
- cart and checkout item metadata;
- customer email item metadata;
- Store API blocks used by the theme.
If a swatch plugin supplies only a plain label, POM Translate can translate a matching registered value. When the integration passes the complete term object, the lookup is exact and does not need to infer which taxonomy owns repeated text.
Avoid technical changes
Do not translate the taxonomy key, attribute database name, variation attribute key, or stored option slug inside product data. Those values connect variations and queries. Translate the public label, term content, and supported localized URL only.
Missing translations fall back to the base label or term.