Practical guidance
Review ambiguous prices and decimal separators
A comma can separate columns or be part of a price. Even after parsing succeeds, the intended number can remain ambiguous.
Ask two different questions
First ask whether the CSV cell was parsed correctly. Then ask what that cell means. In the example below, quotes make 1,250 one cell, but they do not establish whether it means one thousand two hundred fifty or one and a quarter.
SKU,Price
00031,"1,250"Use evidence before normalizing
- Confirm the currency and locale of the source export.
- Compare the value with the original price list or product record.
- Choose the intended decimal representation explicitly.
- Review totals and outliers after the edit, then revalidate the file.
Keep units with their meaning
A weight of 2.5 without a unit cannot safely become 2500 grams. The same principle applies to prices with unexpected currency symbols and counts described in cases rather than units. A useful finding identifies the missing evidence instead of manufacturing a value.
What this check cannot establish
Golanto reports uncertainty and leaves ambiguous values for review. It does not infer currency conversions, tax treatment, exchange rates, stock, or physical units.
Check your file
Start with a copy. Review changes before downloading your import file.
Open the CSV tool