WooCommerce 10.5.2 released: a focused dot release to restore variable product add-to-cart behaviour
WooCommerce 10.5.2 is now available as the current stable tag, released on 16 February 2026. This dot release concentrates on a specific regression introduced in WooCommerce 10.5 that affected some shops using plugins or custom code to alter how product variations are selected.
The official announcement is available on the WooCommerce Developer Blog: https://developer.woocommerce.com/2026/02/18/woocommerce-10-5-2-dot-release/.
What changed in 10.5 and why 10.5.2 matters
WooCommerce 10.5 introduced a change that, for certain store configurations, caused variable products to become unpurchasable because the add-to-cart button could end up disabled. The common factor was variation-handling behaviour being customised, such as when a theme or plugin modifies, replaces, or dequeues the scripts responsible for managing variation selection.
The core issue: variation handling and disabled add-to-cart buttons
Variable products rely on front-end scripts to detect a valid variation choice and then enable the add-to-cart button once all required attributes have been selected. If a site uses custom JavaScript, a performance tool that alters script loading, or a plugin that adjusts variation behaviour, a change within WooCommerce can create unexpected interactions. In this case, a regression meant the logic that enables the button did not always run as expected, leaving customers unable to add variable products to their basket.
What 10.5.2 does: a revert to restore expected behaviour
WooCommerce 10.5.2 reverts the earlier changes that contributed to these compatibility issues. The goal is straightforward: restore the familiar behaviour so variable products can be added to the basket across a wider set of real-world configurations, including shops that have customised variation scripts.
What this update could mean for WooCommerce websites
If your shop uses variable products and you have seen a sudden drop in add-to-cart events, a rise in customer messages about “button not working”, or unusual abandoned baskets since moving to WooCommerce 10.5 or 10.5.1, updating to 10.5.2 may address the problem by returning to the previous working behaviour.
Compatibility improvements for shops using customisations
Many WooCommerce shops extend default behaviour. Examples include custom variation swatches, bespoke themes that modify product forms, scripts that preselect variations, or optimisation plugins that delay or rearrange JavaScript execution. A revert-style dot release is often the fastest way to restore stability when an update unexpectedly changes assumptions that third-party code depends upon.
Potential impact on conversions and customer experience
When variable products cannot be added to the basket, the impact is immediate: customers cannot complete purchases. Even intermittent failures can reduce trust and increase support requests. If 10.5.2 resolves the disabled add-to-cart state on your product pages, you may see an improvement in conversion rates and a reduction in checkout friction.
Questions and answers
Should every shop update to WooCommerce 10.5.2?
If you are already on WooCommerce 10.5 or 10.5.1, updating to 10.5.2 is sensible because it specifically targets a compatibility regression. If you are on an earlier stable version and have no issues, you can still update, but treat it as you would any production change: test first if you have a complex theme or a large plugin stack.
How can I tell if my shop is affected by the regression?
A common symptom is that variable products display attribute selectors correctly, but the add-to-cart button remains disabled even after selecting valid options. Another sign is inconsistent behaviour across devices or browsers, especially where script loading order differs due to caching and performance settings.
What kinds of custom code are most likely to have been impacted?
Customisations that modify variation selection events, replace WooCommerce’s variation scripts, or dequeue core scripts in favour of alternatives are the typical candidates. Sites that use swatch plugins, custom product forms, or performance tooling that defers JavaScript may also be more exposed to subtle front-end regressions.
Does this change anything for simple products?
This release focuses on variable products and the add-to-cart enabling logic tied to variation selection. Simple products generally use a simpler add-to-cart flow, so they are less likely to be affected by this particular regression.
Practical ideas for shop owners and developers after updating
Re-test variable products that use swatches, bundles, or custom selectors
If your store uses variation swatches, custom dropdown replacements, or additional UI elements that drive variation selection, check that selecting attributes reliably enables add-to-cart and that the correct variation is added to the basket.
Review performance and script optimisation settings
Some caching and optimisation configurations can change JavaScript execution timing. After updating, it is worth validating that deferred or delayed scripts do not reintroduce the disabled button state. If your site uses a “delay JavaScript” feature, ensure the variation-handling scripts are not held back until after user interaction in a way that prevents WooCommerce from detecting selections properly.
Monitor key metrics that may have been affected
After deploying 10.5.2, keep an eye on add-to-basket rates for variable products, product page exit rates, and customer support queries tied to purchasing. A small regression can show up quickly in these indicators, and a fix often produces an equally noticeable recovery.
Why dot releases like 10.5.2 are significant
WooCommerce runs on WordPress, the content management system that powers a large portion of the web. WordPress sites often rely on themes and plugins working together, and changes in one component can expose unexpected dependencies in others. Dot releases exist to stabilise behaviour quickly without waiting for a larger feature release cycle, which is especially important when the issue impacts the ability to sell products.
