Pingverablog ← Blog
Home › Blog › WooCommerce 11.3 Before Black Friday: What Changed and What to Test

WooCommerce 11.3 Before Black Friday: What Changed and What to Test

November 13, 2026 · 11 min read

WooCommerce 11.3 Before Black Friday: What Changed and What to Test

WooCommerce 11.3.0 came out on 11 November 2026, sixteen days before Black Friday. It is listed as backwards compatible, but it runs a database update, and it changes how a few REST API endpoints behave. If your store connects to an ERP, a returns app, a help desk, a feed tool or an AI assistant, test those connections on staging before you install 11.3 on the live store. A store with no integrations has less exposure, but it still needs the usual checkout test and a check that the Analytics backfill has finished.

If you cannot test properly before your code freeze, staying on 11.2.2 (released 4 November 2026) through the peak weekend is a defensible choice. Install 11.3 on a staging copy now, so you know what changes when you do update in December.

At a glance

  • WooCommerce 11.3.0 was released on 11 November 2026. It requires WordPress 7.0 and PHP 7.4 or newer, and it includes a database update.
  • The refunds endpoint now rejects line-item amounts that exceed the refund total or a line's refundable balance, returning HTTP 400 or 422 instead of creating the refund.
  • Product API queries that combine on_sale with include or exclude now return fewer products, which can change sale feeds and custom "deals" pages.
  • The old /wp-json/woocommerce/mcp endpoint is gone and now answers with HTTP 410. Assistants connected through it need the WordPress MCP Adapter plugin.
  • A background job fills a new payment_method column in Analytics through Action Scheduler, 500 orders per batch. Large stores on MySQL 5.7 face a full table rebuild.

Why WooCommerce 11.3 matters this month

As of 13 November 2026, the WooCommerce releases page lists 11.3.0 as the current stable version, with no 11.3.1 yet. The release notes headline storefront work: a wider On-Sale Badge block, more styling controls for product blocks and smoother product gallery swipes on mobile. Those are low-risk for most stores. The risk sits in the developer advisories published in the pre-release post on 26 October 2026, which the release notes point back to.

Four of them affect refunds, feeds, integrations and reporting during peak:

  1. Refund validation: starting with 11.3, POST /wp-json/wc/v3/orders/{order_id}/refunds checks explicitly supplied line-item amounts before it creates a refund. WooCommerce says the old behaviour could leave order records and Analytics inconsistent. An integration that sends line_items adding up to more than the refund amount, or more than a line has left to refund, now gets HTTP 400 or 422 with a woocommerce_rest_* error code. The advisory tells developers to "don't assume a refund was created" when they see those codes.
  2. Sale filters: the products endpoints in v2 and v3, the variations endpoints and the Store API products endpoint now apply include and exclude together with on_sale. The advisory's example: with product 10 not on sale and products 13 to 18 on sale, on_sale=true&include=10,13 used to return 10, 13, 15, 16, 17 and 18. In 11.3 it returns only 13.
  3. MCP endpoint removal: WooCommerce 11.3 removes the deprecated /wp-json/woocommerce/mcp endpoint and the REST API key login that went with it. Requests now return HTTP 410. The replacement is the WordPress MCP Adapter plugin with a WordPress application password, and WooCommerce asked users to migrate before upgrading.
  4. Analytics database change: a new nullable payment_method column and index go into the wc_order_stats table. WooCommerce says adding the column is instant on MySQL 8.0 and later with InnoDB, while older servers such as MySQL 5.7 rebuild the whole table. The index needs about 47 MB per million orders.

The 11.3.0 changelog also adds a tool under Status > Tools that finds and re-imports orders whose partial-then-full refunds were counted twice in the Revenue report's returns. If your returns figures looked too high in earlier months, that tool is relevant before you compare this year's peak with last year's.

One more change is cosmetic but generates support tickets. Stores first installed on 11.3.0 or later no longer show the legacy WooCommerce > Reports menu. Existing stores see no change. A plugin can force it back with the woocommerce_show_legacy_reports_menu filter.

