Two hundred certificates, each with a different name. Or ninety invoices, or a rent review letter to every tenant, or name badges for a conference. Someone is about to copy a template two hundred times and change one field in each, and that afternoon is gone.
Mail merge in Word is the feature that removes that job, and it remains one of the most underused things in Office — mostly because people meet it once, hit a formatting problem, and never return to it.
This guide covers how it actually works, how to structure the data so it behaves, the formatting problems that catch everyone, and the situations where mail merge is the wrong tool.
What Mail Merge Does
Mail merge combines two things: a main document containing the layout and fixed text, and a data source containing one row per recipient. Word produces one output per row, substituting the variable fields.
That is the whole concept. The complexity is entirely in the data and the formatting.
It can produce letters, emails, envelopes, labels, and a directory — which is the option that catches people out, because it merges multiple records onto one page rather than one record per page. Certificates, badges and invoices are just letters with a different layout.
Start With the Data
Most mail merge problems are data problems wearing a formatting costume. Getting the spreadsheet right first removes the majority of them.
Structure
- One header row, in row 1, with no blank rows above it and no merged cells anywhere.
- One record per row, with no blank rows in the middle of the data.
- Simple column names without spaces or punctuation —
FirstNamerather thanFirst Name (legal). Word copes with spaces but they make everything harder to read in the field list. - One piece of information per column. Splitting a full name into first and last is what lets you write "Dear Sarah" rather than "Dear Sarah Whitfield".
- Everything on one sheet, with the data as the only thing on it.
Content
- Clean it before merging. Trailing spaces, inconsistent capitalisation and missing values all appear verbatim in the output. Two hundred letters addressed to "dear sarah" is a real outcome.
- Decide what happens when a field is empty. A blank in an address column leaves a gap in the letter unless you handle it.
- Format numbers and dates as you want them to read. More on this below, because it is the classic failure.
- Check for duplicates before merging rather than after printing.
The Formatting Problem Everyone Hits
You merge a currency column and the letter says 1250 instead of £1,250.00. Or a date column produces 3/4/2026 0:00:00. This is the single most common reason people abandon mail merge.
The cause: Word does not inherit Excel's cell formatting. Excel shows you a formatted display of an underlying raw value, and mail merge takes the raw value.
There are two fixes, and the second is the one worth learning.
Fix one: format in the source. Add a column in Excel that produces the text you want as actual text, using a formula, and merge that column instead. Simple, reliable, and clutters the spreadsheet.
Fix two: add a numeric or date picture switch to the merge field. In Word, revealing the field code (Alt+F9 toggles this) shows something like { MERGEFIELD Amount }. Adding a formatting switch controls the output directly:
{ MERGEFIELD Amount \# "£#,##0.00" }produces £1,250.00{ MERGEFIELD StartDate \@ "d MMMM yyyy" }produces 3 April 2026{ MERGEFIELD Surname \* Upper }produces uppercase text
After editing a field code, press F9 to update it. This is the mechanism that makes mail merge genuinely usable for invoices, statements and anything involving money or dates.
Switches worth knowing
| Switch | Produces | Use for |
|---|---|---|
\# "£#,##0.00" | £1,250.00 | Currency amounts |
\# "#,##0" | 1,250 | Whole numbers with separators |
\# "0.00%" | 12.50% | Percentages |
\@ "d MMMM yyyy" | 3 April 2026 | Formal letter dates |
\@ "dd/MM/yyyy" | 03/04/2026 | Short dates |
\* Upper | WHITFIELD | Surnames on labels or badges |
\* FirstCap | Sarah | Cleaning inconsistent capitalisation |
One caution on dates: the pattern uses capital MM for months and lowercase mm for minutes. Getting those the wrong way round produces a date that looks plausible and is wrong, which is exactly the kind of error that reaches two hundred letters.
Conditional Content
The feature that turns mail merge from a name-substitution tool into something that handles real business correspondence.
An IF field lets the document change based on the data. Insert it through the rules menu, or write it directly in the field code. In plain terms:
- If the balance is over zero, include a payment paragraph; otherwise include a thank-you paragraph.
- If the membership type is "Corporate", show a different set of terms.
- If the second address line is empty, skip it rather than leaving a blank line.
That last case is worth setting up as standard, because empty address lines are the most visible sign that a letter was machine-produced.
A related rule, Skip Record If, lets you exclude rows without editing the data source — useful when the same spreadsheet feeds several different mailings.
Running the Merge
- Prepare and save the data source and close it in Excel. An open file can cause connection problems.
- Set up the main document with all fixed text and layout finished. Formatting after merging means formatting every copy.
- Connect the data source and, if prompted about how to connect, choose the option that preserves formatting where it matters.
- Insert merge fields, adding format switches where numbers or dates are involved.
- Add rules for conditional content.
- Preview results and step through several records — not just the first. Check the longest name, the missing address line, the largest number.
- Check for errors using the built-in check, which flags missing fields before you commit.
- Finish the merge to a new document rather than directly to the printer, so you can inspect the output.
- Scan the merged document, particularly the first, last and a few random pages.
Merging to Email
Word can send the merged output as email through Outlook, with one field supplying the address.
Practical constraints worth knowing before planning around it:
- Each message sends individually, so recipients do not see each other — which is the main advantage over a bulk BCC.
- Attachments are not supported natively. If every recipient needs a personalised attachment, mail merge alone will not do it.
- Formatting can shift between Word and the email client. Keep the design simple.
- Volume limits apply at the mail server level, not in Word. Large sends can trip sending limits or spam filters.
- There is no tracking and no unsubscribe handling. For marketing email, a proper email platform is the right tool and may be a legal requirement depending on your jurisdiction.
Mail merge to email suits internal or transactional correspondence to a known list. It is not a marketing tool.
Common Mistakes
- Merged cells or multiple header rows in the data source, which Word cannot interpret.
- Formatting the main document after merging instead of before.
- Currency and dates left unformatted, producing raw values.
- Previewing only the first record, then discovering the problem in copy 140.
- Blank lines from empty fields, unhandled.
- Merging straight to the printer.
- Full names in one column, making informal greetings impossible.
- Dirty data merged as-is — trailing spaces and inconsistent capitalisation.
- Using it for marketing email where a proper platform is needed.
- Not saving the main document with its data connection, so the whole setup is rebuilt next time.
When Mail Merge Is the Wrong Tool
- Personalised attachments per recipient. Word cannot do this natively.
- Marketing email at scale, where tracking, unsubscribe handling and deliverability matter.
- Documents needing a signature from each recipient, which belongs in a form or signing workflow — see professional fillable PDF forms.
- Data collection rather than distribution. If you need information back, you need a form, not a merge.
- Highly designed output such as certificates with complex layouts, where a design application handles variable data more gracefully.
- Genuinely one-off jobs of a handful of documents, where setup time exceeds the saving.
Making It Reusable
The real return comes from treating the merge as an asset rather than a task. A main document saved with its data connection, a data template with the correct column structure, and documented field names mean the next run is minutes rather than an afternoon.
For documents produced regularly — monthly statements, renewal notices, certificates after every course — this is where the time actually goes. The underlying document should also be built on proper Word styles so it stays maintainable, which is the same groundwork described in professional Microsoft Word formatting.
Conclusion
Mail merge is straightforward once you accept that it is a data exercise with a document attached. Structure the spreadsheet properly, use format switches for anything involving money or dates, handle empty fields with conditional rules, and always merge to a document before printing.
Set up once and saved properly, it converts a recurring afternoon into a five-minute job — which is the whole reason the feature exists.
Getting Merge Documents Built
SBTEXMEDIA sets up Word mail merge documents and templates for businesses, HR teams, schools, clinics, membership organisations and non-profits — main documents built on proper styles, data source structure and cleanup, format switches for currency and dates, conditional content for optional paragraphs and address lines, and reusable templates saved with their connections so future runs take minutes. Existing merge documents that have stopped working can be diagnosed and rebuilt.
Related work on Word document formatting and Excel templates is handled by the same team, which matters because the data source is usually half the job.
You can see examples on the portfolio, browse the full range of services, or send your template and a sample of your data for a fixed quote and a delivery date before work begins. More guides are on the SBTEXMEDIA blog.