The latest version of WooCommerce cuts the database queries to load one order management page in half. If you’ve watched that screen crawl on a server that should be fast, the query numbers explain why.

The query reduction gets the headline, but there’s more worth noting in 10.7: a fulfillment API that fills an obvious gap, a store API change that eliminates a common custom endpoint, and a handful of smaller fixes that will quietly save someone an afternoon.

Every page WordPress renders fires dozens of database queries. Each one is a round trip, and they add up fast. Stack enough of those, and even a fast server feels slow.

The order management page made 271, but now it’s 132. Checkout drops another 15%. You don’t configure anything. Update, and it’s done.

We’ll be watching how this holds up in stores with large order histories and heavy plugin/extension stacks — because “51% fewer queries” on a clean test install and “51% fewer queries” on your client’s store with 47 active extensions are different claims. If your numbers look different from these benchmarks, drop them in the comments.

If your client uses a carrier WooCommerce doesn’t know about — regional courier, third-party logistics (3PL), anything with its own tracking portal — you’ve been improvising. Order notes, custom fields, something homemade that now lives in a repo accruing maintenance debt.

10.7 adds custom shipping providers under Settings > Shipping > Shipping Providers. Give it a name and a tracking URL template, and you’re done. WooCommerce turns tracking numbers into clickable links in customer emails and order screens from that point on.

Developers who need more control can use typed PHP methods to get and set tracking numbers and providers. The data store hooks via woocommerce_data_stores, so custom implementations follow the same patterns as the rest of WooCommerce rather than sitting awkwardly beside them.

Still in beta. If you’re running an unusual carrier setup and hit something unexpected, leave it in the comments. The team is actively working through edge cases, and specific reports are more useful than general ones.

Building headless, or with a custom front-end, means you’ve probably written an endpoint you didn’t need to. Product pages need weight, dimensions, related products, upsells, and cross-sells. Before 10.7, there was no clean way to pull all of that in a single request.

Now there is. One request with ?_embed returns the full set: weight and dimensions formatted for display, related products, and upsells included in the same response.

Cached checkout pages now stay functional. Before this release, customers landing on heavily cached pages could silently encounter 403 errors when performing cart operations. This bug doesn’t show up in testing because it only surfaces under specific caching conditions in production. So after you make the update, verify on staging.

Payment gateway credentials containing special characters (like % in a password) could be silently corrupted on save, so the gateway breaks and the error doesn’t point you anywhere useful. Fixed in 10.7.

Shipping partner recommendations in the setup flow now reflect your store’s actual country.

Multicurrency analytics exports now include currency context when running in the background, so Revenue Stats, Taxes, and Variations reports match what you see on screen.

Download directly from WordPress.org. Test on staging first. The update guide includes a checklist if you want one. The full technical changelog is in the developer release notes.

If something looks different after updating — better or worse — let us know in the comments.

About

Brent MacKinnon

Brent MacKinnon is the director of product marketing and developer advocacy at WooCommerce, helping to make the platform better for developers and merchants alike. With over a decade of experience in product marketing and strategy, Brent is passionate about supporting the WooCommerce community and helping entrepreneurs of all kinds succeed with Woo.

The post WooCommerce 10.7: 51% fewer queries, a real fulfillment API, one important cache fix appeared first on MASSIVE News.

Jetpack Search 7.0 adds product-aware filters to WooCommerce stores. Traditional keyword searches match queries to text, potentially forcing high-intent customers to comb through a wall of results to find what they want. Product-aware search helps them find the right product faster by sorting by price range, stock status, color, size, and rating. You can set it up through the block editor, with no custom code required, and the filter blocks inherit your theme’s styling.

Filters that match how they shop

Jetpack Search adds product-specific filter blocks to your store automatically:

• Price range: Customers set a budget and results update instantly. A dismissable chip shows their active price filter, so adjusting it takes one click.
• Rating: Filter by star rating to surface your highest-reviewed products.
• Stock status: Hide out-of-stock products from results. No dead ends, no frustration.
• Product attributes: Size, color, material, whatever you’ve configured. Customers filter by the product details that drive their decision.
• Category, tag, and brand: Your existing product taxonomies, wired directly into search.

Instead of requiring separate plugins or code to bolt these onto a search tool, they’re built into the search experience.

Results that look like products

Search results display as product cards, showing images, prices, and other attributes without clicking into each result. Your search page looks like your store rather than a list of titles.

Sort by what drives purchases

Customers can re-sort results by price (low to high, high to low) and average rating. The default keyword-relevance sort is still there, but shoppers can prioritize the factors that influence buying decisions.

Every filter ships as a WordPress block. You add them the same way you add any block — through the editor, into your search page sidebar or widget area.

