OpenAI changed its feed documentation. Does my Shopify store need a rebuild?
A developer cites OpenAI's Draft schema and asks for feed work. First separate Shopify Catalog from registered OpenAI feed integrations.
· Updated August 22, 2026
- When this applies
- A developer or feed vendor points to OpenAI's Draft schema and asks you to approve a feed rebuild or new variant fields. [1] [2] [3]
- When this does not apply
- Do not approve an OpenAI feed rebuild when the store uses Shopify's native Catalog route, or approve Draft fields for a production file-upload integration; use the current supported contract for the named route. [3] [2] [4]
- Why this matters
- Approving work before identifying the production route can put unsupported Draft definitions into production or add a separate feed that Shopify's native path does not require. [1] [3] [4]
- What to do, or not do
- Ask the current catalog or feed owner to name the production route and provide its exact specification. Use Stable for a registered OpenAI upload; take no feed-build action for Shopify's native Catalog route. [2] [4]
- Sources checked
- August 22, 2026
When a third party is worth paying for, and what you do not have to buy
A developer or vendor may show you OpenAI’s Draft schema and describe it as a required Shopify rebuild. Do not approve the work until the person who owns the current catalog names the production route and links its exact contract.
OpenAI’s product feed page presents two schema views, Stable and Draft. OpenAI says Stable is the supported file-upload path and Draft is available for planning and feedback only.
For a Shopify merchant, there is a second distinction. OpenAI’s file-upload schema describes a feed integration. Shopify’s documented path to ChatGPT is Shopify Catalog. They are related commerce surfaces, but they do not create the same merchant task.
Ask the current owner for one production contract
Ask the person or company that maintains the store’s catalog integration for:
- The production route name and exact specification URL.
- The system that sends product data and the person responsible for failures.
- One example source record mapped to the current production format.
If the route is Shopify Catalog, a separate OpenAI feed rebuild is irrelevant. If the route is a registered OpenAI file-upload integration, the evidence should point to Stable. A Draft link is planning evidence and does not authorize a production migration.
The current supported feed is flat
The Stable schema uses one product or variant per row. Each row needs its own identifier, title, plain-text description, link, image, availability, price, and brand.
Three details are easy to misread when switching between commerce schemas:
| Field | Stable OpenAI file-upload requirement |
|---|---|
description | Plain text, up to 5,000 characters |
price | An amount followed by a three-letter currency code, such as 79.99 USD |
| variants | One product or variant per row, with grouping fields for related variants |
The Stable feed does not require a nested description object with plain, html, and markdown values. It also does not encode 79.99 USD as the integer 7999. Those shapes appear in OpenAI’s Draft reference, which uses nested variants and minor currency units. They are planning definitions, not the current production file-upload instructions.
Variant rows still matter. OpenAI identifies each row with a stable item ID and provides grouping fields such as group_id, variant_dict, color, and size. This lets a supported feed distinguish a blue size 10 shoe from its other variants without turning the feed into a nested product document.
What Shopify supplies
Shopify states that eligible stores are active on ChatGPT by default. Product data reaches ChatGPT through Shopify Catalog, and merchants can manage that access under Sales channels > Agentic.
The same help page says merchants do not need a separate action for product discovery through Shopify Catalog. It also sets the current eligibility floor: the store must sell to customers in the United States, products must be eligible for Shopify Catalog, the supplemental terms must be accepted, and the required store policies must be complete.
That means a standard Shopify merchant should not build or buy an OpenAI feed uploader merely because the public OpenAI schema changed. A custom integration owner using OpenAI’s registered file-upload path has a different responsibility and should follow Stable.
Shopify variant descriptions need care
Shopify has first-class variant fields for options, price, inventory, shipping, and images. Its standard product description belongs to the product. Shopify’s variant editing instructions do not include a separate variant description field.
Custom variant metafields can hold specialized information. Their existence does not prove that Shopify Catalog or ChatGPT consumes them. A merchant should only depend on a custom field for AI-channel transmission when Shopify documents the mapping.
The safe catalog rule is narrower:
- Put shared product facts in the product description.
- Keep variant option values, prices, inventory, SKUs, and images accurate for each variant.
- Use product titles and descriptions to explain differences a buyer must understand when those differences are not represented by standard variant fields.
- Keep Terms of service, Privacy policy, and Return and refund policy complete in Shopify Admin.
What to check in Shopify Admin
Open Sales channels > Agentic and confirm that ChatGPT access matches the store’s intent. Then review the products that matter most:
- Confirm each variant has the correct option values, price, inventory, SKU or barcode, and image.
- Make the product description accurate enough to cover material differences between variants.
- Confirm products remain eligible for Shopify Catalog and available to customers in the United States.
- Complete the required store policies and keep legal disclosures within the first 6,000 characters of the product description, as Shopify instructs.
These checks produce a bounded result: a named production route, one current schema, and a source record that matches it. They do not prove that ChatGPT displayed, ranked, or sold a product.
Frequently asked questions
- Should a production feed use OpenAI's Stable or Draft schema?
- Use Stable. OpenAI states that Draft is published for planning and feedback only and is not supported for production file-upload integrations. [1] [3]
- Do Shopify merchants need to upload an OpenAI product feed?
- Shopify's documented merchant path does not require a separate OpenAI feed. Eligible stores are active on ChatGPT by default through Shopify Catalog, subject to Shopify's channel requirements and merchant controls. [4]
- Does Shopify have a standard description field for each variant?
- No. Shopify's standard product description belongs to the product. The standard variant editor covers options, pricing, inventory, shipping, and variant images. Variant-specific custom data can use metafields, but merchants should not assume a custom field is sent to ChatGPT unless Shopify documents that mapping. [5]