Guides How to get your products into ChatGPT Shopping with a product feed
How to get your products into ChatGPT Shopping with a product feed
How products reach ChatGPT today: Business Hub, the identity check, OpenAI's product feed fields, how they differ from a Google feed and what to prepare.
- ChatGPT finds products on the public web, through private integrations and, for retail, in merchant product feeds.
- Businesses start in OpenAI's Business Hub, claim their business and verify their identity before they can upload products.
- Every row needs nine product fields plus target_countries and store_country; the standard upload currently targets the US.
- Feeds arrive as full snapshots by manual upload, a hosted HTTPS URL or SFTP.
- A Google feed is close but not identical: several fields have other names and seller_name is required.
How products get into ChatGPT today#
OpenAI describes the shopping journey in four steps. A customer describes what they need. ChatGPT looks for options in the public web, private API integrations and, for retail, merchant product feeds. The customer compares offers. The journey then moves to browser use on your website or to a plugin you build.
A product feed is the part you control for discovery. OpenAI suggests one for businesses that sell physical goods, to keep products, images, prices and availability current in its search index. The feed does not update a cart or confirm a purchase: your live website or plugin checks the current offer when a customer acts.
Getting access#
OpenAI's current setup runs through Business Hub:
- Claim your business. Start in Business Hub. If you have an Ads account or work with an OpenAI account manager, your workspace admin should have received a personal claim link. Otherwise, follow OpenAI's claim instructions for businesses.
- Verify your identity. In the product section of Business Hub, complete identity verification. OpenAI requires it before you can upload products.
- Choose markets. Select the countries and currencies where you sell. The standard OpenAI-format upload currently targets the US; use other markets only after OpenAI confirms them for your integration.
- Upload the feed. Choose one delivery method: manual upload, a hosted HTTPS URL or SFTP. Each delivery is a full snapshot of your catalog.
- Fix errors. Review the upload and correct what it reports.
Business Hub onboarding is OpenAI's current process, and the details can change. Check the OpenAI pages linked under Sources before you start.
The fields every row needs#
Submit one row for each purchasable item or variant. OpenAI's schema gives formatting rules for CSV, TSV and JSONL files. These eleven fields are required:
| Field | What it holds | Example |
|---|---|---|
item_id | Stable ID, unique per item or variant | NP-RIDGE2-GRN |
title | Product name with the selected variant; aim for 150 characters or less | Northpeak Ridge 2-person tent, green |
description | Factual plain text; aim for 5,000 characters or less | Freestanding tent with two doors. |
url | Product page, with the variant selected when possible | https://example.com/ridge-2?color=green |
brand | Brand as shown on the product page | Northpeak |
seller_name | Name of the seller supplying the offer | Northpeak Outdoor |
image_url | Main image showing this variant | https://example.com/img/ridge-2-green.jpg |
availability | in_stock, out_of_stock, pre_order, backorder or unknown | in_stock |
price | Regular price as amount and ISO 4217 code | 349.00 USD |
target_countries | Destination countries as ISO codes | ["US"] |
store_country | Country of your store | US |
A minimal JSONL record looks like this:
{"item_id":"NP-RIDGE2-GRN","title":"Northpeak Ridge 2-person tent, green","description":"Freestanding two-person tent with two doors and an aluminum pole frame.","url":"https://example.com/products/ridge-2?color=green","brand":"Northpeak","seller_name":"Northpeak Outdoor","image_url":"https://example.com/images/ridge-2-green.jpg","availability":"in_stock","price":"349.00 USD","target_countries":["US"],"store_country":"US"}
Optional fields worth sending#
- Variants:
group_id,listing_has_variationsset totrueandvariant_dict, for example{"color":"Green"}. Each variant gets its own row, ID, price, URL and images. - Identifiers:
gtin(8, 12, 13 or 14 digits with a valid check digit) andmpn. - Attributes:
condition,product_category(a path from broad to specific, separated by>),material,color,size,gender,age_group, dimensions and weight. - Offer details:
sale_price,shipping_price,additional_image_urls. - Returns and reviews:
accepts_returns,return_deadline_in_days,return_policy,review_count,star_rating.
Leave unknown optional values empty. OpenAI asks you not to send placeholder strings such as null, unknown or n/a. An empty shipping_price means unknown, not free.
How it differs from a Google feed#
| Topic | Google Merchant Center | ChatGPT product feed |
|---|---|---|
| Product ID | id | item_id (id and sku accepted as aliases) |
| Product page | link | url |
| Main image | image_link | image_url |
| Variant group | item_group_id | group_id (item_group_id accepted) plus variant_dict |
| Seller | external_seller_id, multi-seller accounts only | seller_name on every row |
| Availability | in_stock, out_of_stock, preorder, backorder | adds unknown; writes pre_order |
| Category | google_product_category from Google's taxonomy | product_category, a path you supply |
| Market | Set per data source | target_countries and store_country per row |
| GTIN | Strongly recommended when assigned | Optional |
Prices use the same 79.99 USD form in both. A Google feed is a good starting point, but rename the fields and add the seller and market columns before you upload.
Checkout is separate#
Setting is_eligible_checkout to true does not turn on checkout. OpenAI says checkout requires a separately enabled integration, and for it each row also needs seller_privacy_policy and seller_tos URLs. Until then, shoppers act on your own website. OpenAI's playbook lists browser use, plugins, ChatGPT Wallet payments on your existing checkout and Sign in with ChatGPT as the ways to support that step.
What to prepare before you start#
- Keep IDs stable. Do not reuse an
item_idfor another item, and never put a price into an offer ID. - Make product and image URLs public, absolute and preferably HTTPS.
- Write titles and descriptions as plain, factual text about the exact variant.
- Store GTINs as text so leading zeros survive.
- Update the feed when prices, sales or stock change.
- Allow
OAI-SearchBotin robots.txt. OpenAI recommends it so your site can appear in ChatGPT's search results.
Where Central fits#
You choose what goes in (your shop, files or product pages) and where it goes out; Central AI researches, verifies and writes everything in between. Central publishes to the channels you choose, and the first 3 products are free.
Questions
Can any shop send a product feed to ChatGPT?
OpenAI's docs send businesses to Business Hub, where they claim their business and verify their identity before uploading. The standard upload currently targets the US; other markets need OpenAI's confirmation first.
Can I upload my Google Shopping feed as it is?
Not without changes. Several fields have other names, such as url instead of link and image_url instead of image_link, seller_name is required, and every row needs target_countries and store_country.
Does the feed let ChatGPT complete a purchase?
No. OpenAI says the feed does not update a cart or confirm a purchase. Checkout happens on your website, through a plugin or through a separately enabled checkout integration.
Sources
- Submit product feeds · OpenAI developer docs checked 19 November 2026
- Product feed schema · OpenAI developer docs checked 19 November 2026
- Partner Playbook Overview · OpenAI developer docs checked 19 November 2026
- Overview of OpenAI Crawlers · OpenAI developer docs checked 19 November 2026
- Product data specification · Google Merchant Center Help checked 19 November 2026