See It in One Demo
Features / DPV Validation

DPV. Confirm the unit exists
before the press runs.

A CASS-clean address is a well-formatted address. It doesn’t mean USPS actually delivers to apartment 4C in that building. DPV — Delivery Point Validation — is the USPS-licensed verification that confirms each record on the list resolves to an active delivery point at the unit level: the specific apartment, suite, or house number exists, USPS currently routes mail to it, and the carrier puts mail through that door today. DirectMail.io runs DPV on every list, every drop, after CASS standardization and before press queue. Non-deliverable points are suppressed by default. The certification stamps the manifest for full automation postage.

See It in One Demo What is DPV →
How it works

Five steps. Per-record confirmation. Auto-suppression of non-deliverables.

  1. 01

    Every list runs DPV after CASS, before press queue

    Whether the list arrived by upload, SFTP, API, or address append, DirectMail.io routes it through DPV processing immediately after CASS standardization and before any record reaches the press. There is no "skip DPV" toggle on production drops.

  2. 02

    Per-record match against the USPS DPV database

    Each standardized address is matched at the unit level against the USPS Delivery Point Validation database — the registry of every active delivery point USPS currently puts mail through, refreshed by USPS on a continuous cycle.

  3. 03

    Confirmation codes append to every record

    DPV returns one of several codes per record: Y (confirmed delivery point), S (primary number confirmed, secondary missing or invalid), D (primary confirmed but secondary not in database), N (not a confirmed delivery point). The codes append to the record along with vacancy and no-stat flags.

  4. 04

    Default suppression rules apply automatically

    N-coded records are suppressed by default. Vacant addresses are suppressed on consumer campaigns by default. No-stat addresses surface for review rather than auto-suppress. S and D codes surface in the dashboard with a recommendation, and the team can override the defaults per campaign.

  5. 05

    DPV certification stamps the drop

    The DPV pass produces the documentation USPS requires for full automation postage on records claiming the discount. The certification rides with the manifest, no separate filing, and the drop qualifies at the deepest tier the volume and sortation support.

Why it matters

Why CASS without DPV is a paid invitation to dead-letter mail.

CASS standardizes the format of the address so USPS sortation can read it. That step is necessary but not sufficient. A CASS-clean list can still contain thousands of records pointing to apartments that don't exist, suites that were demolished, and unit numbers that were never on the building — and every one of those pieces prints, gets postage, and arrives at USPS to be returned or destroyed. The cost of CASS-clean-but-DPV-failed mail is borne by the mailer in full: the per-piece print, the per-piece postage, the per-piece handling. None of it is recoverable after the piece ships.

DPV closes the gap. Every record gets a per-unit match against the USPS Delivery Point Validation database — the registry of every active delivery point USPS currently routes mail through — and any address that fails to confirm is suppressed before the press runs. The pieces that ship are pieces USPS will deliver. On a 50,000-piece drop with a 4 percent DPV failure rate, that's 2,000 pieces of recoverable cost on print alone, typically several thousand dollars per drop, before the postage discount qualification gets counted.

And the discount matters. DPV is a precondition of full automation postage under USPS rules. A drop that skips DPV pays a higher per-piece postage rate across the entire drop, not just the failing records. The mailer pays twice for the same omission — once on the wasted print and postage of the DPV-failed pieces, and again on the rate increase across the rest of the drop.

Per-drop
DPV runs per drop, not once at list ingest, because the USPS DPV database refreshes continuously as carriers add and retire delivery points in the field. A record that DPV-confirmed last quarter is not guaranteed to confirm this quarter — and the records that flip to N are the records that quietly waste print and postage on every drop that doesn't re-validate.
Source: USPS DPV product specification and Move Update Standard requirements
Use cases

