“Arrived at destination airport / Custom clearance completed”Normalized: in_transit (In transit)YunExpress (yunexpress)UniUni (uniuni)USPS (usps)

YunExpress 'Arrived at destination airport / Custom clearance completed' & Last-Mile Handoff.

Your `YT…` parcel has landed at the destination gateway airport (such as JFK, LAX, ORD, LHR, or YVR), cleared import customs, and is being handed over to the local last-mile courier.

Try a live tracking number:

What is happening in the supply chain

YunExpress manages the origin pickup in China, export consolidation, air linehaul, and import customs entry. Once customs releases the container, YunExpress transfers the parcel to USPS (`92…`), UniUni (`UUS…`), SpeedX (`SPX…`), GOFO (`GFUS…`), Royal Mail, or Evri for final delivery.

Handoff guide: /handoff/yunexpress-to-uniuni →92… USPS Awaiting Item Checker →
Verbatim carrier scan
“Arrived at destination airport / Custom clearance completed”
Normalized API status
in_transit
Typical time to delivery
2–5 business days
Recommended recipient action
Paste your YT… tracking number above to see the extracted local tracking number in the response message, then track that second number for doorstep updates.
Developer / WISMO action
Read the top-level message field in GET /v1/track/{number} (e.g., 'Handed to UniUni as UUSC000019638703' or 'Handed to USPS as 92001901...') and chain a second GET call on the extracted barcode.

How lastscanned normalizes this scan

Instead of maintaining brittle regexes for every carrier's raw scan phrasing across 200 carriers, query GET /v1/track/{number} or connect https://mcp.lastscanned.com.

Get an API keyYunExpress API docs

Synchronous GET request

curl "https://api.lastscanned.com/v1/track/YT2601500703194270" \
  -H "Authorization: Bearer lsk_live_YOUR_API_KEY"

Normalized JSON response

{
  "carrier": "yunexpress",
  "trackingNumber": "YT2601500703194270",
  "status": "in_transit",
  "statusDescription": "Arrived at destination airport / Custom clearance completed",
  "message": "Handed to UniUni as UUSC000019638703",
  "events": [
    {
      "timestamp": "2026-10-26T14:22:00Z",
      "localTime": "2026-10-26T10:22:00",
      "status": "in_transit",
      "description": "Arrived at destination airport / Custom clearance completed",
      "location": "NEW YORK, NY"
    }
  ]
}

Frequently asked questions

Why do YunExpress updates stop or slow down after 'Custom clearance completed'?
Because physical custody transfers from YunExpress's airport broker to the local last-mile carrier (USPS, UniUni, SpeedX, GOFO). Tracking the extracted secondary barcode gives you real-time local hub scans.
Where does lastscanned return the new USPS or UniUni tracking number for YunExpress?
In the top-level message field of the JSON response (for example, 'Handed to USPS as 926129...').

Related cross-border e-commerce scans

View all 45 scan statuses →

All 200 supported carriers

Major carriers

Regional and last mile

International posts and couriers

Cross-border