WooCommerce product tabs can contain important product information, but translating them depends on how those tabs were created. WooCommerce Tab Manager separates tabs attached to one product from global tabs that can be shared across multiple products. WPML documents a different translation path for each type, so identifying the tab structure is the first practical step.
This guide covers the documented workflow for WooCommerce Tab Manager with WPML. It explains the required components, shows how to translate per-product and global tabs, and describes why products using global tabs must also have their own translations. After completing the work, verify representative product pages in each target language. The workflow should not automatically be applied to other tab extensions, custom implementations, or every combination of installed versions, themes, and plugins.
What You Need Before Translating Product Tabs
Documented plugin stack
The Tab Manager-specific WPML documentation lists the following setup for translating this content:
- WooCommerce
- WooCommerce Tab Manager
- WPML
- WPML String Translation
- WPML Multilingual & Multicurrency for WooCommerce
This list describes the documented component stack for WooCommerce Tab Manager. Broader WPML guidance for WooCommerce also identifies WPML core, String Translation, and the WooCommerce compatibility component as part of the translation setup. Before starting, check the current availability and compatibility of the products and versions installed on the site. The documentation describes the workflow, but it does not establish that every version combination behaves identically.
The scope also matters. This article concerns WooCommerce Tab Manager specifically. Another WooCommerce tab plugin may store its content differently and may require another translation process. Do not assume that a workflow documented for Tab Manager applies to an unrelated extension, a custom tab implementation, or every theme configuration.
Per-Product Tabs vs Global Tabs
Choose the workflow by tab type
WooCommerce Tab Manager distinguishes between two useful content structures. A product-level, or per-product, tab is created for one product and customized for that product. Its content belongs to the individual product configuration.
A global tab is reusable content that can be shared across multiple products. It may be included in the default tab layout or added to an individual product layout. Category restrictions can also control which products display it. Consequently, a global tab may be translated correctly but still not appear on a particular product if the relevant layout or category settings do not assign it there.
Use the product translation workflow when the tab is attached to one product. Use the separate Tabs workflow when the content is a reusable global tab. This distinction prevents a common error: looking for a product-specific tab in the global Tabs section, or expecting translation of a global tab to create all associated product translations.
How to Translate Per-Product Tabs
Send the product for translation
For a per-product tab, translate the WooCommerce product to which the tab is attached. In WPML, go to WPML → Translations and locate the relevant product in the Products section. Choose an available translation method and send the product for translation.
According to the documented WooCommerce Tab Manager compatibility workflow, the attached per-product tab is translated as part of the associated product translation. The tab is therefore handled through the product translation task rather than through the separate global Tabs workflow. The important relationship is between the individual product and the tab attached to it.
Before sending the item, confirm that you have selected the product containing the intended custom tab. If several products have similar names or similar content, checking the association first helps avoid translating the wrong product. Keep the process within the WPML translation workflow configured for the site rather than making unrelated changes to translated content that could affect the translation relationship.
Verify the translated product page
When the product translation is complete, open the translated product page on the frontend in the target language. Check whether the per-product tab appears and whether its translated heading and content are shown in the expected product context.
This frontend check is part of the workflow, not a claim about performance, search visibility, or conversion results. If the tab is absent, first confirm that the correct associated product was sent for translation and that the translation is available. The documented process applies to WooCommerce Tab Manager; another tab extension may require a different procedure.
How to Translate Global Tabs
Translate the reusable tab
Global tabs follow a separate path because they are reusable content items rather than tabs belonging to only one product. In WPML, go to WPML → Translations and find the Tabs section. Select the global tab or tabs that need translation, choose an available translation method, and send the selected tabs for translation.
This task translates the shared tab content itself. It does not replace the product translation step. A global tab can be assigned to several products, included in a default layout, or added to an individual product layout. The translated tab therefore needs to be considered together with the products and display settings that use it.
When selecting items in the Tabs section, distinguish global tabs from product-level tabs. The documented workflow does not say that every tab created by another extension will appear or behave in the same way. Keep the process limited to the WooCommerce Tab Manager content model described here.
Translate products assigned to the global tab
After sending the global tab for translation, translate the WooCommerce products that use that tab as a separate task. In WPML, use the product translation workflow in the Products section of WPML → Translations. Select the relevant products, choose a translation method, and send them for translation.
WPML explicitly instructs store owners to translate products using a global tab in addition to translating the global tab itself. This means that translating the shared content alone is not enough. The translated product pages must also exist and be associated with the relevant translated content.
Once both parts are available, open representative translated product pages on the frontend. Confirm that the product is displayed in the target language and that the translated global tab appears where the Tab Manager layout and any category restrictions allow it to appear. If a tab is not visible, check those display rules before treating the result as a translation failure.
Why Global Tabs Require Product Translations Too
Separate content, separate translation tasks
WPML treats a global tab and the WooCommerce products that display it as separate translatable items. The global tab contains reusable content, while each product remains its own WooCommerce content item with its own translated version. These two relationships must therefore be handled separately.
Translating only the shared tab does not create or complete the translated products assigned to it. Without the relevant product translations, there may be no translated product page on which to verify the tab association. Translating the products as well gives WPML the product context in which the translated global tab can appear.
The practical rule is simple: translate the global tab, translate the products that use it, and then check the translated product pages. This does not override the Tab Manager layout or category restrictions. A missing tab may reflect assignment or visibility settings rather than missing translated text.
Troubleshooting Missing Tab Text or Tabs
A cautious diagnostic order
When a tab or its text is missing, use a limited diagnostic sequence instead of immediately changing unrelated settings:
- Check the translation item. Confirm that the correct product was sent for a per-product tab, or that the correct global tab was selected in the Tabs section.
- Check the product translation. For a global tab, verify that the products using it were also sent for translation and that their translated pages are available.
- Check visibility settings. Review the Tab Manager layout and any category restrictions that may control whether the global tab is displayed on the product.
- Check available strings. If relevant extension or plugin strings do not appear in WPML String Translation, use the documented Admin Texts Translation scan as a fallback to register missing strings.
- Retest the frontend. Open the affected product in the target language and check the tab again.
The Admin Texts Translation scan is a fallback for relevant text that is not available in String Translation, not the primary WooCommerce Tab Manager workflow. The available documentation does not provide a complete troubleshooting matrix for every theme, caching layer, third-party extension, or custom implementation. Avoid assuming that a missing tab is a translation problem before checking the content relationship and display rules.
Compatibility and Verification Checklist
Final translation checks
Before considering the work complete, review the configuration and test representative pages:
- Confirm that the site uses the documented WooCommerce Tab Manager and WPML component stack.
- Test at least one product with a per-product tab.
- Test at least one product that uses a global tab.
- Check translated tab headings and tab content in each target language being prepared.
- Confirm that the relevant translated product pages are available on the frontend.
- Review the global tab layout and category restrictions when visibility differs between products.
- Keep compatibility questions specific to the installed versions, theme, and implementation rather than assuming universal support.
The key decision is based on ownership of the tab content. For a per-product tab, translate the associated product through WPML → Translations → Products. For a global tab, translate the reusable tab through WPML → Translations → Tabs and also translate every relevant product that uses it. In both cases, verify the result on translated product pages, because the frontend confirms whether the translated content and product context work together. Explore our WordPress plugins, WooCommerce extensions, themes and membership plans to find the right tools for your website.