Google Merchant Center Price Mismatch: Running Sale Prices Without Price Warnings

Your sale is live, and the next morning Merchant Center lists products under “Mismatched product price”. That is a Google Merchant Center price mismatch: the price Google holds for a product differs from the price on your website. For sales, Google names the usual cause on its page about this error: Any mismatch in date (for example, a wrong start date or timezone) will show an incorrect price.

This post covers one situation: running a sale, and ending it, without disapprovals halfway through. Google only shows your products if it trusts your prices.

Why does a sale cause a Google Merchant Center price mismatch?

Google holds two copies of your price: the one in your product data (your feed, or your platform’s sync), and the one on your product page. Googlebot compares them. Google’s page says Googlebot crawls the data present in the HTML returned from your web server. When the two differ, the product may be disapproved. Google adds: This may lead to an account suspension.

A sale changes the price in two places at once, and they rarely update at the same second. Your store usually changes the moment you save. Your product data changes at the next sync or feed fetch. In between, Google sees two prices.

Merchants still search for the older name of this error, “Mismatched value (page crawl) [price]”. It is the same item-level issue. If Google has gone further and warned your whole account about prices, that is a different process with a review and a deadline; our post on preemptive item disapproval and inaccurate price status covers it.

What does Google say about prices that change more than once a day?

Many stores rely on automatic item updates to cover the gap. Google reads the price from your page and updates the listing. Google says Automations are enabled by default.

Google’s page on automatic updates now carries a clear limit, which trade press dated to late September 2026:

• Automations may not work for products with frequent price or availability value changes (for example more than once per day).
• The product may be disapproved instead of updated if we detect a mismatch.
• We may also stop updates if the total number of detected mismatches becomes too large.

Google’s advice for fast changes is on the same page: If you expect the pricing, availability, and condition of your products to update frequently, you should use the Merchant API to manage product updates.

Our reading: hourly deals, flash sales and repricing apps are the case Google describes. Automatic updates are a patch for small gaps, not a way to run a sale.

How do I set up a sale so the prices match?

Google has three attributes for a sale. Use all three.

1. Keep price as the regular price. Google says When you submit the sale price [sale_price] attribute, continue to submit the full price of your product (the cost when it’s not on sale) by also submitting the price [price] attribute. (Google’s sale price page).
2. Put the deal in sale_price. On the page, Google asks you to Clearly display both non-sale and sale prices on your landing pages, and only the sale price at checkout.
3. Add sale_price_effective_date. Without it, Google says the sale price will be used for your product immediately.

The dates need a time zone. Google’s sale price effective date page says If you don’t include a timezone, we default to the UTC timezone. and If you don’t include a time, the sale price starts at 12 AM, midnight, on the start date and ends at 11:59 PM on the end date. A store in New York that sends no time zone can end its sale five hours before its own midnight in Google’s eyes.

An example for a sale that runs from 9 AM on a Friday to the end of Monday, New York time in November:

price: 60.00 USD
sale_price: 45.00 USD
sale_price_effective_date: 2026-11-27T09:00-0500/2026-11-30T23:59-0500

Then make your store do the same thing at the same times. Google’s page on inaccurate prices asks you to Ensure that updates to your site and product data happen at the same time. (Google).

Does the strikethrough “was” price matter?

Yes, in two ways.

It has to match your data. Google says Make sure that any strikethrough price value displayed on your online store matches the price [price] attribute when the sale price [sale_price] attribute is also provided. If your theme or an app shows a different “was” price from the one you send, that is a mismatch waiting to happen.

It has to be real for Google to show it. Google only shows the crossed-out price and sale badge when the deal meets its rules. On its sale price annotations page, Google says The discount of the sale must be greater than 5% and less than 90%. For Shopping ads in the US, the regular price must have been charged for 5 days within the past 30 days, or 15 days within the past 200. For Shopping ads in the UK, Germany, France, Australia and the other countries listed there, it is 30 days within the past 200.

Our reading: a “launch” or recommended price you never charged won’t earn the badge, and it misleads shoppers about the saving.

If your pages show several crossed-out prices, Google says its system may not find the right one, and You shouldn’t enable automatic updates for price in this case. The switch is under Products → Automations in Merchant Center.

Can tax or currency cause a price mismatch during a sale?

Yes. The sale price follows the same tax and currency rules as the regular price.

• Tax. In the US and Canada, Google wants prices without tax. In the many countries it lists, including the UK, Australia and most of Europe, prices include VAT or GST. Google’s price attribute page says If you’re required to submit VAT in the price, then make sure that the same price including VAT is visible on your landing page and at checkout.
• Currency. Google says the price and currency you send should match the price and currency prominently displayed on your landing page. A currency switcher that rounds sale prices differently from your feed causes mismatches in some countries only.

What happens when your sale ends?

Many sale warnings start here: the store is back to full price, and Google still holds the sale price.

