How to fix inconsistent currency errors in Google Merchant Center for WooCommerce

An inconsistent currency error in Google Merchant Center means that two or more monetary values associated with the same product do not use the same currency.

A WooCommerce product may be submitted with a price in USD while its shipping cost is supplied in EUR. The landing page may display GBP while structured data reports USD. A multi-currency plugin may show one currency to Google and another currency to customers at checkout.

These differences create an unclear purchasing experience. Google cannot reliably determine which currency represents the actual amount a customer must pay.

Google’s official guidance states that the same currency should be used across all relevant attributes. Products affected by inconsistent currencies can be disapproved and become ineligible for Shopping ads and free listings.

Fixing the error requires more than changing the currency symbol beside a product price. The WooCommerce store currency, product values, sale prices, shipping costs, structured data, landing page, checkout process, target-country configuration and active product source must describe one consistent commercial offer.

The short answer

To fix inconsistent currency errors in Google Merchant Center for WooCommerce:

Record the exact Merchant Center issue and affected offer IDs.
Identify the product source responsible for the submitted data.
Match each affected offer to the correct WooCommerce product or variation.
Check the WooCommerce base currency.
Inspect the submitted product price and currency.
Inspect the regular price and sale price.
Check product-level and account-level shipping costs.
Review installment, subscription, loyalty and minimum-order values when used.
Open the product landing page without an administrator session.
Confirm the visible price and currency.
Inspect the page’s structured product data.
Add the product to the cart.
Continue to checkout and confirm the final currency.
Test desktop, mobile and relevant customer locations.
Review multi-currency, geolocation and currency-conversion plugins.
Confirm that caches do not serve an outdated currency.
Use a valid three-letter ISO 4217 currency code.
Keep every applicable monetary attribute in the same currency.
Resynchronise the product through the authoritative integration.
Inspect the processed product in Merchant Center.
Allow Google time to update the Needs attention page.
Confirm that a later scheduled synchronisation does not restore the error.

Google describes the central requirement clearly in its inconsistent currencies guidance: a product should use the same currency across all applicable attributes.

What does inconsistent currency mean in Google Merchant Center?

An inconsistent currency issue occurs when monetary attributes connected to one product use different currencies.

Google gives the example of a product submitted in USD while its shipping rate is provided in EUR.

A similar WooCommerce case could contain:

Regular price: 100.00 USD
Sale price: 90.00 EUR
Shipping price: 10.00 USD

The sale price conflicts with the product’s regular price and shipping currency.

Another case could contain:

Submitted product price: 79.00 EUR
Landing-page price: 79.00 GBP
Checkout price: 79.00 GBP

The numerical value is identical, but the currency is different. These are not equivalent commercial offers.

A third case could contain:

Merchant API price: 1,250.00 TRY
Structured data price currency: USD
Visible WooCommerce price: ₺1.250
Checkout currency: TRY

The visible page and checkout may be correct, but the conflicting structured data can still make the page appear inconsistent to automated systems.

The issue can therefore originate in submitted product data, Merchant Center settings, WooCommerce, the landing page, structured data, shipping configuration or another active integration.

Inconsistent currency and price mismatch are different issues

An inconsistent currency error and a price mismatch can appear similar, but they are not identical.

A price mismatch means the monetary amount differs.

Example:

Submitted price: 100.00 USD
Landing-page price: 120.00 USD

Both values use USD, but the amounts do not match.

An inconsistent currency error means the currency differs across relevant values.

Example:

Submitted price: 100.00 USD
Shipping price: 15.00 EUR

The numerical amounts do not need to be identical because one represents the product and the other represents shipping. The problem is that they use different currencies within the same offer configuration.

A product can have both problems simultaneously:

Submitted price: 100.00 USD
Landing-page price: 120.00 EUR
Shipping price: 15.00 GBP

In this case, the amount and currency both require investigation.

For amount-specific problems, see how to fix price mismatch in Google Merchant Center for WooCommerce.

Inconsistent currency and unsupported currency are also different

An inconsistent currency error means applicable monetary values use more than one currency.

