WooCommerce 11.1.0 was released on September 3, 2026, two days after its planned date, after release candidate testing found mini cart issues. It turns on variation image galleries for every store, adds an optional EU order withdrawal form and raises the minimum WordPress version to 7.0.
The release lists 561 pull requests from 77 contributors and includes a database update. PHP 7.4 remains the minimum PHP version.
Variation image galleries for every store
Variation galleries, introduced as an opt in feature in 10.9, are enabled for all stores in 11.1 and the feature toggle is removed. The WooCommerce Additional Variation Images extension is retired and automatically deactivated on update. If migration has not already completed, an Action Scheduler job copies gallery data from the extension's meta key into core, up to 250 variations per run, without overwriting galleries that already exist. A database update numbered 11.1.0-1 switches the feature on even for stores that had opted out earlier.
Stores using Additional Variation Images. WooCommerce itself recommends testing this upgrade on staging for large variation catalogs. We run the update on a staging copy, wait for the migration jobs to finish, then compare variation galleries against production product by product and check theme templates or custom code that read the old meta key.
An optional order withdrawal form for EU customers
Order Withdrawal is disabled by default. Once enabled under WooCommerce, Settings, Advanced, Features, a request form is available at /my-account/withdraw-order for logged in and guest customers, who can request a withdrawal within 14 days of placing an order. The customer gets an acknowledgment email and the merchant gets an email and an inbox notification. Requests that match an order number and billing email are linked to that order with an order note. Submitting a request does not change the order status or issue a refund, and WooCommerce notes the feature may help but does not guarantee legal compliance.
Selling to customers in the EU. The form is not linked anywhere by default, so enabling it is only half the job. For clients selling into the EU, we enable it on staging, add links in the footer and order emails, and write a short internal process for the team covering how to review a request and issue any refund by hand. Legal questions go to the client's own advisor.
Store API and REST requests get 30 to 42 percent faster
WooCommerce 11.1 no longer registers block types and patterns on requests that cannot render or edit blocks, which WooCommerce says makes Store API and REST requests 30 to 42% faster. Extensions that render WooCommerce blocks during such requests can opt back in with the woocommerce_should_register_blocks filter.
Custom endpoints that render blocks. A custom endpoint that returns rendered product blocks could come back empty after this change. We check client plugins and headless frontends for block rendering inside API requests and add the filter only where it is genuinely needed.
Virtual order addresses and product gallery videos in 11.1
- Orders that need no fulfillment no longer show a shipping address in the admin order summary
- Product galleries can include locally uploaded videos as an experimental feature, off by default
- An experimental option bundles block editor scripts and styles into shared files
remove_order_items()records which items existed when removal was requested, so replacement items are not deleted- A set of stable WooCommerce Admin feature flags now load directly, with deprecation warnings for code that still checks them
Order item deletion and shared editor bundles
WC_Abstract_Order::remove_order_items() now keeps a record of the item IDs present when removal was requested, so items an extension adds before $order->save() survive. WooCommerce says 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. Separately, the experimental unified editor assets option replaces per block editor scripts and styles with shared JavaScript and CSS bundles; frontend assets are unchanged either way.
Custom order storage and editor tooling. Some client builds include bespoke order storage or integrations that rebuild line items. We review those methods against the new deletion behavior and, where editor load time is a complaint, trial the shared bundle option on staging before deciding whether it stays on.
WordPress 7.0 is now required
WooCommerce 11.1 requires WordPress 7.0 or newer, up from WordPress 6.9 in WooCommerce 11.0.
Stores still on WordPress 6.9. Stores that have not moved to WordPress 7.0 will not be offered WooCommerce 11.1. We schedule the WordPress 7.0 upgrade first, retest the theme and checkout, and only then apply WooCommerce 11.1 with its gallery migration.
WooCommerce 11.1 FAQ
Do I need to remove Additional Variation Images myself?
No. WooCommerce automatically deactivates the extension on update and migrates its gallery data into core.
Does order withdrawal issue refunds automatically?
No. A request does not change the order status or issue a refund; the store handles each request manually.
What does WooCommerce 11.1 require?
WordPress 7.0 or newer and PHP 7.4 or newer.
Moving to WooCommerce 11.1 means WordPress 7.0, a gallery migration and possibly a new withdrawal process. Our support and maintenance plans handle all three on staging before anything changes for your customers. Contact us to plan the update.
