How to fix invalid Google Merchant Center price format

Google feed prices need a decimal amount followed by a currency code. Currency symbols, ambiguous separators and explanatory text can prevent clean parsing.

Reviewed October 4, 2026 · Independent guidance · Static feed check with contextual limitations

What does this issue mean?

A normal price such as 19.99 USD uses a period as its decimal separator and a clear currency. A file exported with local formatting may instead contain 19,99 €, a thousands separator, or a localized label. These values require review because changing punctuation can change the intended amount. A valid format does not verify the commercial price.

Why this happens

Common sources include spreadsheet localization, price fields rendered for a storefront rather than exported as feed data, and an integration adding a currency symbol twice. A semicolon-delimited CSV can legitimately contain comma decimals in its source; delimiter detection and price interpretation are different operations. First preserve the record structure, then repair the amount deliberately.

How to diagnose and fix it

1. Check the original amount in your commerce system and identify whether punctuation is a decimal or thousands separator.
2. Use a decimal point and the actual ISO currency code, with no symbol or explanatory suffix.
3. Do not automatically convert ambiguous values such as 1,234; verify whether the amount is 1.234 or 1234.
4. Keep sale_price, base price and cost separate, regenerate the feed and scan all affected offers again.

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

id,price
MUG-01,"19,99 €"

After review

id,price
MUG-01,19.99 EUR

The illustrated conversion assumes the source amount is known. Feed Doctor flags invalid or ambiguous formats and does not infer price, currency, tax, markup or exchange rates.

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.

Frequently asked questions

Related feed issues

• How to fix missing price in a Google Shopping feed
• How to fix invalid currency codes in a Google feed
• 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.