16 min read
Editor’s note: The numbers in this piece come from Adobe Analytics, Checkout.com, Shopify, Salesforce, court filings, and public announcements. We’ve flagged vendor data throughout for transparency.
TL;DR Tap to expand the short version
- Merchants in the UK and US report that AI agents are involved in roughly 3% of transactions today, while 89% say they are actively preparing for agentic commerce.
- On the other side, nearly a quarter of consumers say they will never delegate a purchase to AI, and 27% trust no organisation to operate a shopping agent for them.
- OpenAI started moving Instant Checkout toward merchant apps in March 2026, about six months after launching it.
- Meanwhile on the referral side, Adobe recorded AI-referred retail visitors converting 54% better than non-AI traffic in May 2026, after converting at roughly half the rate a year earlier.
- Shopify reported AI referred orders growing close to 13x year-on-year in Q1 2026, with more than half of those sessions landing straight on a product page.
- For retailers, roughly a third of the content on an average retail product page is unreadable to models.
Table of Contents
How agentic checkout launched
In September 2025, OpenAI put a purchase flow inside a chat window. Instant Checkout launched with US Etsy sellers, and OpenAI named a million Shopify merchants including Glossier, SKIMS, Spanx and Vuori as next in line. The plumbing was the Agentic Commerce Protocol, an open standard co-developed with Stripe.
Perplexity followed in November, opening its PayPal powered checkout to free US users after a year of restricting it to Pro subscribers. Microsoft arrived at NRF in January with Copilot Checkout, auto enrolling Shopify merchants. Google announced the Universal Commerce Protocol the same week, co-developed with Shopify, bringing purchases into AI Mode and Gemini.
So, four surfaces with four payment stacks. An enormous amount of conference stage time and a great many slides with the word agentic on them.
Then somebody decided to do a study. Checkout.com commissioned Census wide to survey 12,005 consumers across the UK, US, Brazil, China, France and the UAE, along with 400 heads of payment at consumer facing merchants, with fieldwork in early March 2026.
Those merchants put AI agents at 3% of transactions. Eighty-nine per cent said they were preparing anyway. Hold those two numbers next to each other and you have the shape of the market as it currently stands: a super expensive readiness programme aimed at a sliver of volume.
The consumer hesitation is predictable. 24% of respondents said they will never delegate a purchase to AI. Another 27% said there is no organisation they would trust to run a shopping agent on their behalf. What’s interesting here is that people did not really refuse the assistant itself, just the idea of handing it the card.
OpenAI narrows the model
On 5 March 2026, Digital Commerce 360 reported that OpenAI was sidelining Instant Checkout in favour of purchases through retailer apps inside ChatGPT. Reporting on the shift put the number of live merchants at around a dozen, and narrowed the future scope to a small set of large integrated retailers such as Target, Instacart, Expedia and Booking.com.
Checkout.com, which sells into this category and has no obvious reason to talk it down, read the move as structural, not directional: AI handles discovery and intent, merchants keep control of checkout. This is exactly the opposite of the story most vendors told in late 2025.
Five days later, a federal judge added a second constraint. In Amazon’s suit against Perplexity, Judge Maxine Chesney preliminary injunction blocking the Comet browser agent from password protected areas of Amazon’s site. The contention was that Comet accessed accounts with the user’s permission, but without authorisation from Amazon.
A customer’s permission alone does not authorise an agent to operate on a merchant’s systems. Agent access is now something to be negotiated instead of taken for granted.
29 SEP 2025
OpenAI launches Instant Checkout with Etsy, on ACP with Stripe
19 NOV 2025
Perplexity opens PayPal checkout to free US users
JAN 2026
Copilot Checkout at NRF. Google and Shopify announce UCP the same week
5 MAR 2026 RETREAT
OpenAI moves Instant Checkout toward merchant apps. About a dozen merchants live
10 MAR 2026 CONSTRAINT
Amazon wins preliminary injunction against Perplexity’s Comet
16 APR 2026 GROWTH
Adobe: AI referred retail traffic up 393% year on year in Q1
20 MAY 2026 GROWTH
Google expands UCP and Universal Cart at Google Marketing Live
The checkout standards
This is why betting on a single checkout integration is a poor use of a quarter. There are at least four live standards, backed by companies that compete with each other, and none has won.
| Standard | Backed by | What it actually does |
|---|---|---|
| ACP | OpenAI and Stripe, adopted by Microsoft | Checkout session handoff. Merchant stays merchant of record and keeps their own PSP |
| UCP | Google and Shopify | Full commerce vocabulary: catalogue, cart, discount codes, loyalty, subscriptions, post purchase |
| AP2 | Google, with 60+ partners including Mastercard, PayPal, Amex, Adyen, Coinbase | Proves the user authorised the purchase, using signed mandates |
| Agent Pay and Trusted Agent Protocol | Mastercard and Visa | Card network level agent identity and tokenisation |
Mastercard’s position, stated in January 2026, is that it participates in all of them. That is the tell. When the networks refuse to pick, the merchants underneath them do not need to either. Every one of these standards, though, sits on top of the same requirement: a structured, accurate, machine readable product feed.
OpenAI’s own documentation says merchants must supply a regularly refreshed structured feed covering identifiers, descriptions, pricing, inventory, media and fulfilment before anything else works. Google is asking for the same thing through Merchant Center. Microsoft through Microsoft Merchant Center. So even though the checkout buttons differ, the shelf underneath is shared.
AI referrals convert
In March 2025, visitors arriving at US retail sites from AI assistants converted 38% worse than everyone else. By March 2026 they converted 42% better. By May 2026, per Adobe’s most recent read, 54% better, with 53% higher revenue per visit and 23% more pages viewed. Adobe bases this on trillion-plus visits to US retail sites.
AI referred visitors, US retail
Adobe Analytics, 2026. Over 1 trillion visits. Compared against all non AI traffic in aggregate.
A sign flip that complete, in twelve months, in a channel that large, does not happen often. Two buts before you quote this internally. Adobe sells an LLM Optimizer product, and this data was published alongside it. The comparison is against non-AI traffic in aggregate, which blends paid search, email, affiliate and organic, so it is not a clean head to head with Google.
Which is why the second dataset matters more than the first. Shopify Q1 data, gathered independently across a different merchant base, found AI referred shoppers converting close to 50% higher than organic search visitors with 14% higher average order values. Referral sessions from AI chatbots grew more than 8x year on year and, more importantly, orders from them grew nearly 13x.
The mechanism sits in one number from that same report: more than half of AI referred sessions start directly on a product detail page, against roughly 20% for organic search. The assistant already comparison shopping. The visitor lands pre-qualified, at the bottom of a funnel you did not have to build.
Sessions starting on a product page
Rather than a homepage or category page
Shopify commerce data, Q1 2026.
Salesforce, measuring a third population of 1.5 billion shoppers, put AI and agent influence at 20% of retail over holiday 2025, worth around $262 billion, and found retailers running their own shopper agents grew sales 59% faster than those that did not.
Three vendors, three methodologies, three commercial interests in the answer, and they agree on the same direction and magnitude.
Product pages remain hard to read
Adobe also ran its Content Visibility Checker across the US retail sector, scoring how much of a page an LLM can actually read. Homepages averaged 75%. Category pages, 74%. Individual product pages came in at 66%. So the page most likely to convert is the page least likely to be readable by the channel converting best.
Page content a model can read
US retail averages. Higher is better.
PRODUCT PAGES BY CATEGORY, MAY 2026
Adobe Content Visibility Checker, 2026. Best retailers 82.5% on homepages, worst 54.2%.
A decade of headless and composable frontend work produced sites where the base HTML is a shell and everything meaningful (reviews, specs, FAQs, social proof) hydrates afterwards through JavaScript. Human browsers wait for it and most generative engines take the base HTML and leave.
Five practical priorities
The work falls into five priorities. The first four improve visibility across every checkout rail; only the fifth depends on a specific integration.
01
Score
What a model can read on 20 product pages
RAIL AGNOSTIC02
Feed
Fix the catalogue before the frontend
RAIL AGNOSTIC03
Measure
Instrument the channel, state its limits
RAIL AGNOSTIC04
Publish
Write what gets cited, not what ranks
RAIL AGNOSTIC05
Connect
Cheapest checkout integration, no more
RAIL SPECIFIC1. Measure page readability
Take twenty product pages spanning your best and worst sellers. Fetch each with JavaScript disabled and read what comes back. Anything missing from that raw HTML (specs trapped in images, reviews loaded by a third party widget, sizing tables rendered client side) is missing from the assistant’s view of you. Record the baseline and give engineering a ranked list.
Below is what you should check on each page:
| Element | Common failure | What the assistant cannot then do |
|---|---|---|
| Price and availability | Injected by JavaScript after load | Include you in any query with a budget or an urgency |
| Specifications | Rendered inside an image or a PDF | Match you to a query with a constraint, which is most of them |
| Reviews and ratings | Third party widget in an iframe | Answer “is it any good” without leaving your page |
| Variants and sizing | Loaded on click | Confirm you have the size or colour asked for |
| Shipping and returns | Behind a modal or an accordion script | Compare you on the thing shoppers abandon over |
| Product schema | Missing, or generated flat by a plugin | Resolve what the page is about with any confidence |
2. Fix product feeds
Every standard on the table (ACP, UCP, Copilot) reads from a structured product feed. Get identifiers, pricing, live inventory, fulfilment options and media complete and refreshed daily. Then add the attributes assistants use to disqualify you: what the product is not for, compatible accessories, materials, care requirements, return window. Google has started accepting product Q&A attributes as feed attributes in Merchant Center.
Sequence it so the cheap work happens first:
| Tier | What it covers | Effort |
|---|---|---|
| Table stakes | GTIN or MPN, title, description, price, currency, availability, image, brand, condition | Usually already there. Audit for completeness, not existence |
| Disqualifiers | Materials, dimensions, compatibility, care, age suitability, what it is not for | Merchandising time. This is where most catalogues are thin |
| Commercial | Shipping cost and speed by region, return window, warranty, stock depth | Systems work, and the tier assistants use to break a tie |
| Freshness | Daily refresh minimum, real time for price and stock | Engineering. Wrong prices in a feed are worse than no feed |
3. Measure AI traffic
GA4 added a native AI Assistant channel on 13 May 2026, with no configuration required. It counts only from launch; Google’s AI clicks remain in Organic Search; and referrer-less sessions still fall into Direct. Keep a parallel custom channel group running, and treat every AI number as a floor.
| Limit | Effect on your reporting | Workaround |
|---|---|---|
| Counts forward from 13 May 2026 only | No year on year comparison, and no baseline before that date | Annotate the date in GA4 and keep any custom channel group you already had running in parallel |
| Google’s own AI surfaces are filed under Organic Search | AI Overviews and AI Mode clicks never appear in the AI Assistant channel | Treat the AI channel as non-Google AI only, and say so on the slide |
| Referrer-less sessions land in Direct | An unknown share of assistant traffic is invisible | Report every AI figure as a floor rather than a total |
Agent traffic distorts paid media reporting in much the same way, which we looked at separately in agent advertising.
4. Publish useful comparisons
Write the comparisons you have been avoiding, including the ones where a competitor wins on a specific dimension. Open each section with a declarative answer to the question in the heading rather than a wind up. Add the specificity that lets a model match you to a narrow query, price bands, use cases, who the product suits badly.
Four formats worth building first, in order of how often assistants reach for them:
- Head to head comparisons, including against competitors. The version where you lose on one dimension is the version that gets quoted, because it reads as evidence rather than marketing.
- Buying guides organised by constraint, not by product. Budget, room size, skin type, skill level, whatever your category’s real filter is.
- Compatibility and fit pages. Explicit lists of what works with what. These answer a query type nobody writes content for and everybody searches.
- Who this is wrong for. The single most citable paragraph you can write, and almost nobody publishes it.
5. Use low-cost integrations
At 3% of transactions, a bespoke integration cannot earn back a quarter of engineering time. If you are on Shopify, most of this is a toggle in Admin rather than a project. Microsoft auto-enrols merchants in Copilot Checkout with an opt out. If you are not on Shopify, route through PayPal or Stripe rather than building against a protocol directly. Check the economics before you switch anything on: trade press has put OpenAI’s merchant fee at reported 4% fee, on top of normal processing, though OpenAI itself has only ever described it publicly as a small fee. Perplexity’s merchant programme has run at zero commission.
Before switching anything on, get answers to these four. They decide whether the integration is worth having at all:
- Who is merchant of record? This determines who owns the customer data, who handles the refund, and whose name appears on the statement.
- What is the total take rate? Platform fee plus your normal processing. Compare it against your contribution margin per order, not against your revenue.
- What data comes back with the order? Email consent, marketing permission and returning customer identity are the three that determine whether this is a sale or a relationship.
- How do you turn it off? Auto enrolment is common. Know the exit before the entrance.
Signals to watch
Microsoft reported that shopping journeys involving Copilot are 33% shorter than traditional search paths, produce 53% more purchases within thirty minutes, and are 194% more likely to end in a purchase when intent is present. Copilot apps have more than 100 million monthly active users. If those figures hold across a wider merchant base, the 3% ceiling rises fast. That assumes the agent reports what happened; false order confirmations show otherwise. A Checkout.com survey found strong merchant expectations, though stated intent remains a weak predictor of behaviour.
Universal Cart is rolling out across Nike, Sephora, Target, Ulta, Walmart, Wayfair and Shopify merchants including Fenty and Steve Madden, announced at Google event. Google can absorb years of unprofitable agentic commerce in a way OpenAI cannot. If checkout inside AI Mode gets genuinely good, the distribution behind it is a different order of magnitude to anything discussed above. Every scenario still requires a model that can read your product page.
Your first 90 days
- Weeks 1 to 2. Run the readability score on twenty product pages. Confirm the GA4 AI Assistant channel is reporting and annotate the date. Establish your baseline before anyone changes anything.
- Weeks 3 to 6. Fix feed completeness first, server rendered product content second. Ship the two comparison pieces your category most obviously lacks.
- Weeks 7 to 12. Switch on whichever checkout integrations are a configuration change rather than a build. Tag those orders separately. Re-score the same twenty pages and report the delta, not the absolute.
The channel is moving too fast for a four week read to mean anything.
Related reading
- False order confirmations, on what happens when the assistant misstates your customer’s cart.
- Agent advertising, on what happens to paid media once bots account for the majority of web traffic.
- AI recommendation signals, on the reputation signals that decide whether an agent recommends you at all.
- Brand protection stack, on keeping listings accurate and defended once you sell in more than one place.
- Stopping copycat listings, the same problem without a legal budget.
FAQ
Agentic checkout is a process that allows shoppers to finalise purchases directly within an AI assistant without navigating to the merchant’s website. The assistant securely collects necessary buyer and payment information, passing it to the merchant to handle fulfilment and order processing.
While the merchant remains the merchant of record, you do lose the direct on-site session, which impacts your ability to perform email capture and post-purchase upsells. Because consent handling for off-site transactions is still evolving, it is recommended to consult with your legal team regarding marketing permissions.
No. These protocols operate at different layers and can work together. They operate at different layers of the transaction stack, with ACP and UCP managing the commerce handoff while others handle authorisation and agent identity.
ChatGPT has shifted toward a more focused approach, moving away from broad product listings in chats to apps built by individual retailers. The scope of the Agentic Commerce Protocol has narrowed to prioritise larger integrated retailers over the initial mass-merchant rollout.
Not settled, and the first ruling went against the agent. In March 2026 a federal judge granted Amazon a preliminary injunction against Perplexity’s Comet browser, finding that it accessed accounts with the user’s permission but without authorisation from Amazon, and that Amazon was likely to succeed on claims under the Computer Fraud and Abuse Act. Perplexity has appealed. For merchants, the practical read is that agent access is becoming something platforms grant rather than something agents take.
Spotted an error, have a correction, or want to pitch a story? Contact [email protected].
Spotted an error in this piece? We correct publicly, tell us via the contact page. Read our corrections policy.
