WooCommerce 10.6.1: Dot Release

WooCommerce 10.6.1 has been released.

WooCommerce 10.6.1 is a maintenance release fixing issues including attribute validation in the Add to Cart block, payment gateway ordering in settings, and shipping address field display.

Current Stable Tag

👉 WooCommerce 10.6.2

Released — March 12, 2026

What’s in this release

Fixed attribute options being incorrectly disabled in the Add to Cart with Options block for variable products whose attribute slugs contain hyphens. The issue occurred because PHP passes attribute names as slugs (e.g., some-name) while the Store API returns labels with spaces (e.g., some name), causing strict comparisons to fail. The fix updates normalizeAttributeName() to replace hyphens with spaces, ensuring consistent normalization across all comparison points. #63647

Newly installed payment gateways now appear above offline payment methods instead of being placed at the bottom of the list. Previously, installed gateways were buried below others, preventing them from being expanded by default on checkout. The updated placement logic inserts new gateways above the offline payment group unless merchants have customized the ordering. #63648

Shipping package titles in the shortcode now displays as “Shipment” instead of “Shipment 1” when only one package is present. The get_shipping_package_name() method now receives the total package count, allowing it to conditionally name single packages as “Shipment” while multiple packages continue to show numbered labels like “Shipment 1” and “Shipment 2”. #63649

8 responses to “WooCommerce 10.6.1: Dot Release”

Niraj

March 12, 2026

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.

Reply
1. Brian Coords
  
  March 12, 2026
  
  Hey Niraj,
  
  The string is set up to be translatable, so it may be an issue with the translation plugin not catching it or having a cached/stale version of what strings are available.
  
  If you’re still having issues, a temporary workaround would be taking advantage of the woocommerce_shipping_package_name filter and overriding it/
  
  Code of translatable string:
  https://github.com/woocommerce/woocommerce/pull/63649/changes
  
  Reply
Régis

March 20, 2026

Hi there,

the release still does not solve the problem at all on our web site. All option blocks are marked as unavailable, nobody can order a product…

Régis

Reply
1. Brian Coords
  
  March 20, 2026
  
  Hi Régis,
  
  A follow-up release with a more robust fix is being tested and should be coming next week.
  
  You can also rollback to WooCommerce 10.5.3 in the meantime.
  
  Reply
Audra Carpenter

March 23, 2026

Hi, we’re also running into an issue where Free Freight is now showing as an option when the UPS options are shown?

The model is, $199 and over is free. And products of a certain weight are Freight (and are free). But the update is now showing all shipping options even when freight shouldn’t be shown.

We are using the official Woo plugin for UPS and reading about it, it looks like there isn’t a way to create a rule to NOT show freight with products unless marked freight in the shipping selection. Haven’t been able to figure a way around it.

Love some direction or ideas here.

Reply
Adil

March 29, 2026

Hi WooCommerce team,

I would like to request a native option to allow customers to submit a product review by giving only a star rating, without being forced to write review text.

Current behavior requires a written comment together with the rating. In many stores, this creates unnecessary friction and reduces the number of reviews submitted, especially on mobile.

Suggested improvement:
Please add a setting such as:

“Allow rating-only reviews”
or
“Make review text optional”

This would let store owners choose between:
– rating + written review required
– rating required, written review optional
– both rating and written review optional/required based on store preference

Why this would be useful:
– lowers friction in the review flow
– can increase review submission rates
– improves mobile usability
– gives merchants more flexibility depending on their review strategy
– avoids the need for custom code or template overrides for a very common use case

This should ideally work natively with WooCommerce product reviews, including verification settings and moderation flow.

I believe this would be a valuable built-in feature for many merchants.

Thanks.

Reply
1. Shani Banerjee
  
  March 30, 2026
  
  Hi Adil,
  
  You can suggest this as a feature request in GitHub issues: https://github.com/woocommerce/woocommerce/issues
  
  I believe it exists as a coupled option for now so that customers cannot leave a disparaging star review without giving feedback. The ability to make it optional is interesting though! Please submit it through GitHub so it can be seen by our Product and Engineering teams.
  
  Reply
  1. Adil
    
    April 1, 2026
    
    Hi Shani,
    
    Thanks for the reply. I’ve already submitted this through the official feature request page, since GitHub redirects feature requests there. I hope the Product and Engineering teams can consider it, as I believe this would be a very useful native option for many stores.
    
    Reply