How to keep your ChatGPT product feed prices and stock up to date
A ChatGPT product feed holds the prices and stock your store had when the file was made. Nothing in it follows your store afterwards, so a sale, a sell-out or a new product reaches ChatGPT only with a new upload. This guide covers when to upload again, what must stay the same between uploads, and when a file upload stops being the right route.
Why the feed goes stale
Three facts from OpenAI’s documentation decide how updates work:
- Every delivery is a full snapshot. Manual upload, a hosted URL and SFTP all deliver the whole catalogue each time, not a list of changes. A new upload replaces the previous file.
- Dates in the feed do not schedule anything. The spec states that sale-window, expiration and availability dates do not schedule price or availability changes. A sale that ends on Friday still shows the sale price until you upload a file without it.
- The feed is not the checkout. When a buyer acts, your website checks the current offer. A stale feed does not sell at the old price; it shows the old price in ChatGPT and then disagrees with your product page.
OpenAI does not set an update schedule. Its guidance is event-based: update the feed when a sale starts or ends, and update availability when items sell out or come back.
When to upload a new file
| Change in your store | What to do |
|---|---|
| A sale starts | Upload with sale_price filled. It must be lower than price and in the same currency, or it is ignored. |
| A sale ends | Upload with sale_price empty. Do not count on an end date to remove it. |
| Regular price changes | Upload with the new price. |
| An item sells out | Keep the row and set availability to out_of_stock. |
| An item comes back | Set availability back to in_stock (or backorder / pre_order if that is the truth). |
| New product or variant | Add a row with a new, never-used item_id. |
| You stop selling a product | Set is_eligible_search to false on its row. OpenAI does not document what happens to an item that is simply left out of the next snapshot. |
Keep item_ids stable
The item_id is how OpenAI tells that the row in today’s file is the same product as the row in last week’s. The spec asks for a stable ID, unique per item or variant, never reused for a different item, and kept the same when price, stock, title or images change.
- Use the SKU where you have one. It survives theme changes, URL changes and re-imports.
- Do not build IDs from row numbers, titles or export dates. Reordering a catalogue or fixing a typo would then turn every product into a new one.
- Give each variant its own ID and keep its
group_idthe same across uploads. - When a product is discontinued, retire its ID. Do not hand it to a new product.
A refresh routine for a file upload
- Make a new file from your store as it is now. With the ChatGPT product feed generator, enter your store’s address again: it reads current prices and stock, and builds the same item_ids as last time as long as your SKUs and product IDs have not changed. If you export from your platform instead, use the same export settings every time.
- Check the file before it goes up. The generator checks its own output; for a platform export, run it through the feed validator. A missing required column rejects the whole file, so one bad export can undo a good feed.
- Upload it in Business Hub under Products, replacing the previous file, and read the result in Upload history.
- Spot-check two or three products in the file against their live pages: one on sale, one out of stock, one recently added.
How often depends on how often your store changes. Our suggestion, not an OpenAI rule: after every sale start and end, and otherwise weekly for a small catalogue whose prices rarely move. If stock changes every day, a weekly file will be wrong most of the week; see the next section.
One limit of our free generator: a run reads up to 250 products and variants. If your store is larger, the file holds the first 250, and a full snapshot of the rest needs another route.
When to switch to a hosted URL or SFTP
Manual upload is fine while you can keep up by hand. Move to an automated delivery when:
- Prices or stock change daily, or you run frequent short sales.
- The catalogue is too large to rebuild and check by hand.
- You use the feed for ChatGPT Ads. OpenAI’s Ads help states that items in an Ads feed expire after two weeks and recommends a hosted URL or automated SFTP uploads.
A hosted URL is a public HTTPS address where your platform or a feed app publishes the current file; SFTP is a server you or your app push the file to. Both are set up in the merchant portal, and both still deliver full snapshots, so the same rules on item_ids and complete files apply. Most stores get there through a feed plugin or app for their platform.
Shopify stores
Eligible Shopify stores reach ChatGPT through Shopify Catalog, which syncs from the store, so there is no file to keep fresh. The routine above is for stores on WooCommerce, Squarespace, Wix and custom platforms, and for Shopify stores that cannot use that route. The format rules are in the product feed format guide.
Questions
How often should I update my ChatGPT product feed?
OpenAI does not set a schedule. It asks you to update when a sale starts or ends and when items sell out or come back. Weekly plus every sale change suits a small, slow-moving store; daily stock changes call for a hosted URL or SFTP.
Can I schedule a sale in the feed in advance?
No. The spec says sale-window and availability dates do not schedule price or availability changes. Upload a file with sale_price when the sale starts, and one without it when it ends.
Do I upload only the products that changed?
No. Every delivery is a full snapshot of the catalogue. Upload the complete file each time, with the same item_ids, so existing items are updated rather than duplicated.
What happens if I change my item_ids?
Each changed ID looks like a new product. Keep IDs stable across uploads, ideally the SKU, and never reuse an old ID for a different product.
More guides
- ChatGPT Business Hub verification failed: why it happens and what to do
- ChatGPT Business Hub outside the US: verification status by country
- How to claim your business in ChatGPT (Business Hub walkthrough)
- ChatGPT Business Hub product feed: format, required fields and common errors
- ChatGPT Business Hub insights explained: mentions, clicks and how to keep history
- ChatGPT Business Agents: who is eligible and what an agent can do