OpenAI product feeds

OpenAI Product Feed SFTP Guide

Publish a complete, current product catalog through a stable delivery process.

Prepare CMS Max catalog data for OpenAI, validate a representative sample, upload the full snapshot by SFTP, and replace the same file or shard set on a predictable schedule.

  • Full snapshot
  • Daily refresh
  • Stable path
  • UTF-8
  • Validated data
OpenAI product feed integration for CMS Max eCommerce
Current snapshot openai_products.parquet UTF-8 / complete catalog / stable filename
Ready
CMS Max catalog Validate Compress SFTP OpenAI ingest

Before the first upload

Collect the feed destination, catalog facts, and owners first.

OpenAI provides the destination and credentials for an approved feed connection. CMS Max helps organize the product data and repeatable export process that supplies it.

Connection details

Confirm the SFTP host, username, authentication method, remote directory, and expected filename supplied by OpenAI.

Current catalog data

Review product pages, image URLs, pricing, availability, seller details, policies, target countries, and eligibility.

Operational ownership

Assign who exports, validates, uploads, monitors failures, corrects source data, and confirms the next successful snapshot.

Delivery requirements

Build one dependable snapshot process around OpenAI's current file-upload rules.

The complete snapshot becomes the source of truth. Each successful refresh should replace the prior snapshot at the same path so the catalog does not fragment into dated copies.

Feed type
Complete product snapshot
Include every currently eligible item in each production refresh.
Cadence
At least daily
Refresh more often when price or availability changes demand it.
Delivery
SFTP
Use the host, credentials, and remote directory provided for the connection.
Preferred format
Parquet
Compressed JSONL, CSV, and TSV are also supported.
Encoding
UTF-8
Keep field names, values, delimiters, and escaping consistent.
File path
Stable filename
Overwrite the same latest snapshot instead of adding dated copies.
Large catalogs
Stable shard set
OpenAI recommends up to 500,000 items and roughly 500 MB per shard.
Launch sequence
Sample, full, automate
Validate about 100 items before moving to the complete production feed.

Product field map

Send stable identifiers, useful product facts, live commerce data, and clear eligibility.

The exact requirements depend on enabled experiences. Use the official stable product specification as the authority when building or changing the export.

Identity

Identify the product

item_id, title, description, url, and brand establish the durable record and customer-facing product.

Media

Show the actual item

image_url should resolve to a clear primary image. Supply optional additional media only when it accurately represents the product.

Commerce

Keep the offer current

price, availability, seller data, target countries, and fulfillment-related fields must match the live store.

Eligibility

Control where it can appear

Set is_eligible_search and is_eligible_checkout correctly. Ads use the separate is_ads_eligible field.

Seller

Represent the merchant

seller_name, seller_url, return_policy, and required policy URLs help connect the product to a responsible seller.

Governance

Follow conditional rules

Checkout, privacy, terms, regional, and category-specific requirements can add fields beyond the base product record.

Read the stable OpenAI product specification

SFTP upload pattern

Replace the current snapshot at the same remote path.

Use the authentication details provided for the connection. A private key is shown below as an example; the actual connection may use another supported authentication method.

sftp / feed upload
sftp -i /path/to/private_key username@sftp-host
cd /remote/path
put feed_snapshot.parquet feed_snapshot.parquet
ls -l
bye

Validation sequence

Prove the structure on a small sample before scheduling the full catalog.

  1. 01

    Check about 100 items

    Use a representative sample with variants, sale pricing, inventory states, images, policies, and different product categories.

  2. 02

    Correct source data

    Fix missing required fields, outdated field names, malformed values, inaccessible URLs, and inconsistent identifiers in CMS Max.

  3. 03

    Upload the full snapshot

    Export the complete eligible catalog using the validated structure and place it at the agreed SFTP path.

  4. 04

    Automate and monitor

    Schedule refreshes, retain delivery logs, review failures, and verify that the latest successful feed reflects the live catalog.

Catalog operations

Handle removals, Ads eligibility, and failures deliberately.

Removing products

Change the next full snapshot

Omit a discontinued product from the next complete snapshot or set is_eligible_search=false when it should no longer surface in search.

OpenAI Ads

Use the Ads eligibility field

Set is_ads_eligible=true for products intended to be eligible for Ads. Create the feed connection and obtain credentials in OpenAI Ads Manager. Eligibility does not guarantee serving.

Review OpenAI Ads feed guidance
Common failures

Correct the data, then resend

Look for missing required fields, unsupported or old field names, malformed prices or Booleans, broken product pages, inaccessible media, and changed shard names.

Implementation references

Use the live OpenAI specifications when the schema changes.

This guide explains the CMS Max workflow. OpenAI's documentation remains the authority for current field definitions, accepted formats, connection requirements, and program eligibility.

Product feed FAQ

Questions about OpenAI feed delivery.

Connection approval, credentials, ingestion results, and product eligibility are controlled by the relevant OpenAI program.

How often should an OpenAI product feed be uploaded?

OpenAI recommends refreshing the full snapshot at least daily. A merchant may need more frequent updates when price, inventory, or availability changes quickly.

Which product feed format should CMS Max export?

OpenAI prefers Parquet and also supports compressed JSONL, CSV, and TSV. Keep the feed UTF-8 encoded and follow the current stable product specification.

Should every upload use a new filename?

No. Use the stable filename or stable shard set assigned to the connection and replace the previous snapshot at the same path.

How should a discontinued product be removed?

Because the full snapshot is the source of truth, omit the product from the next snapshot or mark it ineligible for search according to the specification and intended workflow.

Does an OpenAI product feed automatically make products eligible for Ads?

No. Ads use a separate eligibility field and feed connection in OpenAI Ads Manager. A product marked eligible is still subject to OpenAI's review, policies, and serving decisions.

Can CMS Max help prepare and operate the feed?

CMS Max can help map catalog fields, prepare a representative sample, generate a complete snapshot, and design a repeatable export and SFTP process after the merchant receives an approved destination.

Operationalize the catalog

Connect the CMS Max product catalog to a feed process your team can repeat and monitor.

Plan the field mapping, export, validation, SFTP delivery, refresh schedule, failure handling, and catalog ownership together.

Building Relationships with Web Developers and Marketing Agencies that want better results

The world's fastest and most SEO friendly website code.