We watched an AI agent shop across hundreds of thousands of stores — here's what it actually reads

Chris Jensen· ScandicommerceJuly 27, 2026

We pointed a real AI shopping agent at Shopify's Global Catalog with a vague, human request. It searched the whole market at once, ranked on relevance, and built a checkout — reading only a narrow slice of each product. Here's what that slice is, and what it means for your store.

A real agent shopping the Global Catalog — captured as data, then rendered.

We gave an AI agent a deliberately vague request — “find me something warm to wear indoors, real wool, not synthetic, Norwegian if you can” — and watched it shop.

It didn't open a browser. It didn't visit a store. In a few seconds it queried Shopify's Global Catalog, weighed hundreds of results from merchants it had never been told about, applied a constraint we only implied — Norwegian-made — and returned a 100% traceable merino half-zip from a Norwegian brand, priced better and matched more precisely than the same search typed into Google. Then it built a cart and generated a checkout link, ready to pay.

The surprising part wasn't that it worked. It was how little of each product the agent actually looked at to get there — and what that means for every merchant whose products it will read next.

It isn't a search engine.It's a catalog it queries directly.

The instinct is to picture a smarter Google: the agent “searches the web,” lands on product pages, and reads them like a person would. That's not what happens. Shopify exposes a Global Catalog at a single endpoint. One query reaches across every merchant that participates and comes back ranked by relevance. The agent never crawls store to store — it asks once, and the catalog does the matching on its side. What comes back isn't a page of blue links; it's structured product data the agent reasons over directly.

A shopper

Visits a handful of stores they already know, one tab at a time. Who ranks is decided by ads, SEO and brand recognition.

An agent

Queries the entire network in one call and lets relevance decide. A small Norwegian brand and a global giant are judged on the same fields, in the same pass.

1
query reaches the whole network
100M+
listings ranked by relevance
5
product fields actually read
0
pages crawled

Two catalogs, two jobs

The Global Catalog is cross-merchant and built for discovery. The Storefront Catalog is the same protocol scoped to one store, used for cart and checkout. Discovery happens across everyone; the purchase happens at one merchant. Understanding which is which is the difference between being found and being bought.

The four stages, plainly

Every agent interaction over the Universal Commerce Protocol moves through four clean, permissioned stages. Read top to bottom, it's roughly what a careful human shopper does — the difference is a machine doing it at the scale of the whole catalog, reading structured data instead of rendered pages.

The flow, in four steps

  • Authenticate — the agent presents a profile and is granted a trust tier: what it's allowed to do on your store.
  • Discover — it queries the Global Catalog and evaluates ranked candidates. This is where relevance matching happens.
  • Cart & checkout — it scopes to the chosen store, builds a cart and creates a checkout. Payment stays with the human.
  • Monitor orders — it can track confirmation, fulfilment and delivery, so the relationship continues past checkout.

Trust tiers are your control

Before an agent does anything, it's granted a trust tier — you decide whether it may only discover, or also build a cart and create a checkout on a customer's behalf. Decide that posture deliberately, now, before the traffic arrives.

What this meansfor your product data

Watching the agent discover and choose, it read a narrow, consistent slice of each product. Those few fields carried the entire decision. Everything else in the payload — and there is a lot of it — sat unread while the match was made.

The slice the agent actually read

  • title — what the thing is
  • tags — structured signals to match against the request
  • description — material, origin, weight, use case
  • images — confirm the category
  • variants — whether the size and colour the shopper needed even exist

The fields you may treat as an afterthought are the ones the agent leans on hardest. A title padded for a human skimming a collection page (“NEW ✨ Bestseller — Cozy Winter Knit”) reads as noise to an agent matching “warm wool, made in Norway.” A description that leads with brand story instead of material and origin gives it less to match on. Tags that are internal shorthand leave you invisible to the query that should have found you. There's a specific opportunity for fashion and apparel here: aggregating your product data — consistent material and origin fields, structured variants, tags that describe fit and use — is what makes an agent confident enough to surface you over a bigger competitor whose data is messier. Clean, complete, honest product data isn't hygiene; it's distribution.

One honest caveat about metafields

We observed which fields drove the match in this session — we did not get a guarantee of exactly what every agent reads, and the protocol will evolve. In particular, don't assume metafields and custom attributes are read for matching today; they may not be. Put the truth about your product in the core fields the agent is definitely looking at, not in custom fields it may never see.

What's coming: the Universal Cart

Today an agent that finds products across many merchants still checks out at each one separately — one cart, one merchant, one payment. That boundary is moving. Shopify's Universal Cart — cross-merchant baskets that let an agent assemble items from different stores and check out once — is in early access now. This isn't a prediction; it's a capability being rolled out. When one basket can span merchants, the friction that keeps an agent loyal to one store disappears, and discovery-by-relevance extends all the way through to payment. When the cart no longer belongs to one store, being the best-matched product for your slice of the request is the whole game.

What to doin the next 90 days

Avoid this
  • Titles padded with campaign noise and emojis
  • Descriptions that lead with brand story instead of facts
  • Burying sizes and colours in body copy
  • Relying on metafields an agent may never read
Do this
  • Audit your top 20 products reading only title, tags, description, images and variants
  • Write descriptions as plain facts: material, origin, weight, use case
  • Make every size and colour a real variant, not text
  • Rewrite tags to the words a shopper would actually say
  • Decide your trust-tier posture before the traffic arrives

Questions merchants ask us

If you sell on Shopify, you're very likely in the Global Catalog by default. The question isn't whether an agent can find you — it's whether your product data gives it a reason to choose you.

Want your catalog ready for agent-led shopping?

We help Nordic Shopify merchants get their product data clean, complete and discoverable — the work that decides whether an agent surfaces you or a competitor. Let's look at your catalog together.