How Do You Get Your Products Into ChatGPT in 2026?
You share a structured product feed with OpenAI under the Agentic Commerce Protocol, after being accepted as an approved partner. OpenAI states that onboarding product feeds in ChatGPT is currently available to approved partners, with applications through chatgpt.com/merchants. Once accepted, you deliver product data by file upload, by API, or both, so ChatGPT can index your catalogue and show accurate titles, descriptions, images, price and availability in shopping experiences.
A feed is the foundation for three separate things, and each has its own switch: appearing in search and shopping answers, appearing in ChatGPT Ads, and being purchasable through checkout inside ChatGPT. Most coverage blurs these together. OpenAI's specification keeps them strictly apart, and so does this guide. It is the hub of a five-part series; the spokes cover field requirements, agentic checkout, promotions and the production launch checklist.
Explain It Like I Am Five
Imagine a very helpful shop assistant who does not own a shop. People ask the assistant what to buy, and the assistant can only recommend things it has a list of. Your product feed is the list you hand over: what each thing is, what it costs, and whether it is on the shelf. A good list means the assistant can recommend you. A list with mistakes means it cannot. If you also build a till the assistant is allowed to use, people can pay without leaving the conversation, but the money still goes to your shop, and you still handle returns. And right now, only shops the assistant has invited can hand over a list at all.
| Capability | What it requires in 2026 | Default |
|---|---|---|
| Discovery in ChatGPT search and shopping | Approved-partner feed with nine required fields per row | Search eligibility on when omitted |
| ChatGPT Ads | Feed rows marked Ads-eligible plus an Ads integration | Off unless a feed-level Ads default applies |
| Checkout inside ChatGPT | A separately enabled integration implementing the Agentic Checkout Spec | Off |
| Promotions | The promotions API | None; not deliverable by file |
What Is the Agentic Commerce Protocol in 2026?
The Agentic Commerce Protocol, or ACP, is the set of specifications OpenAI uses for commerce flows in ChatGPT, covering product feeds, agentic checkout and delegated payment. OpenAI points to agenticcommerce.dev and a public GitHub repository for the protocol itself, and publishes its implementation docs at developers.openai.com/commerce, including a machine-readable index at /commerce/llms.txt and Markdown versions of every page.
It is a different protocol from Google's Universal Commerce Protocol, which we covered in our UCP guide. For a brand, the strategic point is that AI shopping surfaces are converging on structured, machine-readable catalogue data with strict validation, whichever vendor is asking. Our broader guide to preparing a brand for AI shopping agents covers that strategy layer; this series covers OpenAI's actual specification.
Who Is Eligible to Use ChatGPT Product Feeds in 2026?
Approved partners, in markets OpenAI has confirmed for their integration, selling products that pass OpenAI's prohibited products policy. Each of those three conditions removes a meaningful share of brands, and it is better to know which applies to you before investing engineering time.
| Gate | What OpenAI states in 2026 | What it means for you |
|---|---|---|
| Partner approval | Feed onboarding is currently available to approved partners; apply at chatgpt.com/merchants. | You can build to the spec, but not switch it on without acceptance. |
| Market | The standard OpenAI-format upload currently targets the US; the shared format represents US, CA and MX; other markets only after OpenAI confirms them. | An Indian feed does not reach Indian shoppers by default. |
| Product policy | Prohibited products include, among others, adult content, age-restricted products such as alcohol, nicotine and gambling, weapons, prescription-only medications, unlicensed financial products and deceptive practices. | OpenAI may remove products or ban a seller for violations. |
| Checkout payments | The checkout spec lists stripe, adyen and braintree as providers and card as the payment method. | UPI-led checkout is not in the current spec. |
Today, the published specification is built around a US default market and card payments through three named providers. That does not make the work pointless for an Indian brand: a clean, validated feed is reusable across every AI shopping surface, and brands selling into the US are directly in scope. But a brand whose customers are mostly in India and pay mostly by UPI should treat ChatGPT checkout as a watch item rather than a 2026 launch, and should ask OpenAI directly about market availability before committing budget.
How Should You Deliver a Product Feed in 2026?
OpenAI's recommended pattern is the full feed once a day by file upload, then updates through the day by API. If your feed is small, you can provide both the full feed and regular updates via the API. File upload is delivered to an SFTP server, and for file upload you overwrite the same file or shard set with your latest snapshot on a regular cadence. For the API, you upsert products.
- Decide on file upload, API, or both.
- Review the specs for that method and confirm required fields, canonical field names and validation rules.
- Validate required fields for every record.
- Upload through the chosen method.
- Keep the feed current by overwriting snapshots or upserting through the API.
One exception changes the plan for most retailers: OpenAI states that promotions data can only be provided via the API. If discounts matter to your conversion, a file-only integration cannot carry them. Our promotions guide covers the schema and its three supported benefit types.
What Does a Product Feed Have to Contain in 2026?
Nine fields per row, one row per purchasable item or variant: item_id, title, description, url, brand, seller_name, image_url, availability and price. Two rules cause most rejected rows. Availability is a closed list, and omitted, empty or unrecognised values reject the row. Prices are written as an amount and a three-letter currency code, such as 79.99 USD, with no thousands separators.
The API product schema is structured differently, with products holding a list of variants and money expressed as integer minor units with a separate currency. Teams that use both delivery methods need two formatters, not one. The full field reference, including variants, returns, reviews and the Google-compatible feed path, is in our product feed requirements guide.
| Delivery method | Money format in 2026 | Structure |
|---|---|---|
| File upload (OpenAI format) | 79.99 USD as a string in major units | One flat row per item or variant |
| API | Integer amount in ISO 4217 minor units plus currency | Product with nested variants |
| Google-compatible file | Decimal amount and currency, normalised to two places | Merchant Center style columns, after OpenAI confirms the format |
How Does Checkout Inside ChatGPT Work in 2026?
You host five HTTPS endpoints that ChatGPT calls to create, update, complete, cancel and retrieve a checkout session, and each response returns the full, authoritative cart. Payment runs through your existing PSP using a single-use delegated token, and you send signed webhooks when orders are created and updated. OpenAI is not the merchant of record: customers see your name on their card statement, and refunds and chargebacks stay with you.
Direct integration with the Delegated Payment Spec is only for PSPs or PCI DSS level 1 merchants using their own vaults; everyone else uses their PSP's implementation, with Stripe's Shared Payment Token named as the first compatible one. The endpoint-level detail is in our agentic checkout merchant guide, and the tests OpenAI requires before you go live are in our production checklist guide.
How Does the Feed Connect to ChatGPT Ads in 2026?
Through the same product data, with its own eligibility flag. In the OpenAI file format, is_ads_eligible set to true marks a product for Ads processing; omitted or empty means disabled unless a feed-level Ads default applies, and it is independent of search eligibility. Ads feeds follow OpenAI's Ads product feeds guide, and the optional ads_metadata field carries product-filter keys configured for your Ads integration, which OpenAI says you should confirm during Ads setup rather than invent.
For marketers this is the most immediately actionable part of the stack, because a feed that is already validated for discovery can be extended for Ads without a checkout build. Our ChatGPT Ads API guide covers campaign structure, bidding and the controls you actually have.
What Can You Not Control in ChatGPT Shopping in 2026?
Whether you are shown. OpenAI's specification says it in five words on the search eligibility flag: eligibility does not guarantee display. A valid, approved, fully populated feed makes your products available to be considered; it does not buy placement, and nothing in the commerce documentation describes a ranking you can configure. Paid placement is a separate product, ChatGPT Ads, with its own controls.
Several other things sit outside a merchant's control in the published specification, and it is better to plan around them than discover them.
| Outside your control | What the documentation says in 2026 | What you can do instead |
|---|---|---|
| Display | Eligibility does not guarantee display. | Improve data quality; use Ads for paid placement. |
| Acceptance | Feed onboarding is currently for approved partners. | Apply early and prepare the feed in parallel. |
| Market | Additional markets apply only after OpenAI confirms them. | Ask directly about your country and currency. |
| Enforcement | OpenAI may remove a product or ban a seller for policy violations. | Audit your catalogue against the prohibited list before submitting. |
| Scheduling | Sale-window, expiration and availability dates do not schedule price or stock changes. | Push updates yourself when prices and stock change. |
| Reconciliation | Conflicting values between top-level attributes and variant options are not reconciled for you. | Keep one source of truth and validate before upload. |
How Do You Improve the Quality of Your ChatGPT Listings in 2026?
By writing for an answer engine rather than a product grid. OpenAI's best-practice guidance asks for concise, factual descriptions, accepting both plain text and bullet-style text. It notes that optional fields such as description.html, description.markdown, categories.taxonomy and seller.links can improve answer quality but are not required for ingestion, and it adds a sensible caution: if an optional field needs brittle transforms, omit it until the data is stable.
This is where the work overlaps with what Distk does for AI search visibility more broadly. A model choosing between products leans on specific, checkable attributes: material, dimensions, condition, return terms, review aggregates. Marketing copy that says "premium quality" gives it nothing to extract. A description that states what the product is made of, how big it is, and what happens if the customer returns it gives it everything. Variant-specific titles, URLs, images, availability and prices, which OpenAI asks for whenever those values differ by variant, matter for the same reason: an answer that recommends the right size in the wrong colour is worse than no answer.
- State facts, not adjectives. Material, size, weight, compatibility and care instructions.
- Declare condition explicitly. Omitted condition may be treated as new; used and refurbished must always be declared.
- Supply returns data properly. Acceptance, window in days, and a policy URL, as separate fields.
- Use consistent seller attribution. One seller name and durable public policy links across the catalogue.
- Encode URLs correctly. OpenAI asks for valid, encoded URLs, for example
%20for spaces.
What Should a Brand Do First in 2026?
Apply, clean the catalogue, and measure, in that order. The application decides whether anything else happens. The catalogue work pays off on every AI shopping surface regardless of whether OpenAI accepts you this quarter. And measurement is the only way to know whether the channel is worth the checkout build later.
| Step | Why it comes now in 2026 | Owner |
|---|---|---|
| Apply at chatgpt.com/merchants | Nothing goes live without approval. | Founder or e-commerce lead |
| Ask about your market | The default target is the US; confirm yours before budgeting. | Founder |
| Audit availability and price exports | The two most common causes of rejected rows. | Catalogue owner |
| Stabilise item, group and offer IDs | Promotions and variants depend on them. | Engineering |
| Add feed attribution to product URLs | OpenAI recommends parameters such as utm_medium=feed; without them the channel is invisible in analytics. | Marketing |
| Decide on promotions | API-only, so it shapes the integration choice. | Marketing and engineering |
| Check checkout fit last | Payment provider and payment method support decide whether it is buildable. | Finance and engineering |
What Are the Common Mistakes With ChatGPT Product Feeds in 2026?
- Building before applying. Feed onboarding is limited to approved partners.
- Assuming your market is covered. Standard uploads target the US until OpenAI confirms otherwise.
- Treating discovery, Ads and checkout as one switch. They are three separate eligibility controls.
- Planning promotions into a file feed. They are API-only.
- Exporting availability or price in the wrong format. Both reject rows.
- Assuming OpenAI handles refunds. You remain merchant of record.
- Skipping feed attribution. You will not be able to tell whether the channel works.
- Selling prohibited categories. OpenAI may remove products or ban a seller.
Key Takeaways for 2026
- Product feeds in ChatGPT are currently available to approved partners, applied for at chatgpt.com/merchants.
- Discovery, Ads and checkout are three separate capabilities with three separate eligibility controls.
- Nine required fields per row; availability and price formatting cause most rejections.
- OpenAI recommends a daily full file upload plus API updates, and promotions are API-only.
- The standard upload targets the US, and the shared format represents US, CA and MX.
- Checkout uses five merchant-hosted endpoints, card payments via Stripe, Adyen or Braintree, and leaves you as merchant of record.
- Feed attribution parameters are how you measure the channel at all.
Distk helps D2C and e-commerce brands in India and internationally decide whether AI shopping surfaces are worth building for yet, prepare catalogue data that passes strict validation, and set up the measurement that proves whether the channel pays before anyone commits to a checkout build. If ChatGPT shopping is on your 2026 list, that assessment is where we start.