WooCommerce 11.1’s released on September 03, 2026. Additionally, WooCommerce 11.1 includes powerful features such as a complete order withdrawal flow for shoppers and a new REST API refund-calculation endpoint. The latest release also brings several bug fixes for the product CSV import and export, along with a focused set of compatibility changes for extension developers.
This blog post will discuss the features and improvements of WooCommerce 11.1.
Order Withdrawal
WooCommerce 11.1 includes the right of order withdrawal functionality to serve better and delight EU customers. As a result, customers can now request a withdrawal from the new My Account page (/my-account/withdraw-order/), no authentication needed.
Consequently, submissions are routed to merchants, who get an email and an inbox notification, allowing them to follow up with the customer. Order withdrawal is deactivated by default; users must enable it in WooCommerce -> Settings -> Advanced -> Features.
Product CSV Import and Export
Many bug fixes have been applied to Product Importing. These include preserving terms and categories in re-uploads and clearing images when the file indicates.
Apart from this, Product Importing now respects existing store currency settings and has improved handling of variation creation when the product is already present.
REST API Refunds and Store API Checkout Totals
The refund flow in the WC REST API has been updated to allow the server to calculate refund totals. Moreover, the new POST /wc/v3/orders/{id}/refunds/preview endpoint allows you to run the calculation and preview the refund without applying it.
In the Store API, checkout endpoints get an optional expected_total: integer field that represents the total the customer sees; if they are charged a different amount, the request will fail with a new 409 woocommerce_rest_checkout_total_mismatch response. This field is then implemented in the Checkout block.
Email Editor Updates
The block email editor lets core/embed insertable for providers that render clickable thumbnails: YouTube, Vimeo, VideoPress, TikTok, and Dailymotion, as well as the WordPress embed, which renders as a rich link card.
Additionally, users can still paste embeds from unsupported providers. That said, the editor gives a warning and provides a link to the delivered result.
Personalization tag callbacks now receive their destination content type. A tag can escape correctly for HTML, plain text, or an href. The new parameter is optional and defaults to HTML; automatic escaping applies only to newly registered text-typed tags.
Variable Product Performance
This release contains various performance fixes, mainly reducing N+1 queries around variations and attributes in both the editor and the frontend, as well as lessening queries related to price caching.
Block Registration is Skipped on Non-Rendering Requests
Previously, block types and patterns were registered on almost every request, not to mention that many did not edit blocks or render.
A new BlockRegistrationContext guard now skips registration on cron, AJAX, and REST API requests. Moreover, it helps preserve front-end, admin, and editor behavior.
One thing to note is that when a product or variation description consists of a WooCommerce block, block types are registered on demand via the woocommerce_short_description filter. Hence, descriptions still render correctly in the products REST API, the Store API, the variation AJAX endpoint, and product webhooks.
Extensions assuming block registration on every request must adapt. The new woocommerce_should_register_blocks filter rejoins in for extensions that render blocks in a skipped context.
Experimental Features
Unified Block Editor Assets
An experimental unified block editor assets feature uses shared JavaScript and CSS bundles to replace per-block editor scripts and styles. Remember that frontend assets remain unchanged. Testing unveiled substantial outcomes – 91.7% fewer editor assets, a 48.3% reduction in network transfer size, and 62.3% smaller style bundles.
The experiment is deactivated by default, and stores can choose to enable it in WooCommerce -> Settings -> Advanced -> Features -> Experimental features. When activated, WooCommerce blocks use the wc-block-library handle rather than individual block handles; editor styles are consolidated under wc-block-library-style; and legacy handles remain registered as placeholders that emit a deprecation warning when enqueued.
Product Gallery Videos Storage
Internal storage for a product video gallery works primarily behind the feature flag as the first step toward product gallery videos. Users can activate this by going to WooCommerce > Settings > Advanced > Features > Product gallery videos (Beta).
Developer Advisories and Compatibility
is_rest_api_request() previously identified only REST requests with pretty-permalink paths under /wp-json/. It now treats a non-empty rest_route query parameter as a REST request.
Wrapping Up
As you may be aware, the WooCommerce 11.1 was released on September 03, 2026.. It is another useful release that helps developers, store managers, and users optimize their WooCommerce stores.
WooCommerce 11.1 enables WooCommerce stores to improve efficiency, stability, and performance, resulting in better customer satisfaction and profitability.
