How often should you update a ChatGPT Ads product feed?

Choose an update cadence based on how quickly your catalog changes, and verify that each update reaches its destination. A recent local scan is not evidence of a recent successful delivery.

Published: 2026-09-17 · Updated: 2026-09-19

Check the current feed

Specification review: September 19, 2026

OpenAI native and Google-compatible feeds have separate availability, identity and eligibility rules. Check the detected mode; XML is not a Google-compatible upload format. Refresh products within 14 days and promptly after price or stock changes.

Crawler access requires manual verification. Schema.org 30.1 additions are optional opportunities with no score impact; page structured data is not scanned. Read the versioned scope and limitations.

What the current documentation says

OpenAI's product-feed campaign guide says items expire after two weeks and recommends hosted delivery or automated SFTP. Do not use that expiry window as a target for stale prices or stock.

Sources: OpenAI: campaigns from product feeds

Prices and availability

Our operational recommendation: update the source when commercial facts change and verify propagation. Record the time of the change, exporter completion and destination acceptance. Choose a frequency that reflects stock turnover rather than assuming one daily run is sufficient for every store.

Catalog additions, removals and other changes

The Advertiser API guide separates supported existing-item deltas from full catalog uploads. It lists title, price and availability deltas; new products and other field changes use an updated catalog. Consult the destination's own removal behavior instead of assuming omission immediately removes an item.

Sources: OpenAI: product-feed setup and updates

Hosted feed versus manual upload

For a manual workflow, name a backup operator and record each upload. For automation, monitor both exporter completion and destination processing. A healthy HTTPS endpoint can serve an old file, while a newly generated file can fail delivery.

What source monitoring can establish

Product Feed Scan monitoring compares scheduled source audits when enabled for your account. It does not upload to OpenAI or measure destination refresh. Monitoring is not publicly enabled for every visitor; a manual source scan remains available.

Practical checklist

Define an owner and acceptable delay for each type of change.
Record a baseline source count and score.
Check after price/stock changes and catalog releases.
Review exporter failures and destination diagnostics separately.
Use available source monitoring or schedule manual audits.

Choose the next check

Independent source analysis. No OpenAI or Google approval, delivery integration or visibility guarantee. A free scan shows priority findings; the complete private report costs €19 once and remains available for 30 days.