An unsupported currency problem means the selected currency is not supported for the intended Merchant Center configuration or target country.

For example:

Product price: USD
Shipping price: EUR

This is an inconsistency.

By contrast:

Product price: XYZ
Shipping price: XYZ

The values are internally consistent, but XYZ may not be a valid supported currency code.

Google requires supported currency values and uses three-letter ISO 4217 codes. The supported languages and currencies documentation explains which currencies are available for each target country and when currency conversion may be used.

Do not change every currency to the target country’s local currency without reviewing the website. The submitted currency must remain consistent with the product page and checkout experience.

Which product values can contain currency?

The exact fields depend on the product, target country and integration. Currency-bearing values may include:

Product price
Sale price
Shipping price
Cost of goods sold
Installment amount
Down payment
Subscription cost
Loyalty or member price
Cashback value
Minimum cart value
Certain product-specific monetary values
Values supplied through custom or supplemental sources

Most ordinary WooCommerce products primarily depend on the product price, sale price and shipping price.

More complex stores may use subscriptions, installment plans, wholesale minimums, membership pricing or country-specific shipping rules. Each additional monetary field creates another place where an incorrect currency can enter the product data.

Google’s product data specification requires accurate product prices and currencies that match the landing page, structured data and checkout.

Why inconsistent currencies occur in WooCommerce

The WooCommerce store currency was changed

A store may originally operate in EUR and later change to USD.

WooCommerce updates the store configuration, but this does not guarantee that every connected system immediately changes. An old product source, shipping rule, structured data cache or scheduled export may continue using EUR.

Changing the store currency does not automatically mean that the numerical product prices have been converted.

If a product previously cost 100 EUR and the store currency is changed to USD, a stored value of 100 may now be interpreted as 100 USD. This is a commercial change, not merely a symbol change.

Before changing the base currency, determine whether product amounts also need controlled conversion.

A multi-currency plugin changes the displayed currency

Multi-currency plugins can select a currency using:

Customer location
Browser language
IP address
Cookie
Customer account
URL parameter
Country selector
Payment method
Cached session
Administrator preference

Google may crawl the page from a location or session that receives a different currency from the one submitted in the product data.

For example, the integration submits EUR, while Google’s crawler receives USD because the multi-currency plugin applies automatic geolocation.

This does not necessarily mean multi-currency functionality must be removed. It means the product URL and data-source strategy must reliably lead Google to the submitted currency.

Product price and sale price use different currencies

WooCommerce normally stores regular and sale prices as numerical values in the store’s active currency. A custom import, currency plugin or integration may attach separate currency information incorrectly.

The result could be:

Regular price: EUR
Sale price: USD
Sale date: active

Google expects the sale price to meet the same fundamental price and currency requirements as the regular price.

The sale price should represent the actual discounted amount available on the landing page and at checkout.

Shipping uses another currency

Shipping is one of the most common causes of inconsistent currency errors.

The product may be submitted in USD while:

Merchant Center account-level shipping uses EUR.
A product-level shipping attribute uses GBP.
A free-shipping threshold is stored in another currency.
A carrier-rate integration returns the store’s former currency.
Country-specific WooCommerce shipping rules use unconverted values.
A supplemental source supplies an outdated shipping amount.
An old feed continues to update shipping information.

Google’s international targeting guidance requires shipping information for a target country to use the same currency as the submitted product prices.

An import uses supplier currency values

A supplier file may contain prices in USD while the WooCommerce store operates in EUR.

If the import converts the product price but not the sale price, shipping charge, minimum order value or custom monetary field, the final product data becomes inconsistent.

Supplier category or warehouse feeds may also overwrite corrected WooCommerce values during the next scheduled import.

Document:

Source currency
Conversion rate
Conversion time
Converted fields
Rounding method
Target WooCommerce currency
Fields excluded from conversion
Import schedule

A controlled currency process should have one clear source of truth.

The currency symbol was mistaken for the currency code

A symbol is not always enough to identify a currency.

The $ symbol can refer to currencies including:

US dollar
Canadian dollar
Australian dollar
Singapore dollar
New Zealand dollar

Merchant product data should use the correct three-letter code, such as:

