Shopify offers.availability for AI shopping agents

An AI shopping agent will not surface a sold-out product. That's not a ranking heuristic — it's an existential trust rule. If ChatGPT recommends a product the user clicks through to buy and finds out-of-stock, ChatGPT loses that conversation; the user goes back to Google. So every AI agent that retrieves your catalog reads exactly one field to decide whether to even put you in the candidate set: offers.availability on your Product JSON-LD. The field has a strict shape — a schema.org vocabulary URL like https://schema.org/InStock — and most Shopify themes ship the wrong shape. The result is a 6-point hole in the score and, more importantly, a per-product surface where the agent has to guess. Agents that have to guess down-rank.

Last updated 2026-04-30 · Deep signal · 6 pts

What it is

The offers node on a schema.org Product represents a buy-able offer for that product — price, currency, condition, availability, who is selling it. The availability property carries a value from a fixed schema.org enumeration:

The "absolute URL" full-credit form is what schema.org documents and what every Google Rich Results Test example shows. Strict JSON-LD parsers — including the ones AI shopping agents run at retrieval time — treat the URL form as a stable, vocabulary-anchored value. The bare-name form ("availability": "InStock") is interpreted as a string rather than a vocabulary URI, and many strict parsers either reject it outright or downgrade their confidence in the offer node. Either way: half credit at best, half a point of trust at worst.

"offers": {
  "@type": "Offer",
  "price": "129.00",
  "priceCurrency": "USD",
  "availability":
    "https://schema.org/InStock",
  "url": "https://store.com/products/foo"
}

"offers": {
  "@type": "Offer",
  "price": "129.00",
  "priceCurrency": "USD",
  "availability": "InStock",
  "url": "https://store.com/products/foo"
}

"offers": {
  "@type": "Offer",
  "price": "129.00",
  "priceCurrency": "USD",
  "availability": true
}

"offers": {
  "@type": "Offer",
  "price": "129.00",
  "priceCurrency": "USD",
  "availability":
    "https://schema.org/InStock"
}
// ...but the variant is sold out

The fourth shape — a hardcoded InStock on a sold-out product — is technically the URL form (full-credit on the static parse) but fails the harder audit: agents that compare the JSON-LD claim against the live page state catch the lie and demote the store on the next crawl. In our launch scan we flag this as a separate alert ("availability emits InStock but rendered HTML shows Sold Out") even when the static signal scores 6/6.

Why AI shopping agents care

• Trust gate, not a ranking factor. An agent that recommends a sold-out product wastes the user's click and burns trust in the agent itself. Most AI shopping retrieval pipelines apply availability != OutOfStock as a hard filter before ranking. A missing or unparseable availability field gets treated conservatively — usually as "unknown, exclude" — which is functionally the same as "out of stock" for retrieval purposes.
• Parseable form keeps you in the candidate set. The schema.org URL form is what every major retrieval pipeline indexes deterministically. Bare-name strings work for Google's tolerant parser but fail strict ones; we have observed it bouncing between half-credit and zero on Bing's Copilot retrieval and on Perplexity's product-card extractor over the past 12 months.
• State-aware downstream signals. A truthful availability field lets the agent surface low-stock urgency, restock dates, and pre-order language correctly. A hardcoded InStock doesn't just lie; it costs you the marketing surface where "back in stock" or "ships in 3 weeks" can drive a purchase the agent would otherwise skip.
• Cross-channel consistency. Google Merchant Center, Shopify Global Catalog, and Meta product feeds all consume the same availability field via different ingestion paths. Get this one wrong and the bad shape replicates everywhere.

How to test it on your store

Open any PDP and view source. Find the <script type="application/ld+json"> block whose body contains "@type": "Product". Inside it, find the offers node, then the availability field.

Three things to verify:

1. The value is the absolute schema.org URL form — starts with https://schema.org/. The bare name ("InStock") is half-credit. Anything else is zero.
2. It tracks live inventory. Open one PDP for a product you know is in stock, one PDP for a product you know is sold out. Verify the JSON-LD reflects the correct state on each. Themes that wire availability to {% raw %}{% if product.available %}{% endraw %} get this for free; themes that hardcoded InStock in a snippet do not.
3. It validates in the Rich Results Test. Paste the PDP URL into Google's Rich Results Test. If you see a "Missing field 'availability'" or "Invalid value for field 'availability'" warning, you have a parseable problem.

How to fix it

"availability": "https://schema.org/{% raw %}{% if product.selected_or_first_available_variant.available %}InStock{% else %}OutOfStock{% endif %}{% endraw %}",

5 mistakes themes keep shipping