What is a deliverability check for direct mail?

A practical guide to deciding whether a mailing record is ready, should be held, or should be excluded before print: address readiness, suppression, duplicate windows, move signals, proofing, and campaign records.

What is a deliverability check for direct mail?

A deliverability check is the operational review that happens before a direct mail record moves to print. It does not guarantee delivery. It decides whether the record is ready enough for release, needs correction, should be held, or should be excluded.

The check should preserve the reason behind every decision. A record that fails because of a missing secondary unit, a suppression match, a recent duplicate send, or an unapproved proof should not disappear into a generic error bucket. The workflow should keep the source record, check result, reviewer, and final action visible.

How is a deliverability check different from address validation?

Address validation is one input. A direct mail deliverability check is broader because it also reviews suppression rules, duplicate-send windows, source-system conflicts, proof readiness, campaign metadata, and hold-or-release decisions.

For address-specific readiness, see the mailable address guide and the address standardization guide. A mailing workflow still needs additional controls after the address looks normalized.

What fields should the check review?

A practical check reviews address completeness, standardized address state, move or returned-mail signals, suppression matches, duplicate-send history, proof status, variable-data readiness, campaign IDs, batch eligibility, and the final hold or release reason.

Check area	Question it answers	Safe workflow outcome
Address completeness	Is the record complete enough for addressing review?	Release, correct, or hold with a missing-field reason.
Standardization state	Has the address been normalized against an address standard?	Keep source and standardized forms visible for review.
Move and ACS signals	Is there a change-of-address or post-mailing feedback signal to consider?	Route to update, suppress, or manual review based on policy.
Suppression match	Should this person, household, or address be excluded?	Exclude or hold with the suppression reason and scope.
Duplicate-send window	Was a similar piece sent recently?	Hold for duplicate review or approve a documented exception.
Proof readiness	Is the creative approved for this data state?	Hold until the proof version and fallback fields are approved.
Campaign metadata	Can the send be measured later?	Attach campaign ID, batch ID, tracking fields, and response sources.

What should teams do with records that fail the check?

Teams should separate failed records into clear outcomes: correct and retry, hold for manual review, suppress for a documented reason, or release only after an approved exception. The final action should stay attached to the record.

This prevents the same record from being reconsidered from scratch during the next import or trigger. For exclusion logic, see the suppression list guide. For repeated-send controls, see the duplicate-send prevention guide.

Operator rule: a failed deliverability check should create a decision record, not just an error message. Save the failed check, reason code, source record, reviewer if any, and final action.

Which USPS sources support address-readiness checks?

USPS Publication 28 and DMM 602 are useful sources for address formatting and addressing rules. USPS Move Update and Address Change Service resources help teams understand move-related and post-mailing address feedback workflows.

Those sources support operational review steps. They should not be turned into a blanket promise that every record is deliverable, every mailpiece will be accepted, or every recipient will receive the piece on a specific date.

How should deliverability checks connect to list hygiene?

Deliverability checks are the campaign-level gate; list hygiene is the ongoing program that improves future audiences. The check should feed failed-address, move, suppression, and duplicate findings back into list-maintenance records.

A good workflow makes bad records less likely to keep returning. For the broader maintenance pattern, see the list hygiene guide and the Address Change Service guide.

How should proofing fit into the check?

Proofing matters because a technically usable address is not enough. The final mailpiece should also show approved creative, address-block placement, variable fields, fallback copy, campaign labels, and any data conditions that affect the printed piece.

USPS Mailpiece Design resources and DMM 201 help teams review layout constraints. Internal proof approval is still an operator control, not a postal approval. For the review step, see the print proof guide.

What should a Sendvo-style workflow keep visible?

A Sendvo-style workflow should keep the source record, address state, suppression result, duplicate-send decision, proof version, campaign ID, batch ID, tracking fields, and deliverability decision together before release.

Sendvo is in beta, so product wording should stay capability-framed. The operational pattern is stable: when software connects audience data to physical mail, the release gate should explain why each record mailed, paused, or was excluded.

FAQ

What is a deliverability check for direct mail?

A deliverability check for direct mail is a pre-release review that decides whether a record is ready to mail, should be held for review, or should be excluded before print. It usually combines address completeness, standardization, move signals, suppression rules, duplicate-send history, proof readiness, and campaign tracking fields.

Is a deliverability check the same as address validation?

No. Address validation is one input. A direct mail deliverability check is broader because it also reviews suppression rules, duplicate-send windows, source-system conflicts, proof readiness, campaign metadata, and whether a record should be held instead of released.

What should teams do with records that fail a deliverability check?

What is a deliverability check for direct mail?

TL;DR