Shopify says in stock, Google Shopping shows sold out — the availability mismatch

Short answer. Shopify's live inventory and the availability Google holds are separate signals on separate schedules, so between feed updates Google works from a stale snapshot. Google also reads your product page directly, and may either correct the listing from your markup or disapprove the item when the two disagree. Its specification requires availability to match across three surfaces: the feed, the landing page and checkout.

Want to know if your store has this right now? Check my store, free 2 min · read-only

Open Shopify admin and a product shows plenty of inventory, ready to sell. Open Google Shopping and the same product shows "out of stock," greyed out, buried below every in-stock competitor, or it doesn't show at all. Nothing in Shopify is wrong. Shopify and Google Merchant Center are simply two separate systems reporting availability on two separate schedules, and when they drift apart, Shopify has no way to tell you.

The reverse happens just as often and is worse: Google still shows a product as in stock after it's actually sold out. Shoppers click an ad or a Shopping listing for an item that isn't there, land on a sold-out page, and bounce, and you've paid for or earned a click that could never convert.

Why Shopify and Google stop agreeing

Shopify's inventory count is authoritative and updates the instant a sale, a restock, or a manual edit happens. But Google Merchant Center doesn't read that count directly: it reads whatever your product feed tells it, and the feed is a separate pipeline with its own update cadence:

  • Scheduled fetches instead of live pushes. Some feed setups pull a fresh file on a fixed schedule (say, once every 12 or 24 hours) rather than pushing changes the moment inventory shifts. Between fetches, Google is working from a snapshot that's already stale.
  • Two feed sources disagreeing with each other. Stores that run both Shopify's native Google & YouTube channel app and a legacy or third-party feed app can end up submitting the same product twice, with the two apps reporting different availability for the same GTIN.
  • Structured data on the page contradicting the feed. Google cross-checks your feed's availability value against what it can verify on the live landing page, including the offers.availability field in your theme's JSON-LD. If a theme caches that value or a variant-level app updates the visible "Sold out" badge without touching the schema, the page and the feed tell Google two different stories.
  • Variant-level stock collapsed into a single product-level claim. Shopify's own structured_data filter documents that products are "output as a schema.org Product if they have no variants, and a ProductGroup if they have one or more variants", with the offer tied to one specific variant. Most themes hand-roll this block instead of calling the filter, so what your store declares for a product whose variants disagree is a decision your theme makes, not a guarantee Shopify gives you. We measured what 26 live storefronts do about it further down.

What Google does when the page and the feed disagree

The feed is not the only thing Google reads. Merchant Center runs a feature it calls automations, and its documentation names the source plainly: "We automatically read the structured data markup and other product data sources on your online store." Automations cover four attributes, price, sale price, availability and condition, and a store can switch them on for availability alone.

What happens next is the part most merchants are never told. Where the page and the feed conflict, Google may simply believe the page. Its own worked example takes a feed price of $4 against a page price of $3 and states that "we'll update the product to $3 USD in your ads or free listings." That is the benign outcome. The same page warns that "The product may be disapproved instead of updated if we detect a mismatch," and that "We may also stop updates if the total number of detected mismatches becomes too large." A store with enough drifting products can therefore lose the mechanism that had been quietly papering over the drift. How long Google takes to notice a change you have already made is a separate question, and we measured it in how long a Shopify product update takes to reach Google.

Reading nothing at all is not a neutral outcome either. Without usable markup Google falls back on what it calls advanced data extractors, and where those cannot settle price, availability or condition, "your products will be subject to product-level disapprovals."

There is also a third surface, and it is the one almost nobody checks. The product data specification asks you to "Match the availability listed in your product data with the availability listed on your landing page and checkout pages," and states that "The availability of all of your products needs to match across all three." Not two systems but three places: the feed, the product page, and what happens when a shopper actually tries to buy.

StoreCanary checks this on your store

Want to know whether your pages and your own stock agree right now? We read the offers.availability on your product pages and compare it with your store's own public catalogue. We flag a page that claims in stock while every variant is sold out, the reverse, a value that is not one Google accepts, and an offer that declares no availability at all: read-only, no admin access, about 2 minutes.

Scan my store for free

Why this is invisible in Shopify admin

Shopify admin only ever shows you Shopify's own view: current inventory, current variant status, current "Active" listing state. It has no visibility into what Google Merchant Center currently believes about that same product, because that belief lives entirely on Google's side, driven by a feed pipeline Shopify doesn't monitor after it hands the data off. A product can sit in Shopify admin looking perfectly healthy while its Merchant Center listing is quietly suppressed, disapproved, or showing the wrong stock state, and there is no notification for that gap inside Shopify itself. You only find out from Merchant Center's own reports, if you happen to check them.