Google recommends explicit currency presentation where symbols may be ambiguous.

Do not infer the Merchant API currency solely from the WooCommerce symbol displayed beside the price. Read the actual configured currency code.

Structured data reports another currency

A WooCommerce theme, SEO plugin, schema plugin or custom code may generate Product and Offer structured data.

Possible conflicts include:

Visible price in EUR but priceCurrency set to USD
Parent-product currency differing from variation currency
Sale price visible but regular price stored in structured data
Cached JSON-LD using the previous store currency
Two schema plugins generating conflicting offers
Theme microdata and plugin JSON-LD using different currencies

Inspect every Product or Offer entity generated on the page.

Disabling one duplicate schema source may be safer than attempting to make several overlapping schema systems produce identical output.

A cache serves an old currency

Page caches, object caches, content delivery networks and reverse proxies can preserve an old currency after WooCommerce settings change.

A crawler may receive a cached USD page while a logged-in administrator sees the current EUR version.

Test the product page:

Logged out
In a private browser window
With an empty cart
Without currency cookies
From relevant target locations
On desktop and mobile
With page cache bypassed
After CDN cache purging

The public response received by customers and crawlers is more important than the administrator preview.

Several product sources control the same offer

The product price may come from PW Merchant API while shipping or another monetary value comes from:

An XML feed
A scheduled CSV file
Another WooCommerce Google plugin
A manual Merchant Center edit
A supplemental source
An ERP integration
A supplier system
An automated Merchant Center rule
An old Content API integration
A custom Merchant API connection

A manual correction may work temporarily and then disappear when another source runs.

The long-term solution is to determine which source owns each field and remove or correct competing operations.

A parent product and its variations are inconsistent

Variable WooCommerce products can produce several submitted offers.

The parent may be interpreted in EUR while one or more variations are submitted in USD. This can happen when:

Variation prices were imported separately.
A currency rule excludes certain variations.
An old value remains in variation metadata.
A default variation controls the visible page price.
The selected variation changes the page currency.
Structured data describes the parent instead of the chosen variation.
The integration reads a different price source from the landing page.

Test each affected offer against its exact variation, not only the parent product.

How to diagnose an inconsistent currency error

1. Record the exact Merchant Center issue

Open Merchant Center and navigate to the affected products in the Needs attention area.

Record:

Issue name
Offer ID
Product title
Data source
Target country
Content language
Feed label
Submitted price
Submitted currency
Detection date
Affected destinations

Google allows affected-product lists to be downloaded for comparison with the uploaded data.

Do not begin by editing a random WooCommerce product with a similar name.

2. Match the offer to WooCommerce

Use the offer ID, SKU and product URL to identify the correct WooCommerce item.

For a variable product, also record:

Parent product ID
Variation ID
Variation SKU
Item group ID
Selected attributes
Variation URL
Variation price

Confirm that the Merchant Center offer actually corresponds to the WooCommerce item being inspected.

3. Identify the authoritative source

Determine whether the affected product is created or updated through:

PW Merchant API
Another Merchant API integration
XML
CSV
Google Sheets
An automated website source
A supplemental source
A manual product entry
Another WooCommerce plugin

The source that will run again is more important than the location used for a temporary edit.

4. Check the WooCommerce base currency

In WooCommerce, review the configured store currency.

Also inspect:

Currency position
Decimal separator
Thousand separator
Number of decimals
Tax display settings
Multi-currency configuration
Geolocation rules
Currency switcher defaults

Formatting settings do not normally change the underlying ISO currency code, but custom integrations can parse formatted prices incorrectly.

5. Inspect the stored product prices

For a simple product, check:

Regular price
Sale price
Sale start date
Sale end date
Current active price
Tax status
Minimum quantity
Subscription or installment values

For a variable product, repeat the review for every affected variation.

Do not assume that the parent price represents every purchasable offer.

6. Inspect the submitted product data

Compare the WooCommerce values with the data actually sent to Google.

Record every field containing a monetary value and its currency.

A simplified comparison might look like:

