WooCommerce 11.1 makes variation image galleries native
Released on , WooCommerce 11.1 promotes variation image galleries to a core feature on every store and retires the extension that used to provide them. Read the WooCommerce release note here.
WooCommerce 11.1 arrived with 561 merged pull requests from 77 contributors. The release is backwards compatible and it carries a database update, numbered 11.1.0-1. That database update is the part worth reading twice, because it switches variation image galleries on for every store, including stores that had previously opted out of the experimental version.
The gallery change is the headline, but it is not the only thing here a merchant will notice. WooCommerce 11.1 also adds an order withdrawal workflow for stores that need to meet EU consumer rules, stops showing meaningless shipping addresses on virtual orders in the admin, ships beta support for video in product galleries, and makes Store API and REST requests between 30 and 42 per cent faster. For a release that breaks nothing, it touches a lot of surfaces store owners actually look at.
How it works
Before 11.1, showing more than one image per product variation meant installing WooCommerce Additional Variation Images, or relying on a theme that implemented its own version. WooCommerce 11.1 makes the capability native and the extension is being retired. There is nothing to enable. The experimental toggle has been removed from the Features screen, and the 11.1.0-1 database update turns the feature on across the board.
The opt-out detail is the sharp edge. A store that trialled the experimental gallery and deliberately switched it off does not stay switched off. The database update enables it anyway. If a product template, a custom theme, or a page builder made assumptions about a single image per variation, that assumption gets tested on live traffic without anyone choosing to test it.
The performance work is quieter but broader in reach. WooCommerce no longer registers block types and patterns on requests that cannot render or edit blocks, which covers most Store API and REST traffic. The result is requests that come back 30 to 42 per cent faster. Extensions that genuinely do render WooCommerce blocks during those requests can opt back in through a new woocommerce_should_register_blocks filter. Product and variation descriptions are handled on demand and need no change at all.
The order withdrawal feature is disabled by default. Switching it on adds a screen to the My Account area where a customer submits a withdrawal request. The request is logged and the merchant is notified by email and in the dashboard. Actually withdrawing and refunding the order stays a manual job, because the process differs from store to store and WooCommerce does not try to guess it.
Two smaller changes round the release out. Orders that need no fulfilment no longer display a shipping address in the admin order summary, so a virtual-only order stops showing a billing-derived address that meant nothing. Store API checkout still retains that data for compatibility, and physical, mixed and unresolved orders keep their details. Separately, video support in the product gallery arrives as an experimental feature, off by default, covering both classic and block-based galleries and accepting locally uploaded video only.
Examples and use cases
A clothing retailer selling the same jacket in four colourways is the obvious winner. Until now that store either paid for an extension or accepted a single photograph per colour. From 11.1 each variation carries its own gallery natively, so a customer selecting olive sees olive from the front, from the back, and in the detail shot, with no plugin sitting in the dependency chain.
The flip side is the store that made a deliberate decision to keep galleries off. Consider a furniture retailer whose variations are sizes rather than finishes, where every variation shares the same photography. Turning galleries on adds nothing for shoppers and may surface duplicate images in the gallery strip. That store now has the feature enabled by a database update it did not request, and the remedy is a template or settings change rather than a toggle on the Features screen.
The order withdrawal screen suits a UK store with meaningful sales into the EU. Rather than fielding cancellation requests through a contact form and hoping somebody spots them, requests arrive logged and notified, which is a materially better audit trail if a dispute goes anywhere. The refund itself still needs a human, so treat it as a workflow improvement rather than automation.
The performance change is most visible on headless builds and on stores leaning heavily on the Store API for cart and checkout. A 30 to 42 per cent reduction on requests that fire during nearly every interaction compounds quickly across a busy catalogue, and it arrives without anyone writing a line of code.
What this means for UK merchants
The first job is an inventory check. Any store running WooCommerce Additional Variation Images needs a plan, because the extension is being retired and the core feature replaces it. Agencies managing several WooCommerce sites should treat this as a portfolio question rather than a per-site one: find every store with the extension installed, confirm the native gallery renders correctly in the active theme, then remove the extension. That is exactly the kind of work a planned WordPress maintenance routine exists to catch before a customer does.
The gallery change also has a search dimension that is easy to miss. More images per variation means more image markup, more alt text to write, and more weight on product pages that may already be heavy. Galleries that ship with empty alt attributes or unoptimised uploads will cost more than they return. If product imagery is a meaningful part of how a store gets found, the rollout is a sensible moment to review how those product pages are built for search, which is the ground WooCommerce SEO work covers.
On the order withdrawal feature, be precise about what it does and does not do. It is built for stores conforming to EU guidelines and it is off by default. UK merchants selling to UK consumers already sit under the Consumer Contracts (Information, Cancellation and Additional Charges) Regulations 2013, which give a 14 day cancellation right on most distance sales, so the underlying obligation is not new even though the WooCommerce screen is. Whether to enable it is a commercial and legal decision rather than a technical one, and it is worth taking your own advice on how a logged request should map to your existing cancellation process.
Practical considerations
Update on staging first, and specifically test the database update rather than just the plugin version bump. Version 11.1.0-1 changes behaviour on stores that had opted out, so staging is the only place to find out what your theme does with multiple variation images before customers do it for you.
Treat the video gallery as a beta, because that is what WooCommerce calls it. It is disabled by default, it accepts locally uploaded video only, and the release notes say it may change in future versions. Locally uploaded video also means your own hosting serves the file, which on shared UK hosting is a bandwidth and page weight question before it is a merchandising one.
Developers maintaining extensions have two deprecations to note. A set of stable WooCommerce Admin features now load directly rather than through the feature configuration pipeline. Features::is_enabled() and window.wcAdminFeatures still return compatibility values, but they now emit deprecation warnings, so those gates should come out before the shims do. Separately, WC_Abstract_Order::remove_order_items() now records which item IDs existed when removal was requested, so replacement items an extension adds before save are no longer deleted by accident. Most extensions need no change, but anyone maintaining a custom order data store should review their get_item_ids() and delete_items_by_ids() implementations.
One further item is worth knowing about even though it does nothing yet. Unified block editor assets, which replace per-block editor scripts and styles with shared bundles, ship as an experimental feature that is disabled in 11.1. With it off, existing handles and per-block assets behave exactly as before, and front end assets are unchanged either way.
FAQ
Do I need to enable variation image galleries in WooCommerce 11.1?
No. The feature is native in 11.1 and is switched on by the 11.1.0-1 database update, including on stores that had previously opted out of the experimental version. The toggle has been removed from the Features screen, so there is nothing left to turn on.
What happens to the WooCommerce Additional Variation Images extension?
It is being retired. WooCommerce 11.1 provides variation galleries natively on every store, so the extension is no longer needed. Stores running it should confirm the native gallery renders correctly in their active theme, then remove it.
Is WooCommerce 11.1 a breaking release?
No. WooCommerce describes 11.1 as backwards compatible. It does run a database update (11.1.0-1) that changes behaviour on stores which had opted out of variation galleries, so testing on staging before updating production is still the sensible order of operations.
Does the EU order withdrawal feature apply to UK stores?
The feature is disabled by default and is built for stores that need to conform to EU guidelines. UK merchants selling to UK consumers already have obligations under the Consumer Contracts (Information, Cancellation and Additional Charges) Regulations 2013, which give a 14 day cancellation right on most distance sales. Whether to enable the screen is a commercial and legal decision rather than a technical one.
How much faster are Store API and REST requests in WooCommerce 11.1?
Between 30 and 42 per cent. WooCommerce achieves this by skipping block type and pattern registration on requests that cannot render or edit blocks. Extensions that do render WooCommerce blocks on those requests can opt back in using the new woocommerce_should_register_blocks filter.
Can I add video to product galleries in WooCommerce 11.1?
Yes, as an experimental feature that is off by default. Enable it under WooCommerce, Settings, Advanced, Features, Product gallery videos. It works in both classic and block-based galleries, supports locally uploaded videos only, and may change in future releases.
