Make product barcode labels and test printed scans
Printing an existing product identifier requires a barcode type matching its code convention. This tool does not assign product codes, so establish the source and rules of the identifier first.

How to use this tool
- Add the spreadsheet containing codes and product names.
- Select code, label-name columns and barcode type.
- Run the task and inspect PDF and SVG product details.
- Download, test-print and scan the labels.
Choose the right settings
Choose the code and display-name columns, then select Code 128, EAN-13 or EAN-8 for the actual identifier. EAN requires valid check digits as well as the correct number of digits.
- Supported input
- CSV,TSV,XLSX
- Available settings
- Key column
- Barcode type
- Label title column
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
code/name CSV → barcode label PDFExamples describe the workflow. Results depend on the source file and settings.
Check the saved result before using it
Compare product names and codes in the PDF labels, then scan a printed sample with the intended scanner. Inspect SVG outputs as well and confirm the decoded value identifies the expected product.
If the result is different from what you expected
Correct blank codes or invalid EAN values in the source before generating the labels again. If a display title is rejected for length, shorten it and inspect lettering and barcode lines.
Limits to keep in mind
- This does not assign product codes. EAN requires a valid check digit. Verify printed labels with a scanner.
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.