The mismatch also runs the other way, and that direction is pure Shopify. Stock can sit in your admin while your storefront tells every shopper, and therefore every crawler, that the product is gone. Shopify documents this for multi-location stores: where the location holding the stock does not fulfil online orders, "that item is still displayed as out of stock to customers on your online store." Admin shows inventory, the page shows sold out, the markup follows the page, Google follows the markup, and no system anywhere raises an error. It is the same shape as a product that is live and sellable while Google has quietly stopped showing it, which we cover in why Shopify products vanish from Google's free listings.

One setting does the same thing in reverse. "Continue selling when out of stock" sits in the Inventory section of a product or variant and can only be chosen while inventory tracking is on. Leave it off and Shopify's rule applies: "An item is out of stock when inventory is tracked and the inventory level is at zero or below." In that state, "customers can't purchase an item until you adjust the inventory levels to add more stock." Switch it on and the variant stays sellable at zero, which is correct behaviour and a perfectly legitimate reason for a page to call itself in stock while the count reads nothing.

The four values Google accepts, and the two that need a date

Feed-side, availability takes one of four values, and the specification's definitions are narrower than the everyday words suggest. In stock means "You're accepting orders for this product and can fulfill the purchase request." It is a claim about fulfilment, not about a number in a box. Out of stock means "You're not accepting orders for this product, or the product isn't available for purchase." Preorder means "You're accepting orders for this product, but it's not been released for sale." Backorder means "The product isn't available at the moment, but you're accepting orders."

Preorder and backorder are the pair stores get wrong, because in ordinary speech they are interchangeable. Google draws the line on whether the product has ever been released. The preorder value "should only be used for new products that haven't been released yet," while "Existing products that are out of stock and will be back in stock at a later date" take backorder instead. Both carry an obligation most feeds miss. You must "Provide the availability date [availability_date] attribute if you submit [preorder] or [backorder] as the availability value," and that date is not a feed-only field: "This information should be visible on your landing page."

On the markup side the vocabulary is wider and the obligation is weaker. Google's merchant listing documentation accepts ten values for offers.availability, running from InStock and OutOfStock through BackOrder, PreOrder, PreSale, SoldOut, Discontinued, InStoreOnly, OnlineOnly and LimitedAvailability. It notes that "The short names without the URL prefix are also supported" and instructs you not to "specify more than one value" on a single offer. The property itself sits in the recommended table rather than the required one, which has a consequence worth stating out loud: a product page that declares no availability whatsoever is perfectly valid structured data, and it is also the page that hands Google's extractor nothing to work with. Which Search Console report surfaces a complaint about this property depends on how Google classified the page, a split we take apart in merchant listings versus product snippets, and the warnings themselves are catalogued in the structured data warnings reference.

What 26 live storefronts actually declare

Documentation tells you what should happen. To see which of these cases turns up in the wild we read the markup on live stores on 9 November 2026. Of 50 candidate domains, 17 were unreachable and 7 did not identify themselves as Shopify-served by response header, leaving 26 Shopify-served storefronts with a readable public catalogue. From each we took up to three products, picked so the sample deliberately contained the hard cases: one whose every variant was unavailable, one with some variants available and some not, and one fully in stock. That came to 55 product pages, every one returning HTTP 200.

Five of the 55, across three stores, carried no Product or ProductGroup block anywhere in the HTML the server sent us. That is not proof the markup is absent, only that it is not in the initial response, and a raw fetch is not evidence either way on a page that assembles itself in the browser. A block that is present but malformed is a third case again, and Google discards the whole of it silently: see unparsable structured data on Shopify. Seven further pages, across four stores, carried a product block that declared no availability at all, which the section above shows is valid markup rather than a defect.

Then the test that matters: does a page whose catalogue holds at least one unavailable variant ever declare itself unreservedly in stock? Twenty-seven pages met that condition and declared something. Exactly one of the 27 declared no out-of-stock value anywhere on the page, and its shape is the mechanism from the first section, caught in the act: a two-variant product with one variant gone, carrying a single Offer marked InStock, with neither a ProductGroup nor a hasVariant array to say anything about the variant that had sold out. The other 26 named the missing variant somewhere in their markup. Of the 16 pages whose variants disagreed with each other, 12 enumerated availability per variant rather than flattening it into one claim. Where a price rather than a stock state is the thing that disagrees, the mechanics and the fix are different enough to need their own page: see the price mismatch trap and the wrong price in Google.

The fully sold-out products came back cleanest of all. Of 14 products with no available variant left, 13 declared OutOfStock. The fourteenth declared PreOrder, which may be entirely accurate for something that has not shipped yet, and we did not try to second-guess that from the outside.

