Price formats and currency codes in product feeds
Technical explanation of price-cell format inconsistencies and ISO 4217 before submission
Detected Symptoms
The price column in Google Merchant Center feed files can be rejected when cell values do not match the technical format. Typical examples include thousands-separator commas, full-width digits or symbols, currency symbols before or after a number, and custom codes that do not conform to ISO 4217.
Root Causes
These issues arise from differences between domestic commercial or accounting display formats and the machine-processing specifications of advertising platforms. Websites and documents commonly add digit separators or currency symbols for readability, while Google Merchant Center's primary specifications require a fixed, machine-readable format.
Accepted input: ASCII digits (leading zeros are allowed), optionally a period or comma followed by 1–2 decimal digits, zero or more separator characters, then a three-letter ASCII currency code, in either case. Separators are characters matched by the regular expression \s (including ASCII spaces, tabs, line breaks, full-width space U+3000, NBSP U+00A0, BOM U+FEFF, and U+2029). This differs from the Unicode whitespace set: U+0085 and U+180E are not accepted. Surrounding characters matched by \s are removed before inspection, but U+0085 and U+180E remain and cause format errors even at cell boundaries. The numeric part is accepted only if conversion to a JavaScript Number produces a finite value; there is no digit-count test. For reference, 309-digit integers may be accepted or rejected depending on their value: 1 followed by 308 zeros is accepted, while 2 followed by 308 zeros is rejected.
Normalized output example: 10.00 JPY. Leading integer zeros are removed, two decimal places are used, the currency code is uppercase, and one ASCII space separates the number and currency. 10JPY, 10 JPY, 10 JPY, 10 JPY, 10.00 JPY, and 10,00 jpy all normalize to this output. This is the output in a corrected file generated with safe fixes; ordinary diagnosis without safe fixes does not apply this formatting. The screen displays findings and the number of applied changes, rather than a list of normalized cell values. Changed values appear in the downloaded change log with before/after values. A cell already in this format produces no change entry.
Official Google requirements: See the official link below (https://support.google.com/merchants/answer/6324371?hl=en). This guide does not claim that a single space is the only accepted format.
Verification Checklist & Implemented Rules
Feed Seibishi performs deterministic syntax checks locally in the browser using the following implemented specification rules.
- INVALID_PRICE: Checks the basic price-cell syntax: ASCII digits, optionally 1–2 decimal places, zero or more separators (regular expression \s; see Accepted input above), and a three-letter ASCII currency code. Thousands-separator commas, full-width digits or letters, currency symbols of either width, three or more decimal places, or a currency code that is not three ASCII letters are detected as format errors.
- INVALID_PRICE_CURRENCY: Checks whether the currency is a valid three-letter standard ISO 4217 code (for example, JPY). The testing code XTS and the no-currency code XXX are not accepted.
Official Google Documentation
For official requirements for the price attribute and data specifications, see the following Google Help documents.