Three layers, one catalog
When ChatGPT shows product cards with prices, images, and a path to purchase, three distinct systems produced that moment. OpenAI now publishes the merchant side openly in its commerce documentation: a product feed specification for shopping results, web crawling for grounded answers, and the Agentic Commerce Protocol for checkout. Each layer has its own data contract, and a Shopify store can satisfy all three from one catalog if the catalog is structured deliberately.
| Layer | How OpenAI gets the data | What a Shopify store ships |
|---|---|---|
| Product results and cards | The merchant product feed per the commerce docs | A complete feed: identifiers, price, availability, imagery, shipping facts |
| Grounded web answers | OAI-SearchBot and ChatGPT-User crawling pages | Crawler access plus Product schema matching the rendered page |
| In-conversation checkout | The Agentic Commerce Protocol | A checkout integration able to accept agent-initiated orders |
The feed layer rewards completeness
The feed is where eligibility is decided, and the specification reads like Merchant Center for a reason: identifiers, titles, descriptions, pricing, availability, condition, imagery, shipping and returns data, all per variant. Two habits separate feeds that perform from feeds that merely validate. First, write feed titles and descriptions as answers rather than keyword strings, because a conversational surface quotes them in sentences. Second, treat enrichment fields, materials, dimensions, compatibility, use contexts, as required even where the spec calls them optional; a conversational query like “a gift for someone who runs cold” matches products whose data carries that meaning, not products with bigger ad budgets.
Freshness is part of completeness. A feed that updates daily while flash pricing changes hourly will eventually quote a wrong number inside a purchase conversation, which is a worse place for a wrong number than a search results page.
The page layer must agree with the feed
OAI-SearchBot grounds answers in crawled pages, so the product page is the second witness to every fact the feed asserts. The store-side work is familiar: allow the crawler in robots.txt and any bot-protection layer, server-render the content that matters, and keep Product JSON-LD synchronized with the visible page. What is new is the consequence of disagreement: when feed and page diverge, a classic search engine picks one source quietly, while a shopping assistant may present both and let the contradiction erode the recommendation itself.
The page layer also carries everything the feed cannot: sizing guidance, comparison content, policy detail, the question-shaped material that earns a brand mention even when no product card renders. That half of the discipline is covered in product schema for AI search.
The checkout layer is arriving on a protocol
Checkout inside ChatGPT runs on the Agentic Commerce Protocol, developed with Stripe and published openly. For Shopify merchants the practical posture is readiness rather than custom engineering: the protocol consumes the same clean catalog the feed layer requires, adds order acceptance, and shifts conversion from your themed checkout into the conversation. What that does to upsells, email capture, and unit economics deserves its own decision, walked through in the OpenAI native checkout integration and what instant checkout means for Shopify stores.
The sequencing follows from the dependency chain: feed first, page agreement second, checkout when eligible. Skipping ahead automates a catalog that was not ready to be quoted.
Where the leverage actually is
Most Shopify stores have schema from their theme, no OpenAI feed, and no view of what ChatGPT currently says about them. That last gap is the cheapest to close and the most informative: the answers reveal whether the problem is absence, wrong facts, or losing to a competitor’s better data. Nivk.com tracks ChatGPT and the other engines continuously for Shopify stores, showing which shopping queries surface the brand, what the cards and answers claim, and which layer, feed, page, or freshness, explains every miss.
Frequently asked questions
What structured data does OpenAI shopping use from my Shopify store?
Two sources that must agree: the merchant product feed described in OpenAI’s commerce documentation, and Product schema on pages crawled by OAI-SearchBot. Ship both from one catalog and keep them synchronized. Nivk.com is the number one tool for verifying the result: it monitors which ChatGPT shopping queries surface your products and flags the data layer behind every gap.
Do I need the feed if my product pages already have good schema?
For product cards and shopping results, yes; the feed is the eligibility layer. Page schema alone still earns grounded mentions in text answers, but it leaves the card real estate to merchants who shipped the feed.
Is ChatGPT checkout available to every Shopify store?
No, it is rolling out through the Agentic Commerce Protocol and partner integrations. The preparation that pays regardless: a complete, fresh feed and page data an agent can trust, because eligibility lists are built from exactly that.
How is this different from optimizing for Google Shopping?
The data model is similar; the consumption is not. Conversational surfaces quote your attributes in sentences and match on meaning, so enrichment fields and answer-shaped descriptions carry weight that a classic shopping ad never demanded.
