Supplier price CSV encoding errors: how to fix them

A supplier sends a price list as a CSV, but some names or currency symbols look wrong when you open it. You might see text such as Café instead of Café, or an unexpected character before a pound sign. That can make a review hard to trust, especially when you are checking product names, prices, and item IDs.

These characters are often an encoding mismatch: the file’s text was read using a different character set than the one used to save it. You can inspect a local copy with the CSV Editor, identify what went wrong, and verify a corrected copy before sending it back.

Check the supplier price CSV

1. Make a copy of the original file, then open the copy in the CSV Editor. Check a few supplier names, product descriptions, currency symbols, and item IDs against the supplier’s source document.
2. Write down examples of what looks wrong and what you expect to see. For example, note whether Café should be Café, or whether a symbol appears as extra characters.
3. Check whether the problem affects text only. Compare several prices, decimal points, thousands separators, and IDs with the source list. Do not assume that a plausible-looking price is correct.
4. Open the unchanged copy using your spreadsheet program’s text import option, if available. Review its preview and encoding choices before loading the rows. Try UTF-8 first for a modern supplier export, or use the encoding specified by the supplier if they provide one.
5. Save any correction as a separate file. Reopen that file and compare the same names, symbols, prices, and IDs before using it for the review.

The CSV Editor can help you inspect, find, and edit rows in a file, but do not assume that editing a cell will repair the file’s original encoding. Keep the untouched source until the corrected copy has passed your checks.

What the characters tell you

Accented letters appear as extra characters

A name such as Café appearing as Café is a common sign that UTF-8 text was interpreted using a different encoding. UTF-8 is a way to represent text as bytes, the stored values in a file. If software reads those bytes using the wrong rules, the letters can turn into mojibake, meaning garbled text created by a decoding mismatch.

A currency symbol has extra marks

A pound sign might appear with an unexpected prefix, or a symbol may become a question mark. Check the exact value against the supplier’s original document. A question mark or replacement character can mean the original character was lost when another program saved the file. Changing the encoding after that may not restore it.

The text looks fine, but columns or prices do not

Encoding controls how text characters are read. It does not usually change a comma into a decimal point or decide where columns split. If a price appears in the wrong column, or a value such as 12,50 is divided unexpectedly, check the CSV delimiter and number format as separate issues.

Item IDs have lost leading zeros

An ID such as 004812 may be treated as a number and displayed as 4812. That is a data type or spreadsheet import issue, not an encoding problem. Keep identifiers as text and compare them with the source. For more detail, see how to fix leading zeros disappearing in a supplier catalog.

Fix the encoding without changing the prices

1. Keep the original unchanged. Duplicate the supplier’s file before testing different import options. If a previous attempt has already replaced characters with question marks, return to the original download instead of making more changes to the damaged copy.
2. Confirm what the text should say. Compare a few distinctive names and symbols with the supplier’s invoice, website, or another trusted source. One example may be a typo in the supplier data, so check several affected rows before deciding that the whole file has an encoding problem.
3. Use the import preview to test an encoding. In a spreadsheet program, choose its option for importing text or CSV and inspect the preview before loading the file. UTF-8 is a sensible first choice for current exports. If the supplier identifies a different encoding, try that instead. Choose the version that displays the known names and symbols correctly.
4. Save a new UTF-8 copy. Once the text is correct, export or save a separate copy using UTF-8 if the program offers that choice. Keep the supplier’s original file and do not overwrite it. Encoding conversion changes how the text is stored, while selecting an encoding during import changes how the existing bytes are interpreted.
5. Compare the business-critical fields. Reopen the saved copy and check at least a few low and high prices, decimal places, currency symbols, product IDs, and supplier names. Compare these directly with the source, especially if the file uses commas inside quoted descriptions or prices.
6. Ask for a clean export if characters remain missing. If the original already contains replacement characters, or no encoding option displays the expected text, ask the supplier to export the file again as UTF-8 or send another source format. Avoid guessing at missing names or prices.

Keep encoding separate from CSV structure

A CSV is plain text organized into rows and columns. Encoding describes how the text is represented; a delimiter, such as a comma or semicolon, separates columns. A file can have the correct encoding and still open incorrectly if the program expects the wrong delimiter. It can also display readable text while silently changing an ID into a number.

For a supplier-price review, treat the file as unverified until both the text and the figures match the source. If you need a broader checklist for encoding, see how to check a CSV file’s encoding before import.

The CSV Editor runs in your browser, and the file you open stays on your device.