Your Cart
WPML WooCommerce shipping method translation

How to Translate WooCommerce Shipping Method Names and Tracking Messages with WPML

Multilingual WooCommerce stores often translate products, pages and checkout content, yet shipping text can remain in the original language. A delivery method name, its checkout description or a tracking notification may be managed separately from product content. This is why looking only in the product translation screen may not reveal the wording that shoppers see.

The general workflow documented for WPML uses WPML → Translations → Strings. From there, you can search for the visible shipping text, the relevant shipping or tracking plugin, or its text domain, and then add the translation for the target language. The exact result still depends on how an extension registers and renders its strings. This guide covers shipping method names, checkout descriptions, tracking messages and a practical process for missing strings.

Why WooCommerce shipping text can remain untranslated

What this workflow covers

Shipping-related wording is not always stored as product content. WooCommerce shipping method names and descriptions are documented as String Translation content, so their normal translation path is different from translating a product. The same principle can apply to text supplied by a shipping extension, tracking plugin or carrier integration, but the available strings depend on how that extension exposes them.

This distinction matters because several types of content can appear close together in the customer journey while using different translation workflows. A shipping label shown at checkout, a description beside that label, a tracking-page message and an email notification may not belong to one identical group. Treat each displayed text in the context where it appears.

The process concerns language shown to customers. Translating a label or notification does not, by itself, change shipping rates, carrier rules, delivery times, tax treatment or fulfillment behavior. Those are separate parts of the store configuration.

Translate WooCommerce shipping method names in WPML

Finding the correct shipping string

For documented WooCommerce shipping method names, start at WPML → Translations → Strings, rather than the product translation screen. The Strings interface lets you search by text and filter by plugin or theme domain and translation status. This is useful when the store contains several similar delivery labels or when the visible wording does not clearly identify its source.

  1. Open WPML → Translations → Strings.
  2. Search for the exact shipping method name visible to shoppers.
  3. If the wording is difficult to identify, search for the shipping plugin name or its text domain.
  4. Use the plugin or theme domain, status and text filters to narrow the results.
  5. Open the relevant string, add the translation for the target language and save it.
  6. Check the localized checkout to confirm that the intended shipping method name is displayed.

Examples documented for this type of workflow include shipping plugins such as Table Rate Shipping, Advanced Shipment Tracking, Flexible Shipping and carrier integrations. These examples should not be treated as a guarantee that every extension exposes its labels in exactly the same way. The relevant text domain is installation- and extension-dependent.

If several strings look similar, compare them with the wording and location shown on the frontend. This helps avoid translating an unrelated label. Keep the scope clear: the translated value changes displayed language text, not the underlying rate calculation or shipping rule.

Translate shipping descriptions shown at checkout

Checking the translated checkout context

Shipping descriptions displayed beside or below a delivery method are also handled through WPML → Translations → Strings in the documented WooCommerce workflow. Search for the description exactly as it appears, then try the relevant plugin name or text domain if a direct text search does not identify it. When many results are returned, filtering by the plugin or theme domain can make the correct entry easier to locate.

After adding the target-language translation, open checkout in that language and inspect the shipping method and its description separately. A translated method name does not necessarily confirm that its accompanying description has also been translated. Check the wording in the same checkout context in which customers will read it.

  • Confirm that the checkout is displayed in the intended target language.
  • Check the shipping method name separately from the description.
  • Review descriptions for every relevant shipping option, not only the currently selected option.
  • If a description is not listed, use the missing-string workflow before assuming that it cannot be registered.

This frontend check is a verification step, not a guarantee that every extension will expose every description for translation. If the string remains unavailable, its registration method or rendering technology may require additional investigation.

Translate tracking notifications and tracking-page messages

Separating email and tracking-page strings

Tracking-related text may come from a separate shipping or tracking plugin rather than from the core checkout content. WPML documents that tracking-notification email text supplied by shipping plugins can register as translatable strings. In practice, open WPML → Translations → Strings and search for the tracking plugin’s name or text domain.

Do not assume that one translation entry covers every tracking location. A notification email and a tracking page can use different strings or templates. Some documented plugin-specific examples include tracking-page templates for Parcel Panel Order Tracking and TrackShip for WooCommerce, but these examples describe documented cases rather than universal behavior for all tracking extensions.

  1. Identify the tracking plugin responsible for the message.
  2. Search String Translation using the plugin name or its text domain.
  3. Look for the wording used in the notification email and the wording used on the tracking page as separate groups.
  4. Add translations for the target language where the relevant strings are registered.
  5. Review each message in the interface where it is displayed.

