WooCommerce 11.3.0 arrived on 11 November 2026, the release store owners should install before Black Friday on 27 November. The update adds a more flexible On-Sale Badge block, wider styling controls for product and catalogue blocks, smoother Product Gallery swipes on mobile, and a refund and returns policy page setting. It also removes the WooCommerce MCP endpoint, so any AI assistant connected through the old endpoint needs a new connection before you update. The release is backwards compatible and needs a database update, so back up first, test on staging, then update live.
Key takeaways
- WooCommerce 11.3.0 was released on 11 November 2026, is backwards compatible, and requires a database update.
- The On-Sale Badge block can now show the discount amount, percentage, or custom text.
- Product and catalogue blocks gain more colour, spacing and border controls, and the Product Gallery uses native scrolling on mobile.
- A new setting lets you set a refund and returns policy page, with structured data so search engines and agents can find it.
- The WooCommerce MCP endpoint is removed. Connections must move to the WordPress MCP Adapter plugin and a WordPress application password before you update.
- Install the 11.2.2 security release from 4 November first, then move to 11.3.0.
What is new in WooCommerce 11.3.0
WooCommerce 11.3.0 is a feature release built from 1,343 pull requests, according to the official release notes. The headline changes are about how products and promotions look to shoppers, plus one policy setting for search engines and AI agents. Under the surface are performance gains and security and bug fixes.
The On-Sale Badge block shows the saving, not just a label
The On-Sale Badge block can now display the discount amount or the discount percentage, or custom text of your choosing. Before this release, the badge was a fixed sale label. Now a shopper can see at a glance that a product is 20 percent off or 15 dollars off, which is a stronger reason to look closer. The block is used across product collections and galleries, and it now comes with full block styling controls, so you can match it to your store without code.
For Black Friday, this is the most useful change in the release: a clear saving on the product grid does more work than a generic sale badge, and you can set it up from the block editor in minutes.
More styling controls for product and catalogue blocks
WooCommerce 11.3.0 adds more styling controls across the Product, Featured Product, Featured Category, Product Categories List, and other catalogue blocks. The colour, spacing, and border controls are curated for each block and documented, so you can get a custom design without custom code. The Featured Category block can also be used inside a Terms Query to build a collection of product categories with a unified design.
Seasonal promotion pages and category landing pages are easier to build and keep consistent. The new controls are additive, but still check your main category pages visually after the update.
Product Gallery swipes feel natural on mobile
The Product Gallery block now uses native scrolling and scroll snap, so images follow a shopper’s finger and respond to quick flicks with natural momentum. It pairs with the recently added product variation image galleries, so shoppers can move through variation images the same way.
Most shoppers browse on a phone, and a stuttering gallery is a quiet reason to leave. After updating, open a product with several images on a real phone, swipe through the gallery, and switch between variations to confirm the images change as expected.
A dedicated refund and returns policy page
Merchants can now define their refund and returns policy page in WooCommerce. WooCommerce labels the selected page in the Pages list and adds structured data linking to it, so search engines and agents can find it.
This matters twice over. Shoppers deciding whether to buy from an unfamiliar store look for a clear returns policy, and a labelled, findable policy page builds trust at the point of decision. Search engines and AI shopping agents also surface policy information alongside products. If your policy currently lives in a generic page or a footer link, assign it through the new setting after the update.
The breaking change: the WooCommerce MCP endpoint is gone
The one change in WooCommerce 11.3.0 that can break a working setup is the removal of the WooCommerce MCP endpoint. MCP, the Model Context Protocol, is the open standard that lets AI assistants connect to tools and data. WooCommerce previously offered its own endpoint at /wp-json/woocommerce/mcp, authenticated with a WooCommerce REST API key. In 11.3.0 it is removed, and requests to it return HTTP 410, with a JSON-RPC error explaining how to connect through the MCP Adapter instead.
The removal also takes out the WooCommerce MCP feature under WooCommerce, Settings, Advanced, Features, the REST-derived abilities for products and orders, the filters that applied only to the old endpoint, and the bundled adapter packages. The Abilities API is part of WordPress core as of WordPress 7.0, which is WooCommerce’s minimum version.
| Before WooCommerce 11.3.0 | From WooCommerce 11.3.0 |
|---|---|
| MCP connection at /wp-json/woocommerce/mcp | Connection at /wp-json/mcp/mcp-adapter-default-server |
| Authentication with a WooCommerce REST API key and the X-MCP-API-Key header | Authentication with a WordPress application password |
| WooCommerce MCP feature toggle under Settings, Advanced, Features | Feature removed; core abilities enabled by default |
| REST-derived product and order abilities from WooCommerce | Purpose-built abilities exposed through the WordPress MCP Adapter |
| MCP Adapter bundled as a Composer library | MCP Adapter 0.7.0 as a WordPress.org plugin |
If an AI assistant connects to your store through the old endpoint, update that connection before you upgrade to 11.3.0. The migration is three steps. First, install and activate the MCP Adapter plugin from WordPress.org. Second, create a WordPress application password for a user with only the capabilities the client needs. Third, point your MCP client at /wp-json/mcp/mcp-adapter-default-server with that username and application password. Stores that had the WooCommerce MCP feature enabled will see an admin notice after updating. Once the new connection works, revoke the WooCommerce REST API keys you created for the old endpoint.
If no AI assistant connects to your store, this change does not affect you. If you do use AI tools with your store, our WooCommerce AI automation guide shows what an assistant can usefully do once it is connected. Extension developers should check the WooCommerce MCP migration guide, because custom abilities registered for the old endpoint do not carry over.
Install 11.2.2 first if you have not already
WooCommerce 11.2.2, released on 4 November 2026, is a security release to install before 11.3.0 if your store is still on an earlier version. It hardens the Store API and REST API, improves CSV data validation, makes admin endpoints more secure, and hardens Store API checkout so an order that cannot be saved does not go on to payment. It also includes a database update to clean up affected data. The release notes publish no CVE numbers for these fixes. Update to 11.2.2, run its database update, confirm the store works, then move to 11.3.0.
How to update to WooCommerce 11.3.0 safely
WooCommerce 11.3.0 is backwards compatible, but a database update and a removed endpoint mean this is not a release to install on a live store without preparation, especially two weeks before Black Friday.
- Back up your files and database. A full backup turns a bad update into a short delay. Follow our WordPress backup guide to back up files and database, store copies safely, and test a restore before you need one.
- Check your MCP connections. If an AI assistant connects to your store, migrate it to the WordPress MCP Adapter plugin and a WordPress application password first. Do not update while a client still points at the removed endpoint.
- Update on staging first. Copy the live store to staging, update WooCommerce there, run the database update, and click through the shop. WordPress 7.2 Release Candidate 1 is due on 17 November, so testing now also prepares you for the next WordPress release.
- Update extensions before WooCommerce. Bring payment gateways, shipping extensions, and WooCommerce add-ons up to date on staging first, so you test the combination your live store will run.
- Update WooCommerce and run the database update. On staging, then on live, update the plugin and run the database update when WooCommerce prompts you. Do not skip it: the store is not fully updated until it has run.
- Set the refund and returns policy page. Assign your existing policy page through the new setting and check that WooCommerce labels it in the Pages list.
- Confirm the store still sells. Place a test order, apply a coupon, check tax and shipping, and confirm order emails arrive. Only then consider the update finished.
What to test after the update
Run these checks on staging, then repeat the short version on live. Each one takes minutes and catches the problems that cost sales during Black Friday.
| Check | What good looks like |
|---|---|
| Product pages and galleries | Images swipe smoothly on mobile, variation images change correctly |
| On-Sale Badge blocks | Discount amount or percentage shows correctly on collections and galleries |
| Category and shop pages | Layouts and styling unchanged, no missing blocks |
| Checkout | Test order completes, tax and shipping correct, order email arrives |
| Refund and returns policy page | Page assigned and labelled in the Pages list |
| MCP connections | AI clients connect through the MCP Adapter, old REST API keys revoked |
Frequently asked questions
Is WooCommerce 11.3.0 safe to install before Black Friday?
Yes, with preparation. The release is backwards compatible, but it needs a database update and it removes the WooCommerce MCP endpoint. Back up, test on staging, migrate any MCP connection first, and update a few days before your Black Friday promotions start, not on the day itself.
Do I need to run the database update in WooCommerce 11.3.0?
Yes. The release notes confirm a database update is required. After updating the plugin, WooCommerce will prompt you to run it, on staging first and then on live.
What happens to my AI assistant connection after updating to WooCommerce 11.3.0?
It stops working if it still points at /wp-json/woocommerce/mcp, because that endpoint now returns HTTP 410. Install the WordPress MCP Adapter plugin, create a WordPress application password, and point the client at the new endpoint before you update.
What is new in WooCommerce 11.3.0 for shoppers?
Shoppers see sale badges showing the actual discount, smoother product image swipes on mobile, and a properly linked refund and returns policy page. Store owners get more styling control over product and catalogue blocks.
Should I update to WooCommerce 11.2.2 or go straight to 11.3.0?
If your store is on 11.2.1 or earlier, update to 11.2.2 first. It is a security release with a database update of its own. Confirm the store works, then update to 11.3.0.
Sources and Further Reading
- WooCommerce 11.3.0: Release notes, WooCommerce Developer Blog, 11 November 2026
- WooCommerce 11.3 MCP Adaptor updates, WooCommerce Developer Blog, 21 October 2026
- WooCommerce 11.2.2: Release notes, WooCommerce Developer Blog, 4 November 2026
- WordPress Backup Guide: Plugins, Host Backups and Restores, WebReOn, 15 November 2026
- WooCommerce AI Automation Workflows, WebReOn
- AI Chatbot for Shopify Setup Guide, WebReOn
- Core Web Vitals WordPress Fix Guide, WebReOn