1. Make sure Jetpack is installed and enabled on your WooCommerce store. 
2. If it isn’t, you can install Jetpack from your admin and select a plan. (Note: Jetpack Search is free for sites with under 5,000 records or 500 search requests per month.) Once installed, navigate to Jetpack → Settings → Performance, scroll to the Search section and toggle on Enable Search. 
3. Open the block editor on your search results page.
4. The WooCommerce-specific blocks (Price Filter, Rating Filter, Stock Status, Product Attributes, Product Filters) appear in your inserter automatically.
5. Drop the filters you want into your sidebar.
6. Customers see them immediately.

No custom code or developer needed. The blocks inherit your theme’s styling, so they look right without CSS overrides.

Jetpack Search 7.0 with WooCommerce features are available now on all WordPress.com sites, and will also be included in the next Jetpack Search plugin release for self-hosted sites. To try it before then, enable it today with the Jetpack Beta Tester.

Get Jetpack Search

About

Brent MacKinnon

Brent MacKinnon is the director of product marketing and developer advocacy at WooCommerce, helping to make the platform better for developers and merchants alike. With over a decade of experience in product marketing and strategy, Brent is passionate about supporting the WooCommerce community and helping entrepreneurs of all kinds succeed with Woo.

The post Jetpack Search now understands your WooCommerce catalog appeared first on MASSIVE News.

This is part one of a three-part series on WooCommerce MCP. This post covers what MCP is, how it works, and how to get started with the built-in Abilities. Part two covers building your first Custom Abilities. Part three goes deeper with advanced demos and production considerations.

I’ve been deep diving into something really exciting in WooCommerce: the Model Context Protocol integration (MCP). MCP first shipped as a beta in 10.3 and has been maturing across releases. Now, with WooCommerce 10.7 and WordPress 6.9+, the stack is solid enough to build some seriously useful things on top of it. So, I went ahead and did exactly that.

Picture this: we’re chatting with an AI assistant, and we say something like “Show me my low-stock products” or “Create a product called Winter Hoodie for $39.99.” Our WooCommerce store responds, does the work, and gives back the results. No clicking through the WordPress Dashboard, no manual REST API calls. Just natural conversation turning into real store actions.

That’s what MCP enables. Throughout this post, I’ll be using Claude Code as the AI assistant, but MCP works with any compatible client: Cursor, VS Code, or anything else that speaks the MCP protocol. Use whatever works best for you.

Let’s explore it together!

Think of MCP as a universal translator between AI tools and our WooCommerce store. Normally, if we want AI to interact with our store, we’d need to:

• Build custom REST API integrations.
• Handle authentication ourselves.
• Write a bunch of code to parse responses.

MCP changes all that. It’s an open-source standard that lets AI assistants like Claude, Cursor, or VS Code talk directly to systems like WooCommerce using natural language.

With MCP:

• AI can discover what our store can do.
• AI can perform those actions safely.
• Everything works within our existing permissions.

So when we say, “List all products under $20 USD,” MCP translates that into something WooCommerce understands, runs it securely, and brings back the results.

Three pieces work together to make this happen, and they all build on existing WooCommerce security.

The building blocks

WordPress Abilities API

The WordPress Abilities API is a way for WordPress plugins to register “Abilities”, basically things they can do. Think of it like a menu: WooCommerce tells WordPress, “Here’s everything I can do”, and AI assistants can read that menu and pick what they need. Each ability has a name like:

• woocommerce/products-list: list all products
• woocommerce/orders-create: create a new order

The Abilities API shipped in WordPress 6.9 as a core feature. It provides a standardized registry that any plugin can hook into, so WooCommerce no longer needs to bundle it separately. For those building Custom Abilities, they’re registered on the wp_abilities_api_init hook (more on this in the part two of the series).

WordPress MCP Adapter

The MCP Adapter is the translator. It takes MCP messages from AI assistants and converts them into something WordPress understands. Think of it as the middleman that speaks both “AI protocol” and “WordPress.”

WooCommerce REST API

The current MCP Abilities bridge to existing REST API endpoints. This means the existing REST API permissions still control everything, and the security stays exactly the same.

In the future, Abilities might go beyond REST and do even more powerful things. But for now, this gives us a solid, secure foundation.

The flow of communication

When we type “list all products” in Claude Code, here’s what happens step by step:

AI Client (Claude, etc.)

    ↓ (MCP protocol over stdio/JSON-RPC)

Local MCP Proxy (mcp-wordpress-remote)

    ↓ (HTTP/HTTPS requests with authentication)

Remote WordPress MCP Server (mcp-adapter)

    ↓ (WordPress Abilities API)