Product price: 125.00 EUR
Sale price: 110.00 EUR
Shipping price: 12.00 USD
Subscription cost: not used
Minimum cart value: not used

This immediately identifies shipping as the conflicting field.

7. Inspect Merchant Center shipping settings

Review both account-level and product-level shipping configurations.

Check:

Target country
Shipping service
Shipping currency
Free-shipping threshold
Flat shipping rate
Carrier rate
Product shipping label
Product-level shipping override
Minimum order value
Handling time
Transit time

Do not convert only the visible shipping rate while leaving a threshold or override in another currency.

8. Open the public landing page

Open the exact URL submitted for the affected offer.

Confirm:

Visible product amount
Visible currency
Selected variation
Sale price
Tax presentation
Currency selector
Location selector
Availability
Add-to-cart status

Repeat the test without being logged in.

Administrator cookies and remembered currency selections can hide the public problem.

9. Inspect structured product data

Review Product and Offer structured data for:

price
priceCurrency
lowPrice
highPrice
Variation offers
Sale offer
Availability
URL

The visible page, structured data and submitted product data should describe the same offer.

10. Test the cart and checkout

Add the product to the cart and continue to checkout.

Confirm:

Product currency
Shipping currency
Discount currency
Tax currency
Order total currency
Payment gateway currency
Final payable amount

A product page that shows EUR but changes to USD during checkout does not provide a consistent purchasing experience.

11. Review country and language targeting

Check:

Target country
Data-source language
Feed label
Google Ads location targeting
Website language
Website currency
Shipping countries
Checkout availability

International targeting should be deliberate. Do not rely on an uncontrolled currency switcher to decide what Google and customers see.

12. Correct the source of the conflict

Change the authoritative configuration that created the incorrect currency.

Possible corrections include:

Aligning a shipping service with the product currency
Correcting a Merchant API currencyCode
Updating the WooCommerce base currency
Fixing a sale-price import
Correcting variation metadata
Removing a duplicate schema source
Purging stale caches
Disabling an old product source
Updating an ERP conversion rule
Creating a country-specific product source
Correcting the landing-page currency logic

Avoid changing several unrelated systems simultaneously. Controlled changes make it possible to identify the real cause.

13. Resynchronise the affected product

Send the corrected product through the authoritative integration.

Confirm that the operation is accepted, but remember that an accepted API response does not guarantee immediate approval.

Google still needs to process the product and evaluate the resulting data.

14. Inspect the processed product

Merchant API distinguishes product input data from the final processed product.

Google’s Merchant API product issue guide explains that processed products reflect data-source merging and rules. There can be a short delay between an update and the final processed state.

Verify:

Offer ID
Processed price
Processed currency
Data source
Target countries
Product issues
Destination status

This helps identify whether another source or rule changed the submitted value.

15. Check the next scheduled operation

After the next scheduled synchronisation, confirm that:

The corrected currency remains present.
The old currency has not returned.
Shipping still matches the product currency.
The page and checkout still display the same currency.
Variations remain consistent.
Another source has not overwritten the correction.

A correction that disappears after synchronisation was probably made in a secondary location.

Using currency conversion correctly

A currency different from the target country’s local currency is not automatically an error.

Google’s currency conversion documentation explains that Merchant Center can automatically show an estimated converted price in the target country’s currency.

For example, a WooCommerce store may charge in USD while advertising to eligible customers in Canada. Google can show an estimated CAD conversion in the ad or free listing while the website continues charging in USD.

For this arrangement to remain consistent:

Product data should use USD.
The landing page should show USD.
Checkout should charge in USD.
Shipping submitted for the product should use USD.
The website should clearly communicate the original currency.
Language requirements must still be met.
Shipping must support the target country.
Applicable price and tax requirements must be followed.

Do not submit CAD merely because Google displays a CAD estimate if the website actually charges USD.

Google’s converted display price and the merchant’s submitted transaction currency serve different purposes.

Merchant API currency representation

In Merchant API, a price is represented using:

amountMicros
currencyCode

Google’s Merchant API Price reference defines one standard currency unit as one million micros.

For example:

{
  "amountMicros": "125000000",
  "currencyCode": "EUR"
}

