How to Fire an Email the Moment USPS Scans Your Mail Piece: A Step-by-Step Guide

Every mail piece sent in the U.S. carries an Intelligent Mail barcode. Every barcode gets scanned as it moves through USPS sortation — by one count, USPS logs more than 60 billion of these scans each year through its Informed Visibility data feed. The last scan — the one that happens at the Destination Delivery Unit, right before a letter carrier picks up the tray — is the single most predictive event in a mail piece’s lifecycle. It means the piece will be in the recipient’s mailbox that day.

Which means if you fire an email at that exact moment, the recipient opens their mailbox and their inbox to find the same offer from the same brand at the same time. It’s a coordinated touch competitors using simple email platforms cannot replicate, because they don’t have the scan data. Here’s how to set it up.

Step 1: Understand what “last scan” actually means

USPS mail moves through a chain of facilities — origin, NDC (Network Distribution Center), SCF (Sectional Center Facility), DDU (Destination Delivery Unit). Each hop produces a scan event. Informed Visibility exposes those events in near-real-time over an API. The “last scan” in IV data is the scan at the DDU — the facility that hands the mail to the carrier for delivery. It lands that day 85%+ of the time, next business day nearly all remaining cases.

Step 2: Queue the email before the drop

The email has to exist, with variable data merged and content locked, before the first mail piece gets scanned. Most teams queue it 48 hours before expected delivery. You aren’t sending it yet — you’re telling the system: for every recipient whose piece gets a DDU scan, fire the matching personalized email to that recipient’s email address.

Step 3: Pair mail records to email addresses

Your mailing list needs a usable email per record, or you need an email-append pass before the drop. On a typical acquisition list, ~40–65% of postal records will have verified email. That’s the universe your scan trigger targets. For the records without email, you can still run a standard post-drop follow-up; they just fall out of the co-landing mechanic.

Step 4: Write email copy that acknowledges the mail

The magic of the scan trigger is acknowledgment. Copy like “you’ll see our offer in your mailbox today” — or the more subtle “keep an eye on your mailbox this afternoon” — creates a cognitive loop the recipient closes when they physically walk to the curb. Don’t throw the co-landing away with generic copy.

Step 5: Let Informed Visibility do the heavy lifting

Once the drop is at the post office, IV takes over. Pieces stream through sortation, each scan lands in the feed, and the trigger fires email the moment a DDU scan hits a record. A 10,000-piece drop typically completes its scan window over about 3–4 days — pieces don’t all deliver the same day. That means the email sends are staged, matching the actual delivery waves.

Step 6: Watch the dashboard

The thing you’re looking for is the correlation between scan-to-inbox time and open rate. Opens spike in the 2–4 hour window after DDU scan. That’s the co-landing effect measured. Response rate and downstream conversion should be compared to a control segment that got mail only.

The failure modes nobody warns you about

Three things break this play if you’re not careful:

• Non-scanning mail. Some pieces — small drops into DDUs that don’t route through full automation — won’t produce a last scan. Your trigger won’t fire. Build a fallback: if no scan event within X days, send a cold email anyway.
• Same-address scans. Apartment buildings can produce scan events that don’t correspond to physical delivery. Rare, but worth logging.
• Email deliverability. A surge of scan-trigger emails can look like a spike to inbox providers. Warm your sending IP before a major drop.

Running it on DirectMail.io

The Scan Trigger is native to the platform. No Informed Visibility API integration on your end — the feed is built in, listened to in real time, and wired to the campaign. See Features for the trigger itself plus the supporting Informed Delivery and email editor capabilities. The CMR Construction case study shows the same infrastructure powering an AI phone qualification flow. The Agencies solution is where this lives for agencies running it for clients.

Why competitors can’t match it

To run a true scan trigger, you need three things wired together: USPS Informed Visibility access, a mailing system that owns the IMb barcode, and an email engine that listens to the IV stream and sends on event. Most direct mail vendors own one or two of those. A handful own all three. The rest integrate, which means lag — and lag kills the co-landing effect.

The pitch to your client is simple: their competitor’s email arrives a week after the mail. Yours arrives the same day. It’s a small difference that changes response rate in a way the competitor can’t copy without rebuilding their stack.