WooCommerce 11.3: What Store Teams Should Test Before the November Release

WooCommerce 11.3: what store teams should test before the November release, by WeVerve Systems

WooCommerce 11.3: What Store Teams Should Test Before the November Release

Black Friday is three weeks away, and WooCommerce has a major release in the middle of the runway. According to the official WooCommerce 11.3 pre-release post by Brian Coords (26 October 2026), version 11.3 is scheduled for the week of 9 November 2026, the first beta is ready for testing, and the release already counts about 1,310 commits from 117 contributors. The current stable line is 11.2.2 as of 4 November 2026.

That timing is awkward for retailers. You want the sale badge, gallery and Analytics improvements live for peak traffic, but you do not want a plugin conflict or a broken refund integration on 27 November. This guide focuses on what store teams should actually test before upgrading, which developer advisories can break integrations, and how to decide whether to ship 11.3 before your code freeze or wait until January.

Key takeaways

  • WooCommerce 11.3 is scheduled for the week of 9 November 2026. The beta is available now; stable WooCommerce remains 11.2.2 as of 4 November.
  • Merchant-facing wins include flexible On-Sale Badge content (text, amount or percentage), more block styling controls, smoother mobile Product Gallery gestures, a selectable refund and returns policy page, and payment method filters in Analytics Orders.
  • Integration risks include removal of the deprecated /wp-json/woocommerce/mcp endpoint, corrected Products API on_sale + include/exclude behaviour, stricter refund REST validation (HTTP 400/422), and ambiguous payment_method columns in custom Analytics SQL.
  • Large stores should plan a quiet window for the wc_order_stats index, which WooCommerce estimates at about 47 MB per 1 million orders.
  • If you cannot finish staging tests before your mid-November code freeze, stay on 11.2.2 through Black Friday and upgrade after the holidays.

What WooCommerce 11.3 is and when it lands

WooCommerce ships major versions on a roughly monthly cadence. 11.3 is the next one after the 11.2 line. The pre-release notes say the first beta is ready for testing, and GitHub has published 11.3.0-beta.2 (2 November 2026) while the stable channel still points at 11.2.2 (4 November). Release week is 9 November 2026, which leaves roughly two weeks before Black Friday on 27 November 2026.

For store owners that is a short window. Install WooCommerce Beta Tester 4.0.0 on a non-production site running WordPress 6.8 or newer, switch to the Beta channel, and run the checks in this article before anyone touches production.

Merchant-facing features worth knowing

Not every commit in a 1,310-commit release matters to a merchandising or operations team. These are the storefront and admin changes that usually show up in retailer testing.

On-Sale Badge: text, amount or percentage

The On-Sale Badge block can now show Text, Amount or Percentage under Badge content. For Amount and Percentage you can add a prefix and suffix, for example “Save ” and ” off” to display “Save 25% off”. The default remains “Sale”, so existing blocks do not need a change. For variable products the badge shows the maximum discount with “Up to”, and on single-product views with Add to Cart + Options it updates for the selected variation. If the selected variation is not on sale, the badge is hidden.

More styling controls and a smoother mobile gallery

Product, Featured Product, Featured Category and Product Categories List blocks gain more colours, spacing and borders. Featured Category can be used inside Terms Query, and Product Result Count and Catalog Sorting are more customizable. Mobile Product Gallery gestures are smoother thanks to native scrolling and scroll snap, so images follow the finger and respond to quick flicks with natural momentum.

Refund and returns policy page

Merchants can select a refund and returns policy page under Settings, Advanced, Page setup. The selected page is labeled in the Pages list, and WooCommerce adds structured data so search engines can find the policy without custom markup. Worth doing before peak season if your returns page is still only linked from the footer.

Purple theme and Analytics payment method filter

Purple, Woo’s official block theme, is now broadly available in the WordPress theme directory, the Woo marketplace and WordPress.com. Separately, Analytics Orders gains a payment method column, filter and CSV export. Under the hood, wc_order_stats gets a nullable payment_method column (gateway ID) and a new index; existing orders are backfilled in the background through Action Scheduler in batches of 500.

Checklist of WooCommerce 11.3 items for store teams covering sale badges, block styling, MCP migration, Products API on_sale, refund REST validation, Analytics payment method and large store index planning
The WooCommerce 11.3 items most likely to touch an online store, in one view.

Changes that can break integrations

These advisories from the pre-release post and the MCP migration guide are the ones most likely to surprise a retailer with custom plugins, ERP connectors or AI tooling.

MCP endpoint removal

WooCommerce 11.3 removes the deprecated /wp-json/woocommerce/mcp endpoint and its REST API key path, and stops bundling the MCP Adapter and Abilities API packages. Core product and order abilities are enabled by default. To keep MCP access, install the WordPress MCP Adapter plugin and authenticate with a WordPress application password. Requests to the old endpoint return HTTP 410. If any AI assistant or internal tool still points at the WooCommerce MCP URL, migrate it before you upgrade.

Products API: on_sale with include or exclude

Several product endpoints now treat on_sale combined with include or exclude the way developers expect. Using any of those parameters alone is unchanged. Combined, they now return the intersection (or exclusion) correctly. Example from WooCommerce: in a store with product 10 not on sale and products 13-18 on sale, on_sale=true&include=10,13 previously returned a wider set including product 10; in 11.3 it returns only 13. Re-test any catalogue sync, sale feed or merchandising tool that mixes those parameters.

Refund REST validation

