Run free scan
Menu
Playbook

Your WooCommerce catalogue and the new AI checkouts

An assistant can now show a product, take the card details and place the order without the shopper ever reaching your shop. Some companies call this assisted checkout. It uses published rules that let a shop share products and complete an order. Underneath it is an open set of rules that any shop is allowed to follow, and it asks a WooCommerce store for two quite different things. Here is what those are, what Shopify merchants get handed, and what is actually available to you today, on 25 August 2026.

Benjamin Ong 7 min read Developer needed (the checkout half; the feed half is not)
Three bands show the product list, the open channel, and the checkout route that stops before the end.

1. It is really three parts, and only one of them is easy

The rules are published openly by OpenAI and Stripe, and anyone may read them. They break into three pieces with plain names.

The product list. A file of everything you sell, with the price, the picture, the web address and whether it is in stock. This is the easy part.

The checkout. A set of web addresses on your own server that an assistant talks to in order to start a basket, change it, and finish the order. This is a developer job.

The payment handover. A way for the shopper's card details to reach you without the assistant ever holding them.

That last one carries the fact that surprises people most. You stay the seller. OpenAI states plainly that it is not the seller of record, and that merchants bring their own payment provider and handle the money exactly as they do for any other order. You remain the seller of record and continue to handle payment, fulfilment, refunds, and disputes.

2. The product list is the half worth doing

You can do this.

The file itself is ordinary. It is a spreadsheet-style list, and it wants the things you would expect: a code, a title, a description, a link, a picture, whether it is in stock, a price and a brand.

Here is the useful part. OpenAI says that if your list already uses a format compatible with Google's, it will read it in that format. So if you already send a product list to Google Shopping, you are most of the way there rather than starting again.

One honest catch. Sending the list is not self-serve. OpenAI's own page says taking on product lists is currently open to approved partners, with an application form. You can prepare the list today. You cannot switch it on yourself.

3. What a Shopify merchant gets handed

It is worth saying this plainly rather than pretending the gap is small.

Eligible Shopify products are shared with ChatGPT by default. For ChatGPT, the customer currently completes the purchase through the merchant's own checkout, opened inside the app or in another browser tab. Its own page says the feature is enabled automatically for eligible stores, and a later Shopify post says products become discoverable in ChatGPT by default, with no separate integrations and no apps.

A WooCommerce owner gets none of that automatically, because WooCommerce is software you run rather than a network you joined. That is the same trade you already made for control over everything else. It does not make WooCommerce the wrong choice. It does mean the work is yours.

4. Where WooCommerce actually stands

WooCommerce publishes its own page on this, and it is refreshingly clear about what has shipped and what has not.

Shipped: a way for AI assistants to talk to a store for management tasks, which arrived in WooCommerce 10.3. WooCommerce is direct that this helps assistants manage a store rather than check out shoppers, so it is not the thing this article is about.

WooCommerce's hub still labels ACP and UCP as coming soon. Its 1 August 2026 article says the Stripe route is rolling out to selected US businesses. Treat access as limited and confirm eligibility before describing it as available.

Meanwhile the official Stripe payment extension for WooCommerce has quietly begun carrying code for this, including a per-product setting to keep an item out of the assistant feed and an option to send the shopper back to your shop to pay instead. It sits in the release notes under upcoming work, and WooCommerce's user documentation does not describe it yet. Read that as arriving, not as ready.

WooCommerce's own advice in the meantime is the same advice we give: make your product data clean and complete, because that is what everything else is built on.

5. What the plugins do, and do not, cover

Developer needed to judge any of these properly.

Search the plugin directory and you will find a dozen offering this. Sorting them takes one question: does it publish a list, or does it run a checkout?

Most publish a list. That is genuinely useful and low risk.

A few claim to run the full checkout. Look at their numbers before you trust one with your orders. As of 25 August 2026 the most installed plugin claiming to handle the checkout had about twenty active installations and had not been updated since November 2025. That is not a criticism of the authors. It is the honest state of a category that is a few months old.

And there is a catch that no plugin can solve for you. Even a perfect checkout on your server does nothing until an assistant has approved you and is pointing at it. The approval is not something you can install.

6. Where this works, and where it does not

This is the section most articles skip, and for a shop in our part of the world it is the one that decides everything.

The payment handover is the binding limit, because without it nothing completes. Stripe documents the supported countries for it, and the list covers the United States, Canada and a long run of European countries. There is no country in Asia on it.

Google's competing standard is similarly bounded. Google documents its in-assistant checkout as applying to products eligible in the United States, Canada and Australia, and to selected merchants only.

WooCommerce's own wording for its Stripe route is that it is rolling out to businesses in the United States.

As of 25 August 2026, Stripe's published route does not include Singapore or Malaysia. That does not establish the availability of every other checkout route. That is a plain fact rather than a discouragement, and it has a useful consequence. It means the only part of this you can act on right now is the product list and the readability of your shop, which happens to be the part that keeps its value whatever happens to any of these standards.

7. What to actually do this month

Publish a clean product list. If you already send one to Google Shopping, check it is complete rather than building a second one.

Fix the product facts on your own pages, because every one of these routes reads them and because it is the only piece that is yours permanently.

Then wait, and recheck in a few months. This is a good thing to be second at.

What this does not do

None of this makes an assistant sell your products. It makes you eligible to be considered by the ones that offer it, in the countries where it runs.

The dates matter more than usual here. Everything above is what these companies published on 25 August 2026, on a subject that has changed several times in the past year. If a name, a country list or a status in this article does not match what you find, believe what you find.

And we do not do any of this for you. We measure whether your shop is readable, which is step one of every route above, and we say what to fix.

Show the technical detail (for your developer)

The Agentic Commerce Protocol is Apache-2.0, maintained by OpenAI and Stripe, and currently marked beta. Latest dated spec version is 2026-04-17. Repo: github.com/agentic-commerce-protocol/agentic-commerce-protocol.

The three component specs are the Product Feed Spec, the Agentic Checkout Spec and the Delegated Payment Spec.

Merchant-hosted checkout endpoints: POST /checkout_sessions, POST /checkout_sessions/{id}, GET /checkout_sessions/{id}, POST /checkout_sessions/{id}/complete, POST /checkout_sessions/{id}/cancel. All endpoints must use HTTPS and return JSON. Headers include Authorization, Idempotency-Key, Request-Id, Signature, Timestamp and API-Version.

POST /agentic_commerce/delegate_payment is called by the agent against the PSP, not against the merchant. Stripe's Shared Payment Token is the first compatible implementation.

On the standard Stripe Agentic Commerce Suite path you do not expose the checkout endpoints at all: Stripe hosts them and calls your side. You upload a CSV product catalogue and receive checkout.session.completed webhooks. Only the custom, off-Stripe path requires you to host the reverse API.

Feed formats: UTF-8 tab-delimited .txt/.tsv, .csv, and gzip variants. OpenAI documents two feed paths. Its native schema uses fields including item_id and eligibility flags. A confirmed Google-compatible feed instead uses fields including id, title, link, availability, and price; accepted products are search-enabled while checkout eligibility is controlled separately.