• With an end date in sale_price_effective_date, Google shows the sale price only for the period you sent, so it switches back on its own. Your store must switch back at the same moment, in the same time zone.
• Without an end date, our reading is that the sale price stays in Google’s data until your next product data update. If the store switches first, the page shows the full price while Google shows the sale price.
• If you extend the sale (for example into Cyber Monday), change the end date in your product data too. Extending it only in the store means Google ends the sale on the old date while your page still shows the deal.
• Remove the crossed-out price when the sale ends, so the page doesn’t show a “was” price for a product that is no longer on sale.

Google’s page on the “Automatic updates: Mismatched price” issue gives the same advice on timing: Schedule feed uploads or updates via the Merchant API immediately after the products have been updated on your website. (Google).

Steps before, during and after a sale

Before (a few days ahead)

1. Pick the start and end times and write them with your time zone offset.
2. Send the regular price, sale price and sale dates, and check in Merchant Center that all three arrived.
3. Check every “was” price is one you have charged, and that the discount is above 5% and below 90%.
4. If a product’s price will change more than once a day, send each change right after the site changes; don’t count on automatic updates.
5. Look at Products → Automations. If your pages show more than one crossed-out price, turn off automatic updates for price.
6. Test one product: the page, its structured data, the cart and the checkout should all show the same sale price.

During

7. A few hours after the start, open Products → Needs attention and filter for “Mismatched product price”. Compare the time Google found each mismatch with when your prices changed.
8. Fix the cause at the source (the app, the sync, the time zone). Our reading: a price edited by hand in Merchant Center can be replaced by your next sync.
9. Request a website check after fixing. Google says Google may take up to 12 hours to review your website.

After

10. End the sale on the site at the end time you sent Google, or push your product data right after you end it.
11. Remove compare-at or “was” prices.
12. The next day, check Needs attention again.

Our price mismatch fix guide has the general fix for this error, for any cause.

On Shopify, WooCommerce and other platforms

Shopify

On Shopify, the original price goes in Compare-at price and the sale price in Price (Shopify’s sale pricing page). Google’s page for the Google & YouTube app gives the timing: After saving your data in Shopify, prices will update on Google within 24 hours. (Google).

That gap is the risk: your store changes when you save, Google’s copy up to a day later. Shopify’s sale pricing page describes no start or end date for a compare-at price, so the sale starts and ends when you or an app save the change. Our advice: change prices when you can check Merchant Center a few hours later, and don’t start and end a sale on the same product within a day.

Selling in several markets? Shopify’s page notes that a market’s fixed prices override the prices and compare-at prices set in the admin, so check the sale in each market. Our Shopify and Merchant Center post explains how the sync works.

WooCommerce

WooCommerce schedules sales itself. In Product data → General, enter the sale price and select Schedule. WooCommerce’s product editor guide says the end date is when the sale price should stop displaying (expires at 11:59 pm). Check that your feed plugin sends the same dates with a time zone, and that the store’s time zone in WordPress settings is the one you mean.

In the WooCommerce cases we have read, the trouble usually sits between the store and Google: a feed plugin that drops VAT, a currency plugin, or a page cache that keeps the old price. Clear the cache when the sale starts and ends.

Other platforms

Check three things: the feed has price, sale_price and sale_price_effective_date with a time zone; the page’s HTML shows the sale price without waiting for a script; and the feed is fetched soon after prices change. Our guide on feeds that don’t match your website shows where to look.

What we see in real cases

Paraphrased from public merchant forum threads, with no names or stores.

• After a feed plugin update, a WooCommerce store’s prices reached Google without VAT. Mismatched items more than doubled within hours, to several hundred, until a later release fixed it.
• Another WooCommerce store’s feed prices sat about a quarter above checkout: a price filter dropped the currency, and a currency plugin converted the number again.
• A store set sale prices and reverted them by hand, with no end dates, and its ads showed a price the page no longer had.
• In a pre-holiday thread, a helper warned that sale prices go live on the store before the feed catches up.
• A merchant had automatic price updates on and still saw price and currency mismatches in three countries.

The pattern: the store’s price was usually right. The timing, the tax or the currency between the store and Google was not. Before a big sale, the free store check reads your storefront and product pages as a visitor sees them.

What Google doesn’t say

• Whether “more than once per day” is a firm limit or an example.
• How many mismatches make Google stop automatic updates.
• Whether the Google & YouTube app sends sale dates from Shopify.

If someone gives you a number for any of these, ask where Google says it.

FAQ

Why does Google show the wrong price after my sale ended?

Google uses the sale price until the end date in your product data, or until your next update if you sent no dates. Send sale_price_effective_date with a time zone and end the sale on your site at that same moment.

Can I change prices several times a day during a sale?

Google says automatic updates may not work for products whose price changes more than once per day, and the product may be disapproved instead of updated. For frequent changes, Google points to the Merchant API.

Does the strikethrough price have to match my product data?

Yes. Google says any strikethrough price on your store should match the price attribute when you also send a sale price. For the sale badge, the discount must also be greater than 5% and less than 90%.

How long does Google take to clear a mismatched product price?

Google says Googlebot re-crawls disapproved products over the next few hours or days, and reapproves them once the prices match. If you request a website check, Google says it may take up to 12 hours to review your website.