WooCommerce 11.1 new features: order withdrawal, variation galleries and what § 20a still needs

WooCommerce 11.1 new features come down to three things: a native order withdrawal form for EU customers, image galleries for product variations, and faster REST and Store API requests. The version came out in early September 2026, and the current stable release is 11.1.2 from 22 September 2026. The withdrawal form is disabled by default. A Slovak store cannot simply switch it on and treat its obligation under § 20a of the Slovak consumer protection act as met: the form is not linked anywhere, and as of 29 September 2026 most of its texts have no Slovak translation.

Below you will find what 11.1 changes, how the new form works, where it falls short of Slovak law and how to update without downtime. We cover the legal obligation itself in detail in our article on the withdrawal button for online stores. If you are still choosing a platform, read our comparison of WooCommerce vs Shoptet. For the stores we build, we handle these changes as part of our e-shops and e-commerce service.

WooCommerce 11.1 new features at a glance: what changes and what you must do

Some changes switch on by themselves after the update, some you have to enable by hand, and order withdrawal also needs extra work from you.

According to the official WooCommerce 11.1 release notes, these are the changes that matter to a store owner:

Feature	State after the update	What to do
Order withdrawal	Disabled	Enable, translate, link and test
Image galleries for product variations	Enabled for all stores, including those that had turned them off	Check the product page for products with variations
Faster REST and Store API requests	Enabled	Test extensions and integrations that output WooCommerce blocks through the API
Videos in the product gallery	Beta, disabled	For testing only for now, supports only videos uploaded directly to the site
Virtual orders without a shipping address in the order summary	Enabled	Nothing, the admin stops showing an address that meant nothing for a virtual product
Unified block editor scripts and styles	Experimental, disabled	Leave it off until a developer has tested it

Variation galleries used to require a separate extension, WooCommerce Additional Variation Images, which WooCommerce is retiring according to the release notes. If you have it installed, check after the update that products with variations show the right photos. Remove the extension only after that check.

Order withdrawal in WooCommerce 11.1: how the feature works

WooCommerce 11.1 adds a public form through which a customer, even without logging in, submits a withdrawal request and gets a confirmation email, while the merchant gets a notification.

1. Enabling: WooCommerce > Settings > Advanced > Features, the Order withdrawal option. The feature is not experimental, it is just disabled by default.
2. Form address: /my-account/withdraw-order. You can change the endpoint under WooCommerce > Settings > Advanced > Page setup, for example to a word in your store's language.
3. Filling in: the customer enters first name, last name, email (twice) and order number. They choose whether they are withdrawing from the whole order or only from selected items, which they describe in a note.
4. Review and confirmation: the form first shows a summary, and the request is sent only with the confirmation button.
5. Confirmation to the customer: an email with the submitted details and the date and time of submission.
6. Notification to the merchant: an email to the site's administration email address (in WordPress under Settings > General) and a notification on the WooCommerce home screen.

If the order number and email match an existing order, WooCommerce links the request to it and adds an order note. If they do not match, the request is still accepted, but the merchant only gets an email saying it needs to be matched by hand. According to the customer order withdrawal documentation, the request does not change the order status, cancel anything or issue a refund. Taking the goods back and refunding the payment stays with you.

The documentation also reveals three details that tend to surprise people in practice:

• One request per order: the form declines a second request for the same order, so the customer has to contact you directly to change anything.
• The emails cannot be edited in the usual settings: withdrawal emails are not listed under WooCommerce > Settings > Emails, so you cannot change their template or recipient there.
• The window is counted from the order: for an order older than 14 days, WooCommerce only shows a warning and does not decline the request.

Does WooCommerce 11.1 meet Slovak § 20a? A point-by-point comparison

The technical basis is there, but without Slovak texts, a visible link and your own handling process, you will not meet the obligation under Slovak law.

The current version of the Slovak consumer protection act No. 108/2024 sets out in § 20a exactly what a withdrawal function must do. WooCommerce itself states in its documentation that the feature may help a store meet these requirements but does not guarantee compliance. The comparison looks like this:

Legal requirement	WooCommerce 11.1	What to add
A function labelled "odstúpiť od zmluvy tu" (withdraw from the contract here) or equally unambiguous wording, clearly displayed and continuously available	The form exists but is not linked anywhere	A link with Slovak wording in the footer, confirmation emails and customer account
Name, contract identification, email	First and last name, email and order number	Check the field translations
Submission via a separate button labelled "potvrdiť odstúpenie od zmluvy" (confirm withdrawal from the contract) or similar	A review step and a Confirm withdrawal button	Translate the button into unambiguous Slovak
Prompt confirmation on a durable medium with the content of the notice and the date and time of submission	An email with the submitted details and the date and time of submission	Check that the email is actually sent and does not land in spam
Easy access, even when the customer checked out as a guest	The form works without logging in	Nothing
For goods, the 14-day period runs from receipt (§ 20(1))	Counts from the order date and only warns	Assess by the date of receipt, not by the warning
Withdrawal from some products only (§ 20(10))	A choice of selected items with a description	Match the description to the order items when handling the request

The biggest gap: the Slovak translation

According to the status of the Slovak WooCommerce translation on translate.wordpress.org, as of 29 September 2026 most texts of the new feature, including the Confirm withdrawal button, have no Slovak translation. A Slovak store would therefore show customers an English form, which hardly meets the requirement for an easily legible and unambiguous label. A Czech translation exists, but the Confirm withdrawal button reads "Potvrdit výběr" in it, which a customer may not connect with withdrawing from a contract. If you also sell to Czechia, check the texts there too.

You can translate the texts with your own language file, a translation plugin or a change in the theme. If you edit the form template directly, expect to check it again with every WooCommerce update.