Step by step: decide and test this week

  1. Write down what talks to the store. List every system that calls the WooCommerce REST API or Store API: ERP, accounting, returns portal, help desk, marketplace connector, feed generator, headless front end, AI assistant. For each, note whether it creates refunds or queries products with on_sale.
  2. Ask each vendor two questions. Does your integration send line_items with refund requests, and does it handle HTTP 400 and 422 responses from the refunds endpoint? Does it combine on_sale with include or exclude? A "yes" to either means you test it before going live.
  3. Check the server. Confirm WordPress 7.0 or later and PHP 7.4 or later. Ask your host which MySQL or MariaDB version runs the database. On MySQL 5.7 with a large order history, plan the update outside trading hours because of the table rebuild.
  4. Clone the store to staging. WooCommerce's update guide says to update WooCommerce, extensions, payment gateways and the theme together on staging, and to keep a backup ready before you click Update WooCommerce Database.
  5. Test refunds. On staging, create an order, then issue a partial refund from the admin and another through each integration that refunds. Confirm each refund appears on the order, in the gateway dashboard where applicable, and in Analytics.
  6. Test sale listings. Load your sale category, your "deals" page and any feed that filters by sale status. Count the products and compare with production.
  7. Reconnect any AI assistant. If anyone on the team uses an AI assistant against the store, move it to the MCP Adapter endpoint /wp-json/mcp/mcp-adapter-default-server with an application password for a user who has only the capabilities it needs. Then revoke the old REST API key.
  8. Update production in a quiet window. Use Coming soon mode as the update guide suggests, run the database update, then place a real order through the live checkout.
  9. Watch the backfill. Under Tools > Scheduled Actions, filter for pending actions and confirm the payment-method backfill drains. If the pending count keeps growing, Action Scheduler is not running, and other scheduled store tasks are waiting in the same queue.

Risk table

Risk Owner Check Frequency
Integration refund rejected with 400 or 422, customer not refunded Developer or integration vendor Refund through each integration on staging; search integration logs for woocommerce_rest_ Once before update, then daily through January returns
Sale feed or deals page shows fewer products Marketing or feed owner Compare product counts on staging and production Before update and after each sale launch
AI assistant loses store access Store owner or agency Reconnect via MCP Adapter and run one read query Once
Slow database update on MySQL 5.7 Host or developer Confirm database version; schedule off-peak Once
Analytics incomplete while backfill runs Store owner Pending actions in Scheduled Actions trend to zero Daily until complete
Checkout regression from the update Developer Real order on live checkout with payment, tax and email checked Right after update

Copyable artefact: WooCommerce 11.3 pre-update test plan

WooCommerce 11.3 test plan
Store: ____________   Staging URL: ____________   Tester: ____________
Current version: ______   Target: 11.3.0   Date: ____________

Environment
[ ] WordPress >= 7.0          [ ] PHP >= 7.4
[ ] Database: MySQL/MariaDB version ______  (5.7 => schedule off-peak)
[ ] Fresh backup of database and wp-content, restore tested

Refunds
[ ] Admin partial refund on a test order: amount, order note, gateway
[ ] Refund via integration 1 (______): created / 400 / 422  code: ______
[ ] Refund via integration 2 (______): created / 400 / 422  code: ______
[ ] Integration shows the error to staff instead of failing silently
[ ] Refund visible in Analytics > Orders

Products and sales
[ ] Sale category count: production ___ / staging ___
[ ] Deals page count:    production ___ / staging ___
[ ] Feed items flagged on sale: production ___ / staging ___

Integrations
[ ] AI assistant reconnected via /wp-json/mcp/mcp-adapter-default-server
[ ] Old WooCommerce REST API key for MCP revoked
[ ] ERP / accounting order sync: test order arrives

Go-live
[ ] Coming soon mode on during update
[ ] Database update completed
[ ] Live order: payment captured, tax correct, customer and admin emails received
[ ] Scheduled Actions: pending count falling over the next hours
Decision: update now / defer until ______   Signed: ______

