Late Shipments, Sendle

Metrics type: Key Metrics • Category: Shipping & Courier

At a glance

Count of Sendle parcels dispatched in the last 7 days whose actual delivery date exceeded Sendle’s quoted ETA window. Sendle is a flat-rate single-courier service (zone-based pricing, published transit estimates per zone), so the on-time question is simpler than a multi-carrier aggregator like EasyPost or Shippo: there is one carrier, one promise per zone, and the late count is what it is. The simplicity is the point. This is the workload number behind the On-Time Delivery Rate percentage.


What it counts	`COUNT(parcels WHERE delivered_at > eta_max AND ship_date >= now-7d)`. Each parcel carries a Sendle-quoted ETA range at booking (for example “1 to 4 business days”); a parcel is late when actual delivery passes the upper bound of that range.
Data source	Late Shipments for the selected period, derived from the Sendle Orders API (`GET /api/orders`) plus tracking events (`GET /api/orders/{sendle_reference}/tracking`). The card reads `state`, `delivered_at`, `estimated_delivery_date_minimum` and `estimated_delivery_date_maximum` per order.
Delivery success criterion	Sendle records `Delivered` once the contracted courier logs proof of delivery (signature or photo on most AU and US routes, scan-only on some metro lanes). States `Unable to Deliver`, `Pickup Attempted` and `Lost` keep a parcel out of the late numerator until a terminal delivered scan arrives.
On-time threshold	Upper bound of Sendle’s quoted ETA window, no grace period. Estimates vary by zone: AU metro 1 to 2 days, AU regional 2 to 5 days, AU remote 4 to 8 days, US zones 1 to 8 days depending on tier. Each parcel is judged against its own zone promise.
Returns / RTS	Sendle’s Return to Sender flow for undeliverable parcels surfaces on Returned to Sender, not here. A failed-then-recovered parcel counts as late if its eventual delivery passes the window.
Service-level scope	All Sendle products pooled. Most AU accounts ship on the standard flat rate; US accounts may mix tiers. The card is tier-aware through the per-parcel ETA, not through a service-code field.
Carbon neutrality	Sendle is 100 percent carbon-neutral by default. This card measures lateness, not carbon. The offset overlay is a financial accounting layer and never affects the late count.
Time window	`7D` (rolling 7-day window). Daily readings are noisy below roughly 150 parcels per day.
Alert trigger	`>5% of total` parcels in the same 7D window (the late count exceeds 5 percent of all parcels with a terminal status in the period).
Roles	owner, operations

Calculation

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

Worked example

An Australian DTC home-goods brand using Sendle for nationwide despatch from a Sydney warehouse. Reading taken at 09:00 AEDT on 12 Mar 26 for the trailing 7 days (05 Mar 26 to 11 Mar 26).

Zone	Parcels (7D)	Delivered late vs ETA	Late share
AU Metro (Sydney, Melbourne, Brisbane)	1,420	38	2.7%
AU Regional (tier-2 cities)	680	47	6.9%
AU Remote (NT, regional WA, Tasmania)	240	62	25.8%
All zones (this card)	2,340	147	6.3%

The card reads 147; the share is 6.3 percent, just over the >5% of total alert threshold. Five things to notice:

Remote zone dominates the late count and the alert. A 25.8 percent late rate on AU Remote contributes 62 of the 147. Strip remote out and the headline drops to 4.0 percent and the alert clears. Remote-zone lateness is structural for any flat-rate single-carrier service: Sendle’s quoted ETAs assume a clean courier handover, which fails more often the further you get from a metro depot.
Sendle is flat-rate, so there is no carrier-mix lever. Unlike an aggregator where the operator can rate-shop between carriers per parcel, Sendle merchants cannot switch courier inside the platform. The levers are: (a) accept the trade and absorb the operational pain, (b) widen the customer-facing ETA in checkout copy to add buffer, or (c) move remote-zone orders to a different carrier entirely (Australia Post Express, StarTrack premium).
Metro at 2.7 percent is healthy. Sendle’s metro performance is competitive with the major Australian couriers, and the value proposition (carbon-neutral, simple flat rate) holds for roughly 80 percent of typical AU DTC volume.
The 6.3 percent trip is the cue to widen checkout copy, not to switch carriers. Sendle merchants typically respond by updating the cart ETA estimate (for example from “2 to 4 days” to “3 to 6 days regional, 5 to 10 days remote”). Customer expectations recalibrate, complaint volume drops, and the operational late count is unchanged but the customer-facing experience improves.
The Q4 pre-Christmas pattern is worse. AU Christmas peak (mid-November to mid-December) typically lifts AU Remote late share to 35 to 45 percent because Sendle’s contracted couriers (Couriers Please, Aramex and their regional partners) hit capacity. Plan checkout copy and despatch cutoffs ahead of the peak rather than reacting to the alert.

