Can an AI agent actually buy from your store?
An AI agent arrives on your product page carrying a customer's instruction. Find a mid-priced one, check it ships to Melbourne, add it to the cart. Everything it needs is right there on the page. Price, stock status, delivery information, an add-to-cart button.
It leaves without buying, because it couldn't work out which part of the page was the store and which part was decoration.
"It leaves without buying, because it couldn't work out which part of the page was the store and which part was decoration."
That's the gap worth understanding this year. The commerce plumbing for agentic buying is largely built, and Shopify built most of it on your behalf without asking. What decides whether an agent can actually complete a purchase is the layer Shopify doesn't control, which is your theme. And on a store that's been customised by three agencies over five years, that layer is usually where the damage is.
What Shopify has already done for you
In January 2026 Shopify announced its agentic commerce platform. Three parts to it:
- The Universal Commerce Protocol — an open standard co-developed with Google.
- A Storefront MCP server — deployed to every individual store.
- The Agentic Plan.
Then in the first week of May 2026, four agent-facing endpoints appeared on stores without any merchant switching anything on:
- /llms.txt — effectively demoted to a pointer now.
- /agents.md — doing the real work.
- /.well-known/ucp
- /sitemap_agentic_discovery.xml
Type your own domain followed by /agents.md into a browser right now. It's almost certainly sitting there.
The agentic commerce stack, by the numbers
6
Capabilities advertised in your live UCP payload
4
Agent-facing endpoints added to every store automatically in May 2026
<0.1
Google's "good" threshold for Cumulative Layout Shift
Your live UCP payload advertises six capabilities: cart, checkout, order, fulfilment, discount, and catalogue search and lookup. Put plainly, an agent that asks your store what it can do is told it can search your catalogue, build a cart, apply a discount, check out and track fulfilment. That is a functioning transaction surface, and you didn't have to do anything to get it.
One wrinkle worth knowing about. There are two protocols in play, not one. ChatGPT transacts through OpenAI's Agentic Commerce Protocol, while Google's AI Mode and Gemini use UCP. Most Australian merchants will end up needing to work with both. Neither of them is the thing that breaks.
The part Shopify can't do for you
Protocol endpoints describe your store. They don't describe your page.
When an agent needs to read the page itself, to confirm a detail, choose a variant, or complete a step the API doesn't cover, it parses the same HTML a screen reader parses. It has no eyes. It cannot look at your beautifully art-directed hero and understand it the way a person does in a quarter of a second. It has a document tree, some roles and labels, and whatever text it can associate with what.
On a heavily customised theme that document tree is usually a mess, and four failures come up over and over:
- Malformed or missing landmark roles. HTML5 gives these to you for free. A header element becomes the banner landmark, nav becomes navigation, main becomes main, footer becomes contentinfo. Themes built out of nothing but div elements get none of that. Neither do themes shipping two elements that both claim to be main, or a footer that never declares itself. There should be exactly one main and exactly one contentinfo on a page. Plenty of stores have zero, or three.
- Unlabelled logo links. The header logo is nearly always the link back to the homepage, and it's nearly always an image with no alt text and no accessible name attached. To a parser that's a link which goes somewhere and says nothing about where. One line to fix, and wrong on a genuinely surprising number of stores.
- Unannotated forms. Inputs with no label, or with a label that's only visually associated rather than programmatically connected. A field an agent can see but cannot name is a field it won't fill with any confidence. This bites on the newsletter signup, which nobody minds, and on the variant selectors and address fields, which matters a great deal.
- Layout that moves while it loads. Cumulative Layout Shift measures how much the page jumps around as it renders. Google's threshold for good is under 0.1, assessed at the 75th percentile of real visits. Above that, humans tap the wrong thing and agents interact with an element that has since relocated. It's the one failure that costs you on both sides at once.
How to check your own store
Half an hour, nothing to install, no developer required:
- Run Lighthouse on your homepage. Chrome, DevTools, the Lighthouse tab, Mobile setting, Accessibility category ticked. The headline score is a rough signal and not worth obsessing over. The failing items listed underneath it are the useful part, and they map almost one to one onto the four failures above.
- Run it again on a product page. Product pages fail differently to homepages, and the product page is where the transaction happens.
- Put the same product URL through Google's Rich Results Test. That shows you what your structured data actually publishes, which is regularly not what the store owner believes it publishes.
- Visit your-domain.com.au/agents.md and your-domain.com.au/.well-known/ucp. Read what your store is currently telling agents about itself. Most merchants have never looked.
- Open PageSpeed Insights and read the CLS figure from the field data section, not the lab data. Lab CLS on a fast connection with no ad blockers and no third-party widgets firing is flattering, and it is not what your customers get.
The point
The uncomfortable finding is this. An agent can have absolutely everything it needs to buy from you and still fail on the page.
"An agent can have absolutely everything it needs to buy from you and still fail on the page."
The protocol handshake succeeds. The catalogue lookup returns your product with the right price. The cart capability is advertised and working. And then the agent reads a page where the navigation, the content and the footer are indistinguishable from one another, the buy button's accessible name is empty, and the variant selector shifts forty pixels down half a second after render.
None of that is a Shopify problem. None of it appears in your conversion rate as an identifiable line. It shows up as an absence, in shortlists you were never on, in a channel you can't yet measure properly.
It's also worth saying that fixing this isn't really an AI project. Landmark roles, labelled form fields, alt text on the logo and a stable layout are accessibility basics that have been the right thing to do since long before an agent could hold a credit card. Agentic commerce didn't create the requirement. It added a second, far more literal-minded audience with no tolerance for ambiguity, and put a commercial number against work that used to get filed under compliance.
The bottom line
Run Lighthouse on your product page template with the accessibility category on and write the number down. Then go through the failing items and count how many relate to structure, naming or labelling, rather than colour contrast. That count is your agent readiness backlog. In our experience it's shorter than people expect, and most of it is theme work measured in hours rather than a rebuild.
For the catalogue side of the same problem, the companion piece is Your product titles don't say what the product is. The protocol lets an agent transact with you. Your data and your markup decide whether it wants to.
At beCommerce, we help Australian Shopify stores fix exactly this layer — the landmark roles, labelling and layout stability that decide whether an agent, a screen reader and a mobile customer can all actually complete a purchase. If you want us to run this audit against your product page template, let's talk.
Is your store making any of these mistakes?
We audit Shopify stores for exactly these kinds of conversion-killing patterns — the ones that have become normalised until you see them through a customer's eyes.
Book your free audit →
