WooCommerce 11.1 shipped on September 1, 2026, and the headline change is that product variation image galleries are now a native, free feature — no extension required — alongside a 30–42% speed boost to the Store API and REST API. Most stores can update without issue, but a few changes touch custom code around product variations and refunds, so it’s worth checking before you click update.
What’s New in WooCommerce 11.1
Variation Galleries Are Now Built In
Until this release, giving each product variation (each color or size) its own image gallery meant installing a separate extension. WooCommerce 11.1 enables Variation Galleries for every store by default. If you sell products with meaningfully different variations — different colors of the same jacket, different finishes on the same part — customers can now see photos specific to the variation they’ve selected, out of the box.
Experimental Product Gallery Video Support
Both classic and block-based product galleries can now include video, in addition to images. This is disabled by default and marked experimental — turn it on under WooCommerce → Settings → Advanced → Features → Product gallery videos. Test it on a staging copy first; experimental features in WooCommerce sometimes change behavior between point releases.
Faster REST API and Store API
WooCommerce’s own benchmarks show Store API and REST API requests running 30–42% faster in 11.1, plus additional performance work for variable products and block registration. If your site (or a plugin you run) leans on the REST API — inventory sync tools, headless storefronts, custom quote or pricing plugins — this is a straightforward win with no configuration needed.
Unified Block Editor Assets (Experimental)
An experimental option consolidates the separate JavaScript and CSS files each WooCommerce block used to load into shared bundles. WooCommerce’s testing measured 91.7% fewer editor assets, a 48.3% smaller network transfer, and 62.3% smaller style bundles in the block editor. This only affects the admin editor experience, not your storefront’s frontend performance — but if you manage a catalog with dozens of block-based product pages, editor load times should feel noticeably lighter once you enable it.
New Refund Endpoint and EU Right of Withdrawal
The REST API gains a dedicated refund endpoint with more accurate refund detail in responses, and stores serving EU customers get built-in support for the EU’s right-of-withdrawal requirements. Product CSV imports also got reliability improvements in this release.
| Feature | Status | Where to enable | Who it affects |
|---|---|---|---|
| Variation Galleries | Stable, on by default | No action needed | Any store with product variations |
| Product gallery videos | Experimental, off by default | Settings → Advanced → Features | Stores with video assets |
| Faster REST/Store API | Stable, automatic | No action needed | Sites using custom plugins or headless frontends |
| Unified block editor assets | Experimental, off by default | Settings → Advanced → Features | Stores with large block-based catalogs |
| Refund endpoint + EU withdrawal | Stable, automatic | No action needed | EU-facing stores, refund/accounting integrations |
Should You Update Now?
For most stores, yes — the stable changes are additive and low-risk. Run through this before you do:
- Take a full backup (database and files) before updating, not just a plugin snapshot.
- Update on a staging copy first if you run any custom code that hooks into product variation data or the REST API’s order/refund endpoints.
- Leave the two experimental features (video galleries, unified block assets) off until you’ve tested them on staging — they’re opt-in for a reason.
- If you use a separate variation-gallery extension, check its changelog for a compatibility note before updating — running two systems that both try to manage variation images can conflict.
- Re-test any custom pricing, quote, or subscription plugin that reads variation or refund data through the REST API, since the underlying response shapes changed slightly for refunds.
If You’re Running Custom WooCommerce Plugins
Most compatibility problems after a WooCommerce update come from custom code making assumptions about internal data structures that the update quietly changes — we cover a general process for catching this before it reaches customers in Plugin Compatibility Testing: A Better Way to Prevent Site Breaks. If you’re not sure whether a custom plugin on your store touches the parts of WooCommerce that changed in 11.1, get in touch and we can review it before you update production.
Frequently Asked Questions
Is WooCommerce 11.1 safe to update to right away?
For most stores yes, since the stable changes are additive. If you run custom code touching product variations or refunds, test on staging first before updating production.
Does WooCommerce 11.1 break custom product variation code?
Not by default, but Variation Galleries are now built in and enabled automatically, so if you use a separate variation-gallery extension, check its changelog for a compatibility note before updating.
Do I need to do anything to get the new Variation Galleries feature?
No — it’s enabled for every store automatically in 11.1. Product gallery videos and unified block editor assets are the two features you have to turn on manually, since both are still experimental.
Featured image: original illustration.