Shopify product availability states for AI shopping agents: the complete guide to InStock, PreOrder, BackOrder, LimitedAvailability, and Discontinued

Why availability is the first filter, not an afterthought

AI shopping agents are recommendation engines that stake their credibility on every citation. Recommending a product that turns out to be unavailable damages the agent's trust with users — and agents don't repeat that mistake. ChatGPT Shopping, Perplexity Commerce, and Google AI Mode all apply availability verification before generating recommendations, which means availability state is an entry gate, not a ranking signal.

The filtering sequence typically works like this:

1. Crawl: the agent's crawler reads your Product JSON-LD and stores the availability value from each Offer
2. Filter: when a user query triggers a product lookup, the agent filters to purchasable states: InStock, BackOrder, LimitedAvailability, PreOrder (if the query allows for future delivery)
3. Rank: within purchasable products, agents rank by relevance, price, trust signals, and review quality
4. Cite: only products that passed the availability filter appear in recommendations

OutOfStock and Discontinued products are filtered out at step 2. If your in-stock products output InStock but your backordered or pre-order products also output InStock, you're not being excluded — but you're corrupting the signal. When an agent crawls your store and later discovers the "InStock" product wasn't available, that mismatch erodes confidence in your catalog signal quality overall.

The 7 schema.org availability values and when to use each

The most consequential distinction is between BackOrder and OutOfStock. BackOrder means "you can buy this now, it will ship when stock returns." OutOfStock means "you cannot buy this right now." AI agents include BackOrder in purchasable recommendations; OutOfStock is excluded. This is why backordered products on Shopify stores that use "continue selling when out of stock" should output BackOrder, not OutOfStock — and definitely not InStock.

Why Shopify's default JSON-LD outputs the wrong state

Shopify's default Product JSON-LD (generated by most themes using Dawn's approach) maps availability using a single condition:

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

product.available is a Shopify Liquid boolean that returns true if any variant can be purchased — which covers three distinct scenarios that require different schema.org values:

The root cause is that product.available conflates three distinct purchase states (ready-to-ship, purchasable-with-delay, pre-order) into a single boolean. Shopify's Liquid API has the granular properties needed to distinguish them — the default theme just doesn't use them.

The master Liquid snippet for correct availability mapping

This snippet reads Shopify's inventory signals at the variant level (not just product.available) and outputs the correct schema.org availability value. Replace the availability line in your sections/main-product.liquid JSON-LD block:

{% comment %}--- Availability mapping ---{% endcomment %}
{% assign av_variant = product.selected_or_first_available_variant %}
{% assign av_url = 'https://schema.org/OutOfStock' %}

{% if product.tags contains 'pre-order' or product.tags contains 'preorder' %}
  {% assign av_url = 'https://schema.org/PreOrder' %}
{% elsif product.tags contains 'discontinued' or product.tags contains 'archived' %}
  {% assign av_url = 'https://schema.org/Discontinued' %}
{% elsif av_variant != blank %}
  {% if av_variant.inventory_management == blank %}
    {% comment %}No inventory tracking — assume InStock{% endcomment %}
    {% assign av_url = 'https://schema.org/InStock' %}
  {% elsif av_variant.inventory_quantity > 0 %}
    {% if av_variant.inventory_quantity < 5 %}
      {% assign av_url = 'https://schema.org/LimitedAvailability' %}
    {% else %}
      {% assign av_url = 'https://schema.org/InStock' %}
    {% endif %}
  {% elsif av_variant.inventory_policy == 'continue' %}
    {% comment %}Continue selling when OOS = BackOrder{% endcomment %}
    {% assign av_url = 'https://schema.org/BackOrder' %}
  {% else %}
    {% assign av_url = 'https://schema.org/OutOfStock' %}
  {% endif %}
{% endif %}

{% comment %}Use {{ av_url }} in your Offer JSON-LD:{% endcomment %}
{% comment %}"availability": "{{ av_url }}"{% endcomment %}

Key decisions encoded in this snippet:

• Tag-first routing: pre-order and discontinued tags override inventory state, because Shopify inventory for pre-order products is often set to "continue selling" which would otherwise map to BackOrder.
• LimitedAvailability threshold of 5: adjust this to your category norm. For luxury goods, 5 might be the right threshold. For commodity products with 1,000-unit runs, you might set it at 3 or even 2. The goal is to signal genuine scarcity, not create false urgency.
• No inventory management → InStock: products without inventory tracking in Shopify are typically print-on-demand, digital, or always-in-stock items. InStock is the safest default.

Per-state JSON-LD patterns with full examples

{
  "@type": "Offer",
  "url": "https://yourstore.com/products/your-product",
  "priceCurrency": "USD",
  "price": "49.00",
  "availability": "https://schema.org/InStock",
  "itemCondition": "https://schema.org/NewCondition",
  "seller": { "@type": "Organization", "name": "Your Store" }
}

{
  "@type": "Offer",
  "url": "https://yourstore.com/products/your-product",
  "priceCurrency": "USD",
  "price": "49.00",
  "availability": "https://schema.org/LimitedAvailability",
  "inventoryLevel": {
    "@type": "QuantitativeValue",
    "value": {{ av_variant.inventory_quantity }},
    "unitCode": "EA"
  },
  "itemCondition": "https://schema.org/NewCondition"
}

