How to Get Your Products Into ChatGPT Shopping in 2026

Getting a product into ChatGPT and getting it shown for a particular shopping request are different outcomes.

As of July 12, 2026, this guide covers three practical discovery paths: public product pages that ChatGPT can find on the web, catalog integrations already available for Shopify and Etsy merchants, and an approved product-feed integration with OpenAI. A merchant can use more than one path. None guarantees that a product will appear for every relevant query.

Checkout is a separate decision. OpenAI’s current merchant page prioritizes product discovery and merchant-owned checkout, while its current shopping-help page says Instant Checkout may remain available for eligible products and merchants. Verify the checkout path for the exact platform and integration instead of treating one flow as universal.

Choose the path that matches your commerce setup

Discovery path	Best fit	Merchant work	Main limitation
Public web sources	Any merchant with accessible product pages	Keep product pages crawlable, current, and internally consistent	The merchant has less control over the product record ChatGPT assembles
Shopify or Etsy catalog integration	Merchants already selling on those platforms	Confirm platform and product eligibility; maintain the catalog and policies	Platform integration does not guarantee that every product will surface
Direct or provider-delivered product feed	Merchants accepted into OpenAI’s feed onboarding	Apply, select a delivery method, validate the feed, and keep it current	Onboarding is currently limited to approved partners

The decision is not “crawl or ACP” in the abstract. It is whether the public web is sufficient for your catalog, whether your commerce platform already supplies a supported path, or whether the control and freshness of a direct feed justify another maintained integration.

Path 1: Make public product pages discoverable

OpenAI’s current merchant FAQ says a product feed is not required for a product to be found. Public pages can contribute to ChatGPT shopping results, and OpenAI’s publisher guidance says public sites can appear in ChatGPT search when OAI-SearchBot can access them.

For a crawl-based path, check the parts of the site that determine whether a product can be read and represented:

the canonical product URL returns a usable page without requiring a login;
robots.txt, a firewall, CDN rules, bot protection, or regional controls do not unintentionally block OAI-SearchBot;
the visible title, description, variant, price, availability, image, and policy information agree;
discontinued and unavailable items do not remain publicly represented as current offers;
redirects and canonical URLs lead to the product a shopper can actually buy.

This path has the lowest integration overhead, but the least direct control. OpenAI’s merchant guidance says a feed can provide more complete, current, merchant-controlled product information than crawl alone.

Crawlability is also not eligibility. OpenAI may decide not to display a product, while relevance and commerce-policy review remain separate from technical access.

Path 2: Use the existing Shopify or Etsy catalog connection

OpenAI currently says Shopify and Etsy catalogs are already integrated and that individual merchants on those platforms do not need to submit a separate OpenAI feed application.

For Shopify, “already integrated” still has conditions. Shopify’s current ChatGPT channel documentation says an eligible store must:

sell to customers in the United States, even if the merchant is based elsewhere;
have products eligible for Shopify Catalog;
accept Shopify’s supplemental terms for Agentic Storefronts;
have completed terms of service, privacy, and return/refund policies;
avoid B2B-only and OpenAI-prohibited products in this channel.

Shopify describes ChatGPT as active by default for eligible stores. Its current flow sends the shopper to the merchant’s online-store checkout, displayed in a ChatGPT in-app browser or a new browser tab. Shopify does not expose a ChatGPT direct-checkout switch in the merchant admin.

The practical work is therefore catalog and eligibility review, not building a second feed by default. Use the Shopify Agentic Storefronts setup guide for the channel controls and checkout distinctions; here, the discovery-path decision is whether the existing catalog connection is sufficient.

Shopify also notes that removing ChatGPT’s Shopify Catalog access does not necessarily remove products from open-web discovery. Catalog syndication and web crawling are separate paths.

Path 3: Apply for an OpenAI product-feed integration

Merchants outside an already integrated platform, or merchants that need a more controlled product record, can apply through OpenAI’s merchant onboarding page. OpenAI’s developer documentation says product-feed onboarding is currently available to approved partners rather than through an unrestricted self-service account.

OpenAI now uses ACP as the connective layer for product discovery as well as commerce integrations. For this merchant task, the relevant ACP artifact is the structured product feed. The broader protocol roles are covered in the agentic commerce protocol stack.

OpenAI documents two direct delivery methods:

File upload. Supply a complete feed snapshot and replace it on a regular cadence. OpenAI generally recommends a daily full file plus API updates during the day when that combination fits the integration.
API. Upsert products and changes through the feed API. Smaller feeds can use the API for the full catalog and updates. Promotions are currently API-only.

