Making a store ready for AI shopping agents comes down to four jobs: give agents clean product data, give them a checkout route, decide on purpose which bots may visit, and measure what they bring. None of it requires rebuilding your site. Most merchants can get there through their platform or payment provider, and in every documented setup you remain the merchant of record. This guide is based on vendor documentation as of November 2026; we have not run a live integration ourselves.
- Rise in AI traffic to US retail sites, holiday 2025 (Adobe)
- 693.4%
- Required fields in OpenAI's product feed
- 9
- AI channels in Shopify Agentic Storefronts
- 4
- Merchant of record under ACP, UCP and Shopify
- You
Why are AI agents a separate channel?
AI agents reach your store in three different ways, and each needs something different from you:
- Discovery. ChatGPT, Google AI Mode, Gemini and Copilot answer "find me a waterproof jacket under $150" by reading product data. If your catalog is missing or stale, you are not in the answer.
- Protocol checkout. The agent's platform calls your checkout through a standard such as OpenAI and Stripe's Agentic Commerce Protocol (ACP) or Google's Universal Commerce Protocol (UCP). The shopper approves inside the agent and you receive a normal order.
- Browser agents. Agents such as Claude Duet, Meta Muse and ChatGPT agent open your website and click through it like a person. Duet's browser sends a distinct User-Agent header and Anthropic publishes the IP addresses it browses from, according to Anthropic's Duet safety article.
The numbers are still small. Adobe's 2025 holiday report found AI traffic to US retail sites up 693.4% year on year while warning that "the base of users remains modest". That is a reason to prepare cheaply now rather than to rebuild your stack. For the shopper side of this, see which AI agents can buy things.
Step 1: Is your product data good enough for agents?
Agents reward structured, current data. Shopify's March 2026 announcement says AI surfaces "favor structured data, with clean attributes and real-time accuracy".
OpenAI's product feed spec requires nine fields on every row: item_id, title, description, url, brand, seller_name, image_url, availability and price. A missing or invalid availability value gets the row rejected. Google reads your existing Merchant Center feed, and only listings with the native_commerce attribute show a Buy button in AI Mode.
Practical fixes that help every agent at once:
- Use real GTINs and MPNs so agents can match your item to reviews and price comparisons.
- Put size, colour and material in attributes, not only in the title.
- State shipping costs and your return window as data. OpenAI's feed has optional
accepts_returns,return_deadline_in_daysandshippingfields. - Update availability and sale prices as they change. OpenAI's spec says date fields do not schedule changes for you.
The full field-by-field breakdown is in our guide to product feeds for AI agents.
Step 2: Which checkout route should you pick?
| Route | Who runs it | Where it sells (as of November 2026) | What you build |
|---|---|---|---|
| ACP | OpenAI and Stripe (open spec, beta) | ChatGPT merchant integrations such as Instacart, Target, DoorDash and Expedia | Agentic Checkout API plus a delegated-payment provider |
| UCP | Co-developed by Google, Shopify, Walmart, Target and others | Google AI Mode and Gemini, select merchants, US, Canada and Australia | Merchant Center feed, native_commerce attribute, Google Pay & Wallet Console |
| Shopify Agentic Storefronts | Shopify | ChatGPT, Copilot, AI Mode, Gemini | Toggle in Shopify Admin |
| PayPal ACP server | PayPal | ChatGPT | Connect your catalog through PayPal |
| Browser agents | The agent vendor | Your normal website | Nothing new, but checkout must work for a careful bot |
Two caveats matter. First, OpenAI scaled back in-chat Instant Checkout in March 2026 (reports give 4, 17 or 24 March) and pushed ChatGPT shopping towards discovery, but ACP itself continues. Second, Google says UCP checkout is limited to selected merchants and rolls out "in phases". Our ACP vs AP2 vs UCP comparison explains how the protocols relate.
If you are on Shopify, start with Shopify and agentic commerce. If you run a custom stack, read ACP for merchants and UCP and AP2 for merchants.
Make your normal checkout agent-friendly too
Browser agents use the checkout you already have. Google's November 2025 agentic checkout required merchants to support guest checkout and Google Pay, TechCrunch reported. Forced account creation, CAPTCHAs on every step and pop-ups that hide the pay button all cause agents to hand the task back to the shopper. Wallets help: Meta Muse and Claude Duet pay with single-use Link cards, and Duet also supports Shop Pay, so accepting Link and Shop Pay covers both. See Stripe Link for AI agents.
Step 3: Who should you let in?
- Agent request
- robots.txt (advisory)
- Bot management / signatures
- Your store
- Order
Your robots.txt decides which crawlers are asked to stay out. It is a request, not a lock. OpenAI's bot documentation separates GPTBot (training), OAI-SearchBot (search results) and ChatGPT-User (pages fetched when a user asks), and says robots.txt rules "may not apply" to ChatGPT-User because a person started the action. Blocking GPTBot does not remove you from ChatGPT shopping; blocking OAI-SearchBot can.
Amazon shows the opposite strategy. As of 10 November 2026, amazon.co.uk/robots.txt disallows 99 named AI crawlers and agents, including ChatGPT-User, Claude-User and GoogleAgent-Shopping, and Amazon blocked Meta Muse on 20 September 2026 because the agent did not identify itself. Our robots.txt guide gives sample rules for allow, block and in-between policies, and which stores allow AI agents tracks what large retailers do.
Verify agents instead of guessing
User-Agent strings can be faked. Web Bot Auth, an IETF draft co-authored by Cloudflare and Google engineers, lets an agent sign each request so you can check which company operates it. Cloudflare began labelling "signed agents" in August 2025, starting with ChatGPT agent. The draft states it "does not authenticate human users", so it tells you who runs the agent, not who the shopper is. See Web Bot Auth for stores.
Step 4: How will you know it is working?
Agent orders arrive through three paths, so measure all three:
- Protocol orders carry their own identifiers. ACP checkout sessions and order webhooks are tied to the agent platform, and Shopify says orders show ChatGPT referral attribution.
- Referral clicks from chatgpt.com, Gemini or Copilot show up as referrers in analytics, when the browser passes them.
- Browser-agent visits show up in server logs by User-Agent and published IP ranges.
Our guide to tracking AI agent traffic sets up each one.
What about llms.txt and other quick fixes?
An llms.txt file is cheap to ship but low impact. An Ahrefs study found 97% of llms.txt files get zero requests, and Google Search does not use it. Spend the time on your feed instead.
Customer service also needs a small update. Under ACP, UCP and Shopify you are the seller, so agent-placed orders follow your normal return policy. Make sure your team can find them, and publish a return policy an agent can read. Shoppers will follow guides such as how to return something your AI agent bought.
- Clean the feedFill required fields, real GTINs, live availability and prices.
- Pick a checkout routePlatform toggle, ACP, UCP or PayPal.
- Fix the human checkoutGuest checkout, wallets, fewer CAPTCHAs.
- Set bot rules on purposeDecide crawler by crawler; verify signed agents.
- Tag and measureSeparate protocol orders, referrals and agent visits.
- Train supportAgent orders are your orders; returns follow your policy.
Are there legal points to check?
In the US, an order placed by an agent is still your sale, so your usual consumer-protection duties on pricing, returns and disclosures apply. Accurate feed data matters: an agent will quote your feed price back to the shopper. UK sellers should read the CMA's 2026 guidance, summarised on Personal Agent UK. Card-network programmes such as Visa Intelligent Commerce and Mastercard Agent Pay mostly work through your payment provider rather than requiring direct work from you.
Bottom line
Start with the feed, because every agent reads it. Turn on your platform's agent channels if you have them, keep checkout simple enough for a careful bot, and make your robots.txt a decision rather than an accident. Then measure for a quarter before investing in custom protocol work.

