Currency consistency
How to fix inconsistent currency in Google Merchant Center
Align the ISO currency in product data with the default landing-page price and a currency the customer can use through checkout.
Reviewed against Google Merchant Center documentation on August 25, 2026. Independent guide; not affiliated with or endorsed by Google.
What the diagnostic means
Google reports inconsistent currency when the currency submitted in product data does not match the product landing page. The same currency also needs to remain usable through checkout.
Common causes
- A regional catalog was exported with the wrong target-country currency.
- Several country feeds were accidentally combined into one file.
- The storefront geolocates visitors and changes the default currency seen by Google.
- The landing page shows the submitted currency but checkout silently switches it.
- A sale price uses a different currency from the regular price.
Resolution checklist
Fix it step by step
- Find affected examples in Merchant Center and record the submitted amount, currency, target country, and URL.
- Check the default landing-page currency without relying on a signed-in or previously localized session.
- Proceed through checkout and confirm the submitted currency can be used for payment.
- Correct the product data or storefront source of truth and split regional feeds when appropriate.
- Resubmit the data and request review only after the end-to-end values agree.
Before you resubmit
- Every price uses an ISO 4217 three-letter code such as CAD, USD, or EUR.
- Regular and sale price use the same currency for a row.
- The feed currency is the default, prominent landing-page currency for the target.
- A customer can complete payment in that currency through checkout.
Regional feed correction
Before
Canada feed price: 39.00 USD Landing page default: 39.00 CAD
After
Canada feed price: 39.00 CAD Landing page default: 39.00 CAD
Frequently asked questions
Can a site offer more than one currency?
Yes. Google says the product-data currency must be the default, prominently listed landing-page currency, and the customer must be able to select it for at least one checkout payment method.
Does a mixed-currency warning always mean the file is wrong?
No. It is a diagnostic signal. Confirm the target and submission design; some data workflows may intentionally contain multiple currencies, while many country-specific feeds should not.
Can FeedGuardrail confirm that the account warning is resolved?
No. It can find file-level currency problems. Resolution also requires checking the live landing page, checkout, Merchant Center processing, and any review instructions in the account.