Home / Data Merge Production / Data Merge CSV Preflight Checker

Variable print · source preparation

Data Merge CSV Preflight Checker

Find source-table problems before linking a variable-print template: exact record locations, duplicate IDs, image-header traps and identifiers that must remain text.

Files stay on this device. No upload or account required.

Enter the source and job settings, then run the check.

What this calculator solves

A data-merge source can be structurally readable yet unsuitable for a production run. An empty name, duplicated recipient ID or damaged reference number may survive a successful import and appear on hundreds of printed pieces. This checker separates broken CSV structure from job-specific data warnings. Use it when receiving customer exports, before linking fields to artwork, and again after an approved correction. It does not create merged pages or decide whether a customer is authorized to use the data.

How to choose the inputs

Paste comma, tab or semicolon data with a header, or select a local CSV/TXT file. A selected file takes priority over pasted text until Reset clears it. Choose the delimiter explicitly when automatic detection is ambiguous. File encoding describes the actual saved bytes, not the language of the names. UTF-8 is the default; Windows-1252 and UTF-16LE are explicit alternatives. Required names must exactly match exported headers. Choose a genuinely unique job ID only when the business rules require uniqueness; two recipients may legitimately share a surname.

How the calculation works

The parser retains every cell as a string and reads quoted separators, doubled quotes and quoted line breaks. Unescaped or unclosed quotes stop processing with a physical-line explanation rather than silently combining records. Once parsed, header count is compared with each record, blank and duplicate headers are listed, required cells are checked, and the optional ID field is reconciled. Leading-zero numbers, identifiers longer than fifteen digits, formula-like values and selected invisible characters are warnings. They are never automatically converted or deleted.

Worked production example

A three-record badge file contains IDs 001, 002 and 003 with a required Name column. All three IDs trigger leading-zero warnings but remain unchanged. If record 2 is changed to ID 001, the checker also reports a duplicate ID referencing record 1. Clearing its Name produces a separate required-value error. Adding a comma to an unquoted company name creates an extra cell and a row-width error. Correcting that company cell to a quoted CSV value fixes the structural error without deleting the company punctuation.

How to interpret the result

Errors identify conflicts with the selected source contract; warnings identify values needing human review. Zero errors is not artwork approval. Download the issue report for the data owner and retain the unchanged original alongside the corrected export. Report record numbers exclude the header; structural width errors also name the physical line, because one quoted record can occupy several lines. Review leading zeros before reopening files in a spreadsheet, then use the image matcher on the same approved source revision. No report is sent to this website.

Common production mistakes

Do not mark every column as a unique key, strip all punctuation to make a warning disappear, or mistake the apostrophe visible in a spreadsheet editor for the literal CSV header. Image fields commonly begin with @; a literal apostrophe exported before that symbol deserves inspection. CSV quoting protects delimiters, not spreadsheet formula execution. Re-saving a long account number after numeric coercion cannot recover lost digits. A browser checker also cannot repair version-specific import bugs by declaring every otherwise valid source defective.

Production assumptions and limitations

Processing is limited to 2 MiB, 20,000 records and 100 source columns per run. XLSX workbooks, formulas, cell formatting and database relationships are not imported. The checker cannot determine whether an address is deliverable, an ID is assigned to the correct person, an image exists or text fits its frame. Encoding compatibility varies by compositor version and selected import settings. The exported report prefixes potentially executable spreadsheet text as a precaution; it is a diagnostic report, not a replacement production source.

Related production workflow and sources

Continue with the Data Merge Image Asset Matcher, then prepare record order in the Cut-and-Stack CSV Sequencer. The production preflight guide explains release checks. CSV parsing is based on RFC 4180 conventions; application behavior remains governed by Adobe's data-merge documentation. Last reviewed: 2026-10-26.