Sibling cards merchants should reference together

Late count is the headline workload number; for Sendle the diagnostic playbook is short because the carrier is fixed.

Card	Why pair it with Late Shipments	What the combination tells you
On-Time Delivery Rate	The percentage counterpart of the same metric.	Rate steady and count climbing means volume is rising with the structural mix unchanged. Rate falling means the network or the zone mix is shifting.
Avg Transit (days)	Companion timing metric.	Late count up plus transit up means couriers are slowing on the routes. Late count up plus transit flat means the ETA quotes were tight at booking.
OTD by Route	The zone-by-zone breakdown.	Pinpoints which zone is dragging the headline, with the most value on AU Remote and US long-haul ground.
First-Attempt Delivery Rate	Re-attempts add days and push parcels past their ETA.	First-attempt rate falling and late count rising points at recipient or address issues, not network capacity.
Failed Deliveries	Failed-then-recovered parcels also count as late.	A failed-delivery climb tracking the late-count climb points at recipient or address problems rather than the network.
Returned to Sender	RTS is the alternate ending for non-delivery.	Both rising together means the network is shedding parcels (theft hotspots, capacity pressure).
Cross-connector: `shopify.unfulfilled_orders`	Upstream pressure.	A slow Shopify-to-Sendle handover eats into transit time and lifts the late count.
Cross-connector: `shopify.refund_rate`	Downstream impact.	A 5-point rise in late share typically precedes a refund-rate climb at 7 to 14 days.

Reconciling against the carrier’s own dashboard

Where to look in Sendle’s own tooling: Sign in to the Sendle Dashboard and open Orders with the Late delivery filter applied. The filter returns the per-parcel late list with the original ETA, the actual delivery date and the destination zone. The closest like-for-like view is Orders, filtered to Late, last 7 days. Sendle does not expose a standalone late-count widget on the home screen, so the filtered order list is the canonical source. For programmatic reconciliation, page the Sendle Orders API and compare delivered_at against estimated_delivery_date_maximum per order; the tracking timeline on each order shows the courier scan history behind the delivered timestamp. Why our number may legitimately differ from Sendle’s portal:

Reason	Direction	Why
ETA window edge	Either	Sendle’s portal sometimes treats the ETA midpoint as “expected” while the card uses the upper bound. A parcel delivered exactly on the upper-bound day classifies differently in the two systems.
Failed-and-recovered parcels	Ours sometimes higher	A parcel that failed delivery once and eventually arrived counts as late here if the eventual delivery passes the ETA. Sendle’s portal sometimes drops recovered parcels from the late list.
Tracking-event ingestion lag	Ours can lag	Sendle pushes courier scans in batches; a parcel delivered a few hours ago may not yet show a delivered scan in our index. We classify conservatively as still in transit rather than guessing late.
Timezone (carrier-local scans)	Boundary days off	The Sendle portal renders in the account’s local zone (AEST/AEDT for AU, the relevant US zone for US). Underlying courier scan timestamps are in carrier-local time. The card normalises to UTC, so boundary-day parcels can land on different days. Over a 7-day window the totals usually agree within 1 percent.
In-transit exclusion	Both exclude	Parcels still in transit sit outside both the numerator and the denominator until a terminal status arrives.

Cross-connector reconciliation:

