What is a merge-purge workflow for mailing lists?

What does merge-purge mean in direct mail?

Merge-purge is the process of merging two or more mailing-list sources, then purging records that should not appear in the final send file. The purge can remove duplicates, suppressed contacts, missing-address records, stale records, or records that fail the campaign's send rules.

The term sounds mechanical, but the workflow is a business decision layer. When the same household appears in three source files, the system must decide whether to mail once, which record wins, which fields survive, and how to explain that decision later.

Why does merge-purge matter before a postcard campaign?

Merge-purge matters because duplicate and conflicting records can waste pieces, create confusing customer experiences, and make campaign attribution harder to read. A clean workflow gives operators one final audience file, a clear suppression count, and a record of why each record was kept or removed.

For example, a real estate list, a CRM export, and a past-customer file may all contain the same address. Without a merge-purge step, a campaign can print multiple postcards for the same household or let a do-not-mail record re-enter the send file through another source.

What fields should be standardized before matching records?

Teams should standardize enough fields to make matching fair before they look for duplicates. Street address, city, state, ZIP Code, secondary-unit details, recipient name, company name, phone, email, source ID, and suppression flags should be normalized as much as possible before rules compare records.

USPS Publication 28 is the main Postal Explorer reference for postal addressing standards, including delivery address lines, last lines, secondary unit designators, street suffixes, and standardized formats. PostalPro also explains that address correction software standardizes spelling, abbreviations, and capitalization as part of postal address-quality processing.

For a deeper address-quality primer, read what address standardization means for direct mail.

What decisions belong in a merge-purge workflow?

A merge-purge workflow should make each keep-or-remove decision explicit. The table below is the minimum decision record a direct-mail team should expect before a campaign goes to production.

How should duplicates be matched and retained?

Duplicate matching should use a written rule, not an ad hoc spreadsheet sort. A team can match by exact address, household, person, company, email, phone, or source ID, then choose one survivor according to source priority, freshness, completeness, and suppression status.

Direct-mail teams should be careful with secondary units. Two records at the same street address may be different apartments, suites, tenants, owners, or businesses. A good merge-purge workflow keeps uncertain matches in an exception file instead of silently deleting them.

How do suppression rules fit into merge-purge?

Suppression rules remove records that should not be mailed for this campaign. The suppression list can include do-not-mail records, prior customers, recent recipients, bad-address flags, internal exclusions, geography exclusions, or contacts that belong to another campaign audience.

The important part is traceability. If a record is removed, the workflow should save which suppression rule removed it and which source supplied that rule. That makes it possible to explain why the final mailing count is smaller than the imported count.

How does merge-purge differ from NCOA and address standardization?

Merge-purge decides which audience records survive. Address standardization cleans the address format so records can be compared and prepared for mail. NCOA-style move-update processing checks mailing records against change-of-address data. They are related controls, but they answer different questions.

PostalPro describes Address Quality Solutions as a way to help business customers manage mailing-list quality, and it separately describes Move Update and NCOALink as change-of-address tools for updating mailing lists before mailing. Merge-purge should sit around those checks, not pretend to replace them.

For the move-update side, read the NCOA guide for direct mail workflows.

What should teams save after merge-purge?

Teams should save the source-file names, import time, rule version, match keys, suppression sources, counts removed, exception file, final output count, approver, and timestamp. The goal is to make the send file explainable without reopening every source spreadsheet.

This record helps operators debug future complaints, reconcile counts, avoid duplicate sends, and understand whether a later campaign used the same rules. It is also the difference between “we cleaned the list” and “we can explain exactly how the final audience was built.”

How does Sendvo fit merge-purge workflows?

Sendvo is in beta as a self-service direct-mail platform. Current public materials describe audience building, browser-based postcard design, USPS tracking, triggered sends, integrations, and an API surface at api.sendvo.io. For merge-purge work, the practical evaluation question is whether the operator can keep source records, suppression decisions, proofing, and send state connected.

This article stays category-focused. It does not claim a specific merge-purge feature, address-certification result, delivery-time result, price, integration behavior, or customer outcome.