DPV

DPV stands for Delivery Point Validation. It is the USPS-licensed verification layer that runs on top of CASS standardization and confirms each address resolves to an actual delivery point USPS recognizes on a carrier route — meaning the specific unit number, suite, apartment, or house number is real and currently receives mail, not just that the street name and ZIP code parse correctly. Without DPV, a standardized address like “500 Main St Apt 99, Springfield IL 62701” can look perfect to CASS while pointing to a unit number that doesn’t exist in the building.

Why this exists at all

CASS was built in the 1990s to standardize address format so USPS sortation infrastructure could read every piece consistently — correct ZIP+4, correct abbreviations, correct directional indicators. But CASS validates structure, not existence. An address could be perfectly standardized and still point to a unit that doesn’t physically exist on the carrier’s route. USPS introduced DPV in 1999 to close that gap. The DPV database lists every active delivery point in the country at the unit level — not just every street, but every door on every street that USPS actually puts mail through. Today, DPV processing is required for any mailpiece claiming full automation postage discounts under the USPS Move Update and automation programs.

How it actually works

A licensed DPV processor (every legitimate mail platform either is one or sits behind one) takes the standardized address output from CASS and matches each record against the DPV database. The match returns a DPV confirmation code — the important ones are: Y (confirmed delivery point), N (not a confirmed delivery point), S (primary number confirmed but secondary missing or incorrect), and D (primary number confirmed but secondary not present in the database). The processor also returns false-positive flags, vacancy indicators (whether the address is currently vacant), and no-stat flags (USPS doesn’t deliver there for operational reasons, like the address is a parking lot or under construction). All of these get appended to the record before any drop runs.

Two important details. First, DPV is a per-unit verification, not a per-building one. A high-rise with 200 apartments can have a CASS-clean street address but still produce 47 DPV failures because units 1A, 12C, and others are vacant, demolished, or never existed. Second, the DPV database is updated by USPS every 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 building was torn down — which is why DPV needs to run per drop, not once at list ingest.

What goes in, what comes out

Input: addresses that have already passed through CASS standardization. DPV operates on the standardized output, not the raw address, because DPV needs the address in canonical USPS format to do the unit-level match. Output: each record gets a DPV confirmation code, a vacancy indicator, a no-stat flag, and any false-positive marks. The mailer decides what to do with each disposition — typical rules are: keep Y and S, optionally include D depending on campaign tolerance, suppress N, suppress vacant if the campaign requires a current occupant, and suppress no-stat unless the campaign specifically targets non-standard delivery points.

Common pitfalls

The biggest pitfall is treating DPV as equivalent to CASS — they are not the same thing. CASS standardizes the format; DPV confirms the unit exists. A “CASS-certified” list can still contain thousands of records pointing to non-existent apartments, and those pieces print and ship and never deliver. The second pitfall is filtering only on the Y code and dropping everything else without review. The S code (primary confirmed, secondary missing) is recoverable on many campaigns — if the recipient name is known and the building has a doorperson or mailroom, the piece often gets to the right hands. Dropping S codes wholesale can suppress meaningful response. The third pitfall is ignoring the vacancy flag. Mail to a vacant address “delivers” in the USPS scan sense (the carrier puts it in the box), but no one is there to respond — the conversion is zero and the postage and print are wasted.

How DirectMail.io runs it

DirectMail.io runs DPV on every address, every drop, after CASS standardization and before press queue. Confirmation codes, vacancy flags, and no-stat flags are surfaced in the dashboard with default rules pre-applied (drop N, drop vacant on consumer campaigns, surface S and D for review). The DPV-certification documentation files automatically with the USPS manifest so the drop qualifies for full automation postage. There is no “skip DPV” toggle on production drops. Details on the DPV validation feature page.

When to use this

• Every drop, period. DPV is a precondition of full automation postage under the USPS Move Update Standard. A list that ran DPV three months ago is not current — the database refreshes monthly and buildings change.
• On lists with apartment-heavy geography. Urban and multifamily-heavy lists have the highest DPV failure rates because unit counts churn fastest. DPV catches the demolished, renumbered, and never-existed units before the print job.
• Before any campaign with high per-piece cost. If the piece is a thick package, a tipped-in sample, or anything else expensive to produce, DPV is the cheapest insurance against printing 800 dimensional mailers that USPS will return as undeliverable.

For the operational checklist DPV sits inside, see the seven-step list-hygiene checklist.