This represents 125.00 EUR.

The currency code should use a valid three-letter ISO 4217 value.

Common implementation errors include:

Sending the WooCommerce symbol instead of the code
Sending $ instead of USD
Using TL instead of the official API code TRY
Converting the amount but retaining the old currency code
Changing the currency code without converting the amount
Applying a conversion twice
Treating decimal values as micros
Reading a formatted price string
Using an outdated cached store currency
Sending price and shipping objects with different currency codes

When moving from older product integrations to Merchant API, confirm that the amount and currency are transformed together.

Updating prices through Merchant API

Google’s current Merchant API supports partial product updates for frequently changing information such as price and availability.

The frequent product updates guide explains the use of productInputs.patch and an update mask.

A partial update must still preserve consistency.

If the WooCommerce store changes from USD to EUR, updating only the product price may leave shipping, sale price or another monetary field in USD.

When a currency change affects several related fields:

Identify every dependent monetary field.
Update the complete commercial offer.
Review account-level shipping settings.
Reinsert the complete product periodically.
Inspect the processed product after data-source merging.

Currency changes should be treated as catalogue migrations, not ordinary price adjustments.

Simple WooCommerce products

For a simple product, compare:

Product ID
SKU
Regular price
Sale price
Active price
WooCommerce currency
Submitted price
Submitted currency
Shipping price and currency
Landing-page currency
Structured data currency
Checkout currency

The same underlying product should remain consistent from WooCommerce to final payment.

Variable WooCommerce products

For variable products, inspect each submitted variation.

Compare:

Parent ID
Variation ID
SKU
Offer ID
Item group ID
Variation attributes
Regular price
Sale price
Active price
Submitted currency
Landing-page selected currency
Structured data offer
Checkout currency

A single incorrect variation can remain disapproved even when the parent and other variations are correct.

If the product page displays a price range, ensure the structured data and variation selection still communicate accurate currencies.

Sale prices

A sale price must use the same currency as the regular product price.

Correct:

Regular price: 100.00 EUR
Sale price: 80.00 EUR

Incorrect:

Regular price: 100.00 EUR
Sale price: 80.00 USD

The sale price must also be available on the landing page and at checkout during the applicable sale period.

Do not use currency conversion as a way to create an artificial discount. Currency conversion and promotional pricing are separate processes.

Subscriptions, installments and member prices

More complex pricing structures require additional review.

For subscriptions, check:

Initial product price
Recurring subscription amount
Billing period
Setup fee
Trial terms
Checkout total
Submitted subscription currency

For installment products, check:

Upfront price
Down payment
Monthly amount
Number of months
Total amount
Currency of every monetary component

For loyalty or member pricing, check:

Standard public price
Member price
Membership eligibility
Currency
Landing-page explanation
Checkout behaviour

Do not place a member-only price in the ordinary product price field when Google provides a dedicated supported mechanism for the relevant programme and country.

Multi-country WooCommerce stores

A store targeting several countries can use different strategies.

One transaction currency with Google conversion

The store charges every customer in one currency. Product data, shipping, landing pages and checkout use that currency. Google may display converted estimates in eligible target countries.

Separate country-specific currencies

The store provides localised product pages and checkout flows for each country.

Each country-specific source should consistently use its intended currency.

For example:

Germany source and landing page: EUR
United Kingdom source and landing page: GBP
United States source and landing page: USD

Country-specific URLs, product data and shipping configurations should not cross unintentionally.

One uncontrolled dynamic URL

The same URL automatically changes currency using IP location, cookies or browser data.

This arrangement can be unreliable if Google and customers receive currencies that conflict with submitted product data.

Use stable URLs, parameters or localisation rules where appropriate and supported by the site architecture.

Google explains the available international combinations in its multiple target countries guidance.

Correcting a large WooCommerce catalogue

For many affected products, create a controlled audit table containing:

Offer ID
WooCommerce product ID
Variation ID
SKU
Product source
Target country
Product price
Product currency
Sale price currency
Shipping currency
Landing-page currency
Structured data currency
Checkout currency
Detected conflict
Required correction
Synchronisation status
Merchant Center status
Last verification date

