Testing Guidelines

Hi @samnajian @senadir ,

Apart from reviewing the code changes, please make sure to review the testing instructions (Guide) and verify that relevant tests (E2E, Unit, Integration, etc.) have been added or updated as needed.

Reminder: PR reviewers are required to document testing performed. This includes:

• 🖼️ Screenshots or screen recordings.
• 📝 List of functionality tested / steps followed.
• 🌐 Site details (environment attributes such as hosting type, plugins, theme, store size, store age, and relevant settings).
• 🔍 Any analysis performed, such as assessing potential impacts on environment attributes and other plugins, conducting performance profiling, or using LLM/AI-based analysis.

⚠️ Within the testing details you provide, please ensure that no sensitive information (such as API keys, passwords, user data, etc.) is included in this public issue.

Test using WordPress Playground

The changes in this pull request can be previewed and tested using a WordPress Playground instance.
WordPress Playground is an experimental project that creates a full WordPress instance entirely within the browser.

Test this pull request with WordPress Playground.

Note that this URL is valid for 30 days from when this comment was last updated. You can update it by closing/reopening the PR or pushing a new commit.

Dear WooCommerce Support Team,

After updating our store to WooCommerce version 10.6.1, we noticed that the recent fix introduced the label “Shipment” instead of “Shipment 1” on the checkout page, which we understand was intended as an improvement.

However, we are currently facing another issue related to this change. In our store, we previously customized this label to “Delivery Charges” using Loco Translate. After the update, the text “Shipment” no longer appears in the translation strings, and even when we attempt to translate it through Loco Translate, the label on the checkout page does not change.

This creates a problem because our checkout page now displays “Shipment”, while our store terminology requires “Delivery Charges” for better clarity for customers.

We kindly request your team to review this behavior and advise whether:

The string “Shipment” is now generated dynamically and therefore cannot be translated via standard translation files.
There is a recommended filter or hook that allows store owners to modify this label.
A fix or improvement can be included in an upcoming WooCommerce update to allow proper translation/customization.

For reference, this issue started after the fix mentioned in the WooCommerce changelog:

We would greatly appreciate your guidance on how to properly change this label to “Delivery Charges.”

Thank you for your continued support and for the improvements your team brings to WooCommerce.

https://drive.google.com/file/d/1BZXJU7GLFUuxOZ73RfutAl2aislrEtCn/view?usp=drivesdk

@jpelectronicindia-droid Does the string not show up after you press "Sync" in Loco Translate? (the button is visible on the image you posted)
If not, you can use this filter in your child theme's functions.php or a mu-plugin:

add_filter('gettext_with_context_woocommerce', function($translation, $text, $context) {

	if($context === 'shipping packages') {

		if($text === 'Shipment') {
			return 'Delivery Charges';
		}

		if($text === 'Shipment %d') {
			return 'Delivery Charges %d';
		}
	}

	return $translation;
}, 10, 3);

Dear WooCommerce Support Team,

After pressing “Sync” in Loco Translate, the string “Shipment” still does not appear in the translation list. Because of this, it cannot be translated directly through Loco Translate.

As a temporary workaround, we tested the following filter in the child theme’s functions.php, which successfully changes the label from “Shipment” to “Delivery Charges” on the checkout page:

add_filter('gettext_with_context_woocommerce', function($translation, $text, $context) {

    if($context === 'shipping packages') {

        if($text === 'Shipment') {
            return 'Delivery Charges';
        }

        if($text === 'Shipment %d') {
            return 'Delivery Charges %d';
        }
    }

    return $translation;
}, 10, 3);

However, the issue remains that the string added/changed via Loco Translate is not detected or translated, even after syncing.

Could you please advise on how this string can be properly made translatable in Loco Translate, or confirm if this is a known issue introduced in WooCommerce 10.5?

gettext_with_context_woocommerce

@jpelectronicindia-droid
As gettext_with_context_woocommerce filter works, it confirms WordPress is seeing a normal translation string at run time, the bug can be in your local translation files or the Loco translate plugin.