Back to Community
Home / Community / Plugin → Google for woocommerce

Troubleshooting Google for WooCommerce Price and Currency Mismatch Errors

37 threads Sep 28, 2025 Plugin → Google for woocommerce

Content

One of the most common and frustrating issues users encounter when integrating their WooCommerce store with Google Merchant Center is the dreaded price or currency mismatch error. These errors can lead to product disapprovals, suspended accounts, and lost revenue from shopping ads.

Based on community reports, these discrepancies typically manifest in a few key ways:

  • Mismatched value (page crawl) [price]: The price in your feed doesn't match what Google's crawler finds on your product page.
  • Mismatched currency: The currency in your feed differs from what's detected on your site or in shipping information.
  • Prices multiplied by thousands: Product prices appear with extra zeros in Merchant Center.
  • Incorrect currency detection: Google detects JPY instead of IDR, or EUR instead of TRY, for example.

Why Do These Mismatches Happen?

After analyzing numerous support threads, several root causes emerge repeatedly:

1. Multi-Currency Plugin Conflicts

This is the single most common cause. The 'Google for WooCommerce' plugin uses your store's primary currency defined in WooCommerce → Settings → General when syncing products. It does not officially support multi-currency plugins like Aelia Currency Switcher, FOX – Currency Switcher Professional, or YITH Currency Switcher. When these plugins change the price displayed to users based on their location, it can create a mismatch between the base price sent to Google and the price seen by Google's crawler.

2. Variable Product Pricing Complexity

For variable products (e.g., fabric sold by the yard and by the bolt), the plugin may sync one variation's price while Google's crawler detects a different variation's price on the landing page, especially if the default variation shown on the site is not the one whose price was synced.

3. Tax Settings (Net vs. Gross Prices)

If your WooCommerce store displays prices excluding tax, but Google Merchant Center expects prices including tax (or vice-versa), a mismatch will occur. This is particularly common with shipping prices, leading to errors like "Shipping Prices Showing as Net Instead of Gross."

4. Automated Price Updates

If you use a third-party API or script to update prices directly in the database without using standard WooCommerce functions, the 'Google for WooCommerce' plugin's async job may not trigger a proper sync, causing the feed to contain outdated prices.

5. Incorrect Store or Language Settings

Google may detect the wrong language or regional settings if your WordPress general settings (Site Language, Site Address country) do not align with your target market in the 'Google for WooCommerce' configuration.

How to Troubleshoot and Resolve These Issues

Step 1: Verify Your Base Currency and Location Settings

Before anything else, confirm your foundational settings are correct.

  • WooCommerce Currency: Go to WooCommerce → Settings → General. Ensure the 'Currency' option is set to your primary, intended currency (e.g., USD, GBP, EUR). This is the currency that will be sent to Google.
  • Store Address: In the same section, confirm your store's address country is correct.
  • WordPress Language: Go to Settings → General and set the 'Site Language' to match your store's primary region.
  • Google Merchant Center Target Country: When setting up 'Google for WooCommerce', ensure the target country you selected includes the country where your primary currency is used.

Step 2: Address Multi-Currency Plugin Conflicts

If you use a multi-currency plugin, this is the most likely culprit. The official stance is that the 'Google for WooCommerce' plugin does not support multi-currency extensions for product syncing.

  • Option A: Deactivate the Multi-Currency Plugin. Test if the mismatches resolve. If they do, you'll need to choose between multi-currency functionality and seamless Google Shopping integration.
  • Option B: Rely on Google's Conversion. The intended workflow is to sync products in your primary currency and let Google Merchant Center handle currency conversion for shoppers in different countries. This requires your Merchant Center account to be set up for this functionality.
  • Check Plugin-Specific Settings: Some currency switcher plugins have settings to force a specific currency for bots or feeds. Explore your plugin's documentation to see if this is an option, though success is not guaranteed.

Step 3: Review Tax and Price Display Settings

Navigate to WooCommerce → Settings → Tax.

  • Check the setting for 'Display prices during cart and checkout'. It's often best to set this to 'Including tax' to avoid confusion.
  • Under 'Display prices in the shop', also consider setting this to 'Including tax'.
  • Ensure your tax rates are correctly configured for your region. Inconsistent prices between the product page and checkout often trigger Google's warnings.

Step 4: Investigate Variable Products

For products with variations that have significantly different prices (e.g., 100g vs. 1kg):

  • Check which variation is set as the 'Default Form Values' for the product. This is often the variation whose price is crawled by Google. The synced price should match this default variation's price.
  • Consider simplifying the product structure if possible, or ensure the default variation is the one you most want to advertise.

Step 5: Force a Re-Sync and Recrawl

After making changes, you need to update the data on Google's end.

  • In your WooCommerce admin, go to Marketing → Google Listings & Ads. The plugin should automatically attempt to re-sync updated products.
  • In your Google Merchant Center account, find the disapproved products and use the 'Request Review' or 'Upload and Validate' function to prompt Google to recrawl your site and re-check the data.

Price and currency mismatches can be complex, but by methodically checking these common areas, you can identify the root cause and get your products approved. The conflict with multi-currency plugins is, by far, the most frequent source of these errors, so investigating that first is highly recommended.

Related Support Threads Support