Supplier data handoff for a large dataset

A supplier file can look complete and still cause trouble after it reaches the next team. A missing header, a changed product ID, or dates written in mixed formats may break an import or make records hard to match.

Before you send a large CSV, check its structure, look for inconsistencies, and keep a clean copy of the original. The CSV Editor opens CSV files up to 10 million rows in your browser and can help you find, edit, sort, and remove duplicate rows.

Check the supplier file before handoff

1. Keep an untouched copy of the supplier's original file. Open a working copy in the CSV Editor so you can inspect the data without risking your source file.
2. Check the header row. Look for blank or repeated column names, spelling differences, and columns that have shifted into the wrong place.
3. Search for a few known records, such as a supplier ID, product code, or product name. Check that the expected values appear under the correct headers.
4. Sort or search important fields to spot inconsistent values. Check IDs, dates, prices, units, and required fields, including entries near the beginning and end of the file.
5. Review repeated rows before removing anything. Use the editor to remove exact duplicates only when you are sure they are accidental, then keep a note of what changed.

A browser can handle a large file more easily than many spreadsheet apps, but performance still depends on your computer's memory and other open tabs. If the file takes a long time to load, close other tabs and applications, then try again with the working copy.

What your checks can reveal

Headers are missing, repeated, or unclear

A receiving system often uses column names to map each value to a field. A blank header or two columns called Code can make the destination system guess incorrectly. Ask the supplier which field each unclear column represents, and agree on one clear header for each field before changing it.

Values appear in the wrong columns

A comma inside a product description can be mistaken for a column break if the CSV quoting is malformed. If a row has more or fewer fields than expected, do not repair it by shifting cells by eye. Compare it with the supplier's source record, correct the structure in a copy, and check the same row again.

An ID has lost leading zeros

Codes such as 001284 are identifiers, not quantities. If a system turns one into 1284, it may no longer match the supplier's record. Treat identifiers as text throughout the handoff. For more on this issue, see why leading zeros disappear from CSV data.

Dates, prices, or units vary between rows

A date such as 04/05/2025 can mean different days in different locales. Prices may mix decimal points and commas, while weights may appear in both kilograms and pounds. Ask the supplier for the intended format and unit, then make the file consistent without guessing what an ambiguous value means.

Repeated records may not be duplicates

Two rows with the same supplier ID can represent separate products, locations, or price periods. Removing repeated rows without checking their other fields can discard valid data. Exact repeated rows are easier to identify, but still confirm the supplier's rules before deleting them.

How to fix common handoff problems

1. Confirm the expected format. Ask the receiving team which columns are required, what each field means, and which date, number, and unit formats it accepts. Do not rely on a previous file unless the requirements are still current.
2. Protect the source file. Save a separate working copy before editing. Keep the original unchanged so you can compare the delivered version with the supplier's file or redo a correction.
3. Repair headers first. Use one clear, unique header per column. Keep the agreed column order if the receiving system expects it, and document any renamed fields.
4. Check IDs as text. Preserve leading zeros, letters, and punctuation in product and supplier codes. Do not sort or calculate these fields as if they were numbers.
5. Standardize only confirmed values. Fix inconsistent date formats, units, and spelling after confirming the intended value. Leave uncertain rows unchanged and ask the supplier to clarify them.
6. Review duplicates with context. Search for repeated IDs and compare the full rows. Remove exact duplicate rows only when they are genuinely repeated by mistake. Keep separate records when another field explains the difference.
7. Check the cleaned copy again. Search for the values you changed, review sample rows from different parts of the file, and compare the final row count with the source. Explain any intentional removals or additions in the handoff note.

Send enough information with the file

A useful handoff includes more than the CSV. Tell the receiving person where the data came from, when it was received, what you changed, and what still needs review. Include the column definitions, expected date and number formats, and the supplier's contact for questions.

• File details: Give the file a clear name and state whether it is the original or a cleaned copy.
• Scope: Record the period covered, the supplier, and the expected record count when you have that information.
• Changes: List renamed headers, standardized values, and any duplicate rows removed.
• Open questions: Identify ambiguous prices, missing values, or records that need supplier confirmation.
• Privacy: Remove personal or confidential fields that the receiving team does not need. Share the file only through an approved channel.

The CSV Editor works in your browser, and files you open stay on your device. Check your organization's rules before using a browser tool with confidential supplier information.