WooCommerce Abilities

    ↓ (REST API calls or direct operations)

WooCommerce Core

In plain terms, Claude Code sends a message to a small proxy tool running on our machine. The proxy converts it to a secure web request and sends it to our WordPress site’s MCP endpoint. The MCP Adapter looks up which ability to run, the ability’s callback executes (querying orders, products, etc.), and the result flows back the same way.

The local proxy (@automattic/mcp-wordpress-remote) is a small Node.js tool we install once during setup and then forget about. Its job is to translate between the way AI clients communicate (stdio) and the way WordPress works (HTTP).

MCP landed as a beta in WooCommerce 10.3 with product and order Abilities. The update since then was the MCP Adapter v0.3.0 migration in 10.4, which updated the transport layer. Since then, the MCP surface has been stable through 10.5, 10.6, 10.6.1, and 10.7, which is what we’re building on.

MCP is still in developer preview, so the built-in Abilities are limited to product and order CRUD (create, read, update, delete). But the foundation is solid, and that’s where Custom Abilities come in.

Out of the box, WooCommerce ships with nine MCP Abilities:

Products:

• woocommerce/products-list
• products-get
• products-create
• products-update
• products-delete

Orders:

• woocommerce/orders-list
• orders-get
• orders-create
• orders-update

This is already powerful enough to build some really cool workflows. But where it gets really interesting is Custom Abilities, and that’s what we’ll dive into in part two of this series.

Prerequisites

• A staging site (WooCommerce MCP is in developer preview)
• WooCommerce 10.7 (or 10.3+)
• WordPress 6.9+ (for the core Abilities API)
• Node.js 22+ (required by the latest mcp-wordpress-remote)
• REST API key with read_write permissions
• An MCP client (I’ll use Claude Code). Note: Claude Code requires a Claude Pro or Max plan ($20/mo+) or Anthropic API credits. It’s not available on the free tier.

Enabling MCP

Option 1: Head over to WP Admin > WooCommerce > Settings > Advanced > Features and enable WooCommerce MCP.

Option 2: Enable via WP-CLI

wp option update woocommerce_feature_mcp_integration_enabled yes

Setting up the connection

Create an API key

• In your store’s WP Admin dashboard, go to WooCommerce > Settings > Advanced > REST API.
• Click Add Key.
• Set permissions to Read/Write.
• Save the consumer key and secret.

Configure Claude Code

Open the Terminal and run:

claude mcp add woocommerce_mcp 

  --env WP_API_URL=https://yourstore.com/wp-json/woocommerce/mcp 

  --env CUSTOM_HEADERS='{"X-MCP-API-Key": "YOUR_CONSUMER_KEY:YOUR_CONSUMER_SECRET"}' 

  -- npx -y @automattic/mcp-wordpress-remote@latest

Important:

• Replace yourstore.com with the actual staging site URL.
• Replace the YOUR_CONSUMER_KEY:YOUR_CONSUMER_SECRET part with the actual API credentials.
• Restart Claude Code to load the new configuration.

For local development with HTTP: For testing locally without HTTPS, add this filter:

add_filter( 'woocommerce_mcp_allow_insecure_transport', '__return_true' );

Let’s explore the default Abilities that come with WooCommerce. These work right away with zero custom code.

List all products

Ask AI client: “List all products in the store.”

What happens behind the scenes:

• MCP calls the ability: woocommerce/products-list
• Returns product data with names, prices, stock status, etc.

Create a product

Try this: “Create a product named ‘Demo Hoodie’ priced at $29.99.”

MCP calls:

• Ability: woocommerce/products-create
• Result: A new product appears in the store!

Update a product

Say: “Update the Demo Hoodie price to $39.99.”

MCP calls:

• Ability: woocommerce/products-update
• The price changes instantly!

Create an order

Try: “Create an order for product ID 56 with quantity 2.”

MCP calls:

• Ability: woocommerce/orders-create
• A new order is created!

Pretty amazing, right? These built-in Abilities make AI-assisted store management feel natural. And this is just the beginning!

In part two, we’ll go beyond the built-ins and build Custom Abilities from scratch — including a Today’s Sales Analytics dashboard, a Low Stock Alert, and a Customer Lookup tool. See you there!

About

Kamlesh Vidhani

Kamlesh is a Happiness Engineer at WooCommerce. He loves helping customers get the most out of WordPress and WooCommerce — the more he sees what’s possible for them, the more excited he gets. Outside of Woo, you’ll find him exploring new tech or a gadget, traveling with no fixed plans, or watching cricket with unreasonable intensity.

The post WooCommerce MCP: Talk to your store like it’s your AI assistant appeared first on MASSIVE News.