Discovery field guide
OpenAI Product Feed Spec: Discovery Fields
Use this page as a companion for planning and review. The current official product-feed documentation remains the source of truth.
Validate a feedStable is the supported path
OpenAI labels the Stable product-feed path as the supported file-upload route. Draft material is for planning and feedback, so do not treat it as production guidance.
Specifications can change. Recheck the official reference before implementing or delivering a feed.
Required discovery data
OpenAI describes one row for each purchasable item or variant. The basic discovery data includes nine required fields that identify the item, its seller, buyer-facing content, price, availability, and public URLs.
- item_id, title, and description
- url and image_url
- brand and seller_name
- price and availability
Format and value rules
Use UTF-8 text and publicly accessible absolute HTTP or HTTPS URLs. Keep identifiers as strings so leading zeros remain intact. Product values should describe the specific purchasable item or variant.
Availability values and price formatting are constrained by the specification. A local validator can identify obvious issues, but the official reference defines what a production delivery accepts.
Discovery, Ads, and checkout are separate
Discovery data can make a product eligible for search, but eligibility does not guarantee display. Ads and checkout have separate, additional requirements and activation paths.
Do not set a field or upload a draft expecting it to enable checkout. Confirm that scope through the relevant approved integration.
Common questions
FAQ
What are the required discovery fields?
The basic product-data section lists item_id, title, description, url, brand, seller_name, image_url, price, and availability.
Which availability values should I use?
Use the values specified in the current official documentation, including in_stock, out_of_stock, pre_order, backorder, and unknown where allowed.
Does discovery eligibility enable checkout?
No. Checkout is a separate scope that requires its own enabled integration and additional requirements.