A displayed price alone is not enough to inform a customer or an agent correctly: it must match the variant that can actually be purchased, in the relevant market, with clear availability information and a realistic delivery estimate. The OpenAI product feed specification defines formats for price and availability, but those format constraints never guarantee that a product will be shown or recommended.
Price, stock and delivery share the same potential weakness: they may be managed by different systems (catalog, ERP, logistics) that synchronize with a delay. That delay remains invisible until someone compares the displayed page with the source that should govern it. Without a usable timestamp, a displayed value cannot tell you when its source last synchronized.
What feed specifications require, without guaranteeing an outcome
OpenAI’s product feed specification illustrates the distinction between a format constraint and a promise of results. The availability field accepts only five values (in_stock, out_of_stock, pre_order, backorder, unknown). The price must be a positive amount accompanied by a three-letter currency code, and a sale price must be lower than the regular price, in the same currency. The fields available depend on the integration format: do not transfer columns from a Google-compatible feed into the standard OpenAI format. The documentation states that a format constraint does not guarantee that every invalid value will be rejected. Check the data before submission, then review the errors actually returned.
The table to maintain for each variant
| Item | Expected source of truth | Visible check | Limitation to note |
|---|---|---|---|
| Price | Merchant catalog or ERP | Active variant on the product page | Promotions, markets and currencies must be checked separately |
| Availability | Inventory system | Actual add-to-cart behavior | Stock can change between two readings taken close together |
| Delivery time | Logistics policy and carrier | Estimate displayed before payment | Geographic or product-specific exceptions may apply |
Four common mistakes to fix first
- Displaying the parent product’s price when the variant selected by the customer has a different price.
- Omitting the availability date when the format accepted by your integration requires it, particularly for preorders and backorders in the Google-compatible section.
- Leaving a promotion visible without clearly readable conditions (end date, relevant market, eligible variant).
- Confusing “in stock” with “fast delivery”: these are two distinct pieces of information, with different sources and update schedules.
Why an organizational fix matters more than a one-off correction
Correcting an isolated product page treats a symptom. The most useful fix is to designate a single source of truth for each type of data and a person responsible for approving exceptions (temporary stockouts, seasonal products, restricted markets). An AI-generated answer, an advertisement or a discovery interface must never become the source of truth for a price: they merely reflect, with an unknown delay, what they have read elsewhere. When there is a discrepancy, correct the source data and then verify the channel’s synchronization: a correct value in the admin interface does not prove that it was received correctly.