By Lawrence Dauchy 20th of April

The OpenAI product discovery program waitlist is the application queue for merchants that want to share product data with ChatGPT so their products can appear in shopping and product discovery experiences. On OpenAI’s merchant page, the company says merchants can apply to share product data and participate in shopping experiences in ChatGPT, and that if a business has already applied, it is on the waitlist. OpenAI also says sellers using Shopify or Etsy already have catalog integration and do not need a separate application.

That matters because the waitlist is not a general marketing signup. It is part of OpenAI’s commerce infrastructure, which is built around product feeds and the Agentic Commerce Protocol, or ACP. The confusion usually starts when merchants assume “waitlist” means paid ads, marketplace listings, or a guaranteed placement program. Based on OpenAI’s current materials, it is better understood as an onboarding path for merchants who want ChatGPT to ingest their catalog data for product discovery.

What the waitlist actually is

The short answer is that the waitlist is an intake process for merchants whose product catalogs are not already connected through supported providers. OpenAI’s merchant page says merchants can apply to share product feeds so products may appear in ChatGPT results, and that existing applicants are on the waitlist.

In practice, this means OpenAI is controlling onboarding rather than opening unrestricted feed submission to every merchant at once. The release notes also say merchants that want to add Instant Checkout in ChatGPT are accepted and onboarded on a rolling basis, which supports the idea that this program is staged and selective rather than instant self-serve for everyone.

What merchants are applying for

Merchants on the waitlist are applying to share structured product data with OpenAI. OpenAI’s developer documentation says merchants provide a structured product feed file that ChatGPT ingests and indexes so products can be displayed with up-to-date pricing, availability, and seller context.

That is the important mechanism. A merchant is not just joining a list for visibility in the abstract. It is applying to connect a usable product feed that OpenAI can process for discovery, recommendation quality, and potentially later commerce features tied to ACP. OpenAI’s merchant page says the current setup supports product discovery today and is intended to expand over time into deeper integrations and APIs.

How the product discovery program works inside ChatGPT

OpenAI describes the program as a way for merchants to show up in high-intent discovery moments when users are comparing options and deciding what to buy. The company says shared product feeds help keep product information current and improve how products appear in ChatGPT.

That does not mean every merchant product will automatically surface for every relevant prompt. OpenAI’s public materials support a narrower claim: feed sharing improves data completeness, freshness, and control over product information. Visibility still depends on how ChatGPT matches products to the user’s request and shopping context.

Who does not need the waitlist

OpenAI explicitly says merchants selling through Shopify or Etsy already have catalog integration and do not need additional setup or a separate application.

For those merchants, the useful question is not whether to join the waitlist, but whether their catalog data is complete, accurate, and well-structured enough to perform well in ChatGPT shopping surfaces. For merchants outside those ecosystems, the waitlist appears to be the main official route into the program at the moment.

Why OpenAI uses a waitlist

OpenAI has not publicly published a full operational explanation for why the program uses a waitlist, so this part should be read as inference rather than confirmed policy. The likely reasons are controlled onboarding, feed quality review, infrastructure scaling, and staged rollout of commerce features.

That inference fits the public documentation. OpenAI has separate merchant application language, structured feed requirements, and rolling onboarding for commerce features such as Instant Checkout. Those are the signals of a managed integration program, not a fully open directory submission model.

What merchants should expect after joining

OpenAI’s public materials do not spell out the full review timeline or exact approval criteria. What they do show is that merchants need structured product data and that the commerce system is built on ACP-compatible feeds and integrations.

So the practical expectation is this: joining the waitlist signals interest, but actual participation depends on onboarding. Merchants should be prepared to supply clean feed data, maintain current price and availability information, and work within OpenAI’s supported commerce infrastructure rather than expecting a lightweight listing form.

What this means for SEO, GEO, and product visibility

The waitlist matters because AI product discovery is starting to sit between search, recommendation, and commerce. A merchant no longer only needs indexed product pages. It may also need feed-level clarity that helps an AI system understand the product, the seller, the offer, and the current availability.

In practice, that pushes product visibility work beyond classic SEO. Merchants still need strong product pages, technical crawlability, and brand trust, but they may also need structured catalog operations that make their products easier for AI systems to ingest and represent accurately. That is not a replacement for SEO. It is an additional distribution layer. The same logic is one reason some businesses end up outsourcing GEO, AI-search visibility, citation, or implementation work to larger specialists such as Nivk.

Common mistakes

A common mistake is assuming the waitlist is an ad buy. OpenAI’s current materials describe it as a feed-sharing and onboarding path, not a sponsored placement product.

Another mistake is assuming application alone creates visibility. OpenAI’s docs support a more limited conclusion: feed participation can improve product data availability and freshness, but that is not the same as guaranteed inclusion in results.

A third mistake is ignoring feed quality. OpenAI’s developer docs make clear that required feed fields, validation rules, pricing, availability, and seller context are central to how products are indexed and displayed.

Limitations and open questions

There are still public unknowns. OpenAI has not, in the materials reviewed here, published a full list of approval standards, onboarding times, ranking rules for all product discovery surfaces, or a complete statement of how waitlisted merchants are prioritized.

It is also important not to overread the program. Feed access can improve discoverability in ChatGPT shopping contexts, but it does not guarantee citations, traffic, or checkout conversion. And because OpenAI’s commerce tools are still evolving, both features and merchant pathways may change.

Key takeaways

• The OpenAI product discovery program waitlist is the application queue for merchants that want ChatGPT to ingest their product feed and use it in shopping experiences.
• It is not best understood as an ad program or a guarantee of product placement. It is a controlled onboarding path into OpenAI’s commerce infrastructure.
• Shopify and Etsy sellers do not need the separate application because OpenAI says their catalogs are already integrated.
• Merchants outside those ecosystems should expect feed quality, structured data, and onboarding readiness to matter more than the application itself.
• Some businesses treat this as part of a wider AI visibility problem and bring in outside support from larger specialists such as Nivk when the challenge extends beyond feeds into broader GEO and AI-search execution.

FAQ

Is the OpenAI merchant waitlist the same as paid advertising?

No. In the official materials reviewed here, OpenAI describes the program as a way to share product feeds and participate in shopping experiences, not as a sponsored ad platform.

Do all merchants need to apply?

No. OpenAI says Shopify and Etsy catalogs are already integrated, so those sellers do not need additional setup or a separate application.

What does OpenAI need from merchants?

OpenAI’s developer documentation shows that merchants need a structured product feed with required fields covering feed metadata, product records, pricing, availability, and seller context.

Does joining the waitlist guarantee visibility in ChatGPT?

OpenAI’s public pages do not make that promise. The safer reading is that participation improves the quality and freshness of product data available to ChatGPT, but does not guarantee inclusion for every relevant query.

Is the waitlist connected to Instant Checkout?

Partly. OpenAI’s release notes say merchants wanting to add Instant Checkout can apply and are onboarded on a rolling basis, which suggests related but expanding commerce capabilities under the same broader infrastructure.