OpenAI Commerce
Structured product data for ChatGPT shopping.
Structured product data for ChatGPT shopping. Catalog ingestion through documented feeds and APIs. Does not replace your storefront, PIM or eligibility review. Individual merchant eligibility and deployed configuration require confirmation. Map this role to your existing stack and confirm the exact version, access conditions and implementation scope before making a merchant decision.
What this establishes
The documented role and version scope in the source ledger.
What it cannot establish
Live merchant deployment, private account eligibility, purchase completion or guaranteed AI selection.
Claim-to-source mapping
- description: Structured product data for ChatGPT shopping. · verified · Checked 2026-09-28 · Sources: openai-commerce, openai-start, openai-feed
- role: Catalog ingestion through documented feeds and APIs. · vendor-claim · Checked 2026-09-28 · Sources: openai-commerce, openai-start, openai-feed
What is documented today.
Each state applies to a named capability and scope. Native describes the product’s own role; it does not mean your merchant account has a live integration.
Shipped / publicly documented
Announced / roadmap
Cannot verify
Channel-ready catalog distribution native / preview
OpenAI Commerce: catalog-distribution in the documented product role only. Not proof of a live merchant account, connector or AI-surface deployment. Confirm plan, market and onboarding.
Agent / commerce connectivity native / preview
OpenAI Commerce: connectivity in the documented product role only. Not proof of a live merchant account, connector or AI-surface deployment. Confirm plan, market and onboarding.
What it does not solve: Does not replace your storefront, PIM or eligibility review.
What it helps with
Catalog ingestion through documented feeds and APIs.
What it does not solve
Does not replace your storefront, PIM or eligibility review.
The merchant work
- Identify which existing capability this would replace or complement.
- Confirm region, plan, data access and integration effort.
- Request a scoped proof of fit before purchasing.
Merchant fit: Merchants seeking ChatGPT catalog access.
Individual merchant eligibility and deployed configuration require confirmation.
| Onboarding | Approved partners; apply through official onboarding. |
|---|---|
| Surfaces | ChatGPT |
| Protocols | ACP |
| Pricing | Unknown |
| Regions | Unknown |
| Integrations | Confirm exact platform and connector; no blanket support inferred |
| History | First observed September 2026 |
What we observed, and when.
First house observation: 28 September 2026. Earlier dates, where known, are effective dates researched retrospectively.
First observed 28 September 2026. One baseline snapshot; no subsequent change is recorded.
Go to the source.
Primary documentation records what is publicly stated. It does not independently prove outcomes or your account’s eligibility.
Claim scope: Structured catalog and inventory ingestion for ChatGPT
Claim scope: Product feed access
Approved partners; file and API delivery. This is not evidence of universal checkout availability.
Claim scope: Full snapshot feed delivery
At least daily delivery recommended; not a scanner protocol endpoint.