We ran Anthropic's Claude Commerce Agents on WooCommerce — and made it EU-ready

On 2 September 2026 Anthropic open-sourced the Claude Commerce Agents blueprint (Apache 2.0). It's two commerce AI agents — a shopping agent a merchant embeds in its own site for customers, and a merchant agent for the back office — with prompts, guardrails and tool contracts. The marquee reference implementations are Shopify, Square, Wix, Visa and Mastercard.

We didn't stop at reading the press release. We picked it up.

What we did

We cloned the official repo (anthropics/commerce-agents), ran its shopping agent — the smoke test passed — and then pointed it at our live WooCommerce store by implementing the repo's StorefrontBackend interface over the store's catalog, cart and orders.

The result: Anthropic's own official agent searched the store for the right product, added it to the cart and called the checkout tool. Not a mockup — the same code Anthropic shipped, running on top of our data layer.

Then came the part that decides everything in Europe.

The repo's checkout doesn't pay — it hands off

Claude Commerce Agents' checkout does not take a payment. It offers a checkout_handoff hook: an abstract point where the adopter attaches their own payment. The repo deliberately leaves it empty, because payment, authorization and compliance are always the deployment's responsibility.

That isn't a shortcoming — it's the EU's only legally sound model. Under PSD2/SCA an autonomous agent has no clear right to pay on its own. So the agent must not pay: it has to hand off to a human.

We implemented that hook to a real Finnish payment. The agent's checkout card carried a genuine Paytrail hosted payment URL (bank, MobilePay, card) that a human approves with their own strong authentication. The model never sees the URL — the repo attaches it to the card payload after the agent's call. We verified the hosted page is genuinely live: OP, Nordea and MobilePay appear, amount €27.00.

See the full proof — official agent + EU payment →

Everything ran in Paytrail's test environment, with a human approving every payment. We claim no live paying customers — the pilot is genuine, in a test environment, and just going to market.

But doesn't WooCommerce already have its own?

It does — and it's fair to be precise about it. WooCommerce shipped its own native agentic commerce: a native MCP server (developer preview, versions 10.3→10.9), an agent checkout (10.7) and it's a launch partner for Stripe's Agentic Commerce Suite. But two things set it apart from what we did. Woo's native MCP is a merchant-side tool — manage products and orders with your own AI — not a customer-facing shopping agent. And the Stripe agent checkout is card-first and US-weighted: it doesn't support EU local methods like bank e-payment or MobilePay. We brought a customer-buying Anthropic agent and an EU-correct payment to Woo — exactly what the native offering leaves open.

Why it matters — and what it says about the market

The release proves our thesis coldly: the agent is now a commodity. Anthropic gave the code away and the platforms wire it in. The competition isn't decided by the agent. It's decided by two things the repo does not ship:

1. The data layer. An agent is only as good as the machine-readable, contextual product data it runs on. On thin data the agent offers "something similar" instead of the right product — and can't buy it. The repo requires rich data but doesn't supply it.
2. EU-correct checkout. checkout_handoff is an empty hook. Someone has to wire it to the store's own payment provider with human SCA — in the EU that isn't optional.

The marquee implementations (Shopify, Square, Wix, Visa, Mastercard) are US/enterprise-weighted. A Finnish mid-size store, on its own platform and its own payment methods, needs an implementer. That's what we do — the data layer and the EU checkout on the store's own platform, on top of the official Anthropic agent.

Make your store Commerce-Agents-ready

Three layers, in the same order every time:

1. Data first. Machine-readable, rich, contextual product data (schema.org, technical fields, use cases, selection guidance) — so the agent recommends the right product.
2. StorefrontBackend. Wire the store's catalog, cart and orders into the repo's interface.
3. EU checkout. Hand payment off to the store's own provider (Paytrail, Klarna, Kustom, Stripe) with human SCA.

The agent goes on top once the data is in shape — not before. Bolting a chatbot onto thin data is exactly why Gartner predicts 40% of agentic commerce projects will be canceled by 2027.

Here's how we did it — proof on WooCommerce and Paytrail → or book a mapping and we'll show you what your store needs.

Related: agentic buying already works today inside the shopper's own AI and the Klarna integration.