ConicPlex

Start Your Project

On this Page

WooCommerce 11.3 Removes a Deprecated MCP Endpoint and Adds REST API Refund Validation

WooCommerce 11.3.0 removes the deprecated MCP endpoint, validates refund line items before processing, and changes how on_sale filtering works with include/exclude on the REST API.

Aftab Memon

November 16, 2026

WooCommerce 11.3.0 shipped on November 11, 2026, and the release that matters most isn’t the new on-sale badge styling. It’s three changes to how the REST API behaves: a deprecated MCP endpoint was removed, refund requests now get validated before they’re processed, and the on_sale filter combined with include or exclude parameters returns different results than it used to. Any store running custom integrations or a third-party plugin that talks to the WooCommerce API should check all three before updating, according to the official release notes on developer.woocommerce.com.

What WooCommerce 11.3 Changes for Developers

The deprecated /wp-json/woocommerce/mcp endpoint and its REST API key connection path are gone in 11.3. The MCP Adapter and Abilities API packages are no longer bundled with WooCommerce core either. If a site still has something calling that old endpoint, per the developer pre-release notes, those requests need to move to the WordPress MCP Adapter plugin, authenticated with a WordPress application password instead of the old connection method.

The bigger change for anyone processing refunds programmatically is on POST /wp-json/wc/v3/orders/{order_id}/refunds. WooCommerce now validates line-item refund allocations before creating the refund: each line has to belong to the order being refunded, the line totals (tax included) can’t exceed what’s actually refundable on that line, and the sum of all lines can’t exceed the top-level refund amount. Send a request that breaks any of those rules and you get a 400 or 422 response with a woocommerce_rest_* error code instead of a refund that doesn’t match the numbers. That’s a good thing for data integrity, but it means any custom refund logic built against the old, unvalidated endpoint can start failing on requests that used to go through silently.

There’s also a quieter breaking change in how the products endpoint handles filtering. Combining on_sale=true with include or exclude on the v2/v3 products and variations endpoints, and on the Store API, now returns a different result set than before. Anyone with a storefront or app pulling sale products by ID should re-test that query against 11.3 rather than assume it still filters the way it did.

What’s new for store owners

On the merchant side, the On-Sale Badge block can now show the discount amount, the percentage off, or custom text, styled without extra code. Several catalog blocks, including Product, Featured Product, and Product Categories List, picked up color, spacing, and border controls. The Product Gallery block gets native scroll and scroll-snap on mobile, so swiping through product images tracks a shopper’s finger instead of jumping between slides. WooCommerce also added a dedicated Refund and Returns Policy page type, which it flags in the Pages list and links via structured data.

One notice worth flagging early: stores still running PHP 7.4 or 8.0 now get a dismissible warning in 11.3. PHP 8.1 becomes the hard minimum starting with WooCommerce 11.6, so this is advance notice, not an immediate cutoff, but it’s worth checking your hosting’s PHP version now rather than scrambling in a few releases.

This release comes a week after WooCommerce 11.2.2 hardened the Store API as part of Woo’s move to a faster patch cadence. Together they’re a reminder that WooCommerce’s API surface is changing release over release, not just its storefront features. Stores leaning on custom plugins or a marketplace or ERP integration built against the REST API should budget time to re-test after every update, not just the security-tagged ones. A WooCommerce development audit is a reasonable way to catch a refund flow or a product sync quietly breaking before a customer notices first.

Sources

Aftab Memon is a Senior WordPress Developer at ConicPlex, working across everything from plugin conflicts and theme customization to full site builds on Elementor and WooCommerce. He spends most of his time in the parts of WordPress that don’t show up in a features list: hosting quirks, hook priority, the difference between a plugin that works in isolation and one that survives a real production stack. He writes here about what actually holds up once a WordPress site is live and being run by a non-technical client, not just what works in a demo.

Leave a Reply

Your email address will not be published. Required fields are marked *

Keep reading

Guides

Flat illustration of a server block connected to a glowing circuit node representing an AI agent calling an API, with smaller connector shapes orbiting nearby

How to Design APIs That AI Agents Can Actually Use

Agent traffic already makes up a meaningful share of API calls at companies like Stripe. Here’s what actually needs to…

Sajil Memon

November 16, 2026

Plugins

Abstract illustration of three shipping zones each with a different order-minimum threshold gauge, with a package icon above

How to Set a Minimum Order Amount per Shipping Zone in WooCommerce (4 Plugins Compared)

WooCommerce only supports one store-wide minimum order amount. Here are 4 real plugins that let you set a different minimum…

Sajil Memon

November 16, 2026

Guides

Illustration of a key connecting a free plugin tier panel to a premium plugin tier panel, representing a WordPress plugin license and subscription system

How to Build a License and Subscription System for a WordPress Plugin

A practical walkthrough of building a WordPress plugin license and subscription system: activation records, a separate update server, and how…

Aftab Memon

November 15, 2026

WhatsApp
Husen Memon
Husen Memon
Typically replies instant