At a glance
Absolute count of Australia Post consignments where the delivered scan landed after the published estimated delivery window for the service tier, in the trailing 7 days. The count is the operational workload behind the On-Time Delivery Rate percentage. A 95 percent OTD on 6,800 weekly parcels is 340 late deliveries, which is roughly 340 customer-service tickets in flight.
| What it counts | COUNT(shipments WHERE delivered_at > estimated_delivery_date) over the trailing 7 days. Deliveries past 14 days roll into RTO/lost territory, see Returned to Sender. |
| API endpoint | GET /shipping/v1/shipments and GET /shipping/v1/track/items/{trackingNumber}. Reads service_code, consignment_id, estimated_delivery_date, delivered_at. In-transit consignments not yet delivered are excluded; only consignments with a final delivered scan and a missed aim count. |
| Service-tier scope | All tracked services (Express Post, Parcel Post, eParcel Premium, StarTrack). The aggregate is the merchant’s total workload; per-tier splits live in siblings. |
| Geographic OTD variance | Late counts skew heavily to remote and regional postcodes where transit-time variance is widest. A merchant with 15 percent volume into outback lanes typically sees 35 to 50 percent of late shipments coming from that 15 percent of volume. |
| Returns / RTO | Outbound only. Returns leg is excluded. |
| Climate handling | Cyclone, bushfire, flood events spike the count for affected weeks; not auto-excluded. The card reports the actual surge so the operations team can staff customer service accordingly. |
| Peak-period seasonality | Late counts roughly 2 to 3 times normal during the 1 to 23 December peak window. Click Frenzy and Black Friday weeks add a 30 to 50 percent surge for 7 to 10 days. |
| Time window | 7D (rolling 7 days). The 7-day window is the typical customer-service ticket review cadence. |
| Alert trigger | >5% of total weekly shipments. For a 6,800 parcel/week merchant, alert fires at 340 late shipments. |
| Roles | owner, operations |
Calculation
Calculated automatically from your Australia Post data. See the At a glance summary above for what the metric tracks and the worked example below for a typical reading.Worked example
The same Brisbane outdoor adventure brand from the OTD Rate example, 6,800 outbound parcels per week, mixed Australia Post service mix. Reading taken at 09:00 AEDT on 12 Mar 26 for the trailing 7 days (06 Mar 26 to 12 Mar 26).| Service tier | Shipments (7D) | Late | Late % |
|---|---|---|---|
| Parcel Post | 3,740 | 252 | 6.7% |
| Express Post | 2,040 | 75 | 3.7% |
| StarTrack Premium | 680 | 16 | 2.4% |
| eParcel Premium | 340 | 9 | 2.6% |
| All AP tracked (this card) | 6,800 | 352 | 5.2% |
>5% of total is just tripped (352/6,800 = 5.2 percent). Three observations:
- Parcel Post is the workload driver. 252 late Parcel Post shipments are 71 percent of the total late count, despite Parcel Post being only 55 percent of volume. The customer-service queue this week will be dominated by Parcel Post WISMO (“where is my order”) tickets.
- The remote tail compounds during wet weeks. Splitting by destination, 134 of the 352 late shipments (38 percent) went to remote/outback postcodes which are 15 percent of volume. Tropical Cyclone activity north of the Tropic of Capricorn this week added roughly 80 of those 134.
- Express Post late count is structural baseline. 75 late Express Post shipments per 7 days is the level for this merchant outside peak. It comes from non-Express-Post-Network postcodes paying the premium but receiving 2 to 4 day delivery, not from network failure on the metro corridors.
Sibling cards merchants should reference together
| Card | Why pair it with Late Shipments | What the combination tells you |
|---|---|---|
| On-Time Delivery Rate | The percentage view of the same population. | Percentage tells you the customer-felt rate; this count tells you the operations workload. |
| Exception Rate | Predictor at 24 to 72 hour lag. | Spike in exceptions today predicts a spike in lates over the next few days. |
| OTD by Route | Where the late shipments are going. | Confirms whether the spike is regional or network-wide. |
| Avg Transit (days) | Mean transit creep is a leading indicator of late count. | A 0.5 day transit increase usually precedes a doubling of late count within 7 days. |
| Failed Deliveries | Different failure mode (attempted but not delivered). | Distinguishes “couriered late but landed” from “couriered on time but no one home”. |
Cross-connector: shopify.unfulfilled_orders | Upstream input. Slow fulfilment makes late count worse. | A backlog 2 to 4 days ago is now a late-shipment surge today. |
Cross-connector: shopify.refund_rate | Downstream consequence. | Late count spike at day 0 typically drives a refund rate spike at day 7 to 14. |
Reconciling against the vendor’s own dashboard
Where to look in Australia Post’s own portal: Australia Post Business → MyPost Business → Reports → Shipment Status → Filter: delivered late. Larger eParcel customers find the same view in eParcel Customer Centre → Performance → Late Shipments Report. Why our number may legitimately differ from Australia Post’s report:| Reason | Direction | Why |
|---|---|---|
| Timezone (AEDT/AEST/AWST) | Boundary day off | Portal reports in account timezone; card stores UTC. A late shipment delivered at 23:30 AEDT shows different “day” depending on which side you read. |
| Customs lag for international | Ours higher | International EMS consignments awaiting customs clearance overseas can sit “in transit” for 5 to 14 days; the portal sometimes pauses the SLA clock during customs, the card does not. |
| Climate-driven exception spikes | Either | Postcodes under official network impact notification (cyclone, flood) are sometimes excluded from the portal’s “late” tally; the card always counts them. |
| Peak-period batch processing | Either | November to December the portal can show a 5 to 7 day lag in the late-shipment tally while batches catch up; the card surfaces what the API has actually returned. |
| In-transit-but-already-late | Ours lower | The card counts only consignments with a final delivered scan past aim. The portal sometimes flags in-transit consignments past their aim as “late” already; the card calls those “exceptions” not “late”. |
| Card | Expected relationship | Causes of legitimate divergence |
|---|---|---|
shopify.unfulfilled_orders | Upstream input. | Webhook delays, B2B/pre-order flows. |
shopify.refund_rate | Downstream sentiment. | Refund rate has many drivers. |