What is Claude Commerce Agents?

An open (Apache 2.0) blueprint Anthropic released on 2 Sep 2026 for two commerce AI agents: a shopping agent a merchant embeds in its own site/app for customers, and a merchant agent for the back office. It's not a finished product but code, prompts and guardrails — running on the store's own ANTHROPIC_API_KEY (Claude API/Bedrock/Vertex/Foundry).

Is there a Claude Commerce Agents implementation for WooCommerce? And WooCommerce's own native agentic commerce?

Anthropic's Claude Commerce Agents blueprint references are Shopify, Wix, Square, Klaviyo, Visa and Mastercard — not WooCommerce. WooCommerce does have its own native agentic commerce, though: a native MCP (developer preview 10.3→10.9, but it's merchant-side product/order management, not a customer-facing shopping agent), an agent checkout (10.7) and Stripe's Agentic Commerce Suite (a launch partner, but card-first and US-weighted — no EU local methods). We ran Anthropic's official shopping agent on Woo (implementing the StorefrontBackend interface) and wired the EU checkout to Finnish payment methods (SCA). Proof: storeoperators.com/en/claude-commerce-agents.

Does Claude Commerce Agents work in the EU (PSD2/SCA)?

The agent yes, but checkout takes work. The repo's checkout doesn't pay — it hands off to the host. In the EU an autonomous agent has no PSD2/SCA basis to pay itself, so we implemented the checkout_handoff hook to a real Finnish payment (Paytrail: bank/MobilePay/card) that a human approves with strong authentication. It's the only legally sound way.

What does the Claude Commerce Agents repo NOT include?

Two decisive things: (1) the data layer — the agent is only as good as the machine-readable, contextual product data it runs on; the repo requires it but doesn't supply it; (2) EU-correct checkout — checkout_handoff is an abstract hook the adopter implements against their payment provider. Those are exactly what we build.

How do I make my store ready for Claude Commerce Agents?

Three layers: (1) machine-readable, rich, contextual product data (schema.org, technical fields, use cases) so the agent recommends the right product rather than 'something similar'; (2) a StorefrontBackend over the store's catalog, cart and orders; (3) EU checkout handoff to the store's own payment provider with human SCA. We do this as one package on the store's own platform.

Why do I need a FI/EU implementation partner?

Because the blueprint is open and the agent is a commodity, but success is decided by data and EU integration — and the marquee implementations (Shopify/Square/Wix/Visa/Mastercard, US/enterprise) aren't built for a Finnish SMB store on its own platform and payment methods. We are that implementer, with a hands-on proof already run.

Claude Commerce Agents

We make your store ready for Claude Commerce Agents — in the EU.

Anthropic released the Claude Commerce Agents blueprint as open source. We took its official agent, ran it against a real WooCommerce store, and wired the EU checkout to a Finnish payment (Paytrail, human SCA). The repo ships the agent, prompts and guardrails — but not the data layer and not EU/PSD2/SCA checkout. That is exactly what we implement.

Anthropic's own open repo + our EU integration and data layer.

Route 01order SMOKE PASSED

Anthropic's official agent — on our store

We cloned Anthropic's open Claude Commerce Agents repo (anthropics/commerce-agents, Apache 2.0), ran the official shopping agent (smoke test passing) and pointed it at our live WooCommerce store by implementing the repo's StorefrontBackend interface. That same official agent searched the catalog for the right product, added it to the cart and called the checkout tool — entirely on Anthropic's code, on top of our data layer.

Anthropic's official shopping agent running against a live WooCommerce store and handing off to Paytrail — The official shopping agent runs on our WooCommerce and hands the payment off to Paytrail.

Route 02order EU / SCA

Checkout hands off to a Finnish payment

The repo's checkout does NOT pay — it hands off. We implemented its checkout_handoff 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 strong authentication (PSD2/SCA). The model never sees the URL — the repo attaches it to the card payload after the agent's call. The hosted page is verified live: OP, Nordea and MobilePay appear. This is exactly what the official repo does NOT ship — it is an abstract hook, and we implemented it EU-correct.

The Paytrail hosted payment page the checkout hands off to, EUR 27.00, awaiting human SCA — The Paytrail hosted payment page the checkout hands off to (€27.00, test environment) — the human approves with SCA.

next · 30 seconds

What does your store look like to AI?

A free audit. No signup, works on every platform.

Book a demo