Join two spreadsheets by code and review unmatched rows
Adding product details to orders requires matching codes across two spreadsheets. Choose the join type according to which records from the first spreadsheet you need to retain.

How to use this tool
- Add the main spreadsheet first and the reference spreadsheet second.
- Select both key columns and a left or inner join.
- Run the task and inspect unmatched codes and added fields.
- Download the joined result and report.
Choose the right settings
Add the main spreadsheet first and the reference spreadsheet second, then select their code columns. Use left to retain all main records or inner to retain only matched records.
Before you start
Establish the meaning of the input
Before converting or arranging data, identify what a row or value represents and keep a source copy. In tabular files, review headers, separators and text encoding; in structured files, inspect the required object or array shape. Identifiers, dates and amounts should not be interpreted solely from how a spreadsheet happens to display them.
Where the tool offers matching columns, type rules or output fields, choose them according to the destination’s requirements. Test a sample with a blank, a repeated value and a value containing punctuation. For labels, charts or personalized documents, check which column supplies each displayed value and whether the source units and wording are correct.
Define a few checks before processing: an identifier that must retain its spelling, a value with a known interpretation and an expected relationship between records. If the tool offers type conversion or matching rules, distinguish a source value from the program’s display of it. Test ambiguous dates or differently written keys before accepting a broad rule. Keep the chosen rules and destination requirements with the result; this makes a discrepancy traceable to input, interpretation or the requested transformation.
Verify values, structure and exceptions
Reopen or import the result using the destination’s settings. Compare headers, record counts and several values with the source, allowing for the operation you requested. A summary, split or duplicate-removal task can legitimately change the count; verify why it changed rather than expecting every transformation to keep identical rows.
Inspect any exception or validation report before continuing. If columns shift, characters are garbled or a key is not found, check delimiters, encoding and exact header spelling first. Encoding data does not encrypt it, and formatting a value does not confirm its meaning. For printed codes or labels, test the actual output before making the full set.
Example input and output
orders + product catalog + code → joined spreadsheetExamples describe the workflow. Results depend on the source file and settings.
Check the saved result before using it
Inspect unmatched codes and the output row count before relying on the joined spreadsheet. Compare added fields such as product names with the corresponding codes in the original reference spreadsheet.
If the result is different from what you expected
Duplicate keys in the reference spreadsheet prevent a single matching record from being selected and are rejected. For missing matches, compare spaces, letter case and leading zeros across both code columns.
Limits to keep in mind
- Duplicate keys in the second spreadsheet are rejected instead of unexpectedly multiplying rows. Inspect unmatched codes in the result.
Continue with a related tool
This guide explains the public browser tool. Keep a copy of the original and inspect the result before sharing it.