Preemptive Item Disapproval and “Inaccurate Price Status” in Google Merchant Center

A batch of your products vanished from Google, and the message in Merchant Center says “preemptive item disapproval”, or an email warns of an “inaccurate price status”. Google defines preemptive item disapproval (PID) in one line: This occurs if the price or availability of your products don’t match between your product data and product pages. (Google’s page on issues in Merchant Center).

Update, 29 October 2026: Google has reworded several of the help pages quoted in this post since it was first published. The quotes are Google’s current wording, checked on 29 October 2026. Where a rule itself is newer than this post, we say so.

In short: Google found prices on your site that didn’t match the prices you sent. You fix the cause, then ask for a review. Here is what Google says about each step, and where it says nothing.

What is preemptive item disapproval?

It is an account-level penalty that acts on products. Google explains the name on its page for Shopify merchants: It’s called “preemptive item disapproval” because Google errs on the side of caution and disapproves items that are likely to violate requirements (Google).

Three facts from Google’s pages matter most:

• It replaces a suspension. Warnings regarding price and availability mismatch between the feed and the landing pages result in preemptive item disapproval instead of an account suspension.
• It is still about the account. Preemptive item disapproval (PID) is still considered account-level enforcement and an account review is required to fully resolve the issues.
• Only price and availability cause it. Only price and availability mismatch between the feed and the landing pages can result in preemptive item disapproval.

Google also says that while you work on it, you can still show other products from your account that meet the requirements. So some products keep showing while others don’t.

Is it the same as a “Mismatched product price” error?

No. Google has two different price problems, and they clear in different ways.

	Mismatched product price	Inaccurate price status
Level	One product	The whole account
Who finds it	Googlebot, when it crawls the page	Google’s policy reviewers
What happens	That product is disapproved	A warning with a deadline, then preemptive item disapproval
How it clears	Google re-crawls and reapproves	You request an account review

The item-level error is the one many merchants still search for under its older label, “Mismatched value (page crawl) [price]”. Google’s current page calls it Mismatched product price and says it clears on its own once the prices match: Googlebot automatically re-crawls disapproved products over the next few hours or days to recheck the price. It still warns that these mismatches may lead to an account suspension. Our price mismatch fix guide covers the item-level error.

The account-level issue has its own page, titled “Inaccurate price status due to inconsistency between feed and landing page”. It opens with Your account has either been warned or your products have been preemptively disapproved due to this error (Google). Google adds that You should have received an email asking you to update your product data by a certain date. Find that email first. It holds your deadline and the examples.

Where do the wrong prices come from?

Google lists the common causes on that page. These are the ones merchants run into most:

1. A sale that started or ended on the site but not in the feed. Google’s own example: For example, if a sale has started or ended but the price in the feed hasn’t been updated and no longer matches your site. Its advice is to Ensure that updates to your site and product data happen at the same time.
2. Sale dates in the wrong time zone. If you schedule sales with the sale price effective date attribute, Google says If you don’t include a timezone, we default to the UTC timezone. (Google).
3. Currency conversion. Currency switchers and multi-market setups can show a different currency on the page from the one in the feed. Google asks that your feed matches the price and currency prominently displayed on your landing page.
4. Prices that change by visitor. Don’t change the price of your product on your landing page based on a user’s location. Google goes further: Additionally, do not change price based on cookies, browsers, devices, or any other factor.
5. Sale and discount apps that rewrite the price after the page loads. Googlebot reads the HTML your server sends, and Google says Prices reflected in the HTML need to match exactly the prices uploaded in Merchant Center. A price added later by a script, or a slow page, can be missed: Google says Make sure to load your price on the landing page immediately.
6. Cached pages. Our reading: if a caching plugin or service keeps serving last week’s page, Googlebot can see last week’s price even after you changed it. Google’s pages don’t mention caching by name; they ask for the same price in the HTML and in your data.
7. Tax. 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. (Google’s price attribute page).
8. Variants. One page, several prices, and the feed sends the wrong one. Our post on variants not matching your Google feed walks through it.

Google also lists structured data that disagrees with the visible price, several prices on one page, minimum order quantities and membership prices.

How do I clear preemptive item disapproval?

1. Read the message and the email. Setup and policy issues sit in a banner: Setup & policy issues show in a banner at the top of your Merchant Center. (Google). Note the deadline if you were only warned.
2. Use the examples to find the pattern. Google says Check the warning email for the examples of products that are affected. Don’t fix only those. Google is clear that There is no exhaustive list of disapproved examples to be shared, so the examples point to a cause that is probably wider.
3. Compare four places for each example. The price a shopper sees, the price in the page’s HTML (view the page source), the price in the structured data, and the price Merchant Center holds. Then add the product to the cart and check the checkout price. Our guide on feeds that don’t match your website shows where to look.
4. Fix the cause at the source. Change the app, plugin, currency setting or sale schedule that produced the wrong price, not the single product. A price edited by hand in Merchant Center can be overwritten by your next sync.
5. Resend your product data. Let your platform sync, or upload the feed again, and check that Merchant Center now shows the new prices.
6. Request the review. If you were warned and fixed it before the deadline, Google says you can request a courtesy review on the account, before the deadline. If you are already in preemptive item disapproval, request a review for the account by selecting “I fixed the issue”.