POST /wp-json/wc/v3/orders/{order_id}/refunds now validates explicitly supplied line-item refund amounts. Invalid requests can return HTTP 400 or 422 with a woocommerce_rest_* error code instead of creating a refund that leaves Analytics inconsistent. Check returns tools and ERP connectors that push line-item refunds, and treat 400/422 as validation failures rather than retrying the same payload.

Analytics SQL and the shop template meta

  • Custom Analytics SQL that joins wc_orders and uses a bare payment_method column can fail with an ambiguous column error, because both wc_orders and wc_order_stats now have that column. Qualify the column with the table name or alias.
  • On large stores, plan a quiet time for the new index. WooCommerce estimates about 47 MB per 1 million orders.
  • On block themes, reading the Shop page _wp_page_template meta now returns archive-product even when a custom template is saved. Extensions that sync that field need a re-check.
  • VAT exemption (is_vat_exempt) and calculated_shipping now persist across customer account saves. Code that relied on a save to clear VAT exemption must clear the flag explicitly.
  • Legacy Reports menu is hidden only on stores first installed on 11.3 or later. Existing stores are unchanged.

What to test: a practical checklist

Use this table to assign owners and decide what must pass on staging before production.

AreaWho owns itWhat to verifyRisk if skipped
On-Sale Badge contentMerchandisingText / Amount / Percentage, prefix/suffix, variable “Up to” behaviourWrong or missing sale messaging on PDPs and catalogues
Block styling and galleryFront-end / themeColours, spacing, borders; mobile swipe on Product GalleryBroken layouts on Purple or custom block themes
Refund and returns pageOps / SEOPage selected under Settings, Advanced, Page setup; structured data presentPolicy not discoverable to search engines
MCP clientsEngineeringOld /wp-json/woocommerce/mcp retired; WordPress MCP Adapter + application passwordAI or internal tools return HTTP 410
Products API on_saleIntegrationsCombined on_sale + include/exclude matches expected SKUsSale feeds and sync jobs return wrong products
Refund REST APIIntegrations / returnsLine-item amounts within remaining refundable balance; handle 400/422Failed refunds or inconsistent Analytics
Analytics payment methodFinance / BIColumn, filter, CSV; custom SQL qualifies payment_methodEmpty Orders report or broken exports
Large-store DB updateOps / DBAQuiet window for wc_order_stats index (~47 MB per 1M orders)Slow admin or I/O spikes during peak
WooCommerce 11.3 upgrade checklist for eCommerce store teams: area, owner, verification and risk.
Diagram of a WooCommerce 11.3 upgrade test path: clone staging, install Beta Tester, run checkout and plugin tests, review advisories, then decide go live or wait until after Black Friday
A safe upgrade path: test on staging with the Beta Tester plugin, then decide before your code freeze.

How to test before you upgrade

Use staging and Beta Tester 4.0.0

Clone production to staging, keep payment gateways and shipping plugins in test mode, and install WooCommerce Beta Tester 4.0.0. The pre-release notes say to update that plugin before trying the 11.3 prerelease, and to use it only on a non-production site on WordPress 6.8 or newer. Switch to the Beta channel and update to the latest 11.3 beta.

Run the storefront and plugin matrix

  • Place test orders with card, wallet and any buy-now-pay-later methods you use in production.
  • Create a full refund and a partial line-item refund through the admin and through any returns plugin or ERP connector.
  • Walk the shop, category and product templates on mobile; confirm gallery swipe and sale badges on simple and variable products.
  • Open Analytics, Orders; confirm the payment method column and filter, and re-run any custom SQL that joins order stats.
  • If you use MCP, complete the migration to the WordPress MCP Adapter and confirm the client can list products and orders.

Quiet window for large catalogues

The Analytics backfill and the new wc_order_stats index are background work, but index builds still read the table. On a large store, schedule the production upgrade for a quiet overnight or early-morning window, watch Action Scheduler, and keep a rollback plan to 11.2.2.

Timeline versus Black Friday

Release week of 9 November sits about 18 days before Black Friday 2026 (27 November). Most retailers freeze code at least a week before peak. A practical plan:

  • Now through early November: stage 11.3 beta, run the checklist above, and file plugin issues with vendors.
  • Release week (from 9 November): if staging is clean and vendors have confirmed compatibility, upgrade production and monitor for 48 hours.
  • Mid November: code freeze. No further major WooCommerce, theme or payment-plugin upgrades.
  • 27 to 30 November: Black Friday through Cyber Monday. Monitor orders, refunds and Analytics only.

If staging still fails on a critical payment, shipping or ERP connector by your freeze date, stay on 11.2.2. WooCommerce will keep shipping patches on the stable line, and an untested major upgrade is a bigger peak-season risk than waiting until January.

Timeline from the WooCommerce 11.3 beta in late October through release week of 9 November 2026, a mid November code freeze and Black Friday on 27 November 2026
Where the 11.3 beta and release week sit against the peak season calendar.

How WeVerve helps

WeVerve Systems builds and supports WooCommerce and headless commerce stacks for eCommerce brands, including payment, shipping and ERP integrations. We can set up a staging copy of your store, install the 11.3 beta, run the checklist in this article, migrate MCP clients if needed, and help you choose a safe upgrade window around Black Friday. Our 24/7 support team can also watch checkout, refunds and order sync through peak season.

If you want a second pair of eyes on your WooCommerce upgrade before the holidays, talk to our team.

Sources

No Comments

Post A Comment