# Your Next Customer Won’t Have Eyes

Author: Gary Q. Smith
Author URL: https://gqsdirect.com/blog/author/gary-q-smith
Published: 2026-10-30
Category: E-Commerce
Category URL: https://gqsdirect.com/blog/category/e-commerce
Meta Title: Your Next Customer Won’t Have Eyes | GQS Direct
Meta Description: Agentic commerce arrived as a discovery channel, not a checkout. Machine-readable product data is where the money is. What to fix first.

URL: https://gqsdirect.com/blog/agentic-commerce-machine-readable-catalog

Somebody asked an assistant for exactly what you sell this morning.

Half-inch brass fittings, in stock, delivered by Friday. The assistant answered in about four seconds and named three companies.

You weren’t one of them.

Not because your price was wrong. Not because your site is ugly. Because when the machine went looking, your catalog didn’t carry the attribute it needed to confirm you qualified — and a machine that can’t verify doesn’t guess.

**It doesn’t bounce. It just never arrives.**

For thirty years we built storefronts for eyes. Banners, navigation, hero images, the fold. I’ve led four e-commerce implementations and I have argued about homepage layout in more conference rooms than I care to count. So take this from someone who has actually run the business:

> “Your homepage is now a courtesy you extend to humans. Your product data is what the machines use to decide whether you exist at all.”

Four lessons, one honest reckoning with the hype, and the question I’d ask if I sat on your board.

## Lesson One: The storefront didn’t disappear. The shelf did.

Merchandising used to be your job. You decided what sat on the category page, what went above the fold, what got the endcap. You controlled the shelf because the shelf was on your property.

When a buyer asks an assistant instead of browsing, that shelf gets assembled somewhere else, in about four seconds, out of structured data. Yours or somebody else’s.

Module 02 made the case that schema stopped being a star-rating trick and became a machine-readable feed. That was true for search. It is now true for the thing that answers instead of searching — and the standard is higher, because an answer engine doesn’t rank you, it either _names_ you or it doesn’t.

Forrester’s Emily Pfeiffer put the problem plainly when she said crawling and scraping is inadequate for commerce. Scraped pages carry stale stock, stale delivery promises, stale shipping terms. An agent that can’t trust the data moves to a merchant whose data it can.

**That’s the whole game. Not aesthetics. Verifiability.**

> **A rule I live by**
>
> A missing attribute is a lost sale you will never see in your analytics.
>
> There is no bounce, no abandoned cart, no exit page. The agent filtered you before you entered the conversation. Nothing in your reporting will ever tell you it happened.

## Lesson Two: The agents aren’t buying yet, and the numbers say so

Now the part most articles on this subject won’t tell you, because it’s bad for the people selling agentic readiness.

**In-chat checkout stalled.**

OpenAI launched Instant Checkout on September 29, 2025, built on the Agentic Commerce Protocol with Stripe. Etsy sellers first, with over a million Shopify merchants promised to follow. By February 2026, Forrester counted roughly **thirty Shopify merchants actually live** on it. In March 2026, OpenAI pulled it back, moving checkout into Apps.

Why? Walmart found that checkout completed inside ChatGPT converted at about **one-third the rate** of sending the same shopper to Walmart’s own site.

Read that twice. The frictionless future converted three times worse than a link.

And yet — this is the part that matters — **discovery is working.** Walmart found ChatGPT drove roughly **twice the new-customer rate** of search engines. A December 2025 Semrush survey of 1,030 US shoppers found **50% bought something after using AI to research it, while only 22% ever bought inside an AI tool.**

Half your market is already being influenced by a machine. Barely a fifth is transacting with one.

Meanwhile the protocol center of gravity moved. On January 11, 2026, Google and Shopify announced the **Universal Commerce Protocol** at NRF, with Etsy, Wayfair, Target and Walmart as co-developers and more than twenty endorsers including Visa, Mastercard, Stripe and American Express. By April, Amazon, Meta, Microsoft and Salesforce had joined its technical council.

So the plumbing is being standardized by everyone at once, while the buying behavior hasn’t arrived yet. That is not a reason to ignore this. It is a reason to **spend on the half that’s paying today.**

> **A rule I live by**
>
> Discover in AI, buy on your site.
>
> Invest in being findable and verifiable. Keep the transaction, the payment relationship and the customer record on your own property until the data tells you otherwise. Right now the data is not close.

## Lesson Three: Your platform already has the plumbing. It doesn’t have your data.

Here’s the assumption I want to kill: that you need to go build an agent interface.

If you’re on Shopify, **you already have one.** Shopify deploys a Storefront MCP server to every store, and agentic storefronts went live by default for eligible US merchants on March 24, 2026. Nobody opted in. It’s running.

Which means the work in front of you is not protocol plumbing. It’s the same thing it has been since Module 03: **somebody has to make sure what flows through the pipe is correct.** Buy the dispatcher. Don’t hand-build the spaghetti.

Where the platforms stand, as I read it:

**Agentic readiness by platform**

Platform

My assessment

Where it stands

Shopify

**Leader**

UCP co-author; Storefront MCP on every store; agentic storefronts on by default for eligible US merchants

