Late Shipments, EasyPost

Metrics type: Key Metrics • Category: Delivery Performance

At a glance

Absolute count of EasyPost-booked parcels that delivered after the underlying carrier’s estimated delivery date in the trailing 7 days. This is the numerator behind the On-Time Delivery Rate percentage and the daily worklist for your despatch and customer-service teams. Because EasyPost aggregates across USPS, FedEx, UPS, DHL and regional carriers, one count replaces three or four separate carrier dashboards.


What it counts	`COUNT(EasyPost shipments WHERE actual_delivery_date > est_delivery_date AND status = 'delivered')` over the rolling 7-day window. Each delivered-late parcel scores once, regardless of which underlying carrier carried it.
Data source	EasyPost Tracker objects via the unified Tracking API. The card reads each `Tracker`’s normalised `status`, the `est_delivery_date` recorded against the shipment at purchase, and the delivered scan timestamp from the carrier’s `tracking_details` array.
Late definition	Delivered after the carrier-supplied estimated delivery date. EasyPost normalises every carrier’s estimate into one field, so a late FedEx Ground parcel and a late USPS Ground Advantage parcel are scored on the same basis.
In-flight handling	Parcels still in transit are excluded until they show a `delivered` scan. A parcel past its estimate with no delivered scan yet does not count until it actually delivers (or is reclassified as a failure on Failed Deliveries).
Returns / RTO	Excluded. Return-to-sender parcels are counted on Returned to Sender, not here.
Refund eligibility	Carrier-dependent. The FedEx Express subset and USPS Priority Mail Express subset carry a money-back guarantee; USPS Ground Advantage, Priority Mail, Media Mail and FedEx Ground / Home Delivery do not. Split the count by carrier before filing.
Test-mode	Excluded. Shipments bought against an EasyPost test API key are filtered out.
Time window	`7D` (rolling 7 days). Daily readings are noisy below roughly 200 parcels per day; use the weekly view for trend.
Alert trigger	`>5% of total` (late count exceeds 5 percent of total delivered shipments in the period). For a 3,500-parcel-week merchant that is 175+ late deliveries.
Roles	owner, operations

Calculation

Calculated automatically from your EasyPost data. See the At a glance summary above for what the metric tracks and the worked example below for a typical reading.

Worked example

A US mid-market apparel merchant despatching roughly 3,400 parcels a week, multi-carrier through EasyPost with rate-shopping enabled. Reading taken at 09:00 ET on 12 Mar 26 for the trailing 7 days (06 Mar 26 to 12 Mar 26).

Underlying carrier	Shipments (7D)	Late (delivered after estimate)	Late %	MBG-eligible?
USPS Ground Advantage	1,510	96	6.4%	No
USPS Priority Mail	880	68	7.7%	No
FedEx Ground	480	22	4.6%	No
FedEx 2Day	95	2	2.1%	Yes
UPS Ground	280	14	5.0%	No
OnTrac (regional)	195	8	4.1%	No
All carriers (this card)	3,440	210	6.1%	mixed

The card reads 210 late shipments. The alert at >5% of total has tripped at the aggregate (6.1 percent). Five things to notice:

The percentage felt fine, the count is the workload. 210 late parcels equals roughly 17 to 32 inbound customer contacts over the next two to three days at the industry rule of 8 to 15 percent of late deliveries generating a “where is my order” touchpoint. At around 8 minutes per ticket that is 2 to 4 staff-hours a day generated by carrier delay alone. The CS rota needs to know before the parcels miss, not after the inbox fills.
Only 2 of 210 are refund-claimable. The FedEx 2Day subset is the only money-back-guarantee leg here. Operations file those two via FedEx Billing Online; the other 208 are pure customer-experience cost with no carrier recovery. Do not waste analyst time chasing refunds on Ground services that never had a guarantee.
USPS is the dominant late-driver (164 of 210, 78 percent). Rate-shopping correctly captured the USPS cost saving, but the on-time gap is real. The action is to tune the EasyPost rate-rules: upgrade Priority Mail to FedEx Ground on zone 5 and above where the transit gap is widest, accepting a marginal cost rise for an estimated 30 to 50 fewer late parcels a week. Validate the cost trade on Cost by Zone before changing the rules.
OnTrac at 4.1 percent is excellent for a regional carrier. OnTrac and peers like LSO and LaserShip frequently beat the national carriers inside their coverage footprint. Rate-shopping selected them correctly here, so leave that lane alone.
Compare against the prior week. Volume up 12 percent week-over-week, late count up 18 percent week-over-week. The rate is climbing faster than volume, which points to a specific carrier or zone degrading rather than simple seasonal load. Drill into OTD by Route and Shipments by Service to localise it.

Sibling cards merchants should reference together

Late shipment count is the workload metric. Pair it with these to plan response and find root cause:

Card	Why pair it with Late Shipments	What the combination tells you
On-Time Delivery Rate	The percentage view of the same parcels.	The rate tells you how the multi-carrier network is performing; the count tells you how much work lands tomorrow. Read both.
Shipments	Volume context for the count.	Late count rising in line with volume means the rate is flat; rising faster means the rate is degrading.
Exception Rate	Lead indicator.	A rising exception rate predicts a rising late count at a 1 to 3 day lag.
Failed Deliveries	The harder failure tail.	A late parcel that never delivers escalates here; watch the two together during disruption.
Open Claims	The recovery pipeline.	The MBG-eligible late subset flows into claims; typical conversion is small but worth filing.
OTD by Route	Splits the count by lane.	Shows which route is dragging the aggregate and where a renegotiation or rate-rule change pays back.
Avg Transit (days)	The slower upstream signal.	A creeping average transit time is the early warning that the late count is about to rise.

