What is the Agentic Commerce Protocol?

What the protocol is

The Agentic Commerce Protocol is a written set of rules for how a shopping assistant buys from a store without clicking through the website. An agent, here, is the assistant inside a chat product such as ChatGPT. You describe what you want, it searches a catalog, and it can place the order by calling the store’s checkout in software, rather than by loading your theme and tapping buttons the way a person would.

A protocol is the shared language for that conversation, so the assistant and the store agree on how a cart, a price, and a payment are described. Without one, every store would invent a private API and the assistant could not shop across them.

The ACP repository says OpenAI and Stripe maintain that specification, and the status badge still says beta. Versions in the repo are dates. The latest stable snapshot listed there is 2026-04-17, and it covers checkout plus a cart, a product feed, orders, authentication, and an MCP binding, which is a way for the assistant’s tools to call that same checkout. Older snapshots stay in the repo. A date in that tree is a revision of the spec, not a version of your Shopify theme.

Stripe’s ACP docs describe the same protocol as something Stripe, OpenAI, and Meta created. The spec repository does not list Meta as a maintainer. If you are reading the repo, you are reading what the spec contains, and if you are reading Stripe’s page, you are reading how Stripe wants a payment integration built. Those two pages can name different companies, so quote the page you actually followed.

ACP’s introduction says the agent renders the checkout screen and collects the payment details, while the seller keeps the commerce backend and the payment processing it already uses. The shopper does not have to walk your templates. Your product photo, a popup, and a reviews widget are not part of that conversation, because the conversation is an API call, not a page load.

What Shopify publishes instead

Shopify’s path for this is not the Agentic Commerce Protocol. Shopify’s January 11, 2026 announcement names the Universal Commerce Protocol, co-developed with Google, as the open standard, and the same post says ChatGPT, Microsoft Copilot, Google AI Mode, and Gemini are turned on from the Shopify admin in a screen called Agentic Storefronts. Shopify’s agent docs describe catalog search, carts, a checkout handoff back to the merchant, and order tracking. Some trusted agents can finish checkout themselves. Other flows send the buyer to your storefront to pay.

You can see which of those your shop is advertising without a developer account. Copy the hostname that ends in myshopify.com and request https://that-host/.well-known/ucp in a browser.

You want a JSON document, not the HTML of the theme. Shopify’s profile docs say that business profile describes the protocol version, the services, the capabilities, the payment handlers, and the signing keys.

A JSON document at that URL means the shop is publishing Universal Commerce Protocol, which is not an ACP endpoint and not a speed score. If the URL returns a 404, do not add a fake JSON file to the theme, because Agentic Storefronts is an admin setting and Shopify publishes the profile on the storefront host when that setting is on.

Pasting a script into theme.liquid, or installing a speed app, does not turn one protocol into the other. They are two specifications, written by different companies, for the same kind of job.

When your product page still loads

A purchase that finishes inside the chat never requests your product image, so it cannot change Largest Contentful Paint. Good LCP is 2.5 seconds or faster at the 75th percentile of real users, and that number only describes someone who loaded a URL. A lab run of the product page cannot tell you whether ACP or UCP is switched on, and a fast product page does not implement either protocol.

The visit that still hits your theme is the handoff. Shopify’s agent docs say some flows turn a cart into a checkout and send the buyer to the storefront to pay, and when that person lands on a product page the app embeds in the head still run. They compete with the image the same way they do for any other visit.

Open that live product URL, not the theme editor preview, because the preview often hides app embeds. In Chrome DevTools, open the Network panel, disable the cache, and reload, then find the product image request.

You should not expect an ACP call in that list, because the introduction says the agent buys without traversing the site. What you should see is the theme, Shopify’s own assets, and the app embeds. Shopify’s theme guidance treats third-party JavaScript as a common reason a light theme feels heavy once it is live.

If one of those scripts evaluates before the product image finishes, it is on the critical path for the handoff visit, which means the browser spent the start of the page on the app instead of the photo. Does Klaviyo slow down Shopify is that same Network panel check aimed at one onsite script.

If the theme marks the product image as lazy while a chat widget starts immediately, the browser fetches the widget first. Google’s LCP guide says the LCP image should be discoverable early and fetched with high priority, so do not lazy-load the hero on that landing.

What you change

Start with the profile rather than the theme. Open /.well-known/ucp on your myshopify host and read the protocol version and the capabilities it lists. If a channel you expected is missing, use Agentic Storefronts in the admin, the screen that covers ChatGPT, Copilot, and Google, and request the profile URL again. Leave theme.liquid alone unless you already have two copies of the same marketing tag, because protocol support is not a script you paste in.

On the product page, stop lazy-loading the hero, because a buyer sent over from chat to finish paying is waiting on that image. If third-party tags still sit ahead of the image in the Network panel, load those tags after the page is usable, and do not delay Shopify checkout or payment scripts. Place a test order the way a shopper would, including a handoff from a channel you turned on, and tap the form and add to cart on a phone.

Whoosh does not implement ACP or UCP. App Sequencing loads known third-party scripts after the product image so they do not race it, and it does not copy the theme. Everything adds a prerender of the likely next page and a preload of the real LCP image, and it does not prerender cart, checkout, or account. App Sequencing is US$99/month and Everything is US$149/month, each with a 7-day free trial. Add ?whoosh=disable on a product URL when you want one view with Whoosh off.

If the UCP file is already there and field LCP on the product page is at or under 2.5 seconds, leave the theme alone. The remaining work is the catalog data and which channels are enabled. The FAQs cover how the app behaves once it is installed, and the free speed audit measures the product page before you touch a tag.