What happens after you hit send: a mail delivery timeline for businesses
By Justin Winter · Updated August 22, 2026
Every order is handed to USPS the next business day after it's placed, then travels 3–5 business days for First-Class or Certified, or 1–3 business days for Priority. For customer-facing SLA language, a safe planning window is 5–7 business days from request to delivery — but treat that as a suggestion, not a guarantee, since USPS transit times are service estimates, not commitments.
This is a planning and expectation-setting guide for support and ops teams, not a delivery guarantee. Use it to write accurate SLA language and to know what to check when a customer asks where their letter is — the underlying transit times are USPS estimates, and individual letters can run a day or two outside them.
The stages, in order
| Stage | What happens | Typical timing |
|---|---|---|
| Order placed | Customer uploads text or a PDF, selects a mail class, and pays. | Day 0 |
| Payment & screening | Order is validated and queued for printing and mailing. | Same day, automated |
| Handed to USPS | Letter is printed, enveloped, and physically handed to USPS. | Next business day after the order |
| USPS transit | Moves through the USPS network. Certified and Priority generate scan events; plain First-Class generally does not. | 3–5 business days (First-Class, Certified) or 1–3 (Priority) |
| Delivery | Letter reaches the recipient's mailbox or address. | End of the transit window above |
Why the handoff date matters more than people expect
The single most common source of a "why is my letter late" ticket is a miscounted start date. A letter is not dropped into the USPS network the moment an order is placed — it's printed and handed off the next business day. An order placed Friday afternoon is handed to USPS on Monday, not Saturday, which means the whole 3–5 day (or 1–3 day) transit clock doesn't start ticking until then. When you're counting days for a customer, always count from the handoff date, not the order timestamp.
Suggested SLA language by mail class
- First-Class ($1.99): "Expect delivery within 5–7 business days of your request." No tracking is included by default, so there's no mid-transit confirmation to point to — only the eventual delivery.
- Certified ($12.99): Same 5–7 business day planning window as First-Class, but with tracking available at every stage via /track/{trackingNumber}.
- Certified + electronic Return Receipt ($14.99): Same 5–7 business day window, plus a signed delivery confirmation once the letter arrives — useful when a customer's own SLA requires proof, not just speed.
- Priority ($24.99): "Expect delivery within 3–4 business days of your request." Fastest option, with tracking included.
Frame all of the above internally as a suggested default, not an official paperplane guarantee — build in the buffer day or two precisely because USPS transit times are service standards, and individual letters (rural routes, weather, holiday volume) can run past them.
Handling "where's my letter" tickets
For Certified or Priority orders, the fastest resolution is pointing the customer straight to /track/{trackingNumber} — it shows every USPS scan recorded so far, including acceptance, transit, and delivery events. That page is the source of truth; there's no need to relay scan details manually once a customer has the link.
For plain First-Class mail without an added tracking option, set expectations up front: there is no scan-by-scan visibility, so support has no more insight mid-transit than the customer does. The only way to confirm delivery is the recipient acknowledging receipt, or the letter clearing the outer edge of the estimated window without any return-to-sender signal. If a customer needs visibility while a letter is in transit, that's a reason to recommend Certified or Priority on future orders, not something support can manufacture after the fact for a First-Class letter already in the mail stream.
What this guide is — and isn't
This is a reference for writing customer-facing language and triaging delivery questions, built from paperplane's actual handoff and USPS's published service standards. It is not a guarantee of specific delivery dates for any individual letter — USPS does not offer that for First-Class, Certified, or standard Priority Mail, so paperplane can't either. When in doubt, quote the range, point to tracking where it exists, and treat outliers as exceptions to investigate rather than evidence the range is wrong.
Related guides
Common questions
What SLA language should we give customers who ask when their letter will arrive?
A workable default is "expect delivery within 5–7 business days of your request." That covers the next-business-day handoff to USPS plus the 3–5 day First-Class/Certified transit window, with a day or two of buffer for real-world variance. For Priority orders, tighten it to "3–4 business days" (next-day handoff plus 1–3 day transit). Present this as an internal planning estimate, not a contractual guarantee — USPS does not guarantee First-Class, Certified, or standard Priority delivery dates.
A customer says their letter is late. What do we check first?
First confirm when the order was actually placed and count business days from the next business day after that (not from the order timestamp itself — weekend and after-cutoff orders shift the handoff date). If the letter was sent Certified or Priority, check /track/{trackingNumber} for the latest USPS scan. If it was plain First-Class with no added tracking, there is no scan trail to check — the only signal is whether the recipient has confirmed receipt.
Why can't we just tell customers an exact delivery date?
Because USPS publishes service standards, not guarantees, for every class except Priority Mail Express. Weather, holiday volume, and rural or remote routes can add a day or two beyond the typical window on any given letter. Committing to an exact date invites a dispute you can't control the outcome of — a range is both more honest and easier to defend.
Does tracking update in real time while the letter is in transit?
For Certified and Priority mail, USPS posts scan events as the letter moves through the network, visible at /track/{trackingNumber} — typically an acceptance scan, one or more transit scans, and a delivery scan. Plain First-Class mail (no Certified or Priority upgrade) is not scanned at each stage by default, so there's no mid-transit visibility — the first confirmation is usually the recipient acknowledging receipt.
Should we quote different timelines for Certified vs. Certified with Return Receipt?
No — the added electronic Return Receipt doesn't change transit speed, only what you can prove afterward. Both travel at the same 3–5 business day First-Class pace. Return Receipt just adds a delivery confirmation with the recipient's signature captured electronically, which matters for proof-of-delivery SLAs but not for the timeline itself.