Card	Expected relationship	Causes of legitimate divergence
`shopify.unfulfilled_orders`	Upstream input. Shopify hands orders to Sendle via webhook; the handover lag is usually under an hour.	Manual bookings made outside Sendle, B2B or pre-order flows.
`shopify.refund_rate`	Downstream sentiment proxy.	Refund rate has many drivers (sizing, quality, returns); lateness is one input with a 1 to 2 week lag.

Known limitations / merchant FAQs

Why is my late count higher in remote zones? Sendle’s flat-rate model means remote zones are effectively subsidised by metro volume. The contracted couriers servicing remote routes (regional partners under Couriers Please and Aramex in AU, partnered last-mile in the US) run on tighter margins with less buffer, so capacity pressure hits remote first. This is structural, not a fault of any single delivery. Sendle is carbon-neutral. Does that affect on-time performance? No. The carbon-neutral claim is delivered through offset purchasing on the back end, not through any change to courier routing. The same parcels travel through the same couriers; carbon neutrality is a financial overlay. Late count and OTD are measured on physical delivery only. My checkout shows “1 to 4 business days” but Sendle quotes 1 to 5. Which one drives the late count? The card uses Sendle’s quoted ETA (1 to 5), not your checkout copy. If your checkout is tighter than Sendle’s quote, customers perceive lateness even when the card reads on-time. Align checkout copy to Sendle’s actual ETA windows. A common pattern is the card reading a healthy 96 percent while customer satisfaction is poor because the checkout over-promised. What about parcel cover and lost-parcel claims? Separate flow. Sendle includes basic cover on AU and US shipments (AUD 100 / USD 100 by default, with extra cover purchasable per parcel). Lost-parcel claims appear on Open Claims, not here. A lost parcel is not late: it never delivers, so it stays off this card entirely. Why is my AU Metro late share creeping up over the past 90 days? Three usual reasons. (1) Volume growth pushing existing capacity, especially Sydney and Melbourne. (2) Sendle adjusting its courier-partner mix without changing the flat rate (operationally invisible to you). (3) Your own postcode mix drifting into outer-metro suburbs that price as Metro but behave like Regional. Pair with Cost by Zone to see whether cost stays flat (Sendle shifted couriers) or rises (your zone mix changed). Can I switch Sendle off for remote zones and use Australia Post Express instead? Yes, this is the standard remote-zone pattern. Most Sendle merchants use Sendle for roughly 80 percent of volume (metro and tier-2 regional) and pay the premium for AU Post Express on remote and time-sensitive parcels. The cutover lives in your Shopify or BigCommerce shipping rules, not in Sendle. This card tells you where the cutoff should sit. How do I reduce remote-zone late count without switching carrier? Three actions. (1) Widen the ETAs in checkout copy to bake in buffer (most effective and free). (2) Move remote despatch from once-daily to once-every-two-days, batching for consolidated full-load pickup; this often improves outcomes because the courier collects a larger consolidated batch with priority routing. (3) Shift customer comms to expectation-setting language (“delivery in 5 to 10 days, sometimes longer”); perceived lateness drops even when operational lateness does not. My AU Christmas late count is 35 percent. Is that normal? Yes, structurally. AU Christmas peak (mid-November to mid-December) consistently lifts late share to 30 to 50 percent on Sendle. This is the trade-off of a flat-rate single carrier: an aggregator can divert volume to a less-saturated network during peak, but a single-carrier merchant cannot. Plan customer communication ahead and consider a supplemental Express option for time-sensitive parcels in this window. Failed deliveries versus late shipments, what is the difference? A failed delivery (recipient not home, signature refused, address inaccessible) is a separate event on Failed Deliveries. A failed-then-recovered parcel that eventually delivers counts as late here if the eventual delivery passes the ETA window. A failed-then-RTS parcel goes to Returned to Sender and never appears on the late count.

Tracked live in Vortex IQ Nerve Centre

Late Shipments is one of hundreds of KPI pulses Vortex IQ tracks across Sendle 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 carrier’s own dashboard

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 carrier’s own dashboard

​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 carrier’s own dashboard

Known limitations / merchant FAQs

Tracked live in Vortex IQ Nerve Centre