ChatGPT Merchant Setup: How to Get Your Products Into ChatGPT Shopping

Search "ChatGPT merchant setup" right now and a good chunk of what comes back still walks you through enabling Instant Checkout, step by step, as if it's the current path to selling inside ChatGPT. It isn't, as of October 2026. OpenAI retired the native Instant Checkout experience in March 2026, about six months after launching it, and the term doesn't even appear in OpenAI's current developer documentation anymore (developers.openai.com/commerce). If you're setting this up today, working from a guide still built around Instant Checkout will walk you straight into dead ends. Here's what's actually live.

What changed, briefly

OpenAI launched Instant Checkout in late September 2025, with Etsy as the first live integration and Shopify merchants rolling out shortly after, built on top of the newly announced Agentic Commerce Protocol (ACP), developed jointly with Stripe as an open standard for in-chat transactions (OpenAI). Walmart joined with roughly 200,000 products that November. The pitch was straightforward: a user finds a product in a ChatGPT conversation and buys it without leaving the chat.

It didn't get the adoption OpenAI wanted. By the time the feature was pulled back, only a small number of Shopify's millions of merchants had actually gone live with it, and Walmart's own data reportedly showed in-chat checkout converting far worse than simply sending the shopper to Walmart's own site (CNBC). On March 24, 2026, OpenAI confirmed it was moving away from the native, OpenAI-hosted checkout experience, shifting toward a model where ChatGPT focuses on product discovery and recommendation, and retailers build their own in-chat experiences (or redirect out to their own site) for the actual purchase (CNBC).

The underlying technology didn't disappear, the branding and the default assumption did. OpenAI's current checkout specification describes what it calls Agentic Checkout, not Instant Checkout, and states its purpose plainly: to "enable merchants to run end-to-end checkout flows inside ChatGPT while keeping orders, payments, and compliance on their existing commerce stack" (OpenAI commerce docs). That's a meaningfully different posture than the original pitch. Checkout, when it happens inside the chat at all, happens on infrastructure the merchant controls, not a payment flow OpenAI operates on your behalf.

Here's the timeline in one place, since the pace of change is itself the reason so much existing advice is stale:

What "merchant setup" actually means today

Two separate things get bundled under "ChatGPT merchant setup," and conflating them is where most confusion comes from.

The first, and the one that matters for almost every merchant: getting your product catalog into ChatGPT's discovery and recommendation layer, so your products can surface when someone asks a shopping-related question. This runs on a product feed, the same basic mechanism that powers Google Shopping, and it's the part OpenAI is actively expanding access to.

The second, narrower thing: building an actual in-chat purchase flow using the Agentic Checkout and Delegated Payment specs, so a shopper can complete a transaction without leaving ChatGPT. This still exists as a documented capability, but it's opt-in, technical, and not something most merchants need to touch to benefit from showing up in ChatGPT's product recommendations at all.

Start with the feed. Only build the checkout integration if you have a specific reason to want a fully in-chat purchase flow rather than sending the shopper to your own site, which is also a perfectly normal outcome of being discovered in ChatGPT. Showing up in that discovery layer at all depends on the same crawlability basics covered in our guide to getting cited by ChatGPT: if OAI-SearchBot can't reach your site, a perfect product feed won't be enough to get you surfaced in conversation around your category even if the feed itself is accepted.

Applying as a merchant

Go to chatgpt.com/merchants and fill out the merchant application. The form asks for basic business details, your primary product categories, and whether you're interested in feed-based discovery, checkout integration, or both. OpenAI doesn't publish a stated review timeline for applications.

You can skip this step entirely if you sell through Shopify or Etsy. Both platforms already have direct integrations into ChatGPT's commerce ecosystem, meaning your catalog can be eligible for discovery without a separate application or manual feed setup on your part, beyond whatever platform-level opt-in each one requires on their side.

As of this writing, ChatGPT Shopping is live for users in the United States specifically. OpenAI has described building toward a self-serve merchant platform for broader data integration, with plans to expand to more merchants and regions over time, though no firm international timeline is public (chatgpt.com/merchants). If you sell primarily outside the US, applying now still makes sense to be positioned for whenever that expands, but don't plan a launch around a specific date OpenAI hasn't committed to.

