Feed and data quality

What does Availability mismatch mean in Google Merchant Center?

Availability mismatch issues usually mean the submitted availability and the visible product-page availability are out of sync.

What it means

The feed may say a product is in stock while the page suggests otherwise, or the page may use variant or preorder logic that Google reads differently than the feed does.

How FeedIQO helps monitor it

FeedIQO helps teams see which products are affected, track recurring mismatch patterns, and attach fix notes to the issue group that caused the drift.

Fix workflow

Use a structured check, fix, and follow-up process

These lists are meant to keep the page useful without pretending the same fix works for every store.

Common causes

  • Inventory sync timing is delayed
  • Variant defaults do not match the submitted offer state
  • Preorder or backorder messaging is not reflected in the feed logic

How to check it

  • Compare the live product page message to the submitted availability value
  • Test how variant selection changes availability on the landing page
  • Review recent inventory app or sync changes

How to fix it

  • Align the inventory source of truth used by the feed
  • Make the shopper-visible availability unambiguous on page load
  • Recheck the issue after the next inventory and feed sync cycle
Related resources

Keep moving through the Merchant Center workflow

These links connect the error explanation to the feed, disapproval, and health-check workflows that usually matter next.

Related guides

Price Mismatch

See a closely related Merchant Center issue or glossary page.

Price Mismatch

Landing Page Not Available

See a closely related Merchant Center issue or glossary page.

Landing Page Not Available

Product Url Mismatch

See a closely related Merchant Center issue or glossary page.

Product Url Mismatch

Related tools

Free product feed audit

Request a manual audit when error patterns point back to feed quality.

Free product feed audit

Related features

Product feed audit

Review the feed workflow that often sits underneath Merchant Center errors.

Product feed audit

Product disapproval monitoring

Track product-level consequences when the error affects approvals.

Product disapproval monitoring

Merchant Center health checker

See how this error type fits into the broader account health picture.

Merchant Center health checker
FAQ

Questions teams usually ask about this issue

The answers stay general on purpose because Google can evaluate different stores and catalogs differently.

FAQ

Yes. Variant defaults and dynamic inventory messaging are common reasons Google sees a different availability state than the one submitted.

No. Repeated mismatch issues also create a trust problem because they suggest the product data is not stable.