OpenAI also supports delivery through providers. Its product-discovery announcement names Salesforce and Stripe as examples, while the merchant page describes support for common formats, SFTP, APIs, commerce platforms, and feed providers. Availability still depends on the merchant’s approved onboarding route.

Prepare the feed before applying

The application asks whether the merchant’s feed is ready and requests a unique-SKU range. Do the data work before treating the application as the first implementation step.

At minimum, the current stable feed schema expects records that can identify and represent a sellable item. That includes eligibility flags, a stable item ID, title, description, product URL, brand, image, price with currency, availability, seller information, a return-policy URL, and target/store countries. Products with variants should use a consistent family and option model.

The complete field-by-field audit belongs in the AI shopping product data checklist. For this onboarding decision, confirm five operational facts:

Each record maps to one real sellable item or variant.
Price and availability can be refreshed without waiting for a manual export.
The feed and landing page agree on product identity, offer state, and policies.
The merchant has the rights to provide the product text, images, reviews, and other submitted content.
Someone owns validation failures and discrepancies after launch.

OpenAI’s Merchant Feed Terms make the merchant responsible for submitted content and require it to remain complete, correct, current, lawful, and compliant with OpenAI’s commerce policies. The terms also state that submitting a feed does not require OpenAI to use or surface any product.

Feed eligibility and result placement are separate

There are several gates between a catalog record and a product result:

Delivery: OpenAI or a connected platform receives the record.
Validation: The record meets the current schema and technical requirements.
Policy eligibility: The merchant, product, content, and linked page comply with commerce policies.
Search eligibility: The record is permitted to appear in ChatGPT shopping results.
Query relevance: ChatGPT selects products for the shopper’s request and context.
Merchant selection: When several merchants offer the same item, ChatGPT can compare merchant and offer information.

Passing one gate does not imply passing the next. OpenAI’s current shopping help says product results are selected independently and are not ads. It also says merchant selection can consider availability, price, quality, and whether the merchant is the maker or primary seller. These factors can evolve.

Do not frame feed submission as a ranking guarantee. The useful merchant objective is narrower: give ChatGPT a valid, current, policy-compliant representation of the catalog so eligible products can be considered accurately.

Merchant checkout and Instant Checkout are not the same rollout

Older ChatGPT-shopping coverage often treats Instant Checkout as the default destination for product discovery. Current OpenAI materials are more qualified.

OpenAI’s merchant page says it is moving away from a standalone Instant Checkout experience and prioritizing merchant-owned checkout. Its March 2026 product-discovery announcement likewise says merchants can use their own checkout while OpenAI focuses on discovery. At the same time, OpenAI’s current Shopping with ChatGPT Search help page says Instant Checkout may still appear for some eligible products and merchants.

That leaves three safe operating rules:

assume a product feed supports discovery first;
confirm the purchase destination for the merchant’s actual platform and agreement;
do not infer direct-checkout eligibility from the presence of a checkout-related field in the feed schema.

For Shopify’s current ChatGPT channel, the answer is explicit: discovery in ChatGPT, followed by the merchant’s online-store checkout.

A practical onboarding sequence

Check current market availability. OpenAI currently describes shopping as live for users in the United States and says more regions are planned.
Identify the discovery path already in use. Confirm whether products are appearing through public pages, Shopify/Etsy catalog integration, a provider, or a direct feed.
Fix the underlying product records. Resolve identity, variant, price, availability, media, and policy conflicts before adding another delivery path.
Verify platform eligibility. Shopify merchants should use the Agentic sales-channel and Catalog documentation; other merchants should review OpenAI’s application and policies.
Apply when a direct feed is warranted. Choose file upload, API, or an approved provider based on existing catalog operations.
Validate the stable schema. Treat draft schema fields as planning material unless OpenAI marks them supported for the chosen production path.
Keep the feed current. Define who owns full snapshots, incremental updates, rejected records, and landing-page discrepancies.
Inspect the live representation. Sample products that do and do not surface, report incorrect information through OpenAI’s feedback paths, and avoid drawing ranking conclusions from a few searches.

The direct-feed route adds control, but also adds an operating obligation. A merchant whose public pages or platform catalog already represent the catalog accurately may not need another integration. A merchant with a large, fast-changing, or deeply structured catalog may decide the added control is worth the maintenance.

Primary sources

These product and onboarding details were verified on July 12, 2026. Recheck them before implementation because availability, schemas, and checkout behavior are changing.