Building the product feed

This is the part worth getting right, because a bad feed is the single most common reason products don't show up accurately, and OpenAI's specification is more particular about format than a lot of third-party guides suggest.

Nine fields are required for every product: item_id, title, description, url, brand, seller_name, image_url, availability, and price. OpenAI's own spec is blunt about one common shortcut: "use a real brand and seller name, not placeholders" (OpenAI product feed spec). Beyond the required set, recommended fields cover variant data (for products with size or color options), additional product attributes, extra image URLs, sale pricing and shipping and return terms, and review data like star rating and review count, all of which the documentation describes as improving ranking, relevance, and buyer trust, not just display accuracy.

Pay attention to file format, since this is where a lot of guides written before the spec matured get it wrong. The current specification treats JSONL (JSON Lines) as the primary supported format, with CSV and TSV (including gzip-compressed versions of either) also supported. Plain JSON, XML, RSS, Atom feeds, and spreadsheet formats are explicitly not supported. If you've got an existing Google Merchant Center feed in XML, you cannot point it at OpenAI's ingestion as-is; it needs to be converted to one of the accepted formats first.

Submission is file-based rather than a live API call in the current documentation, referencing a dedicated file upload process once you're an approved merchant. Keep availability and pricing current; the specification's own language stresses submitting current stock status with every row and updating availability the moment an item sells out or comes back, though it doesn't commit to one universal refresh cadence, so check the current guidance for your integration method rather than assuming a fixed number.

The most common way merchants sabotage their own feed has nothing to do with missing fields and everything to do with lazy ones: a placeholder brand name copied from a template, a seller name that doesn't match what's on the actual storefront, or an availability field that was accurate the day the feed was built and hasn't been touched since. OpenAI's documentation flags the placeholder problem specifically because it's common enough to call out by name. A technically complete feed with stale or generic data in it will pass validation and still perform badly, because the problem isn't structural, it's that the content itself gives a model nothing specific to work with.

If you want in-chat checkout, not just discovery

For merchants who do want a shopper to be able to complete a purchase without leaving ChatGPT, that capability still exists through the Agentic Checkout Spec, paired with the Delegated Payment Spec for handling the actual payment credential securely. The flow, per OpenAI's documentation, has ChatGPT create a checkout session with the cart, let the user adjust it, hand off for payment, and then receive a webhook confirming the order, while the merchant's own systems handle the order, payment processing, and compliance throughout.

Stripe co-developed the Agentic Commerce Protocol and is the first supported implementation of the Delegated Payment Spec, through what's called a Shared Payment Token. If you already process payments with Stripe, enabling the agentic payment flow is a small, well-documented integration rather than a ground-up build. If you use a different payment processor, OpenAI's protocol is designed so you can still participate, either through Stripe's Shared Payment Token API or by adopting the Delegated Payment Spec directly, without switching processors.

"Merchant Center," clarified

The name invites a mix-up worth heading off directly. Google Merchant Center is Google's own product-data platform, built to power Google Shopping ads, free product listings, and Google's AI shopping surfaces. ChatGPT has no equivalent product called a "merchant center." The closest thing is the application and feed-submission process at chatgpt.com/merchants described above, which is a separate system with its own feed specification, not an extension of or integration with Google's.

Some tooling vendors claim a Google Merchant Center feed can be adapted to cover much of what OpenAI's spec requires, since the underlying product attributes (price, availability, images, identifiers) overlap conceptually. That's plausible as a starting point for mapping your data, but the two feeds are not interchangeable files, given OpenAI's required fields and supported formats differ from Google's, so treat an existing Merchant Center feed as a useful data source to pull from, not a file you can submit directly to OpenAI unmodified.

Shopify and Etsy specifics

Shopify shipped Agentic Storefronts as the centerpiece of its Winter '26 Edition, announced December 10, 2025, letting a merchant enable the feature once inside Shopify admin and have their catalog, pricing, and inventory data syndicated out to ChatGPT, Microsoft Copilot, and Perplexity simultaneously, without a separate integration built for each platform (Shopify). For a Shopify merchant, this is the lowest-effort path into ChatGPT's discovery layer: the setup lives in Shopify's own admin rather than in a separate application to OpenAI.