{
  "@type": "Offer",
  "url": "https://yourstore.com/products/your-product",
  "priceCurrency": "USD",
  "price": "89.00",
  "availability": "https://schema.org/PreOrder",
  "availabilityStarts": "{{ product.metafields.preorder.ship_date | date: '%Y-%m-%d' }}",
  "additionalProperty": [
    {
      "@type": "PropertyValue",
      "name": "preorderDeposit",
      "value": "{{ product.metafields.preorder.deposit_amount | money_without_currency }}"
    },
    {
      "@type": "PropertyValue",
      "name": "estimatedDelivery",
      "value": "{{ product.metafields.preorder.ship_date | date: '%B %Y' }}"
    }
  ],
  "itemCondition": "https://schema.org/NewCondition"
}

{
  "@type": "Offer",
  "url": "https://yourstore.com/products/your-product",
  "priceCurrency": "USD",
  "price": "49.00",
  "availability": "https://schema.org/BackOrder",
  {% if product.metafields.inventory.restock_date != blank %}
  "availabilityStarts": "{{ product.metafields.inventory.restock_date | date: '%Y-%m-%d' }}",
  {% endif %}
  "additionalProperty": {
    "@type": "PropertyValue",
    "name": "backorderNote",
    "value": "Ships when restocked — order secured at current price"
  },
  "itemCondition": "https://schema.org/NewCondition"
}

<!-- In <head> of the product page -->
<meta name="robots" content="noindex,follow">

{
  "@type": "Offer",
  "url": "https://yourstore.com/products/discontinued-product",
  "availability": "https://schema.org/Discontinued",
  "additionalProperty": {
    "@type": "PropertyValue",
    "name": "discontinuedReason",
    "value": "Product line ended — see current alternatives"
  }
}

Multi-location inventory: when availability varies by store

Shopify's multi-location inventory is one of the more complex availability scenarios for structured data. When a product is InStock at your Los Angeles warehouse but OutOfStock at your New York warehouse, what does the schema.org availability value say?

The standard approach is to use the aggregate availability: if any location can fulfill the order, the Offer availability is InStock or LimitedAvailability. The location-level detail is expressed through shippingDetails and, for BOPIS (Buy Online Pick Up In Store) scenarios, through availableAtOrFrom pointing to the fulfilling location.

{
  "@type": "Offer",
  "availability": "https://schema.org/InStock",
  "availableAtOrFrom": {
    "@type": "Place",
    "name": "CatalogScan Store — Los Angeles",
    "address": {
      "@type": "PostalAddress",
      "addressLocality": "Los Angeles",
      "addressRegion": "CA",
      "addressCountry": "US"
    }
  },
  "shippingDetails": {
    "@type": "OfferShippingDetails",
    "shippingDestination": {
      "@type": "DefinedRegion",
      "addressCountry": "US"
    },
    "deliveryTime": {
      "@type": "ShippingDeliveryTime",
      "handlingTime": { "@type": "QuantitativeValue", "minValue": 1, "maxValue": 2, "unitCode": "DAY" },
      "transitTime": { "@type": "QuantitativeValue", "minValue": 2, "maxValue": 5, "unitCode": "DAY" }
    }
  }
}

For stores with Shopify POS + online inventory, where some products are in-store only, use InStoreOnly combined with availableAtOrFrom pointing to your physical location. AI shopping agents treat InStoreOnly as a purchasable state for users willing to pick up — Perplexity Commerce and Google AI Mode both surface InStoreOnly products in local product queries.

Availability state and offerCount: why it affects recommendation slots

AI shopping agents don't just read the primary Offer's availability — they assess the offer array's overall quality. A product with a single Offer that's InStock is simpler to recommend than a product with a ProductGroup of 12 variants where 10 are OutOfStock and 2 are InStock. When the ratio of unavailable-to-available offers is high, agents may deprioritize the product in favor of cleaner catalog entries.

The practical implication: for products with high variant counts and mixed availability, include only currently purchasable variants in your primary Offer array. You can structure this in Liquid:

"offers": [
  {% for variant in product.variants %}
    {% unless forloop.first %},{% endunless %}
    {% assign v_av = '' %}
    {% if variant.available %}
      {% if variant.inventory_quantity < 5 and variant.inventory_management != blank %}
        {% assign v_av = 'https://schema.org/LimitedAvailability' %}
      {% else %}
        {% assign v_av = 'https://schema.org/InStock' %}
      {% endif %}
    {% elsif variant.inventory_policy == 'continue' %}
      {% assign v_av = 'https://schema.org/BackOrder' %}
    {% else %}
      {% assign v_av = 'https://schema.org/OutOfStock' %}
    {% endif %}
    {
      "@type": "Offer",
      "sku": "{{ variant.sku }}",
      "name": "{{ variant.title | escape }}",
      "price": "{{ variant.price | money_without_currency }}",
      "priceCurrency": "{{ shop.currency }}",
      "availability": "{{ v_av }}",
      "url": "{{ shop.url }}/products/{{ product.handle }}?variant={{ variant.id }}"
    }
  {% endfor %}
]

This outputs per-variant availability across the entire variant array — giving AI agents a complete picture of which sizes, colors, or configurations are actually available. See the ProductGroup JSON-LD guide for how to wire this into the ProductGroup.hasVariant pattern for maximum variant visibility.

5 common availability schema mistakes

FAQ