Mail merge, without the old Word headaches without the old Word headaches

Why Word Mail Merge Gets Frustrating

The classic Word mail merge process involves inserting merge field codes into a template document, linking the document to a spreadsheet data source, and previewing the output before completing the merge. It works — in theory. In practice, merge fields break when a template is moved or shared, formatting shifts unpredictably between records, and the output is typically one long document rather than individual files. Getting a separate, printable PDF per recipient requires additional steps that aren't obvious.

What a Modern Mail Merge Looks Like

EZdoc takes the same inputs — a document layout and a data file — but removes the friction. You describe or upload a template, connect a CSV or Excel file, and EZdoc maps the columns automatically. No merge-field syntax to learn, no fragile data source links to maintain, and no "field not found" errors when someone opens the template on a different computer. The output is one PDF per recipient, rendered consistently, delivered as a ZIP.

One File per Recipient, Not One Combined Document

The biggest structural difference from a Word mail merge is the output format. Word produces one combined document with all recipients concatenated — useful for quick review, not useful for distributing or printing individually. EZdoc produces a separate file per row. Each recipient's document stands alone, named by the data that identifies them, making it straightforward to email them individually or print them in any order.

When to Use the API Instead

For scheduled or event-driven merges — weekly renewal letters, triggered membership notices, automated billing — the REST API accepts template merge jobs from your system. Submit the data programmatically, poll the job until it completes, then download and deliver the output through your own system. The template stays the same; only the data changes with each run.

Your Existing List Works

If you've done a Word mail merge before, you already have a CSV or Excel file with your recipient data. That same file works in EZdoc without reformatting. The column headers become the field names, and EZdoc handles the mapping. The transition from a Word-based workflow to EZdoc is a data file upload, not a migration project.