PPOM fields fail to display on WPML translated product pages

If PPOM fields appear on the original WooCommerce product but do not appear on the translated product page, the field group is usually attached to the original product only.

Why this happens

PPOM product-specific assignments are tied to the WooCommerce product's WordPress post ID. WPML creates a separate translated product for each language, and each translation has its own product ID.

Because of that, a PPOM meta group that is attached directly to the original product does not automatically carry over to the translated product page.

How to fix it

Option 1: Attach the field group through categories or tags

If your translated products share synchronized product categories or product tags in WPML, attach the PPOM meta group to that shared category or tag instead of attaching it only to one product.

This is usually the best option for multilingual stores because one category-level or tag-level assignment can cover multiple translated products.

For the available attachment methods, refer to Attach meta groups to products.

Option 2: Attach the field group to each translated product

If category or tag assignment does not fit your store setup, manually attach the PPOM meta group to each translated product.

After saving the field group and the translated product assignment, clear your site cache and retest the translated product page in an incognito or private browsing window.

Current limitation

⚠️ Warning: PPOM does not currently include native WPML compatibility for automatically remapping translated product IDs to the source product ID. There is also no supported ppom_get_product_id hook or similar filter available for this workflow at the moment.

If you need the same PPOM fields across multiple translated products, use shared category or tag assignments whenever possible. Otherwise, attach the field group to each translated product individually.