Got an email from a client last week. He forwarded me the official announcement about WooCommerce and Stripe exploring AI and asked, “Ahmad, what is this? Do we need to bolt some new AI thing onto the site? Are we going to lose sales if the store can’t talk to Siri?”
He was talking about the new push for WooCommerce Agentic Commerce, which is a fancy term for letting AI assistants search for products and even buy them for a customer, all without the customer ever visiting your site. Hands-off shopping.
My first instinct was to tell him it’s just noise. I’ve been doing this for 14+ years, and I’ve seen a dozen “future of commerce” trends come and go. Most of them are marketing fluff, so I told him to hold off, that it was probably another buzzword.
Then I actually dug into the developer docs. And man, I was wrong. This one’s different.
What is this “agentic commerce” thing, really?
The official post over at the WooCommerce Developer Blog gives a decent high-level view, but it’s a bit corporate. Here’s the plainer version. WooCommerce is building a new protocol, basically an API endpoint, called the MCP (Merchant Communication Protocol). It sits on top of a new Abilities API. Think of it as a standardized way for an external, approved application, like an AI assistant, to ask your store questions and tell it to do things.
Instead of a customer clicking “Add to Cart,” their AI assistant makes a secure API call to your store to do it for them. This isn’t some far-off idea; the first version is already rolling out. And here’s the useful part: it’s built to be extensible. That means we devs can, and should, teach it new tricks.
For example, you could register a custom “ability” for a client’s specific fulfillment plugin. The AI could then ask your plugin for an estimated delivery date directly. This doesn’t replace the website. It turns your store into a data source these new agents can work with. Here’s what a simple registration might look like:
<?php
add_action( 'init', function() {
if ( ! function_exists( 'register_ability' ) ) {
return;
}
register_ability(
'my_store:get_custom_stock_status',
[
'description' => 'Get a detailed stock status for a given SKU.',
'callback' => 'my_store_get_stock_status_callback',
'parameters' => [
'sku' => [
'type' => 'string',
'description' => 'The product SKU to check.',
'required' => true,
],
],
]
);
} );
function my_store_get_stock_status_callback( $params ) {
$product = wc_get_product( wc_get_product_id_by_sku( $params['sku'] ) );
if ( ! $product ) {
return new WP_Error( 'not_found', 'SKU not found.' );
}
// Custom logic to determine lead times, warehouse location, etc.
return [
'sku' => $product->get_sku(),
'in_stock' => $product->is_in_stock(),
'quantity' => $product->get_stock_quantity(),
'shipping_eta' => '2-3 business days',
];
}So, what’s the point?
You don’t need to panic and go hire an “AI developer,” at least not yet. But you can’t ignore it either. It comes back to the fundamentals you should have been focused on all along:
- Clean product data: If your product titles, descriptions, and attributes are a mess, an AI won’t make sense of them. Garbage in, garbage out.
- Structured metadata: Are you using proper schemas? Are your custom fields logical? An AI needs structured, predictable data to understand your catalog.
- A solid foundation: The whole system relies on WooCommerce being open and extensible. If your site is built on a rickety pile of poorly coded plugins, it’ll crumble under these new demands.
The AI is just a new customer that happens to be a robot. If your data isn’t clean and your APIs aren’t stable, it won’t be able to buy anything. And that’s it.
Look, this stuff gets complicated fast. If you’re tired of debugging someone else’s mess and just want your site ready for what’s next, drop my team a line. We’ve probably seen it before.
The takeaway is simple: focus on data quality, and the rest follows. It comes down to whether your store’s data is already clean and structured enough for these tools to work with.
