WooCommerce 11 updates: what changed in 2026 and how to update

At the time of writing (November 2026), the current stable WooCommerce release is 11.2.1, and WooCommerce 11.3 is scheduled for the week of 9 November 2026. WooCommerce labelled 11.0 and 11.1 as backwards compatible, but several releases include database updates and behaviour changes that can affect custom code and extensions. Most stores should update, but test on staging first rather than clicking update on a live shop.

Here is what changed between 11.0 and 11.3, what it means for store owners and developers, and a safe process for updating.

WooCommerce releases at a glance

WooCommerce now needs WordPress 7.0 or higher and PHP 7.4 or higher, according to its WordPress.org listing.

What changed for store owners

WooCommerce 11.0

• Guest order claiming: customers can find earlier guest orders and link them to their account, with email validation.
• Performance work on queries, the Store API and stock status handling, aimed mainly at stores with large catalogues or many orders.
• Analytics: refunds are now factored into sales endpoints, and failed historical data imports can be retried.
• Experimental features: abandoned cart emails, block-based email editing and a new settings interface. They are labelled experimental, so try them on staging first.

WooCommerce 11.1

• Variation image galleries are now native and enabled for all stores. The database update switches them on even for stores that had opted out, and the WooCommerce Additional Variation Images extension is being retired.
• An optional right of withdrawal feature for EU orders, disabled by default, which adds a withdrawal request form to My Account. Withdrawals and refunds remain manual. If you sell to EU consumers, check with your legal adviser what your obligations are; this is general information, not legal advice.
• Product gallery videos (beta), off by default and limited to locally uploaded videos.

WooCommerce 11.2

• The CSV importer can match existing products by GTIN, UPC, EAN or ISBN when there is no ID or SKU.
• New configurable emails for order withdrawal requests, for both customer and merchant.
• Security fixes. The release notes ask merchants to update all stores to 11.2.

WooCommerce 11.3

• On-sale badge options: show text, the amount saved or the discount percentage, with prefix and suffix text.
• More styling controls (colours, spacing and borders) on Product, Featured Product, Featured Category and Product Categories List blocks.
• A refund and returns policy page setting under Settings, Advanced, Page setup, which WooCommerce links in structured data.
• Analytics: orders gain a payment method column, CSV export column and filter.
• The legacy Reports screen is being retired. It is hidden on new stores installed on 11.3 or later, and WooCommerce recommends moving to Analytics.

Changes developers should check

The pre-release posts list several changes that can break custom integrations:

• 11.1: blocks are no longer registered on requests that cannot render them, which WooCommerce says makes Store API and REST requests 30 to 42% faster. Extensions that render WooCommerce blocks in those requests need the woocommerce_should_register_blocks filter.
• 11.2: PublishPress Future versions 3.0.0 to 4.10.3 can cause a fatal error. Update it to 4.10.4 or later before updating WooCommerce. Malformed download permission data is now rejected, so custom or imported download links may need reissuing.
• 11.3: the on_sale filter combined with include or exclude now returns stricter results in the REST and Store APIs.
• 11.3: refund requests through the REST API are rejected with HTTP 400 or 422 if line-item amounts contradict the total or exceed the refundable balance.
• 11.3: custom analytics SQL that joins wc_orders and uses a bare payment_method column will fail with an ambiguous column error. Prefix it with the table name.
• 11.3: the deprecated /wp-json/woocommerce/mcp endpoint is removed. AI and MCP clients should use the WordPress MCP Adapter plugin with an application password.

Large stores should also note the 11.3 analytics migration. WooCommerce says adding the new column is instant on MySQL 8.0 or later with InnoDB, but the index needs roughly 47 MB per million orders, and on MySQL 5.7 the whole table is rebuilt. Schedule that update for a quiet period.

Read the release notes, update on staging, test checkout end to end, then update production.

How to update WooCommerce safely

1. 1 Back up the site and database. Several 11.x releases include database updates.
2. 2 Update WordPress core and PHP first if they are behind, so WooCommerce's requirements are met.
3. 3 Check extension compatibility, especially payment gateways, shipping plugins, subscriptions and anything named in the release notes.
4. 4 Update on staging and test the full journey: product pages, variations, cart, checkout with each payment method, order emails, refunds and downloadable products.
5. 5 Check the admin: orders, analytics, any custom reports and integrations that read order data.
6. 6 Update production during a quiet period and watch for failed payments or errors over the next day.

Frequently asked questions

Should I update to WooCommerce 11.3 on release day?

If your store relies on custom code or several extensions, waiting a few days lets any maintenance release land and lets extension authors confirm compatibility. Security releases are different: apply those promptly after a quick test.

Do I still need the Additional Variation Images extension?

Variation galleries are built into WooCommerce from 11.1, and the extension is being retired. Test the native feature on staging and plan to remove the extension.

What happens to the old WooCommerce Reports screen?

It is being retired. From 11.3 it is hidden on new stores, and WooCommerce recommends moving your reporting to Analytics now.

Need help with WooCommerce updates?

If you would prefer someone to test and apply WooCommerce updates for you, our WordPress and WooCommerce team can audit extensions, run staging tests and fix compatibility issues. If performance is on your list too, see our guide to speeding up a slow WordPress site, or get in touch about your store.

Sources: WooCommerce 11.0 release notes, WooCommerce 11.1 release notes, WooCommerce 11.2 release notes, WooCommerce 11.3 pre-release, WooCommerce on WordPress.org