This separation is important for troubleshooting. A translated checkout label does not prove that tracking notifications are translated, and a translated email does not prove that the tracking interface uses the target language. Translation affects displayed messages; it does not alter fulfillment or carrier behavior.

When shipping strings are missing from String Translation

A practical missing-string sequence

A required shipping string may not appear immediately in String Translation. WPML’s documented troubleshooting process begins with the frontend. Visit the page where the missing wording actually appears, such as the relevant checkout or tracking interface. Loading the text there can help WPML register a frontend string.

Next, open Admin Texts Translation from the Strings area and scan the relevant plugin or theme. Select the strings that should be available and add them to String Translation. Return to the Strings screen, search again and translate the registered entry if it is now available.

Use the following sequence:

  1. Open the frontend page where the untranslated shipping or tracking text appears.
  2. Note the exact wording and the context in which it is displayed.
  3. Go to the Strings area and open Admin Texts Translation.
  4. Scan the relevant shipping plugin, tracking plugin or theme.
  5. Add the required strings to String Translation.
  6. Return to String Translation and search by visible text, plugin name or text domain.
  7. Translate the entry and verify it again in the target-language frontend.

Some checkout or tracking text may be generated by JavaScript. For that case, WPML documents a separate workflow: enable Detect strings in JavaScript files, revisit the frontend page where the text appears, and scan the relevant plugin or theme through the WPML compatibility settings. Then return to String Translation and translate the strings that were registered.

JavaScript-string detection may affect performance, so disable it after the required strings have been scanned and registered. This process is diagnostic rather than a guaranteed fix. If an extension does not expose its text in a way WPML can register or configure, the string may still require further compatibility work.

Check the String Translation prerequisite

The documented Strings workflow depends on the WPML String Translation add-on being installed and active. Without it, the Strings tab and related string-management tools are unavailable. Before investigating domains or JavaScript behavior, confirm that this required component is present and active.

When making changes, avoid editing plugin files. File-level changes can be overwritten by plugin updates and can make later troubleshooting more difficult. Use a backup or staging test before applying translation or configuration changes to a production store, especially when the text is part of checkout or customer notifications.

Verification checklist before publishing translation changes

What translation does and does not change

Before publishing, review the complete customer path rather than checking only one isolated string. Test checkout in each target language and examine both the shipping method name and its description. Then review tracking notifications and tracking-page messages separately, because they may be supplied by different components or rendered in different ways.

  • Check the localized checkout in each target language.
  • Confirm that every relevant shipping method has the intended displayed name.
  • Review the description associated with each shipping option.
  • Test tracking-page messages separately from tracking-notification emails.
  • Recheck the relevant plugin or theme workflow if a string remains unavailable.
  • Use a staging test where possible before applying production changes.
  • Keep a backup before changing translation or related configuration settings.

A translation should change the language of displayed labels, descriptions and notifications. It should not be treated as a change to rates, carrier rules, delivery times, tax treatment or fulfillment behavior. If checkout behavior appears different after a configuration change, investigate that configuration separately from the translation itself.

Also verify that the selected string belongs to the correct plugin or theme. A similar phrase can appear in more than one domain, and translating the wrong entry may leave the customer-facing text unchanged. If the wording is loaded dynamically, repeat the frontend and JavaScript detection workflow only as needed, then disable JavaScript detection after scanning.

The normal starting point for WooCommerce shipping translations in WPML is WPML → Translations → Strings. Search by visible wording, plugin name or text domain, and treat shipping labels, checkout descriptions, tracking pages and notification emails as potentially separate groups. If a string is missing, load it on the frontend, scan the relevant plugin or theme through Admin Texts Translation, and use JavaScript detection only for text generated that way. Finally, verify every customer-facing context and remember that translation changes displayed language, not shipping logic. Explore our WordPress plugins, WooCommerce extensions, themes and membership plans to find the right tools for your website.

Free Worldwide shipping

You can download the products right away at wpbetterplugins.com

Immediate delivery

After the payment is credited, the product is ready for download

International Warranty

Offered in the country of usage

100% Secure Checkout

Stripe / Apple Pay / Google Pay / MasterCard / Visa

Zadzwoń