Fix: price mismatch (value mismatch) disapproval
A price mismatch disapproval means your feed price does not match your landing page. Here is what causes it and how to keep feed and site in sync.
What a price mismatch disapproval is
Google disapproves a product for a price mismatch (sometimes shown as a value mismatch) when the price in your feed does not match the price a shopper sees on your landing page. Google checks this because showing one price in an ad and a different price at the store is a poor and potentially deceptive experience, so it is one of the disapprovals Google enforces strictly.
This issue can escalate. A small number of mismatches disapproves individual products, but widespread or repeated price and availability mismatches can trigger a broader account-level warning or suspension. It is worth fixing fast and at the root.
What causes the mismatch
The mismatch is almost always a timing or formatting problem between your feed and your site, not a pricing decision. The usual culprits are:
- Stale feed: your site price changed but the feed has not refreshed yet.
- Sale price not reflected: a sale went live on site but the feed still has the old price (or vice versa).
- Currency or format mismatch: the feed omits the currency, uses the wrong one, or formats the number differently than the page.
- Tax or shipping confusion: the feed price includes or excludes a cost that the landing page shows differently.
- Crawl issue: Google cannot read the price on the page (it is loaded by script Google does not execute, or it is behind a variant selector).
How to fix it
The fix is to make the feed price and the landing-page price agree, in value, currency, and format, and to keep them agreeing as prices change.
- 1Confirm the actual current price on the live landing page for an affected product.
- 2Check the feed's price attribute (and sale_price if on sale) matches that value exactly, including currency.
- 3Make sure availability and price reflect the variant Google lands on, not a default.
- 4If the feed is just stale, increase your feed refresh frequency so it tracks site changes.
- 5If the page price is hard for Google to read, expose it cleanly in the page markup or via product structured data.
- 6Re-run the feed and request re-review; the count should clear once they agree.
The real fix is refresh frequency
Almost every price mismatch comes down to the feed lagging the site. If your prices change daily but your feed refreshes weekly, you will get mismatches constantly. The durable fix is to refresh the feed at least as often as your prices change, so the gap between a price change on site and the same change in the feed is as small as possible.
For stores with sales, flash deals, or dynamic pricing, this means frequent automated refreshes, not a manual export when someone remembers. The feed has to track the site automatically.
How MartechFlow prevents mismatches
MartechFlow keeps price in sync by pulling fresh data from your source on the schedule you set and republishing the feed automatically, so the feed price tracks your site. You map your price and sale_price fields once, set the refresh frequency to match how often your prices move, and the feed stays current without manual exports.
Because sale and original prices flow through the same pipeline, your discount badges on social images recompute from the same numbers, so the ad creative never shows a price the feed contradicts. Set the right refresh cadence and price mismatch largely stops happening.