Where DPV pays back fastest.

  • Apartment-heavy and urban campaigns

    Buildings with high unit-count churn produce the highest DPV failure rates. DPV catches the demolished, renumbered, and never-existed units before the print job — recovering the apartment-level pieces that would otherwise go to USPS dead letters.

  • High per-piece-cost dimensional mailers

    When the piece is a thick package, tipped-in sample, or anything else expensive to produce, DPV is the cheapest insurance against printing hundreds of premium pieces for addresses that don't exist.

  • Compliance-driven mail

    Regulated industries that must reach every customer (utility statements, voter notices, insurance disclosures) need DPV-certified delivery on every record. The DPV documentation answers the regulator's "did this actually go to a real address" question.

  • Acquisition campaigns on rented lists

    Prospect lists from data partners or co-op providers vary widely in DPV quality. Running DPV on every ingested list separates the deliverable records from the ones that look clean but won't reach a real recipient.

DPV FAQ

Questions teams ask before deploying.

Short answers. For implementation specifics on confirmation-code handling, vacancy suppression rules, or no-stat overrides, book a demo.

  • What is DPV and why does it matter for direct mail?

    DPV stands for Delivery Point Validation. It is the USPS-licensed process that verifies each address on a mailing list is a real, deliverable point on a carrier route — the specific unit number, apartment, or suite exists and currently receives mail. CASS without DPV produces a standardized address; DPV confirms USPS actually delivers to that exact unit. Without DPV, a CASS-clean list can contain thousands of records pointing to apartments or suites that don't exist, and those pieces print, ship, and never deliver.

  • What is the difference between CASS and DPV?

    CASS standardizes the address format — abbreviations, ZIP+4, directional indicators — so USPS sortation infrastructure can read it. DPV verifies the standardized address is a real delivery point USPS recognizes at the unit level. CASS validates structure; DPV validates existence. They run in sequence: CASS first, then DPV against the CASS output. Both are required for full automation postage discounts under USPS rules.

  • What do the DPV confirmation codes mean?

    Y means the address is confirmed as an active USPS delivery point — the safest bucket. S means the primary number (street number) is confirmed but the secondary number (apartment, suite) is missing or incorrect. D means the primary is confirmed but the secondary is not in the DPV database. N means the address is not a confirmed delivery point. The platform suppresses N by default; Y, S, and D surface in the dashboard with default treatment recommendations the team can override per campaign.

  • How often does the USPS DPV database change?

    USPS updates the DPV database on a continuous cycle as carriers add and retire delivery points in the field. A record that DPV-confirmed in January may DPV-fail in May because the unit was demolished, the building was converted, or the carrier reorganized the route. That's why DPV needs to run per drop, not once at list ingest — last quarter's DPV pass does not guarantee deliverability on this quarter's drop.

  • What is the typical DPV failure rate on a real list?

    It depends on the geography. Urban and apartment-heavy lists run higher DPV failure rates because unit counts churn fastest — buildings get demolished, units get renumbered, vacant units accumulate. Rural and single-family-heavy lists run lower failure rates because the delivery points are more stable. Across mixed national consumer lists, a single-digit-percentage DPV failure rate per drop is typical; on apartment-heavy urban subsets, the rate can run materially higher.

  • Does DPV suppression actually save money or is it just for compliance?

    Both. Compliance side: full automation postage requires DPV-certified records. Cost side: every DPV-failing piece is a paid print, paid postage, and paid handling on something that returns or destroys at USPS. On a 50,000-piece drop with a 4% DPV failure rate, that's 2,000 pieces of recoverable cost on the print alone — typically several thousand dollars per drop, recoverable in full by running DPV.

  • Is DPV billed separately in DirectMail.io?

    DPV processing is built into the platform alongside NCOA, CASS, LACSLink, and DSF2 — not invoiced as a separate per-record line item. Every drop clears the full pre-flight hygiene pass before press queue as part of standard operations. Plan tiers and volume details live on the pricing page; the principle is that DPV is a precondition of the drop, not an add-on the team can accidentally skip.

Run DPV on your next drop.

30-minute demo. We’ll process a sample of your list, show the DPV confirmation buckets, surface the apartment-heavy DPV failures the team would have eaten on the next drop, and walk through the automation-postage qualification documentation USPS receives with the manifest.

See It in One Demo All features →