Weekly ecommerce tips, deals & news.
A price mismatch is when your product feed and your landing page quote different prices. The product data says one thing and the page says another. Shopping channels treat that gap as a trust problem, not a typo, and they act on it.
A price mismatch happens because two systems describe the same product and only one of them just changed. Think of it as a menu in the window and a menu at the table. The kitchen updated one of them this morning.
Your store is the table menu, and the feed is the one in the window. A shopper who spots the difference stops trusting both.
Prices drift apart at predictable moments, and timing causes most of them. First is the sale. A discount goes live on your store, and the feed still carries yesterday’s figure until it refreshes.
Next is the variable product. Your feed sends one price while the page loads with a different variation preselected. The crawler reads whatever the page shows by default.
Then there is tax and currency. A feed may quote one country’s price while the page geolocates the visitor. The gap that produces looks exactly like an error.
Rounding and formatting cause a quieter version. A feed sending 19.9 against a page showing 19.90 can trip a strict comparison. So can a currency symbol the crawler cannot parse.
Finally there is structured data. Your page can display the right price while its markup still carries an old one. In practice, the crawler often trusts the markup over the visible text.
Shopping channels respond to a price mismatch by removing the listing rather than warning the shopper. Google states the expectation plainly. Someone clicking a listing should see the same price on your landing page.
When that breaks, the affected products are disapproved and stop appearing. Repeated problems escalate, and the account itself can be warned or suspended.
Recovery is automatic but not instant. Google recrawls the page once you fix it, and those crawls usually finish within 24 to 48 hours. If you request a manual review instead, that review takes 7 business days to complete.
A disapproved product earns nothing while it waits. That is the whole cost, and it is easy to underestimate. A product removed on a Friday is invisible for the weekend it was meant to sell in.
The loss compounds on your best products. Shopping feeds send most of their traffic to a small share of your catalog. A mismatch on those items costs more than the same error on a slow seller.
Sale periods make it worse, because a price change is what triggered the disapproval. Your discounted products go missing during the exact window the discount was for.
There is a second cost when the mismatch runs the other way. A shopper clicks a low feed price and meets a higher one on your page. They have been quoted a number that changed. AdTribes covers the diagnostic side in its guide to Merchant Center diagnostics.
Price mismatches are not published as an industry statistic, but the shopper reaction is well measured. Price changes between the listing and the final total are among the strongest reasons people abandon a purchase.
In Baymard’s list of checkout abandonment reasons, 40% of abandoners picked extra costs being too high. That figure covers shoppers with an actionable reason, excluding those just browsing.
The mechanism is the same one a price mismatch triggers. A number goes up between the moment of interest and the moment of paying. So a feed that quotes low and a page that charges more is buying clicks it will not convert.
A price mismatch in practice shows up as traffic disappearing from products that were selling fine. Here is a hypothetical example. Imagine a homeware store running about 900 products through a shopping feed.
In this scenario, the feed regenerates once a day at three in the morning. That schedule has worked for two years without a problem. Prices normally change a few times a month.
Then the store runs a two-day flash sale starting on a Friday morning. Discounts go live on 240 products at nine o’clock.
As a result, the feed carries the old prices for eighteen hours. The crawler reads the discounted pages and compares them against the feed. Every one of those 240 products is flagged.
The store had also linked the sale from an email campaign. Those clicks still landed, so the page traffic looked healthy. Only the shopping channel went quiet, which is why nobody spotted it sooner.
Meanwhile the discounted products vanish from shopping results on the busiest day of the sale. Nobody notices until Saturday afternoon, when someone checks why clicks collapsed.
Worse, the sale ends before the listings recover. The feed refreshes at three on Saturday and the recrawl lands after the discounts have already expired.
So the store ties the feed to the prices rather than the clock. A price change now triggers a feed refresh instead of waiting for the nightly run.
Next, sale planning includes the feed. Discounts are scheduled to start after a confirmed refresh, not before one.
The team also adds one alert. If disapproved products rise above a handful in a day, somebody gets a message. That single check would have caught the flash sale within the hour.
Finally, someone checks the diagnostics screen on the morning of every sale. In short, the feed stopped being a nightly chore. It became part of the price change itself.
| What you’re comparing | Price mismatch | Availability mismatch |
|---|---|---|
| What disagrees | The figure on the page | The stock status on the page |
| The usual trigger | A sale or a price change | A sellout between refreshes |
| What the shopper meets | A different number at checkout | A product they cannot buy |
| The fix | Refresh the feed on price change | Sync stock more frequently |
A price mismatch and an availability mismatch are the same failure wearing different clothes. Both come from a feed describing a page that has since changed. So the fix for both is refresh frequency rather than a one-time correction. Fixing only the prices leaves the stock version waiting to happen.
Usually a day or two once the page and the feed agree again. Google recrawls the landing page on its own schedule after a fix. A manual review is slower than waiting for that recrawl.
So fix the underlying gap first and let the recrawl find it. Requesting a review before the fix simply restarts the clock.
Because the crawler sees whichever variation your page loads by default. Your feed might send the lowest price across the range. The page then opens on a different variation at a higher one.
Send the price of the variation your link actually lands on. Alternatively, preselect that variation so the page and the feed agree.
You could, and it would cost more than the mismatches do. Discounting is not the problem, and the timing gap is. A store that refreshes its feed on every price change can discount as often as it likes.
Treat the feed refresh as part of the price change itself. Then the sale and the listing move together.
A price mismatch matters because it removes your products at the exact moment you wanted them seen. The trigger is usually a discount, so the listings disappear during the promotion. In short, a feed that updates on the clock will always lag a store that updates on demand.
Copyright © StoreOwnerTips.com. All Rights Reserved.
