How to fix invalid currency codes in a Google feed
Use the real offer currency represented by an ISO code. A three-letter string that looks like a code may still be unknown or inappropriate for the submitted offer.
Reviewed October 4, 2026 · Independent guidance · Static feed check with contextual limitations
What does this issue mean?
Currency is part of price and distinguishes values that share a symbol such as dollars. USD, EUR, GBP and JPY are codes, while US, €, dollars and localized currency names are not equivalent machine values. A valid code does not establish that your target market, page or checkout uses that currency consistently.
Why this happens
Incorrect codes may be hardcoded in a feed template, copied from a country code, or taken from storefront display text. Regional catalogs can export a base-store currency while links select another market. Changing the code alone without changing the verified amount can misrepresent the price.
How to diagnose and fix it
- Check the actual selling currency for the offer and the destination used in its product link.
- Use the correct supported ISO code next to the amount, without substituting a country abbreviation.
- Verify the amount and currency together across feed, public page and checkout.
- Regenerate the export and review regional pricing rules rather than applying a catalog-wide currency guess.
Before and after example
The examples are illustrative. Replace them with verified information for your own offer; copying an example identifier, amount or URL would introduce incorrect data.
Before
price = 19.99 USAfter review
price = 19.99 USDFeed Doctor validates format and recognized codes but does not convert currencies or determine which currency your business should use. The selected scan country is context, not permission to rewrite all prices.
Shopify fix
Find the affected product and exact variant in your Shopify catalog, then identify which product field or Google & YouTube channel setting supplies price. If a separate feed app generates your export, inspect its mapping instead of assuming the channel settings control that file. Change verified source data, save it, and obtain a fresh export.
Compare one affected variant and one previously correct offer before making a bulk change. Do not change stable IDs just to improve a report score. If the issue involves identifiers, verify whether the connector reads barcode, brand or manufacturer reference data. If it concerns a live page or shipping account setting, a feed-column edit alone may not resolve it.
WooCommerce fix
Open the relevant product or variation and inspect the attribute consumed by your Google feed integration. Google for WooCommerce can map product attributes into feed attributes; third-party feed generators may use different mappings. Check both the stored value and the exported result, especially when parent attributes are inherited by variations.
Update the source value or mapping deliberately and regenerate the feed. Keep product identity, currency and variant relationships consistent. Avoid editing only a downloaded snapshot if a scheduled exporter will replace that change. For an account or website issue, repair the effective configuration and public offer as well as reviewing the file.
Verify the repair before submitting
Keep the original feed as a backup and compare the same affected product IDs in the regenerated file. Confirm that the expected product count remains unchanged and that no unrelated fields disappeared. If you applied a bulk rule, inspect offers outside the original affected set as a control; an overly broad mapping can fix one problem while creating another.
Run a new static scan, then separately check live product information and your Merchant Center diagnostics. File format validation cannot determine every policy, account, image or website condition. Processing and recrawling take place in Google’s systems, so a corrected file is not an immediate promise of approval. Use the actual updated diagnostics to decide whether additional investigation is required.
Scan your feed for this issue
Check all parsed products in an XML, CSV or TSV feed. Preview the score and issue samples free; unlock affected-product details and downloadable reports with a one-time payment. Conditional findings remain marked for review.
Check My FeedFrequently asked questions
Does this finding always mean my product is disapproved?
Feed Doctor validates format and recognized codes but does not convert currencies or determine which currency your business should use. The selected scan country is context, not permission to rewrite all prices.
Can Feed Doctor fix price automatically?
Only deterministic formatting changes are available in Fix & Export. Missing identifiers, prices, business facts and ambiguous values require manual action. Review every change and remaining finding before submitting a repaired feed.
Should I fix the exported file or my store?
Correct the source product or feed integration whenever possible. A downloaded file edit may be overwritten by the next scheduled export. Keep a backup and compare the exact affected IDs in a fresh feed snapshot.
Do I need to connect Google to scan a feed?
No. Feed Doctor accepts a Google-format XML, CSV or TSV file, or a public HTTPS feed URL. It checks the feed without accessing your Merchant Center account. Reports are private to your browser and expire after 7 days.
Related feed issues
- How to add a missing currency to Google feed prices
- How to fix invalid Google Merchant Center price format
- How to investigate price mismatch in Merchant Center
Official references: Google product data specification, Shopify Google & YouTube requirements, WooCommerce attribute mapping. Requirements can vary by product, country and account setup.