Product feed price: check the amount and currency format
When a price-format issue appears, first verify the amount and currency against your product records. Then normalize the representation and compare the corrected file with its change log.
View the synthetic example · Pre-submission checklist · Free diagnostics
Check amount, decimals and currency
Google specifies a number and an ISO 4217 currency code, with 15.00 USD as a text-file example. The amount and currency must also match the landing page and checkout. This format checker cannot verify that match.
This tool checks an ASCII number, one or two decimal places if present, and a three-letter ASCII currency code. The value 8 EUR is accepted for inspection and becomes 8.00 EUR with safe fixes. Acceptance does not establish that a selling price is correct or approved by Google.
The tool does not infer a replacement amount for ¥1,200, 1,200 JPY, 100 JPY or 10.123 JPY. For INVALID_PRICE, check separators, full-width characters and decimal places; for INVALID_PRICE_CURRENCY, verify the currency code. Do not remove commas by guessing their meaning.
Compare values before and after safe fixes
The synthetic example records 010,00 jpy → 10.00 JPY and 8 EUR → 8.00 EUR. Do not generalize this decimal-comma example to thousands separators. The tool does not invent prices or convert currencies.
The screen shows findings and the number of changes. Check corrected cell values in the downloaded feed and change JSON. A value already in normalized form produces no change entry.
Try the two-product demonstration
This local demonstration uses two fictional products, not customer results. The example.test URLs are placeholders, not real product pages. The displayed seller identity is synthetic too.
Save synthetic input · Corrected example · Change-log example
Open free diagnostics, select the saved synthetic input and run inspection. Before fixes: two errors and one identifier warning. After safe fixes: six changes, zero errors and one warning. Price and header normalization are recorded separately from the diagnostic error count.
| Row and column | Before | After |
|---|---|---|
1 · id
|
ID
|
id
|
1 · title
|
Title
|
title
|
2 · price
|
010,00 jpy
|
10.00 JPY
|
2 · availability
|
In Stock
|
in_stock
|
3 · price
|
8 EUR
|
8.00 EUR
|
3 · availability
|
Out of Stock
|
out_of_stock
|
MISSING_PRODUCT_IDENTIFIER remains after fixes. Do not infer a GTIN, brand, MPN or a “no identifier” setting. Investigate actual product identifiers and applicable requirements. Do not submit this synthetic example as real product data.
Save for later: pre-submission checklist
- Keep the original under a separate name. Do not overwrite it with the corrected file.
- Check the delimiter, required columns, row cell counts, empty values, duplicate IDs and product count.
- Match amount, currency and decimals to product records. Verify landing-page and checkout prices.
- Save the corrected feed and change JSON separately. Review before/after values, rows, columns and reasons. Investigate unexpected changes before submitting.
- Review remaining warnings. Do not invent product facts such as GTIN, brand or MPN. Verify actual information and the applicable Google requirements.
- Separately check actual stock, URL reachability, images, policy compliance and Google processing results. Format checks do not guarantee approval. Pause submission while problems or uncertainties remain.
Bookmark this section or use your browser’s Print to save it as a PDF checklist. This checklist does not save your selected feed or results.
Inspect your own file for free
All-row diagnostics are free within 5 MiB. Corrected-feed and change-log export are free for up to 50 products. Feeds with 51 or more products can still be diagnosed free within 5 MiB. Feed data is processed in your browser without uploading your catalog to an application server.