Do I need a review, or will Google re-crawl?

For the account-level issue, you need a review. Google’s page on issues says A review is required to resolve these issues. Re-crawling alone clears single “Mismatched product price” disapprovals, not the account’s status.

What Google says about that review:

• The review will take 7 business days to complete.
• Note that failing this review will place the account in a cooldown period of 7 business days before a new review can be requested.
• There is no way to receive or request an extension on the enforcement deadline in your email.
• Reaching out to the support team will not trigger an account review.

If you miss the deadline while warned, Google says However, Google will perform a manual review once the deadline has passed. Its review page adds that Google support can’t bypass or shorten the cool down period. Because a failed review costs at least a week, check your fixes on live pages before you press the button.

Do automatic item updates help?

They can. Google says automatic updates will help reduce the risk of preemptive product disapproval (PID) for issues such as price and availability mismatches. They read the price from your page’s structured data and update your listing. Google says Automations are enabled by default. (Google’s page on automatic updates), so check they haven’t been switched off: Products → Automations.

Two limits. Google says Automations aren’t a replacement for regular updates of your product data. And if your product pages show several strikethrough prices, You shouldn’t enable automatic updates for price in this case. Our reading: automatic updates patch small gaps; they don’t fix a feed that is out of step with the site.

On Shopify, WooCommerce and other platforms

Shopify

Prices usually reach Google through Google’s sales channel app. Places to look: compare-at prices that differ from the sale shown on the page, apps that change prices in the browser, and currency or market settings that show shoppers a different currency from the one in the feed. Google’s page for Shopify merchants says that for an account in preemptive item disapproval you can request a review with the Request review button in Merchant Center, and the app’s Settings tab has a Request re-review link (Google). Our Shopify and Merchant Center post covers how the connection works.

WooCommerce

In the cases we have read, mismatches usually come from plugins that sit between the store and Google: the feed plugin, a caching or performance plugin, a currency switcher, or a dynamic pricing plugin. Check that your prices include or exclude tax in the way Google expects for your country, and clear any page cache after a price change. If you request the review from your plugin, Google notes that If you’re working with a third-party platform, some of these instructions may not apply to you.

Other platforms

Wherever your product data comes from, Googlebot compares it with the HTML your server sends. Make sure the visible price, the HTML and the structured data carry the same price and currency, without waiting for a script.

What we see in real cases

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

• A WooCommerce store had its whole account placed in preemptive disapproval for availability. A plugin update had broken the sync, and cache and performance plugins were blocking it, so Google kept seeing old stock data.
• A store selling in several regions built one feed per currency and still got “inaccurate price” warnings. A currency switcher on the site showed Google a different price from the feed.
• A Shopify store turned on selling in several markets and found its structured data kept one fixed currency while the page showed local prices.
• A Shopify merchant found the Google app had stopped sending price changes to Merchant Center. They tested it by changing a price, and worried stale prices would get the account suspended.
• A WooCommerce merchant set sale prices and reverted them by hand, without end dates, and found ads showing a price the product page no longer had.

The pattern: in most of these cases the price in the store was right. Something between the store and Google was not: a plugin, an app, a currency setting or a cache. Before you request a review, the free store check reads your storefront and policy pages as a visitor sees them.

Update, 28 October 2026: Google has since added a warning to its page on automatic updates, which trade press dated to late September 2026. It now says Automations may not work for products with frequent price or availability value changes (for example more than once per day). and The product may be disapproved instead of updated if we detect a mismatch. If your prices change several times a day, automatic updates are no longer a safety net. Google’s page on inaccurate price status now also mentions availability, suggests Shopify users toggle the sync off and on to force a re-sync, and recommends turning on automatic item updates. In August 2026, a WooCommerce plugin forum also reported a plugin update that sent prices without VAT and produced hundreds of mismatches within hours.

What Google doesn’t say

• How many mismatched products lead to an inaccurate price status.
• How Google’s reviewers choose which products to check.
• How long products stay disapproved after a successful review before they show again.

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

FAQ

Is preemptive item disapproval the same as an account suspension?

No. Google says price and availability mismatch warnings result in preemptive item disapproval instead of an account suspension, but it is still account-level enforcement and needs an account review to be fully resolved. Products that meet Google’s requirements can keep showing in the meantime.

How long does a review for inaccurate price status take?

Google’s page says the review will take 7 business days to complete. If the review fails, the account goes into a cooldown period of 7 business days before you can request a new one.

Will fixing my prices clear preemptive item disapproval on its own?

Not fully. Google says a review is required, so once your prices match, request a review with “I fixed the issue”. A single “Mismatched product price” disapproval is different: Google re-crawls the product and reapproves it when the prices match.

Can Google support give me more time or a full list of the affected products?

No. Google’s page says there is no way to receive or request an extension on the enforcement deadline, and that there is no exhaustive list of disapproved examples. It also says contacting support does not trigger an account review.

Should I turn on automatic item updates?

Google says automatic updates help reduce the risk of preemptive product disapproval for price and availability mismatches, and they are on by default. Google also says not to enable them for price if your product pages show several strikethrough prices.