Group affected products by root cause:

Incorrect account-level shipping currency
Incorrect product-level shipping currency
Old WooCommerce store currency
Multi-currency output
Variation-specific issue
Sale-price import issue
Structured data conflict
Stale cache
Supplier import
Duplicate data source
Merchant API mapping error
Unsupported currency
Target-country configuration

Correcting one shared shipping service may resolve thousands of products. Editing those products individually would waste time and could introduce new errors.

Test a small representative group before applying a catalogue-wide change.

How PW Merchant API fits into currency management

PW Merchant API is designed to support controlled WooCommerce and Google Merchant API product operations.

Depending on the installed version and supported configuration, it can help users:

Read supported WooCommerce product data.
Prepare product prices for submission.
Use the configured product currency.
Work with simple and variable products.
Create and update supported product data.
Schedule catalogue operations.
Review successful and unsuccessful operations.
Identify products requiring attention.
Maintain a more organised synchronisation workflow.

PW Merchant API can communicate the supported price and currency obtained from the authoritative WooCommerce configuration.

It cannot independently guarantee that every external system uses the same currency.

PW Merchant API cannot:

Correct an unrelated multi-currency plugin automatically.
Control another active product source.
Change Merchant Center account-level shipping without a supported operation.
Determine which currency a merchant intends to charge.
Convert product amounts safely without an approved business rule.
Correct conflicting theme or SEO structured data.
Prevent a supplier import from overwriting WooCommerce.
Guarantee immediate Merchant Center processing.
Guarantee product approval.
Guarantee Shopping ad visibility or sales.

WooCommerce remains the commercial product-data source, PW Merchant API manages supported communication and Google independently processes and evaluates the submitted offer.

Common currency correction mistakes

Changing only the currency symbol

Replacing $ with € does not convert USD values into EUR.

Changing the code without converting the amount

Changing 100 USD to 100 EUR changes the commercial price.

Converting the amount twice

A supplier import may convert USD to EUR before a multi-currency plugin converts the value again.

Ignoring shipping

Product and sale prices may be correct while the shipping service remains in another currency.

Editing only Merchant Center

A later WooCommerce synchronisation can restore the original value.

Testing while logged in

Administrator cookies may display a different currency from the public page.

Ignoring structured data

The visible price may be correct while JSON-LD reports an outdated currency.

Assuming the target country requires local transaction currency

Google currency conversion may support a non-local transaction currency when all relevant requirements are met.

Using ambiguous symbols

A dollar symbol does not identify whether the currency is USD, CAD, AUD or another dollar currency.

Using TL in API data

A website may display “TL” for customers, but the standard ISO currency code used in structured product data and Merchant API is TRY.

Forgetting variations

One variation can retain an old currency even when the parent product is correct.

Ignoring scheduled imports

A corrected value may be overwritten during the next supplier or ERP operation.

Updating the complete catalogue immediately

Test a small group before applying a new conversion or mapping rule to every product.

Frequently asked questions

What causes inconsistent currency errors in Merchant Center?

The error occurs when applicable monetary values for a product use different currencies. A common example is a product price in USD and shipping cost in EUR.

Does the WooCommerce currency symbol need to match Merchant Center?

The underlying currency must match. Display symbols may vary in format, but Merchant product data should use the correct ISO 4217 currency code.

Can I use TL instead of TRY?

You may display TL to customers if it is clear, but structured product data and Merchant API should use the official TRY code.

Can the product and shipping use different currencies?

No. Shipping submitted for the product should use the same currency as the product price.

Can the regular price and sale price use different currencies?

No. Both values describe the same product offer and should use the same currency.

Is a non-local currency always disallowed?

No. Google supports currency conversion for eligible international targeting scenarios. The submitted currency must still match the website, checkout and relevant shipping information.

Does Google convert my WooCommerce checkout currency?

No. Google may display an estimated converted price in an ad or free listing. The merchant’s website and payment process remain responsible for the actual transaction currency.

Why does Google see a different currency from me?

