At a glance
Share of Australia Post consignments that threw at least one tracking exception event in the trailing 30 days. An exception is any non-happy-path scan: held at parcel locker, address invalid, attempted delivery (recipient absent), held at depot, network impact (cyclone, flood), customs hold for international. The rate is a leading indicator: rising exceptions today predict falling On-Time Delivery Rate over the next 24 to 72 hours.
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 Brisbane outdoor adventure brand from earlier examples, 27,200 outbound consignments in the trailing 30 days. Reading taken at 09:00 AEDT on 12 Mar 26.
The card reads 3.6 percent, alert at
>3% is tripped. Four observations:
- Network impact accounts for the spike above baseline. Outside the wet season this merchant runs a 2.0 to 2.5 percent baseline. The 0.57 point contribution from cyclone-affected postcodes is the difference between a healthy and a tripped reading. The action is to annotate the alert as weather-driven, not to change operational process.
- Parcel locker overflow is structural in metro lanes. 1.15 percent held at parcel locker is a metro-customer choice (recipient nominated locker delivery) compounded by Australia Post locker capacity in dense suburbs. Locker overflow returns to the depot if not collected in 48 hours. Expect to see this rate climb 1 to 2 points during November and December as gift volume fills lockers.
- Address invalid is upstream, not Australia Post. 0.45 percent address invalid traces back to Shopify checkout address validation. Suggests a checkout audit; the merchant could enable Australia Post’s DPID address verification API at checkout to halve this rate.
- Customs hold is the international tail. 48 consignments held at destination customs is roughly 6 percent of the merchant’s international EMS volume. Most clear within 3 to 5 days; rate is consistent with cross-border to UK / EU / US.
Sibling cards merchants should reference together
Reconciling against the vendor’s own dashboard
Where to look in Australia Post’s own portal: Australia Post Business → MyPost Business → Tracking → Filter: Exceptions. eParcel customers get the same view in eParcel Customer Centre → Tracking → Exception Report, which provides per-event-type breakdowns. Why our number may legitimately differ from Australia Post’s report:
Cross-connector reconciliation:
Known limitations / merchant FAQs
My exception rate just doubled overnight. What changed? Three usual causes, in order of likelihood: (1) A network event, check Australia Post’s important updates for cyclone, flood, bushfire, or industrial-action notifications. (2) A label-data regression, check whether your checkout pushed a recent change to address validation; misformatted addresses cause “address invalid” exceptions in batches. (3) A specific postcode tail, use OTD by Route to see if the spike concentrates in 2 or 3 postcodes (a local depot disruption) or spreads uniformly (network-wide). Why is my exception rate so much higher than UK or US peers? Geography. Australia’s address-format heterogeneity in regional and remote areas means “address invalid” runs structurally higher than in the UK (which has a national PAF) or the US (which has standardised ZIP+4). Add in the climate-driven network impact contribution from cyclone and flood events, and an Australian DTC merchant should expect 1.5 to 2.5 percent baseline vs a UK merchant’s 0.8 to 1.5 percent. Compare your reading to your historical baseline, not to UK / US benchmarks. The portal shows a different exception rate. Which is right? Both for slightly different denominators. Australia Post’s portal often counts events; the card counts shipments. A consignment with three exception events (held, attempted, redelivered) counts as 3 in the portal’s event view but as 1 in the card. The card’s view is more useful for customer-service staffing because it correlates 1:1 with WISMO ticket volume. Should I worry more about “held at parcel locker” or “address invalid”? Different signals. Held at parcel locker is a recipient-behaviour issue (delivery option chosen but not collected); the merchant cannot directly fix it but should warn customers in the post-purchase email that lockers expire in 48 hours. Address invalid is a checkout-process issue; the merchant fixes it by enabling address validation at checkout. The first is acceptable structural noise; the second is a process bug. How do international EMS customs holds affect this rate? Customs hold counts as an exception once the carrier issues theCUSTOMS_HOLD event, which is typically 3 to 5 days after the parcel reaches the destination border facility. International exceptions are typically 3 to 8 percent of international volume vs less than 2 percent for domestic. If a merchant’s mix is 20 percent international, customs holds alone contribute roughly 0.6 to 1.6 points to the headline rate.
The wet season spike feels unfair. Can I exclude flood-affected postcodes?
Operationally yes (use OTD by Route to see the affected postcodes and adjust your customer-service expectations), but the card never silently excludes. The reasoning: customers in flood zones still expect their parcels and still call your support line; muting the signal would hide the workload. The right move is to annotate the alert as weather-driven and adjust thresholds for the affected weeks, not to redefine the metric.
What is “Recipient not present” telling me, and is it my fault?
Australia Post attempted delivery, no one was home, and the parcel was either left for collection at a locker / depot or returned for redelivery. Not the merchant’s fault; recipient-behaviour. But it is a checkout opportunity: offer parcel-locker delivery, weekend delivery, or signature-on-file at checkout to reduce attempted-delivery rate. Aussie DTC baseline is 0.8 to 1.2 percent; if you are above 2 percent, your address mix may be skewed to apartments without concierge.
My alert just fired during Black Friday. Is this normal?
Mostly yes. Exception rate climbs 1 to 3 points during peak from “held at parcel locker” overflow (lockers fill faster than customers collect) and “held at depot for collection” (depot capacity stretched). The action is to pre-warn customers in the BFCM order-confirmation email that lockers may fill up and to prioritise direct-to-door delivery for time-sensitive items. Reset thresholds for the BFCM week so you do not get re-alerted every reading.