Prepare WooCommerce for translation

Complete these requirements before translating a live store. They separate catalog content managed by POM Translate from software messages supplied by WooCommerce and its extensions.

Required setup

• Activate WooCommerce and POM Translate.
• Configure a base language and at least one additional language.
• Enable the product post type and the WooCommerce taxonomies you intend to translate.
• Use WordPress permalinks rather than relying on temporary rewrite state.
• Install WooCommerce language packs for every storefront locale, or prepare equivalent PO/MO files through Translations → Software translations.
• Use a test product and test payment method for end-to-end verification.

POM AI is optional. It can create translation drafts only when its own license, domain authorization, credits, and local quotas are available.

Decide what is translatable

Translate editorial values:

• product titles, long descriptions, and short descriptions;
• selected product metadata;
• product category, tag, and attribute term names, descriptions, and slugs;
• registered tab, form, and account labels;
• WooCommerce email subjects, headings, additional content, and footer text.

Do not translate operational commerce data such as prices, stock quantities, SKUs, tax classes, order numbers, gateway identifiers, or customer addresses.

Establish a test matrix

Include at least:

1. A simple product.
2. A variable product with a global attribute.
3. A category archive and a product-tag or attribute archive.
4. Classic cart/checkout or the corresponding Blocks flow used by the site.
5. My Account with an endpoint that has a trailing value, such as an order.
6. One customer email in HTML and plain text.
7. One order created in each enabled target locale.

If the store uses subscriptions, follow-up emails, custom checkout fields, product add-ons, payment-gateway emails, or PDF invoices, test each extension separately. POM Translate deliberately excludes common gateway and PDF email templates from its managed email lifecycle.

Expected result

The base product and order remain the canonical records. Language changes affect public text and URLs, not shared commerce values or order identity.