How to make AI shopping agents pick your Shopify store

There is a version of e-commerce arriving where your customer never sees your store. An agent does the searching, the comparing, and increasingly the buying, and it makes its decision from structured data long before a human would have look

There is a version of e-commerce arriving where your customer never sees your store. An agent does the searching, the comparing, and increasingly the buying, and it makes its decision from structured data long before a human would have looked at your photography. AI shopping agents do not browse, they query, which means the thing deciding whether your product gets recommended is the machine-readable data behind your product page rather than anything a designer touched, and most merchants have never once looked at what theirs actually says.

So we looked at ours. We run two Shopify stores, and this is what we found, what the protocols are doing, and what actually closes the gap.

The shopper is quietly becoming a machine

This stopped being speculative sometime around the start of this year.

Adobe's Q1 2026 data has AI-referred shoppers converting 42% better than human-referred ones, and retailers with agent integrations reported outsized growth over Cyber Week. Meanwhile the plumbing got standardised fast. Google launched the Universal Commerce Protocol with Shopify at NRF 2026, letting agents pull live pricing and inventory, build carts, and check out. Stripe and OpenAI's Agentic Commerce Protocol does a parallel job behind ChatGPT Shopping. Commercetools has a decent overview of where this is heading.

The direction is not subtle: your catalog is becoming an API that machines call.

Agents do not see your design, they read your data

This is the part merchants resist, because it devalues the thing they spent money on.

An agent asked to find "a warm floor lamp under 200 euro that ships to Germany and can be returned" does not look at your hero image. It reads fields. Title, price, currency, availability, shipping destination, delivery time, return window, ratings. Then it compares you against everyone else who published those fields cleanly. If one of those fields is missing or stale, you are not ranked lower. You are excluded from the comparison, silently, before it begins.

Beautiful does not equal effective has always been our position on storefronts. Agentic commerce makes it literal. The prettiest store with incomplete data loses to a plain one with complete data, every time, because only one of them is legible.

What we found on our own two stores

Rather than theorise, we pulled a product page from each of our Shopify stores, Warm Shelf (home decor and lighting) and Zenyzen (wellness devices), and read the structured data an agent would actually receive.

The good news first, and it surprised us slightly. Shopify's defaults are stronger than the discourse suggests. Both stores emit four JSON-LD blocks per product page, including Product and Offer with live price and availability, plus MerchantReturnPolicy, OfferShippingDetails, and ShippingDeliveryTime. That is most of what an agent needs to answer "can I buy this, for how much, will it arrive, can I send it back." If you are on Shopify and have done nothing, you are further along than you think.

That is the honest state of our own houses, and we are fixing it rather than writing a victory lap. The lesson generalises: the defaults get you to legible, the gaps are where you get beaten, and you cannot see any of it from the storefront.

The prerequisite nobody wants to hear

Before protocols and schema, there is a blunter requirement: the agent has to be able to find you at all.

If your product pages are not in the index behind the assistant, you cannot be recommended by it, full stop. For ChatGPT that means Bing. For assistants grounding on other engines it means other indexes, which is exactly why we wrote about getting discovered by Brave Search and why the whole AEO playbook matters here. Perfect schema on a page no index has crawled is a beautifully labelled box in a warehouse nobody has the address for.

The checklist that actually closes the gap

1. Read your own structured data. Pull a product page, find the JSON-LD, and look at it. Most merchants have never done this once. It takes ten minutes.
2. Add review and rating schema. This is the highest-value gap for most Shopify stores, ours included. Agents lean on third-party validation to break ties.
3. Keep price and availability accurate in real time. An agent that gets a stale price and a failed checkout learns not to send you buyers.
4. Publish BreadcrumbList. Cheap, and it hands agents your category structure instead of making them infer it.
5. Make sure you are indexed, on Bing and the other engines behind the assistants, not just Google.
6. Watch the protocols. UCP and ACP are where the catalog-as-API future is being standardised. You do not have to implement them this quarter. You do have to know they exist.
7. Do not rip out the page-builder tax and replace it with a schema tax. Fast, clean, server-rendered pages are the substrate for all of this, which is exactly why we pulled GemPages and rebuilt on native Shopify sections.

The pattern here rhymes with everything else in AI visibility right now. The winners are not the merchants doing something clever. They are the ones who are simply legible to machines, consistently, in a market where most of their competitors are still optimising exclusively for eyes.