Google Merchant Center Availability Mismatch: How to Fix It
Google Merchant Center Availability Mismatch: How to Fix It
Your Google Merchant Center product says:
In stock
but your website says:
Sold out.
Or the opposite happens:
Your product is available to buy, but Google still treats it as out of stock.
This is an availability mismatch, and it is usually a sign that different parts of your product-data system are telling Google different stories.
The problem may come from:
your submitted product data
your product landing page
structured data
the selected variant
checkout availability
inventory synchronization
preorder or backorder settings
or simple timing differences between updates
Before changing your entire catalog, work through these checks first.
What Does “Availability Mismatch” Mean?
Google Merchant Center uses the availability attribute to understand whether a product can currently be purchased.
The main values include:
in_stock
out_of_stock
preorder
backorder
The important part is not simply choosing one of these values.
The information submitted to Google should agree with what a shopper actually experiences on your website.
For example:
Product data
in_stock
Product page
Out of stock
Those two signals conflict.
But availability problems can also be much less obvious.
Your visible page might say “In stock” while your structured data still contains OutOfStock.
Or the product itself may be available while the specific size selected by the URL is sold out.
That is why availability troubleshooting should look at the entire product path.
1. Check the Availability Submitted to Google
Start with the product inside Merchant Center.
Record:
product ID
submitted availability
product URL
variant information
last update time
Then open the exact product URL.
Ask a simple question:
Can a normal customer actually purchase this exact product right now?
If Merchant Center says:
in_stock
but the website does not allow the customer to buy the item, something is wrong.
Similarly, if Google receives:
out_of_stock
while the item can clearly be purchased, your submitted product data may be stale.
The first comparison should therefore be:
Merchant Center availability ↔ website availability
2. Check the Exact Product Variant
Variants are one of the easiest ways to create an availability mismatch.
Imagine a shoe with these sizes:
Size 8 — In stock
Size 9 — In stock
Size 10 — In stock
Size 11 — Out of stock
Your product data describes:
Size 11
but the landing page automatically opens:
Size 9
A customer looking at the page may think everything is fine because Size 9 can be purchased.
But the offer Google is evaluating may actually represent Size 11.
This means you need to ask:
Is this product available?
and also:
Is this exact variant available?
Those are not always the same question.
Whenever possible, make sure your submitted URL and product attributes identify the correct:
size
color
material
model
configuration
pack quantity
capacity
A variant mismatch can easily appear to be an inventory problem.
3. Check the Structured Data
Just like price, availability can exist inside the machine-readable data of your product page.
A page might visually display:
In stock
while its structured data contains something equivalent to:
OutOfStock
A normal visitor will probably never notice.
Google can.
Product structured data commonly contains an Offer with availability information.
For example, machine-readable availability may represent:
InStock
OutOfStock
PreOrder
BackOrder
The important thing is consistency.
Compare:
Submitted availability
↓
Visible page availability
↓
Structured-data availability
These signals should describe the same purchasing situation.
4. Check Whether Inventory Changed Recently
Sometimes there is no complicated technical error.
Your systems are simply updating at different times.
For example:
9:00 AM
Your product has 1 unit remaining.
Website: In stock
Product data: In stock
9:15 AM
A customer buys the final unit.
Website: Out of stock
Product data: In stock
6:00 PM
Your product feed finally updates.
For several hours, your website and submitted product data were inconsistent.
This becomes more important when you have:
fast-selling products
flash sales
limited inventory
large catalogs
several warehouses
multiple sales channels
frequent inventory changes
If your stock changes often, inventory freshness becomes part of product-data quality.
5. Check Your Checkout Experience
Do not stop at the product page.
A product can appear available on the landing page but become impossible to purchase later.
For example:
The page says:
In stock
The Add to Cart button works.
But during checkout:
This product is no longer available.
That is still a poor representation of product availability.
When troubleshooting a difficult case, follow the same path a customer would:
Product page
↓
Select exact variant
↓
Add to cart
↓
Proceed to checkout
↓
Confirm that purchase is actually possible
This is especially useful when inventory is controlled by another app, warehouse system or ecommerce plugin.
6. Do Not Confuse Preorder With In Stock
A product that has not been released yet should not simply be marked:
in_stock
just because customers are allowed to place an order.
That situation may actually be:
preorder
Google treats preorder as a separate availability state.
If you use preorder, you should also provide an appropriate availability date indicating when the product becomes available.
That date should be clearly represented to the customer on the landing page.
For example:
Preorder now — ships October 15
is different from:
In stock — ships today
Both accept orders.
But they represent different fulfillment situations.
7. Understand the Difference Between Backorder and Out of Stock
These two situations are also different.
Out of stock
You are currently not accepting orders for the product.
Backorder
The product is not currently available, but you are still accepting orders and expect to fulfill them later.
If a product is on backorder, the availability information should accurately represent that condition.
Do not mark a product in_stock simply because the checkout button is still active.
Ask:
Can this product actually be fulfilled now?
If not, determine whether it is:
out of stock
backordered
or available for preorder
Choosing the correct state gives both customers and machines a clearer understanding of the offer.
8. Do Not Use “Out of Stock” Just to Pause a Product
Sometimes a merchant does not want a product to appear temporarily.
The tempting solution is to change:
in_stock
to:
out_of_stock
even though the item is actually available.
That creates inaccurate product data.
Availability should describe whether the item can actually be purchased.
It should not be used simply as an on/off switch for advertising or visibility.
If you want to temporarily stop a product from being shown, use the appropriate Merchant Center controls rather than sending false inventory information.
The general rule is simple:
Availability should represent reality.
A Simple Availability-Mismatch Checklist
Before changing your entire feed, check these eight areas.
1. Submitted availability
What availability value is currently being sent to Google?
2. Visible page status
Does the product page clearly show whether the item can be purchased?
3. Exact variant
Is Google evaluating the same color, size or configuration that the landing page opens?
4. Structured data
Does the machine-readable availability agree with the visible page?
5. Checkout
Can the exact product actually be purchased?
6. Inventory timing
Did stock recently change before your product data updated?
7. Preorder or backorder
Are you using the correct availability state?
8. Other products
Does the same issue appear on several products?
This final step is important.
One affected SKU may indicate an isolated mistake.
Ten similar products with the same inconsistency may indicate a larger synchronization problem.
Example: A Variant Problem That Looks Like an Availability Problem
Imagine you sell a jacket in three colors.
Black
In stock
Blue
In stock
Green
Out of stock
Your submitted offer is for:
Green jacket
But the product URL opens with:
Black selected by default.
When someone manually checks the page, they see:
In stock
and assume Google is wrong.
But Google may actually be evaluating the Green variant.
The underlying problem is not necessarily inventory synchronization.
It is that:
the submitted offer and the landing-page selection do not represent the same variant.
This is why checking only the visible “In stock” message can produce the wrong diagnosis.
Example: Structured Data Is Out of Date
Consider another product.
Visible page:
In stock
Merchant Center:
In stock
Everything appears correct.
But the page's structured data still says:
OutOfStock
because an ecommerce plugin did not refresh the markup after inventory returned.
Now three sources say:
Feed → In stock
Visible page → In stock
Structured data → Out of stock
That is exactly the type of inconsistency worth finding before repeatedly resubmitting products.
Can Automatic Updates Fix Availability Problems?
Google Merchant Center can use information from your website to automatically update certain product information.
That can help reduce some temporary discrepancies.
However, it should not become your main inventory-management strategy.
If:
your page is ambiguous
your structured data is wrong
the wrong variant loads
or your underlying feed is consistently stale
you still have a source-data problem.
Think of automatic updates as a backup mechanism.
Your goal should still be:
Website inventory and submitted product data update together as closely as possible.
What Should You Do After Finding the Mismatch?
Do not randomly change the Merchant Center value until the warning disappears.
Instead, identify the source of truth.
A better process is:
1. Confirm the real inventory state
↓
2. Identify which system contains the wrong value
↓
3. Correct the source data
↓
4. Verify the landing page
↓
5. Verify the exact variant
↓
6. Verify structured data
↓
7. Confirm checkout availability
↓
8. Update or resynchronize your product data
This is more durable than correcting symptoms one product at a time.
Start With Three Products, Not Your Entire Catalog
If you are not sure whether your store has an availability-data problem, you do not necessarily need to inspect every SKU first.
Choose three representative products.
For example:
Product 1
A simple product currently in stock
Product 2
A product with several variants
Product 3
A product that recently went out of stock or returned to stock
For each one, compare:
visible availability → exact variant → structured data → product-data status
If all three agree, that is useful evidence.
If multiple conflicts appear in a tiny sample, a larger catalog audit may be justified.
Check Three Product Pages for Free
Mingche provides a free Product Page Check for three distinct product URLs from the same store.
The check reviews publicly accessible product-page signals such as:
price
availability
variants
structured data
You do not need to upload your entire catalog for the initial check.
The purpose is to help identify visible product-data inconsistencies before deciding whether a broader audit is necessary.
Start the Free Product Page Check →
Open the free product-page check
When a Full Audit Makes More Sense
A three-product check is only a sample.
A broader audit becomes more useful when:
many products show availability issues
inventory changes frequently
you have large numbers of variants
several systems manage inventory
your structured data and storefront disagree
Merchant Center repeatedly reports mismatches
you cannot identify which system contains the incorrect value
The goal is not simply to change every warning.
The goal is to understand:
where your product data stops matching the actual buying experience.
Final Takeaway
An availability mismatch is not always a simple:
“In stock vs. out of stock”
problem.
It can originate anywhere in the chain:
inventory system → product data → exact variant → structured data → landing page → checkout
When those systems agree, Google receives a much clearer description of what a customer can actually buy.
When they disagree, repeatedly changing one field may only hide the real problem.
Start small.
Check a few representative products.
Find the conflicting source.
Then fix the system that produced the wrong information.
Disclaimer
Mingche is an independent product-data readiness service and is not affiliated with or endorsed by Google.
Product-data auditing or correction does not guarantee Google approval, inclusion, ranking, traffic or sales. Google independently determines Merchant Center eligibility and policy compliance.
Comments
Post a Comment