Same Product Different Prices: Why GMC Suspends You

Price inconsistency is one of the top three causes of Google Merchant Center misrepresentation suspensions. The issue seems simple, but in practice it has many forms: feed price versus product page price, tax-inclusive versus tax-exclusive display, sale price timing gaps, currency conversion errors and geo-based price variations that Google's crawler encounters differently than your customers do. This guide covers every price consistency scenario we have seen cause suspensions and how to fix each one.

How Google Detects Price Inconsistencies

Google's systems run automated crawls of merchant product pages and compare the prices found against the prices submitted in the feed. The comparison is exact: same currency, same value to the cent, same tax inclusion rules for the target market. These crawls happen continuously, not just when you submit your feed. A product page that shows $39.99 but has your feed submitting $34.99 will be flagged within hours of the next crawl cycle.

Google also uses shopping agents, automated systems that simulate a purchase flow from ad click through to cart. These agents check prices at the product page level, at the cart level and sometimes at the checkout initiation level. Prices that change between these stages, even due to automatic coupons or cart-level discounts that should not apply, trigger additional flags.

The Most Common Price Mismatch Scenarios

1. Sale Price in Feed But Full Price on Product Page

You added a sale price to your feed but forgot to update the sale price on the product page, or the sale ended on your website before the feed was updated. The consumer clicks an ad showing the lower price and lands on a product still displaying the original price. Fix: always use the sale_price and sale_price_effective_date attributes in your feed. Set the effective date range to match exactly when the sale price is active on your website. When the sale ends, remove the sale_price from the feed at the same time you remove it from the product page.

2. Tax Display Rules for Different Markets

In the EU and Australia, consumer-facing prices must include VAT or GST. If your feed submits ex-tax prices while your product pages display tax-inclusive prices, Google sees a price mismatch. Conversely, if your feed includes tax but your product page shows an ex-tax price, the same mismatch applies. Check the tax display requirement for each country you target and configure your feed prices to match the display format your product pages use.

3. Currency Converter Plugins

Currency converter plugins on your website change the displayed price dynamically based on the visitor's location or browser settings. If Google's crawler visits your product page and the plugin serves a different currency or exchange rate than your feed submits, Google records a price mismatch. The safest approach: use hardcoded prices for your primary market and submit separate feeds with correct currency for each additional market rather than relying on dynamic conversion on the product page.

4. Geo-Restricted Pricing

If your website charges different prices based on visitor country, and Google's crawler originates from a different country than your target market, it may record the wrong price from your product page and compare it against your feed price. If you use geo-based pricing, test your product pages using Google's URL inspection tool in Search Console with your target market's crawler settings to see what price Google actually reads.

5. Wholesale or B2B Price Showing to Crawlers

Sites that serve a lower B2B price to all visitors, or that show a B2B price before a login check kicks in, may serve the B2B price to Google's crawler. If your feed contains the retail price, Google sees a price lower than what you submitted and flags the inconsistency. Check your product pages while logged out and with cookies cleared to confirm the price Google's crawler would see.

Fixing Price Consistency Before Your Appeal

Run a price consistency audit before submitting any reinstatement request. Export your current feed and for each product, load the product page in a private browser window (no cookies, no login) and compare the displayed price against the feed price. Do this for at least 50 products if you have a large catalog, focusing on products that have been modified recently or that are on sale. Fix every mismatch before appealing.

For sale pricing, check that your sale_price_effective_date values in the feed match the sale period on your website. Expired sale prices in your feed that still point to full-price product pages are a common audit failure point. Read our full misrepresentation guide for the complete audit process, and our suspension fix guide for the reinstatement appeal process.

Find Every Price Mismatch in Your Feed

Our audit compares your feed against your live product pages across 52 policy checks including price consistency. Get your prioritized fix list now.

Run Free Audit

Preventing Price Mismatches Going Forward

Enable Automatic Item Updates in GMC under the Settings menu. With this enabled, Google reads prices directly from your product page's structured data markup during its crawl cycles, which means short-lived feed lag no longer creates a mismatch window. Pair this with regular feed submissions (at least daily) and a structured process for coordinating price changes across your website and feed simultaneously.

If you run frequent promotions, consider using Google's Promotions feature in GMC rather than modifying base prices. Promotions layer discount information onto your existing feed price without creating price attribute mismatches, and they display a "special offer" label in your Shopping ads that can improve click-through rates.

Frequently Asked Questions

Can I charge different prices to logged-in members versus anonymous visitors?

Yes, but you cannot use the member price in your Google Shopping feed if the member price is lower than what anonymous visitors see. Your feed price must match the price an anonymous consumer sees on your product page. Member pricing shown in your feed to consumers who then land on a higher price page creates a misrepresentation violation.

Does applying a Shopify discount code at checkout create a price mismatch?

Discount codes applied at checkout do not create a GMC price mismatch on their own because the product page price is not changed. The mismatch occurs when your feed price differs from your product page price. If you run a sale where the product page shows a sale price, update your feed's sale_price attribute to match.

My products are priced differently on Amazon and my website. Does that matter for GMC?

Your prices on other marketplaces like Amazon do not affect your GMC compliance. Google only compares your feed price against your own website's product page price. Having different prices across marketplaces is normal and does not violate GMC policy.

How do I handle bundle pricing in my GMC feed?

Bundles must be submitted as a single product with a single price that matches the bundle price on your product page. Do not submit bundle components individually if the consumer-facing purchase is a bundle. Mismatches between bundle price in the feed and individual component prices on the website trigger availability and price mismatch flags.

Also see: Full Suspension Checklist and GMC Appeal Process Guide.