WooCommerce 11.1: What Actually Changed (September 2026)

WooCommerce shipped version 11.1.0 in the first week of September 2026 – two days later than originally planned, after the team found problems during testing that were worth holding the release for. Here is what actually changed, dated and sourced from WooCommerce's own developer blog, and what it means if you are running WooCommerce or weighing it against Shopify.

Shipped two days late, on purpose

WooCommerce had targeted 1 September 2026 for the 11.1.0 release. On that date, the team posted that it was holding the release after finding “certain issues around the mini cart” during testing of the first release candidate, along with some additional fixes worth including. A second release candidate followed, and the stable version went out on 3 September. Two days is not a long delay, but it is a useful, honest data point: even a mature, widely used open-source project still catches release-blocking bugs at the last minute, and holding a release rather than shipping around a known cart bug is the right call to make.

It is also a reminder of what an open, community-maintained release cycle looks like from the outside – a public post naming the exact problem, a short revised timeline, and a version that shipped once testing actually passed, rather than a fixed date defended regardless of what testing turned up.

The headline change: variation images, on by default

The most visible change in 11.1.0 is that product variation image galleries are now enabled by default for every store. Previously, showing a distinct set of gallery images per variant – a different photo set for each colour of the same t-shirt, for instance – required a separate extension called Additional Variation Images. WooCommerce is folding that functionality into core and retiring the standalone extension, which is a reasonable move: a common storefront need moving from a bolt-on extension into the base product is generally good news for a store that was paying for or maintaining that extension separately.

This is the kind of change that matters most to fashion and accessories sellers, where the same product often comes in several colourways and a shopper expects the gallery to update to match whichever swatch they click, rather than showing one generic product shot regardless of the variant selected. Stores that previously worked around the missing feature with a manual gallery hack, or simply accepted a mismatch between the selected colour and the photo shown, get a first-party fix instead of a patched-together one.

Two features shipped cautiously, switched off by default

Two other additions are worth knowing about even though neither is turned on out of the box. The release adds support for an EU order withdrawal feature, letting customers submit a withdrawal request through their account – relevant for stores selling into the EU, where consumer rights around order cancellation are a real compliance area, though the feature ships disabled and each store needs to evaluate whether and how to switch it on for their own situation. The second is experimental support for video in product galleries, limited for now to locally uploaded video files rather than externally hosted ones, also disabled by default. Both being off out of the box is a sensible way to ship a feature that touches either legal compliance or media handling – it gives store owners the choice rather than changing behaviour under them.

A performance claim worth checking on your own store

WooCommerce's own release notes state that Store API and REST requests run 30 to 42 percent faster in 11.1.0, attributed to optimised block registration that skips processing for requests that will not end up rendering blocks anyway, plus unified block editor assets that cut down the number and size of editor-related requests. That is a meaningful claimed improvement if it holds up, though it is worth treating as the vendor's own benchmark rather than an independently verified number until you have measured it against your own store's traffic and block usage. If your store leans heavily on the block editor or makes frequent Store API calls, this is one worth testing directly with your own before-and-after numbers rather than taking on faith.

The Store API specifically underpins a lot of what a shopper actually feels as speed – the cart drawer updating when a quantity changes, a mini-cart total refreshing without a full page reload, block-based checkout steps loading their data. A genuine improvement there is more likely to be felt on a mobile connection, where every extra round trip to the server costs more relative time than it does on a fast desktop connection.

What this means if you are running WooCommerce today

The release is described as backwards compatible and requires a database update on install – standard practice for a WooCommerce version bump, but worth planning around rather than running during a peak sales window, on general principle rather than any specific warning in this release. Beyond that, 11.1.0 came out of a genuinely large release cycle: 561 pull requests from 77 contributors, according to WooCommerce's own release notes, which is a reasonable proxy for how active and well-resourced the core project currently is. If you rely on the retired Additional Variation Images extension specifically, check that your store's variant images still display as expected after the update rather than assuming the migration to core functionality is silent and complete on every setup.

The practical advice is unchanged from any WooCommerce release: run the update on a staging copy of your store before touching the live site, particularly given the database update, and confirm checkout still works end to end with a real test order once it is live. None of the changes in 11.1.0 are described as breaking, but “backwards compatible” in a release note is a starting assumption to verify against your own specific combination of theme and plugins, not a guarantee that covers every installed setup.

The wider point: this is what “free” software still costs

None of this is a criticism of WooCommerce – a two-day delay to fix a mini-cart bug is exactly the caution you want from a platform millions of stores run on. But it is a useful, concrete illustration of something worth remembering when you hear WooCommerce described as the free alternative to a hosted platform: someone still has to track release notes, plan update windows around sales periods, and verify that a retired extension's replacement behaves the way the old one did. That work is real even when the software itself costs nothing, and it is the trade-off we go through in more detail in our Shopify vs WooCommerce cost comparison.

Where this leaves a Shopify-curious store owner

If update-tracking and compatibility-checking is not how you want to spend a Tuesday, it is a fair reason to prefer a hosted platform that handles this layer for you. Shopify folds this kind of maintenance into its subscription, and on the theme side, Kiosk builds numbered Shopify editions with the features stores commonly reach for extensions to get – wishlist, quick view, subscriptions, bundles – included in the theme rather than sold and maintained separately. See the full range at Kiosk, including two free editions if you would rather look at the code first.