AI shopping assistants now answer questions like "waterproof hiking boots under $150, in stock near me." They choose products from structured data. If your catalog is messy or out of date, the agent has little to work with.
Three efforts are pushing catalog data toward a common shape:
The details differ by protocol, and some checkout features are limited to approved partners. The data work underneath is the same for all of them.
OpenAI's spec asks for nine fields on every item or variant: item_id, title, description, url, brand, seller_name, image_url, availability and price. Optional fields cover variants, attributes, shipping and returns. Treat the nine as your minimum for every feed, whichever platform you target.
Example feed row (JSON for readability):
{
"item_id": "BOOT-TRAIL-42-BLK",
"title": "TrailMaster Waterproof Hiking Boot, Black, EU 42",
"description": "Leather hiking boot with a waterproof membrane and Vibram sole.",
"url": "https://example.com/products/trailmaster-black-42",
"brand": "TrailMaster",
"seller_name": "Example Outfitters",
"image_url": "https://example.com/img/trailmaster-black.jpg",
"availability": "in_stock",
"price": "129.00 USD"
}
Check the current spec for exact value formats before you publish. Accepted values for fields such as availability and price can change.
Agents compare concrete items. A boot sold in five sizes and three colors is fifteen items, each with its own ID, price and stock count. Put the color and size in the title and in structured attributes. A single listing with a "choose a size" dropdown tells an agent nothing about what is in stock.
Format errors are easy to make:
490.00 and EUR). Strings like "490,00 € all included" break parsers.https://schema.org/InStock.Agents and crawlers also read your product pages. Your page markup has to agree with your feed, because mismatches get flagged.
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Product",
"name": "TrailMaster Waterproof Hiking Boot, Black, EU 42",
"sku": "BOOT-TRAIL-42-BLK",
"gtin13": "0123456789012",
"brand": { "@type": "Brand", "name": "TrailMaster" },
"image": "https://example.com/img/trailmaster-black.jpg",
"offers": {
"@type": "Offer",
"price": "129.00",
"priceCurrency": "USD",
"availability": "https://schema.org/InStock",
"url": "https://example.com/products/trailmaster-black-42"
}
}
</script>
Generate this from the same source as the feed. Two hand-maintained copies will drift apart.
Stale stock data sends shoppers to products they can't buy. The platform receives the feed you push, so you control how current it is.
Being in a feed makes you eligible for discovery. Checkout inside an assistant is a separate integration, and for some platforms it is limited to approved partners. Start with clean data, then apply to the checkout programs that fit your stack.
Specs in this area are changing quickly. Check the official documentation from OpenAI and Google for current field names and eligibility before you implement.