Worked scenario (illustrative)

An agency maintains a WooCommerce store that sells kitchenware. A returns portal issues refunds through the REST API and sends line_items with every request. The portal also adds a fixed restocking amount on the order level, so for some returns the line allocations add up to more than the final refund amount.

On staging with 11.3, the agency runs ten test returns. Seven succeed. Three come back with HTTP 400 and woocommerce_rest_invalid_refund_amount, and the portal marks them as "processing" with no error shown to staff. On the live store, those three customers would have waited for money that was never sent, and the team would have learned about it from support emails in December.

The agency sends the failing payloads to the portal vendor, keeps production on 11.2.2 through Cyber Monday on 30 November, and schedules the 11.3 update for the first week of December once the vendor ships a fix. The numbers here are invented for illustration.

Common mistakes

  • Reading "backwards compatible: yes" as "nothing to test". The advisories list changes in API behaviour that integrations will notice.
  • Retrying a rejected refund with the same payload. WooCommerce's guidance is to correct the allocation rather than resend it.
  • Assuming the Analytics numbers are final right after the update while the backfill is still running in Action Scheduler.
  • Testing only the storefront homepage. None of the risks above would make the homepage fail, and an uptime check stays green through all of them.
  • Updating on the Thursday before Black Friday because the dashboard shows an update badge.

Limitations of this guide: it covers the advisories WooCommerce published for 11.3.0 as of 13 November 2026. Extensions and payment gateways ship their own changes, and a dot release such as 11.3.1 may change the picture. Check the releases page before you update.

FAQ

Should I install WooCommerce 11.3 before Black Friday?

Install it on staging now. Update production only if your integrations pass the refund and sale tests and you have time to watch the store for a few days before 27 November 2026. Otherwise stay on 11.2.2 and update in December.

My refund integration returns error 422 after the update. Was the refund made?

No. WooCommerce's advisory says invalid requests now return HTTP 400 or 422 "rather than creating a refund". Check the order notes and the payment gateway, fix the line-item amounts, and send a corrected request.

Where did WooCommerce > Reports go?

Stores first installed on 11.3.0 or later no longer show the legacy Reports menu; existing stores keep it. The page still loads at admin.php?page=wc-reports, and a plugin can restore the menu with the woocommerce_show_legacy_reports_menu filter.

Keep watching after the update

A refund integration that fails or a feed that shrinks can leave the site looking healthy while customers and revenue are affected. Pingvera's WordPress connector sends WooCommerce order events (order.created and order.failed) to a timeline that also shows deploys and incidents, and its anomaly detector alerts when orders fall below the hourly baseline while the site is still up. If you log the 11.3 update as a deploy, you can see order flow before and after it on one screen. For the wider update routine, see how to update WooCommerce safely, WooCommerce checkout monitoring and payment-to-order reconciliation. If an assistant connects to your stores, monitoring in your AI assistant covers the MCP side.

Sources

  • WooCommerce 11.3.0 release notes
  • WooCommerce 11.3: What's coming for developers (pre-release advisories)
  • WooCommerce 11.3 and MCP: migrating to the MCP Adapter
  • WooCommerce releases
  • WooCommerce 11.3 readme and changelog
  • How to update WooCommerce

Last reviewed: 13 November 2026

Know about problems before your customers do

Pingvera watches whether an online business actually works — uptime, checkout, orders, domain, SSL and server — and alerts you in Telegram, email or a webhook before a customer has to tell you.

Start free

Read next: How to Update WooCommerce Safely Before Black Friday: Test Update Roll Back · WooCommerce checkout monitoring: how to catch a dead checkout before the client calls.

Read next: How to Test a Website Backup Restore · Black Friday Code Freeze 2026: What to Lock and Still Patch · Black Friday Website Crash: A First-Hour Store Runbook · GA4 Purchase Event Not Firing: Pre-Black Friday Check · Run a free site check.

← All articles · Privacy policy · pingvera.com