Etsy was OpenAI's original launch partner for the shopping feature in 2025 and has remained integrated through the shift away from native Instant Checkout, with product discovery continuing even as the transaction itself has moved back toward Etsy's own site in most cases.

What's still limited

If you're new to this whole category and commerce is just one piece of a broader AI-search strategy, GEO for beginners is a reasonable place to get oriented before narrowing in on the shopping-specific work here.

Geography is the clearest limit: shopping discovery and any checkout features are currently scoped to US ChatGPT users, by OpenAI's own account. Self-serve tooling for merchants outside the existing Shopify, Etsy, and direct-application paths is still described as something OpenAI is building, not something broadly live today. And the in-chat checkout capability, however it's branded going forward, is clearly secondary to discovery in OpenAI's current priorities after the Instant Checkout pullback, so expect the product feed and recommendation side of this to keep getting the bulk of OpenAI's attention and documentation updates for the foreseeable future.

None of this is static. A spec that changed its primary supported file format and retired a flagship feature's name within about a year of launch is not one to treat as settled. Check developers.openai.com/commerce directly before building anything, rather than working from a guide (including parts of this one, eventually) that's more than a few months old.

That pace is also the reason it's worth building the feed yourself or with a developer who reads the actual spec, rather than relying entirely on a third-party agency's packaged "ChatGPT shopping setup" service frozen to whatever the protocol looked like when they built their offering. A feed that was compliant in January can fail validation by October if a required field changed, and the entity actually accountable for noticing that is whoever owns the feed, not a vendor who shipped it once and moved on.

Google is building the same thing on its side. Our explainer on Google's Universal Commerce Protocol (UCP) covers how agentic checkout works in AI Mode and Gemini, and how its setup compares to OpenAI's.

FAQ

Is Instant Checkout still a thing in October 2026?

Not as a distinct, branded feature. OpenAI retired the native Instant Checkout experience in March 2026 and now describes the equivalent capability as "Agentic Checkout," built to run on the merchant's own systems rather than an OpenAI-hosted flow. Guides still structured entirely around enabling Instant Checkout are describing a version of the product that no longer exists in that form.

Do I need to apply at chatgpt.com/merchants if I already sell on Shopify?

No. Shopify's Agentic Storefronts feature, part of its Winter '26 Edition, syndicates your catalog to ChatGPT (and Copilot and Perplexity) directly from Shopify's own admin, without a separate OpenAI application.

What file format does OpenAI's product feed actually require?

JSONL is the primary supported format, with CSV and TSV (plain or gzip-compressed) also accepted. Plain JSON, XML, RSS, Atom, and spreadsheet files are explicitly not supported by the current specification, which matters if your existing product feed was built for Google Merchant Center or another platform that expects XML.

Can international merchants apply even though shopping is US-only right now?

You can apply at chatgpt.com/merchants regardless of location, but ChatGPT Shopping is currently live for US users specifically, and OpenAI hasn't published a firm timeline for expanding beyond that. Applying now positions you for when access widens; it won't get you into a market OpenAI hasn't opened yet.

What happened to the retailers who built Instant Checkout integrations before March 2026?

Reporting on the pivot describes most of them, including Shopify's early adopters and Walmart, continuing with product discovery through the same underlying feed infrastructure, while the actual purchase step moved back to redirecting shoppers to the merchant's own site in most cases rather than completing in-chat. The work merchants did building a feed wasn't wasted; the checkout-specific integration work on top of it, for those who'd built one, became optional rather than the default path.

Does getting my products into ChatGPT's feed guarantee they'll be recommended?

No. Being in the feed makes you eligible to be surfaced; it doesn't make you the one recommended over a competitor with a similarly complete feed. That recommendation question runs on different signals (reviews, comparison content, consistent entity data) covered in our piece on getting recommended by ChatGPT, which is worth reading alongside this one once your feed is actually live.

If you sell through Shopify or Etsy, confirm the integration is actually switched on in your platform admin before assuming you're covered. If you don't, build your product feed against OpenAI's current spec, in JSONL or CSV, with real brand and seller names and current availability on every row, and apply at chatgpt.com/merchants this week rather than waiting for a clearer signal that isn't coming before the next spec change does.