Possible causes include geolocation, cookies, currency-switcher settings, page caching, CDN caching, browser language or different logged-in and public sessions.

Should I disable my multi-currency plugin?

Not automatically. First determine whether it produces an unstable or conflicting experience for the submitted product URL. A correctly configured multi-currency system may be used.

Can structured data cause currency problems?

Yes. Conflicting priceCurrency values in Product or Offer structured data can make the landing page appear inconsistent.

Do I need a separate product source for every currency?

Not in every case. Google currency conversion can support one transaction currency across eligible target countries. Localised sources may be appropriate when the website genuinely provides country-specific prices and checkout currencies.

Can I correct the product directly in Merchant Center?

A direct edit may resolve a manually controlled product, but an active WooCommerce integration can overwrite the change. Correct the authoritative source whenever possible.

How does Merchant API represent currency?

Merchant API price objects use amountMicros and currencyCode. The currency code is a three-letter ISO 4217 code.

Does an accepted Merchant API operation mean the error is fixed?

Not necessarily. Google must process the submitted input, merge applicable sources and evaluate the final product.

How long does the correction take?

Processing time varies. Google notes that changes may take time to disappear from the Needs attention page. Avoid repeatedly changing a verified configuration while processing is still underway.

Can another data source restore the wrong currency?

Yes. XML feeds, supplemental sources, scheduled imports, other plugins, manual rules and ERP connections can overwrite corrected values.

Does fixing the currency guarantee approval?

No. Google evaluates other product data, landing pages, policies, account settings and destination requirements independently.

Final checklist

Before considering an inconsistent currency issue resolved, confirm that:

The exact Merchant Center issue was recorded.
All affected offer IDs were identified.
Each offer was matched to the correct WooCommerce product.
The correct variation was inspected.
The authoritative data source is known.
Competing product sources were reviewed.
The WooCommerce base currency was confirmed.
The product regular price uses the intended currency.
The sale price uses the same currency.
Product-level shipping uses the same currency.
Account-level shipping uses the same currency.
Free-shipping thresholds were reviewed.
Minimum-order values were reviewed.
Subscription values were reviewed where applicable.
Installment values were reviewed where applicable.
Member or loyalty prices were reviewed where applicable.
A valid ISO 4217 currency code is used.
A symbol was not mistaken for a currency code.
The amount was not converted twice.
The currency code was not changed without converting the amount.
Supplier imports were reviewed.
ERP conversion rules were reviewed.
Multi-currency rules were reviewed.
Geolocation behaviour was tested.
Currency cookies were cleared during testing.
The exact public product URL was opened.
The visible price and currency are correct.
Structured product data uses the correct currency.
Duplicate structured data was removed or corrected.
The selected variation displays the expected currency.
The cart uses the expected currency.
Shipping at checkout uses the expected currency.
Discounts use the expected currency.
The order total uses the expected currency.
The payment gateway accepts the intended currency.
Desktop and mobile results were checked.
Logged-out and private-browser results were checked.
Page and CDN caches were purged.
Target countries were reviewed.
Data-source language was reviewed.
Shipping countries were reviewed.
Google Ads location targeting was reviewed.
Google currency conversion was understood correctly.
The submitted currency matches the currency charged by the website.
Every relevant monetary attribute uses one currency.
The correction was made in the authoritative system.
The affected offers were resynchronised.
The operation results were checked.
The final processed products were inspected.
Google was allowed time to process the changes.
The Needs attention page was checked again.
A later scheduled operation did not restore the old currency.
A small product group was tested before bulk changes.
The final currency configuration was documented.

An inconsistent currency issue should be treated as a complete offer-consistency problem, not simply a formatting error.

The product price, sale price, shipping cost, structured data, landing page and checkout should all describe the same transaction currency. If currency conversion is used for international targeting, the original currency charged on the website must still be communicated clearly and consistently.

A reliable correction identifies the affected offer, finds every monetary value associated with it, corrects the authoritative source and verifies the processed product after the next scheduled synchronisation.

When WooCommerce, PW Merchant API, Merchant Center, the landing page and checkout all communicate the same currency, the error is less likely to return and customers receive a clearer purchasing experience.