Variation galleries and a faster API: what you will notice in your store

Customers see dedicated photos for each variation and connected systems get faster responses, but custom themes and extensions need testing.

From version 11.1, image galleries for variations are enabled for all stores. A database update enables them even where the owner had turned them off. For a range with colours or sizes this is useful: the customer sees photos of exactly the variation they are choosing. Still, the 11.1.2 dot release already had to fix a bug in which rendering variation galleries fell into infinite recursion when a theme called the get_available_variations function directly in a template file. Stores with a custom theme should therefore check product pages with variations on a test copy.

WooCommerce 11.1 also stopped registering blocks on requests that do not render them. According to WooCommerce's measurements, this makes Store API and REST API requests 30 to 42% faster. That affects block-based cart and checkout, which use the Store API, as well as integrations with stock, accounting or ERP systems that talk to the store through the API. An extension that outputs WooCommerce blocks through the API must opt back in with the new woocommerce_should_register_blocks filter, otherwise it returns raw block markup instead of content.

One more small point for custom themes: according to the developer changelog, the quantity buttons have a new order in the markup so that it matches what the customer sees and the site better meets accessibility rules. A theme whose CSS relied on the old order may break.

How to update to WooCommerce 11.1.2 without downtime

Update straight to 11.1.2, on a test copy first, and after going live run through a full purchase and the withdrawal form.

After 11.1 came two dot releases, both with security fixes. Version 11.1.1 from 18 September 2026 tightened API permissions, authentication checks and session handling. Version 11.1.2 from 22 September 2026 tightened validation of email product reviews and fixed the variation gallery bug mentioned above. The dot releases need no database update; version 11.1.0 does.

1. Backup: back up the store's database and files.
2. Test copy: run the update on staging first. The process is in our article on WordPress updates with staging and rollback.
3. Database update: when moving to 11.1, run it right after updating the plugin.
4. Purchase test: a product with variations, the cart, payment and the confirmation email.
5. Withdrawal test: if you enable the feature, send a test request as a guest and check both the customer's and the merchant's email.
6. Integrations: check that stock, invoicing and carriers receive orders as before.
7. Go live and check: only then update the live store. If something breaks, see our guide on what to do when a site stops working after a WordPress update.

Keep an eye on your PHP version too. According to WordPress.org, WooCommerce currently requires PHP 7.4 or newer, but the WooCommerce team proposes raising the minimum to PHP 8.1 from version 11.5, which it targets for January 2027. For now this is a proposal, not a confirmed decision. A store on PHP 7.4 or 8.0 would then not receive newer WooCommerce versions until PHP on the hosting is upgraded.

In practice: what we deal with in WooCommerce stores

Most of the work is not in enabling the feature but in what happens after a request is sent.

In WooCommerce stores we see in practice that the form itself tends to be the easy part. The harder part is agreeing who handles the request, how it is matched with the returned goods and the refund, and when the customer hears from you next. Because WooCommerce does not change the order status, a request can easily get lost without an agreed process. On top of that, the notification goes to the site's administration email address, which in smaller companies is not infrequently read by someone other than the person handling orders.

This is where a simple automation pays off. An incoming request can create a task, post a message to a team channel or log a return record. You will find examples of similar scenarios in our article on automations for small businesses with n8n and Make.

How we handle it at Denva: before launching a store, we go through the whole purchase as a real customer, from adding to the cart through payment to the confirmation email. After launch we do not leave you on your own, and if you want, we keep looking after updates and monitoring.

When you can do it yourself and when to bring us in

You can handle it yourself if:

• the store runs on a standard theme without modified WooCommerce templates,
• you can prepare a backup and a test copy,
• you can translate the form texts and add the withdrawal link to the footer and emails yourself.

It is worth bringing us in if:

• the store has a custom theme or modified product page and account templates,
• it is connected through the API to stock, accounting or a carrier,
• you want withdrawal requests handled automatically, not by hand from an inbox.

Conclusion: roll out WooCommerce 11.1 new features, but not blindly

WooCommerce 11.1 gives Slovak stores a useful basis for the mandatory withdrawal function, variation galleries without an extra extension and a faster API. Update straight to 11.1.2, and on a test copy first. Treat the withdrawal form as a starting point: until it has Slovak texts, a visible link and a tested handling process, it will not meet the requirements of § 20a for you. If you are not sure how this looks on your store, a no-obligation consultation is a good first step.

FAQ

Frequently asked questions.

Do I have to enable order withdrawal in WooCommerce 11.1?

Yes, it does not switch on by itself; it is disabled by default. If you sell to consumers at a distance through a website, Slovak law has required a withdrawal function since 19 June 2026, so either enable and complete it, or use another solution that meets § 20a.

Does the native WooCommerce form comply with Slovak law?

Not fully on its own. It covers the required details, two-step submission and a confirmation email with date and time, but it lacks a visible link and, as of 29 September 2026, a Slovak translation of most texts. WooCommerce itself says it does not guarantee compliance.

Does WooCommerce cancel the order after a withdrawal request?

No. The request does not change the order status, cancel it or issue a refund. WooCommerce sends a notification and, when the order number matches the email, adds an order note. You handle the return and the refund.

Which WooCommerce version should I update to?

To 11.1.2, the current stable release as of 29 September 2026, which includes the security fixes from 11.1.1 and 11.1.2. Update on a test copy first, because moving to 11.1 runs a database update.

Do I still need an extension for variation galleries after the update?

No, image galleries for variations are part of WooCommerce core from 11.1 and are enabled for all stores. The WooCommerce Additional Variation Images extension is being retired; you can remove it after checking your products with variations.