commercetools / Saleor

**Leader**

API-first GraphQL; clean structured product models; custom agent interfaces are straightforward

BigCommerce

**Mid-tier**

Strong native metadata feeds; programmatic checkout through partners

Salesforce Commerce

**Mid-tier**

Joined the UCP technical council in April 2026; custom API work still required

Adobe Commerce — ACCS

**Mid-tier**

API-first and out-of-process by design — the shape agents want

Adobe Commerce — PaaS

**Laggard**

Heavy custom development for agent endpoints; manual schema refactoring

WooCommerce

**Laggard**

No native agent endpoints; plugins and custom code

_My assessment, not a published index. Verify against your vendor’s current roadmap before you decide anything._

Note the Adobe split, because it inverts Module 05. On the SaaS edition you lose PHP and the extension library — and that same out-of-process, API-first architecture is exactly what an agent wants to talk to. The thing that costs you flexibility buys you readiness.

**Nothing is free. Everything trades.**

## Lesson Four: Six things to fix, in the order that pays

Resequenced by what returns money this year, not by what’s most exciting.

1. **Validate your schema.** Clean JSON-LD on every product template — Product and Offer on all of them. **AggregateRating only where genuine reviews exist**, because marking up ratings you don’t have is a policy violation, not a growth tactic.

2. **Complete the catalog.** Material, size, color, dimensions, compatibility, finish. Answer engines filter on attributes. A blank field isn’t a gap in your listing — it’s a disqualification you never see.

3. **Sync price and stock in real time.** If indexed data and live checkout disagree, the agent abandons and learns not to trust you. Module 03 was about exactly this failure, and it is still the one that quietly costs the most.

4. **Build off-site trust.** Language models cross-reference third-party platforms to validate quality. Your Trustpilot profile and your review volume now feed a recommendation engine, not just a badge.

5. **Have the vendor conversation.** Ask your platform three questions: what’s on by default today, what’s on the roadmap, and what does your UCP position look like. Make them answer in writing.

6. **Agentic checkout last.** When the conversion data turns, you’ll want to be ready. Today it hasn’t.


The first three are blocking and tackling. They are also where nearly all of the available money is.

> **A word to the next generation**
>
> Learn product data. Attributes, identifiers, taxonomy, feed hygiene — the unglamorous middle of this business.
>
> Every generation gets a new interface. This one happens to be a machine that reads instead of looks. The people who understood the catalog underneath the interface have been winning for forty years, and that isn’t going to stop now.

> **Your next step**
>
> Pick your ten best-selling SKUs. Open each one’s structured data and count the empty attributes.
>
> That number is your agentic readiness score, and it costs you nothing but an afternoon to find out.

## If I Sat on Your Board: The question I’d ask

Not which protocol. Not what we’re building.

> When a buyer asked an assistant about our category last month, how often were we in the answer — and who here is responsible for checking?

Three possible answers. _We’ve never looked_ means you are flying blind in a channel that already influences half your market. _We looked once_ means somebody was curious but nobody owns it. _Here’s the number, here’s the trend, and here’s the SKUs we fixed_ means you have a merchandiser for the machine age.

The agents aren’t coming for your storefront.

**They’re coming for your data. Give them something worth finding.**

_Next in this series —_ [**_Module 07: The Re-Platforming Payoff_**](https://gqsdirect.com/blog/replatforming-payoff) _The market share and the margin you suffered through the whole project to go get._

> **About the author**
>
> **Gary Q. Smith** — President, GQS Direct, LLC
>
> Gary pairs four decades of P&L-accountable direct marketing leadership with practitioner-level command of today’s commerce stack. He is currently an AI evangelist and practitioner and has led four e-commerce website implementations and integrations, built marketing databases, was architect and project leader for a custom ERP system, and managed omnichannel marketing strategy and communications for several businesses.
>
> _Most consultants have studied these problems. GQS Direct has owned them._
>
> [**Start with a complimentary consultation →**](https://gqsdirect.com/booking.html)

**The E-Commerce Implementation Series**

- [Module 01 — Re-Platforming Is a Systems Project, Not a Web Design Project](https://gqsdirect.com/blog/replatforming-is-a-systems-project)

- [Module 02 — Your Redirect Map Is Worth More Than Your Theme](https://gqsdirect.com/blog/redirect-map-seo-preservation-migration)

- [Module 03 — Middleware: The Key to Effective Integration and Project ROI](https://gqsdirect.com/blog/middleware-integration-project-roi)

- [Module 04 — The Open-Source Paradox: Hidden Maintenance and DevOps Costs](https://gqsdirect.com/blog/open-source-paradox-three-year-tco)

- [Module 05 — Your B2B Buyer Is Not a Consumer With a Bigger Cart](https://gqsdirect.com/blog/b2b-ecommerce-platform-decision)

- Module 06 — Your Next Customer Won’t Have Eyes _(you are here)_

- [Module 07 — The Re-Platforming Payoff](https://gqsdirect.com/blog/replatforming-payoff)


---
This blog is powered by Superblog. Visit https://superblog.ai to know more.
---