Product price is the required feed attribute in a ChatGPT Ads product feed that states what a shopper pays, carried as a value plus currency so ChatGPT shows accurate pricing in shopping results and sponsored cards. It is the structured price in your catalog, separate from price text, the string that renders inside the ad creative.
If you sell in ChatGPT, product price decides whether your item surfaces for budget-bound questions like a gift under $100 and whether the shown price matches checkout. Send a stale or wrong price and OpenAI can flag the row, drop it from eligibility, or show an old figure that erodes trust when someone clicks.
In a ChatGPT Ads product feed, the product price attribute records what a shopper pays for one item, expressed as a numeric value and an ISO 4217 currency code. OpenAI treats it as a required field, so a row missing a valid price cannot appear in ChatGPT shopping results or product feed ads. Because the merchant pushes the feed instead of letting ChatGPT crawl it, the price you submit is the price the system trusts and shows.
The attribute is one value in the feed's required set, which also covers the item identifier, title, description, link, image, availability, brand, and seller name. Price sits next to optional pricing fields such as sale price with start and end dates, so promotions stay structured. The value must match the live price on your landing page, because OpenAI reconciles the two and surfaces the lowest price it can confirm.
Product price is a catalog input, separate from price text on the ad card and from the bid and budget that set what you pay OpenAI. AirOps keeps feed values like price aligned with the organic answers you compete in.
Product price moves through the feed pipeline the same way every other attribute does, but it carries extra weight because shoppers and OpenAI both check it against your live page.
Set the value: Enter the price as a number plus its currency in the product feed, matching the amount on your live product page.
Submit the feed: Push the feed to OpenAI's endpoint; validation checks each row, and any with a missing or malformed price is rejected.
Reconcile: OpenAI compares your feed price with the price on the crawlable landing page and resolves the lowest confirmed figure.
Display: ChatGPT renders the price inside shopping results and sponsored product cards when a conversation shows buying intent.
Refresh: You resend updated prices frequently so sales, repricing, and currency changes stay current across surfaces.
The displayed price tells you what a shopper will see before they click, and whether your item clears a stated budget. It does not tell you whether you won the placement, since bids, budgets, and relevance decide that separately.
Resources: Read AirOps' best practices for targeting, creative, and policy in ChatGPT ads
Product price is where your catalog meets a shopper who has already named a budget, so it directly shapes whether ChatGPT puts your item in front of a ready buyer. Get it wrong and the cost compounds: your item can drop out of eligibility, or it shows a figure that breaks trust at the moment of decision, right before checkout.
Eligibility gate: A row without a valid price cannot serve at all, so a feed error silently removes products from both shopping results and sponsored cards, often without an obvious error message.
Budget matching: Conversational shoppers state ceilings like "under $50," and an accurate price is what lets ChatGPT include or exclude your item against that constraint.
Trust at click: When the price in the answer matches checkout, buyers convert; when it lags your repricing, they bounce and your spend is wasted on a dead click.
Ecommerce managers use product price to keep the figure in their ChatGPT feed matched to live checkout so sponsored cards never show a stale amount.
Growth marketers use product price to qualify which SKUs surface for budget-bound prompts and concentrate spend on items shoppers can afford.
Performance marketers use product price alongside sale price to push structured promotions into ChatGPT without rewriting ad copy.
A valid product price is always two parts, a numeric amount and an ISO 4217 currency code, and ChatGPT treats a price without a clear currency as incomplete, which can hold the row back from accurate international display.
The price in your feed has to match the price a shopper finds on the landing page, because OpenAI cross-checks the two and will favor or surface the lowest figure it can confirm, so a mismatch can quietly suppress or reprice your listing.
Promotions belong in dedicated sale price fields with start and end dates, so the discount is structured data ChatGPT can read instead of text hidden in the title or description, where the model is far less likely to act on it.
Surface your item for budget-specific prompts inside ChatGPT shopping and sponsored cards.
Keep the displayed figure matched to checkout so buyers do not abandon on a price gap.
Push promotions through structured sale price fields without rewriting a single line of ad copy.
Protect eligibility by giving every row a valid value plus currency.
Compete on current pricing by refreshing the feed as often as you reprice.
Match the feed price to your live landing page exactly, because OpenAI reconciles the two and trust depends on it.
Include the currency code on every row, so international surfaces can display and qualify your item.
Use dedicated sale price fields with start and end dates for promotions, keeping discounts machine-readable.
Refresh pricing frequently, since stale values invite rejected rows and wrong figures on live cards.
Validate new rows before launch, because a missing or malformed price quietly blocks eligibility.
Keep product price consistent with any price text on the creative, so the card and the catalog tell one story.
Avoid treating price as a set-and-forget field. Competent teams load a catalog once and move on, then a seasonal repricing or a currency shift leaves ChatGPT showing a figure that no longer matches checkout, and the gap only shows up as lost conversions.
AirOps: Connects your ChatGPT Ads account and brand data so feed values like product price stay aligned with the organic answers you compete in.
OpenAI Ads Manager: The native interface where you create the product feed, run validation, and launch product feed campaigns that read your price attribute.
Google Merchant Center: Maintains the Google Shopping-format catalog, including price and currency, that maps directly into the ChatGPT feed.
Audit your prices: This week, pull your existing Google Shopping or store catalog and confirm every item has a current value and a currency code. No budget approval needed. A clean starting list makes every later step faster.
Fix parity gaps: Compare each feed price against the live landing page and correct any mismatches in your catalog source so the fix sticks.
Structure promotions: Move active discounts into dedicated sale price fields with start and end dates so they read as data. Discounts hidden in the title are easy for the model to miss.
Validate and submit: Push a sample feed to OpenAI, clear any rows flagged for missing or malformed prices, then upload the full catalog. Fixing them at the source keeps the row eligible.
Automate refreshes: Schedule frequent feed updates so repricing, sales, and currency changes reach ChatGPT before a shopper sees an old figure.
Product price is the required ChatGPT Ads feed attribute that states what a shopper pays, as a value plus a currency.
You set it in the product feed and refresh it often so the displayed figure tracks your real pricing.
It only works when the feed price matches your live landing page, because OpenAI reconciles the two.
A missing, stale, or wrong price pulls the item from eligibility or shows a figure that breaks trust.
The biggest gains come from automating refreshes and structuring promotions as sale price fields.
Product price and price text answer two different needs. Product price is the structured value in your product feed, a number plus a currency code that OpenAI uses to decide eligibility, match budget-bound prompts, and reconcile against your landing page. Price text is the human-readable string that appears on the ad card, the phrasing a shopper actually reads. One is catalog data the system reasons over; the other is display copy. In practice you want them consistent: if your feed says the item costs forty dollars but the creative shows a crossed-out higher number, the mismatch confuses shoppers and can undercut trust at the click. Keep the authoritative amount in the product price attribute, let OpenAI pull from it, and treat price text as presentation that should never contradict the figure the feed reports. When the two align, your card reads cleanly and your listing stays eligible to serve.
Update product price whenever your real price changes, and run it on an automated schedule instead of by-hand edits. ChatGPT reads the price from the feed you push, so the figure a shopper sees is only as current as your last submission. OpenAI accepts frequent refreshes, so high-velocity catalogs with daily repricing, flash sales, or currency swings should sync many times a day; a slow-moving catalog can refresh less often but should still send at least a daily snapshot. The practical test is simple: if a price could change between now and tomorrow, your update cadence needs to be faster than that change. Tie the feed to the same system that controls your store pricing, so a change in one place propagates automatically. Manual uploads drift the moment someone forgets, and a stale price is what triggers rejected rows and lost trust on live cards.
The product price ChatGPT shows can differ from your site for a few concrete reasons. First, ChatGPT displays the price from the last feed you pushed, so if your site repriced after that submission, the answer lags until your next refresh. Second, OpenAI reconciles your feed against the crawlable landing page and tends to surface the lowest price it can confirm, so a promotion live on your site but absent from the feed can produce a gap. Third, currency and regional display can change how the figure renders for different shoppers. Fourth, caching means a very recent change may not propagate instantly across every surface. None of this is random: each cause traces back to a timing or parity difference between what your feed states and what your page shows. Closing the gap means tightening refresh cadence and keeping feed and page prices in lockstep.
Yes, you control product price directly, with one important limit. The value you put in the feed is authoritative, so whatever amount and currency you submit is what OpenAI reads and displays in shopping results and sponsored cards. That is real, direct control that crawl-only setups do not give you. The limit is that OpenAI still reconciles your feed against your public landing page and favors the lowest confirmed price, so you cannot show one figure in the feed and a different, higher one on your site and expect the feed number to win. You also cannot force a placement by pricing alone, because bids, budgets, relevance, and policy decide whether your card serves. What you can do is keep the price accurate, current, and consistent with your page, structure discounts in sale price fields, and refresh often. Do that and the price shoppers see is the price you intend.
A good product price setup is less about the number itself and more about accuracy, freshness, and parity. Every row carries a valid value and currency, so nothing drops out of eligibility on a technicality. The feed price matches the live landing page, so OpenAI's reconciliation never surfaces a surprise figure. Promotions run through dedicated sale price fields with start and end dates, so discounts are read as structured data. Refreshes are automated and frequent enough that a shopper never sees yesterday's price on a card. And the feed value stays consistent with any price text on the creative. If you want a single benchmark, aim for zero rows rejected for price issues and zero visible gaps between the card price and checkout. Hitting that consistently matters more than any particular price point, because it is what keeps your listings both eligible and trusted.