> ## Documentation Index > Fetch the complete documentation index at: https://docs.vortexiq.ai/llms.txt > Use this file to discover all available pages before exploring further. # Late Shipments, FedEx > Late Shipments for FedEx stores. Tracked live in Vortex IQ Nerve Centre. How to read it, why it matters, and how to act on it. **Metrics type:** [Key Metrics](/nerve-centre/overview#metrics-types-explained) • **Category:** [Shipping & Courier](/nerve-centre/connectors#connectors-by-type) ## At a glance > Absolute count of FedEx parcels that arrived after their committed delivery date in the rolling 7-day window. The "how many problem shipments do I have right now?" companion to [On-Time Delivery Rate](/nerve-centre/kpi-cards/fedex/on-time-delivery-rate). Where the rate tells you a percentage, this number tells you the workload, customer-service tickets, refund risk, and money-back-guarantee claim queue. | | | | ------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **What it counts** | `COUNT(shipments WHERE actualDeliveryDateTime > scheduledDeliveryDate)`, in the trailing 7 days. Each shipment counts once. Shipments still in transit are excluded until they post a final scan, so the number can climb after a weather event as previously-in-transit parcels resolve as late. | | **Delivery success criterion** | A shipment moves out of "late" only after FedEx posts a Code 01 (DL) Delivered scan with a date later than `scheduledDeliveryDate`. Until then it sits in a transit state and does not count. | | **On-time threshold** | `actualDeliveryDateTime > scheduledDeliveryDate` (no grace window). Use the same date-level commit as [On-Time Delivery Rate](/nerve-centre/kpi-cards/fedex/on-time-delivery-rate). | | **Returns / RTO** | **Excluded.** RTS (Return to Sender, Code 70) parcels do not count as late deliveries; they appear in [Returned to Sender](/nerve-centre/kpi-cards/fedex/returned-to-sender). | | **Service level scope** | **All FedEx services pooled** (Ground, Home Delivery, Express, SmartPost, International). Each shipment is scored against its own service-specific commit. | | **Zone variance** | Far-zone Ground shipments (Zone 5 to 8) account disproportionately for late counts. A coast-to-coast Ground parcel is roughly 3x more likely to be late than a same-metro Zone 2 parcel, even though both have FedEx commits. The count reflects actual customer-impact, not normalised by zone. | | **Money-back guarantee impact** | FedEx Express late shipments are claimable for a freight refund within 15 days. Late count for Express services = your refund-claim queue. **File the claims**, the typical recovery is $8 to $35 per shipment depending on service tier and weight. | | **Peak-period behaviour** | The 7-day window means Q4 spikes are visible within days, not averaged out. Black Friday week routinely produces 5x to 10x normal late count for DTC merchants on FedEx; the surge tapers across the next 2 to 3 weeks as the network catches up. The 7D window flags the spike fast; act on it within 48 hours. | | **Time window** | `7D` (rolling 7 days) | | **Alert trigger** | `>5% of total`, fires when the late count exceeds 5 percent of total shipments in the window | | **Roles** | owner, operations | ## Calculation Calculated automatically from your FedEx 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 DTC home-goods brand shipping out of Columbus, OH using FedEx as primary carrier. Reading taken at 09:00 ET on 12 Mar 26 for the trailing 7 days (06 Mar 26 to 12 Mar 26). | FedEx Service | Shipments (7D) | Late shipments | Late rate | Refund-claim eligible? | | ---------------------------- | -------------- | -------------- | --------- | ---------------------- | | Ground (Zone 2 to 4) | 1,840 | 38 | 2.1% | No (Ground excluded) | | Ground (Zone 5 to 8) | 1,210 | 142 | 11.7% | No | | Home Delivery | 580 | 24 | 4.1% | No | | 2Day (Express) | 320 | 11 | 3.4% | Yes ($14 to $22 each) | | Priority Overnight | 110 | 4 | 3.6% | Yes ($28 to $45 each) | | **All services (this card)** | **4,060** | **219** | **5.4%** | **15 claimable** | The card reads **219 late shipments**, alert tripped at >5% of total (5.4% > 5%). Five things to notice: 1. **The Zone 5 to 8 Ground bucket is 142 of 219 (65%) of the late count, despite being only 30% of volume.** This is the single largest lever. Either pre-position inventory in a second DC closer to East Coast customers, switch high-value Zone 5 to 8 SKUs to 2Day Express (small unit cost increase, much better on-time), or accept the SLA hit and adjust customer-facing promise copy. 2. **15 Express shipments are claimable for refunds totaling roughly $250 to $600.** Filing claims is a 10 to 20 minute task in FedEx Billing Online per shipment; small-merchant ops teams skip this and leave money on the table. Set up a weekly Friday cadence to review this card's Express subset and file claims for everything over 1 day late. 3. **The 5.4% late rate just clipped the alert threshold.** The 30D version of the same metric likely reads lower because the 7D window catches a recent weather event in the Midwest and East Coast that the 30D smooths. Open the [Exception Rate](/nerve-centre/kpi-cards/fedex/exception-rate) card to confirm whether weather (Code 12 HD) or address-correction (Code 09 NF) drove the spike. 4. **219 late shipments mean roughly 219 customer-service tickets in the next 5 to 7 days.** Customers reach out 1 to 4 days after expected delivery; with 219 misses today, expect a customer-service ticket spike starting tomorrow. Pre-arm the CS team with bulk-update messaging templates for "your FedEx shipment is delayed, here is the new ETA" sourced from FedEx Tracking API. 5. **219 lates over 4,060 shipments is high but recoverable.** The benchmark for healthy DTC FedEx volume is 1.5% to 3% late rate at steady-state, climbing to 6% to 12% in Q4 peak. At 5.4% in non-peak March, this merchant has a real operational issue, not Q4 noise. Investigate the East Coast Ground lane immediately. ## Sibling cards merchants should reference together Late count is a workload number; it pairs naturally with the rate, root-cause, and downstream-impact cards. | Card | Why pair it with Late Shipments | What the combination tells you | | ------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | [On-Time Delivery Rate](/nerve-centre/kpi-cards/fedex/on-time-delivery-rate) | The percentage version, smoothed at 30D vsP. | Rate flat + count climbing = volume grew, late count growing in proportion. Rate dropping + count climbing = real degradation. Rate flat + count flat = healthy steady state. | | [Exception Rate](/nerve-centre/kpi-cards/fedex/exception-rate) | Lead indicator. Exceptions (weather Code 12, address Code 09, hold Code 67) precede missed deliveries by 12 to 48 hours. | Spiking exceptions today = spiking late count tomorrow. Use this combo for forward-looking alerting. | | [Avg Transit (days)](/nerve-centre/kpi-cards/fedex/avg-transit) | Companion timing metric. | Rising transit days + rising late count = network is slower than the commit calendar; renegotiate carrier timeline or lean into Express. | | [OTD by Route](/nerve-centre/kpi-cards/fedex/otd-by-route) | Splits late count by origin-destination zone. | Concentration in 1 to 2 lanes = inventory-allocation fix; spread across all lanes = network-wide / weather event. | | [Returned to Sender](/nerve-centre/kpi-cards/fedex/returned-to-sender) | Adjacent operational issue. | Late and RTS together typically peak after weather events; treat as a single workload. | | [Failed Deliveries](/nerve-centre/kpi-cards/fedex/failed-deliveries) | Subset of lates that never delivered. | Failed deliveries are a worse customer outcome than late deliveries; pull this number first when triaging late count. | | [Priority Overnight Service Promise](/nerve-centre/kpi-cards/fedex/priority-overnight-service-promise) | Premium-tier subset, money-back claimable. | Late count for Priority Overnight is the highest-value claim queue; file these first. | | [Open Claims](/nerve-centre/kpi-cards/fedex/open-claims) | Where late shipments graduate to financial dispute. | Rising late count today predicts a 1 to 2 week-lagged climb in open claims. | | Cross-connector: [`shopify.unfulfilled_orders`](/nerve-centre/kpi-cards/shopify/unfulfilled-orders) | Upstream pressure. | Climbing Shopify backlog precedes late count climbing 1 to 3 days later. | | Cross-connector: [`shopify.refund_rate`](/nerve-centre/kpi-cards/shopify/refund-rate) | Downstream financial impact. | Late count today predicts refund rate climbing in 7 to 14 days as customers escalate. | ## Reconciling against the vendor's own dashboard **Where to look in FedEx's own dashboard:** [FedEx Reporting Online](https://www.fedex.com/wpor/web/jsp/login.jsp) (FROL) → **Reports → Service Performance → Late Shipments**, filtered to *All Services, Last 7 Days*. The audit-level table at *Tracking → Detailed Tracking → Filter "Delivered Late"* shows each tracking number with the gap between `scheduledDeliveryDate` and `actualDeliveryDateTime`. For Express claim eligibility, see *FedEx Billing Online → Money-Back Guarantee → Eligible Shipments*; that view filters to claimable late Express shipments specifically. **Why our number may legitimately differ from FedEx's portal:** | Reason | Direction | Why | | ----------------------------------------------- | ---------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Time zone / boundary days** | Either | FROL defaults to billing time zone; the card uses UTC. The 7D rolling window means boundary day shifts can move the count 5 to 15 shipments either way. | | **Service-disruption exclusions** | FedEx may show lower | FedEx's portal excludes shipments to ZIPs flagged suspended (named storms, wildfires). The card includes them. During disruptions the portal may show 20% to 40% fewer late shipments than this card. | | **Multi-piece scoring** | Either | Master-tracking-level scoring vs piece-level scoring (see [On-Time Delivery Rate](/nerve-centre/kpi-cards/fedex/on-time-delivery-rate) reconciliation table). | | **Tracking sync lag** | Ours lower for "today" | Tracking-scan delay of 30 minutes to 4 hours means today's count understates; T-2 days fully reconcile. | | **Hold-at-location / customer-requested holds** | Either | A shipment held at a FedEx location at customer request (HAL) may post `actualDeliveryDateTime` after `scheduledDeliveryDate` even though the customer asked for it. The card counts it late. FROL may exclude HAL events under "customer-controlled" filtering. | | **In-transit shipments** | Both rolling | Shipments still in transit are excluded from both numerator and total. As they deliver, the rolling 7-day count grows. A weather event today produces visible late counts over the next 5 to 10 days as previously-in-transit parcels resolve. | **Cross-connector reconciliation:** | Card | Expected relationship | What causes legitimate divergence | | -------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------- | | [`usps.usp_late_shipments_count`](/nerve-centre/kpi-cards/usps/late-shipments) | Peer carrier. Independent populations. | Different parcels entirely; not reconcilable. | | [`easypost.eas_late_shipments_count`](/nerve-centre/kpi-cards/easypost/late-shipments) | If EasyPost is the booking layer in front of FedEx, EasyPost's FedEx subset matches this card at T-1. | EasyPost may have rate-shopped some volume to USPS or UPS. | | [`shopify.unfulfilled_orders`](/nerve-centre/kpi-cards/shopify/unfulfilled-orders) | Upstream pressure indicator. | Webhook lag, B2B flows. | | Customer-service ticket volume | Downstream. | Each late shipment generates 0.4 to 0.7 tickets on average; the card predicts ticket volume at 1 to 4 day lag. | ***
Documentation cross-reference (for agencies running multiple carriers) Late-shipment counts exist with similar definitions on other carriers. These are not parallel measurements; the cross-link exists for documentation navigation across multi-carrier accounts. * [`usps.usp_late_shipments_count`](/nerve-centre/kpi-cards/usps/late-shipments) * [`easypost.eas_late_shipments_count`](/nerve-centre/kpi-cards/easypost/late-shipments)
## Known limitations / merchant FAQs **My late count went up but the rate stayed flat. Should I worry?** Probably not, the rate is the meaningful signal. If volume grew proportionally and the rate stayed flat, your network is performing the same; you just have more parcels. The late *count* tells you absolute workload (CS tickets, refund-claim queue), not network health. Use the rate for "is FedEx degrading?" and the count for "how much work do I have today?". **Should I file money-back-guarantee claims for every late Express shipment?** Yes if the merchant ships meaningful Express volume. Each claim recovers the freight charge ($8 to $45 typically). For a brand doing 100+ Express shipments a week, even a 3% late rate yields 3 claims/week × \~$25 = ~$3,900/year recovered. Set up a Friday review cadence: filter this card to Express services, late by 1+ days, and file via FedEx Billing Online. The FedEx API also exposes a claim-eligibility flag if you want to automate. **Why are most of my lates Ground in far zones?** Two reasons. (1) **Distance**, more handoffs between hubs increase failure modes (truck breakdown, weather between hubs, hub-mis-sort, address-correction at the destination terminal). Each handoff has a small fail probability that compounds. (2) **Zone-specific commit calendars**, far-zone Ground commits 4 to 5 days; any single-day slip in transit pushes it past the date threshold. Same-zone Ground commits 1 to 2 days, has slack. Pre-positioning inventory to a second DC closer to your far-zone customers is the structural fix. **A weather embargo just hit, what happens to this card?** The 7D count climbs over the next 5 to 10 days as previously-in-transit shipments resolve as late. Watch the [Exception Rate](/nerve-centre/kpi-cards/fedex/exception-rate) card peak first (within 24 hours of the embargo), then this card peaks 3 to 5 days later, then [Open Claims](/nerve-centre/kpi-cards/fedex/open-claims) climbs 7 to 14 days later. Triage by service: Express late counts go to claim-filing first; Ground late counts go to customer-service messaging. **Can I tell which lates are FedEx's fault vs my fault vs the customer's?** Partly, via FedEx Tracking API exception codes. Code 12 (HD, weather) and 07 (EX, network exception) are FedEx-side. Code 09 (NF, address not found) and 67 (CD, customs) are merchant or customer-side. Code 08 (HL, hold at customer request) is customer-side. The card pools all causes; FROL exposes per-shipment exception codes for triage. The 60% to 70% of misses that are operational (FedEx-side or merchant-correctable) are the actionable subset. **SmartPost and Ground Economy parcels show up as late, why?** SmartPost (now FedEx Ground Economy) hands the parcel to USPS for the final-mile leg. The card uses FedEx's `actualDeliveryDateTime` which fires when USPS scans the final delivery. SmartPost has materially weaker on-time than pure FedEx Ground (4 to 8 percentage points worse) because USPS final-mile is less reliable. If your merchant uses SmartPost heavily, the card's late count will reflect the USPS handoff lag. Switching cost-sensitive parcels from SmartPost to FedEx Ground typically lifts on-time but raises unit cost 15% to 25%. **Can I exclude shipments suspended by FedEx (storm, wildfire) from the count?** Not currently. The card scores by raw scan dates. FedEx's portal excludes them; that is why your portal number reads lower during disruptions. The roadmap includes a "fault-attribution" overlay that classifies each late as FedEx-fault, merchant-fault, customer-fault, or carrier-suspended, but it ships in a later wave. **My customer is complaining about a late delivery I cannot find on this card. Why?** Two reasons. (1) **Sync lag**, scans take 30 minutes to 4 hours; if the customer just got the parcel today and called immediately, the card may not have caught up. (2) **In-transit when the customer called**, shipments still in transit do not count as late until they deliver. A parcel that the customer expects today and is showing "out for delivery" but did not actually arrive will show as late tomorrow once FedEx posts the next-day Delivered scan. Always cross-reference customer complaints by tracking number against FedEx Tracking API directly, not against this card alone, for live disputes. **The alert tripped at 5.4% of total. Is the threshold right?** The 5% default is a healthy-merchant baseline. Most DTC brands on FedEx run 1.5% to 3% late rate at steady state, so 5% is a meaningful alert. For high-volume brands shipping 50,000+ parcels a month, 5% can mean 100+ late shipments a day, set a tighter alert at 3% to 4%. For low-volume brands (\<5,000 parcels/month), individual zone or weather events can spike daily late rate to 10%+ on noise; consider raising to 7% or moving to the 30D rolling rate for stability. **How does FedEx's surge pricing affect this card?** Surge pricing affects [Avg Shipping Cost](/nerve-centre/kpi-cards/fedex/avg-shipping-cost) directly; this card indirectly. During surge weeks (Q4 peak, hurricane response, post-storm catch-up), FedEx allocates capacity to Express services first to protect the money-back guarantee, leaving Ground capacity-constrained. Ground late count climbs disproportionately. Plan around this: shift volume toward Express in surge windows even at higher unit cost. *** ### Tracked live in Vortex IQ Nerve Centre *Late Shipments* is one of hundreds of KPI pulses Vortex IQ tracks across FedEx 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](https://app.vortexiq.ai/login) or [book a demo](https://www.vortexiq.ai/contact-us) to see this metric running on your own data.