What AI Checkout Could Mean for Your Brand

When an AI assistant helps a customer buy, who takes the sale? What brand leaders need to know about AI checkout.

5 min read
What AI Checkout Could Mean for Your Brand

Most people who run an e-commerce brand have never had to think about a shopping assistant completing a purchase. A recommendation, yes. A shortlist in ChatGPT or Gemini, perhaps. The payment still happens on your site, in your checkout, on a card your processor charges.

For a UK brand, the useful question is which shopping services can send you an order, where they operate and who takes the sale. Support for a protocol and availability to a customer are separate questions.

The name for the shared language behind that question is Universal Commerce Protocol, or UCP.

Availability checked 30 October 2026. Google's guide describes approved checkout and cart integrations. Stripe's merchant suite lists Great Britain among its supported countries. These are different parts of the purchase journey; check the service, customer market and checkout path for your business.

Two early bets

In late 2025 these looked like two products competing for the same job.

OpenAI and Stripe built Instant Checkout. From 29 September 2025 a US shopper in ChatGPT could buy from Etsy, then from some Shopify merchants, without leaving the chat. ChatGPT took the order. Stripe sat underneath. It was a product: a Buy button inside a conversation.

Google took a different route. On 11 January 2026 it published UCP: an open specification, not a consumer Buy button. An assistant and a store exchange a short list of what each can do. If both sides support checkout, they can run a checkout. If both support a cart, they can share a cart. Nobody in the middle takes the sale. On the checkout specification the merchant stays merchant of record. A wallet tokenises the card. Your payment provider charges it.

They looked like they were competing. By spring they were not.

On 24 March 2026 OpenAI said Instant Checkout had not given merchants enough flexibility. ChatGPT would keep helping people find products. The purchase would finish on the merchant's own site. That is the direction described in its product discovery announcement.

A paper speech bubble with a hole cut in it, connected by an amber thread to a paper shopfront.
ChatGPT kept helping people find products. The purchase went back to the merchant's checkout.

Stripe did not pick a side. It joined the UCP Governing Council on 28 April 2026 and still processes cards on many of these orders. OpenAI and Stripe's older checkout protocol still has a public repository. Stripe's seller documentation now treats that protocol and UCP as alternative rails.

Instant Checkout as a product receded. UCP stayed.

What actually happens in a UCP purchase

A person asks an assistant for something they want to buy. The assistant finds a product. That still depends on your catalogue being true: price, stock and the live offer. That is the work in Feed Completeness. The assistant then asks your store, through UCP, whether it can start a checkout. A wallet tokenises the payment. A payment provider takes the charge. Your company stays merchant of record: returns, tax, chargebacks. That is true on the open specification and on Google's Buy path. Turning on Shopify Agentic Storefronts does not, by itself, move that job to Shopify.

Instant Checkout, 2025

  1. Shopper

    Asks in ChatGPT

  2. ChatGPT

    Finds the product and takes the order

  3. Stripe

    Charges the card

A UCP purchase

  1. Shopper

    Asks an assistant

  2. Assistant

    Finds a product

  3. Your store

    Agrees checkout

  4. Payments

    Takes the charge

Illustrative. Instant Checkout kept the buy inside the chat. A UCP purchase asks your store to run checkout, then a payment provider charges the card. Your company stays merchant of record unless you already use a reseller arrangement such as Managed Markets.

That diagram shows one possible purchase path. Which parts a customer can use depends on the shopping service, merchant and market.

Where it lives now

Three different things get called UCP. They are easy to collapse into one slide.

The specification is a document and a GitHub repository. Anyone can implement it. This article's August examples used v2026-08-25. Having the document does not put a Buy button in front of a customer.

For a hosted store, ask your commerce provider which agent-shopping integrations are available to your business and which markets they cover. Confirm who takes the order, handles payment and remains responsible for returns. A setting in your store does not establish availability across every shopping assistant.

Google's current Merchant Center guide, checked on 30 October 2026, describes checkout on Google's services and a cart handoff to a merchant's website. Approval is required, and feature support varies. Check the integration path and access available to your account.

Three parts to check

The rules

The specification

A shared language any assistant and any store can implement.

Your store

Your hosted store

Ask your provider which shopping integrations and markets your store supports.

Google access

Google shopping

Checkout or a cart handoff, subject to Google's approval and feature support.

What to confirm

Supported capabilities

What to confirm

Store and market access

What to confirm

Approval and available features

A supported protocol, a store connection and a customer checkout are separate. Confirm each with the provider you plan to use.

A UK store's ability to connect does not establish which checkout paths its customers can use. Ask about both merchant access and customer availability.

What this could mean

A shopping assistant may compare your product using information outside the page a customer sees. If the weekend sale is missing from those records, the comparison may use the wrong price. Keep the offer consistent across your website and shopping listings.

If you already sell through Managed Markets, you already know what it means when Global-e is merchant of record. Shop Pay never did that. Agentic Storefronts, on its own, does not either.

ChatGPT, for now, is a discovery referrer. Treat it that way until OpenAI's own page says otherwise.

You do not need a UCP programme. You do need one person who is watching. Someone who can answer, without a vendor on the call:

  • Have we opened Agentic Storefronts, and do we still take the sale on an ordinary order?
  • Is the Merchant Center record true this week?
  • If Google or OpenAI announce a UK surface, who reads that note the same day?

Salesforce Commerce and custom stacks are a later engineering decision. Salesforce's UCP guide, as of 28 August 2026, is written for Google and US English. That is not work to start so a board pack can say you have UCP.

Working groups for food and hotels have been seated. Their detailed schemas were still unpublished on 28 August 2026. Fashion and home brands do not need to build against them. They are a sign that the industry is writing one way for an assistant to talk to a shop, across more than clothing checkout.

What to do now

Start with what is available to your business and market. Assign someone to follow material changes and keep product information consistent across your website and shopping listings.

Ask your team which integrations are active, where customers can buy and who owns each order. Check the answer against current provider guidance before investing in new work.

Bring what you know. Explore what comes next.

Find your place among people building brands, strengthening customer relationships and trying new approaches.