Rule reference · OpenAI Stable file upload
OpenAI product feed rules (Stable file upload)
The OpenAI Stable product-discovery schema explained field by field: the nine required basics, the optional and conditional fields around them, and exactly which checks this MVP runs.
64 versioned rules across 3 rulesets · ruleset 1.0.0 · rule data verified 11 November 2026 · no account needed for a local run
Rules
19 OpenAI Stable rules
Required fields
9 basic discovery fields
Last verified
11 November 2026
Ruleset version
1.0.0
Which OpenAI surface this covers
This ruleset validates the published Stable file-upload product-discovery schema. It is not the Draft schema, not the Ads feed, not Checkout, and not a REST feed API. Those are separate integration scopes with their own onboarding, and the MVP does not check them.
It is also not the ChatGPT Business Hub upload contract. Business Hub is a separate merchant-facing surface and is handled as a manual readiness checklist; see the Business Hub readiness checklist. Passing this ruleset does not certify Business Hub ingestion.
The nine required basic fields
item_id, title, description, url, brand, seller_name, image_url, availability, price.
Missing any of these is an error for the row. Everything else in the schema is optional, conditional, or guidance — seller_url in particular is optional and is never treated as a base discovery blocker.
Availability must be one of in_stock, out_of_stock, preorder, backorder, discontinued. Price is decimal major units, a space, then an uppercase ISO 4217 code — for example 79.99 USD — with no grouping comma and no exponent.
Required basic fields (1)
The nine required discovery fields of the Stable file-upload schema.
Rule | Requirement | Field | Reported when it fails | Source |
|---|---|---|---|---|
OpenAI required discovery field is missing OAI-DISC-001 · v1.0.0 | required | — | Error The Stable file-upload discovery schema has nine required basic fields. Fix: Populate each required field using the Stable schema and the correct data type. | Official source 11 November 2026 |
item_id (1)
One stable, unique string per sellable item or variant.
Rule | Requirement | Field | Reported when it fails | Source |
|---|---|---|---|---|
OpenAI item_id is missing or duplicated OAI-ID-001 · v1.0.0 | required | item_id | Error Each item or purchasable variant needs a stable unique item_id. Fix: Provide a stable unique string ID per sellable item/variant. | Official source 11 November 2026 |
Title and description guidance (2)
Length guidance only: exceeding it is a warning, not a rejection.
Rule | Requirement | Field | Reported when it fails | Source |
|---|---|---|---|---|
OpenAI description exceeds guidance OAI-DESC-001 · v1.0.0 | recommended | description | Warning The schema gives description length guidance; exceeding the suggested length is not by itself a hard rejection. Fix: Keep the description factual, clear, and concise. | Official source 11 November 2026 |
OpenAI title exceeds guidance OAI-TITLE-001 · v1.0.0 | recommended | title | Warning The schema gives concise title guidance; exceeding the suggested length is not by itself a hard rejection. Fix: Keep the product title concise and factual. | Official source 11 November 2026 |
Product URL (1)
Absolute public HTTP(S) URL.
Rule | Requirement | Field | Reported when it fails | Source |
|---|---|---|---|---|
OpenAI product URL is invalid OAI-URL-001 · v1.0.0 | required | url | Error Product URL must be an absolute public HTTP(S) URL. Fix: Provide the public product URL. | Official source 11 November 2026 |
Image URL (1)
A direct public image URL. Availability and MIME checks belong to the scanner, not to this rule.
Rule | Requirement | Field | Reported when it fails | Source |
|---|---|---|---|---|
OpenAI image URL is invalid OAI-IMG-001 · v1.0.0 | required | image_url | Error Image URL must be an absolute public HTTP(S) URL pointing directly at the image. Remote availability and MIME checks are handled separately by the scanner. Fix: Provide a direct public image URL. | Official source 11 November 2026 |
Availability (1)
The five allowed values in the Stable schema.
Rule | Requirement | Field | Reported when it fails | Source |
|---|---|---|---|---|
OpenAI availability value is missing or unrecognized OAI-AVAIL-001 · v1.0.0 | required | availability | Error Availability must be one of the five allowed values for the Stable discovery schema. Fix: Use one of the documented availability values. | Official source 11 November 2026 |
Price (3)
Money syntax, positivity, and the sale-price relation.
Rule | Requirement | Field | Reported when it fails | Source |
|---|---|---|---|---|
OpenAI price is not in the required money syntax OAI-PRICE-001 · v1.0.0 | required | price | Error Decimal major units, a space, then an uppercase three-letter ISO 4217 code. No grouping comma or exponent. Fix: Rewrite the price as e.g. 79.99 USD. | Official source 11 November 2026 |
OpenAI price is not positive OAI-PRICE-002 · v1.0.0 | required | price | Error The regular price must be greater than zero. Fix: Correct the price to a positive amount. | Official source 11 November 2026 |
OpenAI sale price relation is invalid OAI-PRICE-003 · v1.0.0 | optional | sale_price | Error When a sale price exists it must be greater than zero, below the regular price, and in the same currency. It is never silently replaced. Fix: Set a sale price below the regular price in the same currency, or remove it. | Official source 11 November 2026 |
Discovery flags (1)
Optional booleans that must be well-formed when present.
Rule | Requirement | Field | Reported when it fails | Source |
|---|---|---|---|---|
OpenAI is_eligible_search value is malformed OAI-SEARCH-001 · v1.0.0 | optional | is_eligible_search | Error Optional boolean; omitting it defaults to true and is not an error. A malformed supplied value is an error. Fix: Use true or false, or omit the field. | Official source 11 November 2026 |
Seller fields (1)
Optional enrichment that is never a base discovery blocker.
Rule | Requirement | Field | Reported when it fails | Source |
|---|---|---|---|---|
OpenAI seller_url is optional OAI-SELLER-001 · v1.0.0 | optional | seller_url | No action seller_url and other optional enrichment fields are never base discovery blockers. Fix: No action required. | Official source 11 November 2026 |
Variants (4)
Group identity, variant flags, variant_dict consistency and per-variant details.
Rule | Requirement | Field | Reported when it fails | Source |
|---|---|---|---|---|
OpenAI variant group identity is invalid OAI-VARIANT-001 · v1.0.0 | conditional | group_id | Error When a record belongs to a variant group, the group ID must differ from the item ID and stay stable. Fix: Give each variant its own item_id and a shared group_id that differs from every item_id. | Official source 11 November 2026 |
OpenAI variant flags or variant_dict are incomplete OAI-VARIANT-002 · v1.0.0 | conditional | — | Error When variants are represented, listing_has_variations must be true and variant_dict must be a non-empty object with stable option keys and values. Fix: Set listing_has_variations and provide variant_dict for every variant row. | Official source 11 November 2026 |
OpenAI variant_dict conflicts with top-level option values OAI-VARIANT-003 · v1.0.0 | conditional | — | Error variant_dict and the top-level color/size values must not conflict. Fix: Make variant_dict and the top-level option fields agree. | Official source 11 November 2026 |
Per-variant details are not variant-specific OAI-VARIANT-004 · v1.0.0 | recommended | — | Needs review Price, availability, URL and images should differ per variant where the variants differ, unless the feed proves they are identical. Fix: Check that each variant row carries its own price, availability, URL and images. | Official source 11 November 2026 |
Market context (1)
A standard upload serves the US market; extra markets need separate setup.
Rule | Requirement | Field | Reported when it fails | Source |
|---|---|---|---|---|
Standard OpenAI upload defaults to the US market OAI-MARKET-001 · v1.0.0 | informational | — | No action Extra market setup is required; global or multi-market support must not be inferred from target_countries or currency. Fix: No action required for a US upload; extra markets need separate setup. | Official source 11 November 2026 |
Out of scope (2)
Ads and Checkout are separate integration scopes and are not validated here.
Rule | Requirement | Field | Reported when it fails | Source |
|---|---|---|---|---|
OpenAI Ads fields are out of MVP scope OAI-ADS-001 · v1.0.0 | informational | — | Not applicable is_ads_eligible, Ads metadata and Ads-specific setup are not checked in this MVP. Fix: No action required. | Official source 11 November 2026 |
OpenAI Checkout fields are out of MVP scope OAI-CHECKOUT-001 · v1.0.0 | informational | — | Not applicable Checkout requires a separate enabled integration and onboarding; it is not checked in this MVP. Fix: No action required. | Official source 11 November 2026 |
Variant modeling, in one place
What the rules require when variants exist
Each variant row needs its own item_id; the shared group_id must differ from every item ID in the group and stay stable across uploads; listing_has_variations must be true; and variant_dict must be a non-empty object whose keys and values agree with the top-level option fields.
Where the checker stops
Whether two rows really are the same product is a merchandising decision. The checker flags grouping that is likely incomplete and per-variant details that look copy-pasted across variants, and asks for review rather than restructuring your catalog.
What this ruleset cannot evaluate
- Whether your account is approved for the file-upload onboarding path. That is an account relationship, not a data property.
- Whether a feed packaged as raw CSV will be accepted by a delivery workflow that expects SFTP plus compressed or Parquet files. This MVP is a preflight analyzer, not a packager.
- Whether additional markets are enabled. A standard upload serves the US; row-level target_countries does not activate another market.
- Whether the platform will ingest or display the items. There is no ingestion or approval signal available here.
Sources used by this ruleset
The Stable schema is a live specification. Each rule records its own source and last-verified date (11 November 2026 for this ruleset version), and a change in the published schema produces a new ruleset version rather than a silent edit.