Read honestly, that cuts against the alarm this article could otherwise raise. On established storefronts of this kind the markup and the catalogue agree nearly everywhere, and the collapse case we set out to find turned up once in 27 opportunities. These are counts from one afternoon's sample rather than rates, and the population is the least likely one to show the defect: brands at this size have usually paid someone to get the theme right. It is good evidence about what themes declare, and weak evidence about how often this breaks across Shopify as a whole.

What it costs you

In-stock product showing as out of stock: a product your feed reports as unavailable is not offered to shoppers as buyable, so it effectively disappears from Shopping results even though it's fully sellable. You lose the impressions and the sale without any error being raised anywhere.

Out-of-stock product still showing as in stock: worse, because you're actively spending impressions, and often ad budget, sending shoppers to a product they can't buy. And the exposure runs past the wasted click. Google's misrepresentation policy lists among its unacceptable business practices "Listing items as available when you lack the capability to fulfill the orders". It then sends you straight to the attributes this article is about: "View the Product data specification attributes on availability and price for specific guidelines to comply with this policy." That policy is enforced at account level, and Google states that violations of this kind are suspended "upon detection and without prior warning": there is no warning stage to escalate through. We took that apart for Shopify stores in the misrepresentation suspension article.

How to check your own store

  1. In Merchant Center, open the Products page and then its "Needs attention" tab, which is the path Google documents today: "use the “Needs attention” tab in Merchant Center to diagnose any issues with your products." Filter for availability warnings to see which items Google currently believes are mismatched.
  2. Pick five of your currently out-of-stock products and view each one's page source: search for "availability" inside the JSON-LD block and confirm it says OutOfStock, not InStock.
  3. If you run more than one sales-channel or feed app connected to Google, check Merchant Center's Apps and Products tabs for duplicate submissions of the same item under different feed sources.
  4. Take one product whose variants do not all have stock and read its markup variant by variant. If the page carries a single Offer and no hasVariant array, it is making one claim for the whole product: confirm that claim is the one you want Google to act on.
  5. Walk the third surface. Add a sold-out variant to the cart and go as far as checkout, because the specification requires availability to "match across all three" and checkout is the one nobody looks at.
  6. Check how your feed actually updates, rather than assuming. Shopify documents only that the Google & YouTube channel "automatically syncs your products and relevant information about your Shopify store", with no stated frequency and no mention of inventory on that page. Read the app's own settings rather than trusting a remembered figure, and check any secondary feed app for a manual or scheduled sync that could run a day behind on fast-moving items.

This is the same category of failure as the redirect-to-homepage mismatch and the price mismatch trap we've covered separately: Merchant Center is comparing your feed's claims against the live reality of the page, and any gap between the two (price, landing page, or availability) gets treated as misrepresentation, not as a stock update.

The fix: one source of truth, pushed live

  • Use a single feed source. If you're running Shopify's native Google & YouTube channel alongside a separate feed app, pick one and disconnect the other: duplicate submissions are the most common cause of contradictory availability for the same product.
  • Confirm your feed pushes on inventory change rather than on a fixed schedule, especially for products that sell out quickly.
  • Keep theme JSON-LD in sync with real stock. This usually means confirming your theme (or the inventory app you use) actually updates offers.availability when a variant sells out, not just the visible "Sold out" label on the page.
  • Make the markup speak per variant. If one offer covers the whole product, a single sold-out size is invisible to Google. A theme that emits an offer per variant states the real position without you having to maintain anything.
  • Check the third surface, not just two. The specification asks for availability to agree across product data, landing page and checkout, and checkout is the one that never gets tested.
  • Date your preorders and backorders. The attribute is otherwise "Optional for each product" but "Required if you set the availability [availability] attribute to preorder or backorder," it exists to "tell customers when a preordered or backordered product will be shipped," and it may run "up to 1 year in the future." Google also asks for that date to be visible on the landing page, so a feed-only value leaves half the requirement unmet.
  • Re-check after any theme or app change. A theme update or a new inventory app is the single most common moment this drifts, since it's exactly when the code that writes the schema gets touched.

Is this happening on your store right now?

Merchant Center will not tell you until it disapproves a listing. The product is live in your store, and Google Shopping is showing a different price, the wrong availability, or nothing at all. The only way to know is to check the feed the way Google reads it.

  • 90+ checks, the way Google reads your product feed. Price and availability mismatches, missing identifiers, redirect chains.
  • Read-only. No app to install, no admin access, nothing changes on your store.
  • The exact fix for each page, in plain English, so you or your developer can act the same day.

Across full-catalog scans of more than 90,000 Shopify product pages, about 1 in 4 stores had at least one critical Google visibility issue.

Scan my store for free

Free scan: issue types, counts and first fixes. Full report on every product page, not a sample: $49 once, no subscription.

Next in this cluster