Reconciling against the source

Where to look in the EasyPost dashboard and in the underlying carriers’ own portals: EasyPost is an aggregator, so reconciliation has two layers. First, the EasyPost dashboard: EasyPost Dashboard → Logs / Trackers, filter by status and date range. Each Tracker row shows the tracking number, carrier, estimated delivery date and the latest scan, which is the same data the card reads. Second, the underlying carrier’s own tracking portal (USPS Tracking, FedEx Tracking, UPS, DHL), which holds the authoritative scan history for parcels that carrier physically moved. When a number disagrees, the carrier portal is the source of truth for the scan; EasyPost mirrors it after ingestion. The closest like-for-like view in EasyPost is All Carriers, Last 7 Days, status Delivered, delivered after estimated delivery date. Why our number may legitimately differ from EasyPost’s or the carrier’s record:

Reason	Direction	Why
Tracking-event latency	Ours can lag	EasyPost polls carrier tracking and pushes webhook updates roughly every 30 to 60 minutes, and carriers backfill scans 12 to 48 hours late during peak. A parcel delivered four hours ago may not yet show a delivered scan in our index; the count converges by T-2.
Carrier-local scan timestamps	Boundary days off	Carrier scan timestamps are recorded in the local time of the scan location, not your account time zone. A parcel scanned at 23:30 Pacific can land in a different reporting day than your ET dashboard, shifting a handful of parcels across the 7-day boundary.
Estimate revisions	Either	Some carriers revise the estimated delivery date mid-transit after a weather hold. EasyPost stores the estimate captured at purchase; the carrier portal may show the revised estimate, so “late against original” and “late against revised” can differ.
Filter scope	Either	Match “All Carriers” in the EasyPost filter to the card. A single-carrier filter will always show fewer late parcels than the aggregated card.
Test-mode parcels	Ours lower	The card excludes shipments bought on a test API key; an unfiltered dashboard export may include them.

Cross-connector reconciliation:

Card	Expected relationship	Causes of legitimate divergence
Direct-FedEx late count (if the merchant also runs FedEx directly)	The EasyPost-FedEx subset should match the FedEx-direct count for the same parcels.	A direct FedEx integration also counts parcels not booked through EasyPost; populations differ.
Direct-USPS late count	Same logic for the USPS subset.	Same caveat: direct USPS includes non-EasyPost volume.

Known limitations / merchant FAQs

How do I file money-back-guarantee claims for these late parcels? Filter the late list by carrier to find the MBG-eligible subset (FedEx Express services, USPS Priority Mail Express), then file directly in the carrier’s portal: FedEx Billing Online for FedEx, the USPS website for USPS. EasyPost does not file carrier MBG claims on your behalf. EasyPost’s own parcel-insurance product has a separate claim flow on Open Claims, and that is the only claim type EasyPost itself adjudicates. Why does the count differ from my customer-service team’s count? Two reasons. (1) CS counts customer-reported late, the card counts data-confirmed late; some customer reports are just tracking-feed lag, not an actual late delivery. (2) CS often folds in “shipped late from the warehouse” complaints, whereas this card is delivery-late only. For the despatch-floor side, look at Label Generation Success, where a dip blocks parcels at the bench before they ever ship. My USPS subset is dragging the count. Should I switch USPS off in rate-shopping? Test before disabling. The USPS cost saving on sub-1lb volume is typically 20 to 40 percent. Run the math: extra CS cost per late parcel (roughly 4 to 12 US dollars) multiplied by the additional lates if USPS stays in the mix, versus the freight saving on that USPS volume. Most merchants come out ahead keeping USPS rate-shopping on and instead upgrading only the worst zones. Can EasyPost rate-shop on on-time history rather than price alone? Yes on enterprise plans. Custom rate-rules can weight recent on-time performance per lane into the carrier selection, so the rate-shopper prefers carriers performing well on the specific lane being booked. Speak to your EasyPost account manager to enable it. Why does the count spike on Mondays? Weekend-despatched parcels deliver Monday or Tuesday on most ground services, and some miss the estimate on the Tuesday poll. Monday’s reading also catches up backlogged late counts from Saturday and Sunday. The 7-day rolling window smooths this; do not act on a single Monday spike. How does Q4 peak affect the count? Expect volume up 30 to 80 percent and the late count up 200 to 400 percent from late November through December as the carrier networks strain. The rate climbs too, but the absolute count is the operational reality your CS rota has to staff against. Plan headcount on the count, not the percentage. A parcel shows late here but the carrier portal says delivered on time. Which is right? Check the estimated delivery date each side used. The card scores against the estimate captured at purchase; the carrier portal may have silently revised its estimate after a weather or network hold. The scan timestamp itself should agree once ingestion catches up; the disagreement is almost always about which estimate the parcel was measured against.

Tracked live in Vortex IQ Nerve Centre

Late Shipments is one of hundreds of KPI pulses Vortex IQ tracks across EasyPost and 70+ other ecommerce connectors. Nerve Centre runs the detection layer; Vortex Mind investigates the cause when something moves; Ask Viq lets you interrogate any number in plain English. Start for free or book a demo to see this metric running on your own data.

Get Started

The AI OS

At a glance

Calculation

Worked example

Sibling cards merchants should reference together

Reconciling against the source

Known limitations / merchant FAQs

Tracked live in Vortex IQ Nerve Centre

​At a glance

​Calculation

​Worked example

​Sibling cards merchants should reference together

​Reconciling against the source

​Known limitations / merchant FAQs

​Tracked live in Vortex IQ Nerve Centre

At a glance

Calculation

Worked example

Sibling cards merchants should reference together

Reconciling against the source

Known limitations / merchant FAQs

Tracked live in Vortex IQ Nerve Centre