At a glance
Share of international Australia Post parcels that cleared both Australian export processing and destination-country customs within 5 days of lodgement. Customs is the single biggest source of unpredictable delay on cross-border parcels, and it is almost always a paperwork problem you can fix at source: a missing or wrong customs declaration, an unparseable HS tariff code, or an under-declared value. A reading below 80 percent points to a systematic declaration issue (often the B374 / electronic customs declaration data) or a destination-country backlog.
| What it tracks | COUNT(intl WHERE customs_cleared_at <= lodged_at + 5 days) / COUNT(intl WHERE customs_cleared_at IS NOT NULL OR target_passed) over the rolling 30-day window. The clearance milestone is detected from the tracking-event stream. |
| Data source | International consignments from the Australia Post Shipping & Tracking API. Reads the article ID, lodgement scan, and the customs-related tracking events: AU export clearance, “held in customs” / “released by customs” at destination, and the destination handover scan. Declaration data originates from the electronic customs declaration (the B374 declaration data lodged with the article). |
| Clearance definition | ”Cleared” means the parcel has passed AU export and received a destination-customs release (or onward-movement) scan. A parcel still showing “held by customs” past the 5-day mark counts as a miss. |
| Service scope | International outbound only (International Standard, International Express, and tracked international products). Domestic parcels have no customs leg and are out of scope. Inbound returns are excluded. |
| Time window | 30D vsP (rolling 30 days, period over period). International volumes are lower, so daily readings are very noisy; use the 30-day view. |
| Alert trigger | <80%. Below 80 percent more than one international parcel in five is stuck in customs beyond 5 days, which is a paperwork or destination-backlog signal worth investigating, not background noise. |
| Roles | owner, operations |
Calculation
For each international consignment, the card finds the lodgement scan (clock start) and the destination-customs release scan (clock stop), then tests whether the elapsed time is 5 days or less. Parcels released within 5 days score on time; parcels released after 5 days, or still held in customs once the 5-day target has passed, score as a miss. The 5-day window deliberately spans two customs touchpoints: AU export processing and destination-country import clearance. Most of the variance lives at the destination. Key points:- The delay is usually documentation, not the carrier. Australia Post moves the parcel; customs holds it. The most common triggers are a missing or malformed electronic customs declaration, an HS tariff code that the destination cannot parse, an under-declared or zero-declared value, or restricted-goods flags. These are fixable upstream in your label / manifest data.
- Destination backlog is the other driver. Peak seasons, destination-country processing changes (for example EU IOSS / VAT-at-import handling, UK import VAT rules), and customs-staff actions can hold parcels regardless of perfect paperwork. When the miss is concentrated on one destination and your declarations are clean, it is a backlog, not your error.
- Scan coverage varies by lane. Some destination carriers provide a clean “released by customs” scan; others only emit an onward-movement scan. The card uses the best available release signal per lane, which is why clearance precision differs between countries.
Worked example
An Australian skincare brand shipping internationally from Mascot, NSW (2020), around 1,150 international consignments in the trailing 30 days. Reading taken at 09:00 AEST on 14 Apr 26 for the window 16 Mar 26 to 14 Apr 26.| Destination | Intl consignments | Cleared customs within 5d | Clearance rate |
|---|---|---|---|
| New Zealand | 420 | 408 | 97.1% |
| United States | 310 | 245 | 79.0% |
| United Kingdom | 180 | 119 | 66.1% |
| Singapore / Hong Kong | 130 | 122 | 93.8% |
| Canada / rest of world | 110 | 86 | 78.2% |
| All international (this card) | 1,150 | 980 | 85.2% |
<80% is not tripped at the aggregate, but the UK lane at 66.1 percent is well below it. Five things to notice:
- The UK lane is the problem, and it is probably paperwork. A single destination 19 points below the next-worst lane is the classic signature of a declaration defect, not a network failure. Pull the held-in-customs UK consignments and inspect their electronic customs declarations for missing HS codes, blank descriptions, or zero-value declarations. Fix the manifest data at source and the lane recovers within a cycle.
- NZ and Singapore set the achievable ceiling. At 97 and 94 percent, these lanes prove your origin processing and carrier hand-off are clean. The variance is downstream, in the destinations that hold parcels.
- The US at 79 percent is a watch, not yet an alarm. Just below the floor and on high volume. Check whether the misses cluster on a value band (de-minimis threshold edge cases) or on a product category (restricted-goods flags). The fix differs.
- A clean declaration cannot fix a destination backlog. If UK declarations are demonstrably clean and the lane is still slow, the cause is destination-side processing, not you. Annotate the period and watch for recovery rather than chasing your own paperwork.
- Read it next to the tracking-gap card. International parcels get a longer grace window before a tracking gap is flagged precisely because customs holds are normal. A parcel held in customs at day 4 is fine here and fine there; a parcel with no scan at all for 5 days is a different problem. Pair with Shipments with Tracking-Event Gap >24h (domestic) / >5d (intl).
Sibling cards merchants should reference together
Customs clearance is the cross-border speed-and-paperwork metric. Pair it with these to localise the cause:| Card | Why pair it with Customs Clearance Rate | What the combination tells you |
|---|---|---|
| International Destinations, Top 10 | Which destinations carry your volume. | A clearance miss concentrated in a high-volume destination is far more costly than the same rate on a long-tail country. |
| Shipments with Tracking-Event Gap >24h (domestic) / >5d (intl) | The international grace window exists because customs holds are normal. | Distinguishes a legitimate customs hold from a parcel that has genuinely gone dark. |
| Avg Transit (days) | Total door-to-door time, of which customs is one slice. | If transit is long but clearance is fast, the delay is in linehaul or last-mile, not customs. |
| Returned to Sender | Parcels customs rejects often come back. | A customs failure on a lane often shows up later as a returned-to-sender spike on the same destination. |
| Exception Rate | Held-in-customs is an exception type. | A rising international exception rate predicts a falling clearance rate. |
| Open Claims | Lost or destroyed international parcels become claims. | Long customs holds that end in seizure or loss convert into claims; this is the upstream signal. |
| On-Time Delivery Rate | Blended OTD that customs misses drag down for international lanes. | Isolates how much of an OTD dip is customs versus domestic transit. |
Reconciling against the source
Where to look in Australia Post’s own tooling: Per-article customs milestones appear on the Australia Post tracking portal and, for account holders, in MyPost Business and the Australia Post Merchant Portal consignment detail, which lists the AU export scan, the held / released customs events, and the destination handover. The same events are exposed through the Shipping & Tracking API tracking-events endpoint. The declaration data you lodged (the electronic customs declaration / B374 content) is visible against the article in the manifest. The closest like-for-like check is to take a sample of consignments this card flagged as missed, open each in the tracking portal, and confirm the days between the lodgement scan and the destination-customs release scan exceed 5. Why our number may legitimately differ from Australia Post’s view:| Reason | Direction | Why |
|---|---|---|
| Destination-scan availability | Either | Some destination carriers emit a clean “released by customs” scan; others only an onward-movement scan. Where the explicit release scan is missing, the card infers clearance from the next movement, which can differ from the portal’s interpretation by hours. |
| Scan timezone is destination-local | Boundary days | Customs and destination scans are timestamped in the destination’s local time, while the lodgement scan is AEST / AEDT. The 5-day elapsed calculation accounts for the offset, but a near-boundary parcel can sit on either side depending on how each system normalises the zones. |
| Tracking-event ingestion lag | Ours can lag | The tracking-events feed batches scans; a customs-release event from overnight may not be ingested for minutes to a few hours. A just-cleared parcel can briefly still read as held. |
| AU export vs destination clearance split | Different attribution | The portal shows each customs event separately. This card collapses both touchpoints into a single 5-day clearance test, so it will not, on its own, tell you whether the delay was at AU export or destination import; inspect the per-article scans for that. |
| Declaration-data correction mid-flight | Either | If a held parcel’s declaration is amended and re-presented, the clearance timestamp reflects the second presentation. The portal shows the full hold-and-release history. |
| Card | Expected relationship | Causes of legitimate divergence |
|---|---|---|
Cross-connector: shopify.international_order_share | The demand side of cross-border volume. | A rising international order share raises exposure to customs delay even at a constant clearance rate. |
Cross-connector: shopify.refund_rate | Downstream impact of stuck international parcels. | Long customs holds drive cross-border refunds at a longer lag than domestic; many other drivers exist. |