WooCommerce 11.3 beta is available for testing ahead of the release week of November 9, 2026. The prerelease adds more styling options to product blocks, new sale-badge displays and payment-method filters in Analytics. For developers, the bigger work is checking integrations against changes to refund validation, product queries and the MCP connection path.
The WooCommerce 11.3 developer announcement, published October 26, says the release has 1,310 commits and 117 contributors so far. Those figures describe the beta at announcement time, not a final release. WooCommerce is asking developers to test it and send feedback before the planned release week.
What WooCommerce 11.3 beta changes for developers
The short version: test extensions that use product queries or REST refunds, and review custom Analytics queries that refer to payment methods. WooCommerce 11.3 also adds several editor and reporting features that store owners can see directly, but API behavior is where an update is most likely to expose assumptions in custom code.
The beta expands styling controls for Product, Featured Product, Featured Category and Product Categories List blocks. The new options include colors, spacing and borders. Featured Category can also appear inside a Terms Query block, and Product Result Count and Catalog Sorting receive more customization options.
Product Gallery gets updated mobile gesture support. The announcement describes images following a user’s finger and responding to quick flicks with native scrolling and scroll snap. That is a front-end change worth checking on mobile layouts that use the gallery, especially before updating a live store.
Sale badges can show the customer’s savings
The On-Sale Badge block gains options to display a discount amount or percentage, alongside the existing text option. Merchants can add a prefix or suffix, so a percentage could display as “Save 25% off.” Existing blocks keep the default “Sale” text unless someone changes the setting.
Variable products have a specific behavior: the badge shows the maximum discount with “Up to,” then reflects the selected variation’s discount on single-product views using Add to Cart + Options. If the selected variation is not on sale, the badge is hidden; clearing the selection restores the “Up to” display.
WooCommerce also adds a refund and returns policy page setting under Settings → Advanced → Page setup. The chosen page appears labeled in the Pages list, and WooCommerce adds structured data that links to it for search engines.
Review product queries and REST refunds
A developer advisory changes how product endpoints combine on_sale with include and exclude. Using any of these parameters alone is unchanged. The difference applies when they are combined: results now reflect both conditions rather than the earlier inconsistent behavior.
| Request | WooCommerce 11.3 behavior |
|---|---|
on_sale=true + include | Returns included products that are on sale. |
on_sale=false + include | Returns included products that are not on sale. |
on_sale=true + exclude | Returns on-sale products except those excluded. |
on_sale=false + exclude | Returns products that are not on sale, except those excluded. |
The change affects the Products REST API, Product Variations REST API and Products Store API. Developers whose requests combine these parameters should rerun tests and confirm that the returned products match the intended filters.
WooCommerce 11.3 also validates explicit line-item amounts sent to POST /wp-json/wc/v3/orders/{order_id}/refunds. Allocations must fit the refund’s total amount and the remaining refundable amount for each order line. Invalid requests can return HTTP 400 or 422 with a WooCommerce REST error rather than creating the refund.
That response change matters to payment and order integrations: a request that previously produced an inconsistent refund may now fail. Handle validation errors as failures, inspect the response before recording a refund as complete, and correct the submitted amounts instead of retrying the same payload.
Analytics adds payment-method reporting
The Analytics Orders report gains a payment-method column, CSV export field and advanced filter. The change adds a nullable payment_method column and an index to wc_order_stats; an Action Scheduler task backfills existing orders in batches of 500.
WooCommerce says that building the index still reads every row of the table and estimates about 47 MB of index space per million orders. On older database servers, adding the column can rebuild the table. Operators of large stores should account for the database work when planning the update.
There is also a query compatibility issue for extensions: custom Analytics SQL that joins wc_orders and uses an unqualified payment_method can fail because both tables now have that column. Qualify the column with its table or alias, and review whether the join is still needed.
FAQ about WooCommerce 11.3 beta
When is WooCommerce 11.3 scheduled to ship?
The announcement schedules the release for the week of November 9, 2026. That is a planned release week; the beta announcement does not give a specific final release day.
What should extension developers test first?
Start with product API requests that combine on_sale and include or exclude, and refund requests that provide explicit line-item amounts. Also check Analytics SQL for unqualified references to payment_method.
How can developers test the beta?
The announcement directs testers to use the WooCommerce Beta Tester plugin, switch to the Beta channel and update to 11.3.0-beta.1. It says to test on a non-production site running WordPress 6.8 or newer.
Next step: install the beta on a staging site and run the affected API, refund and Analytics tests before the planned November release week.