Who delivers YunExpress (`YT...`) packages in Poland?

YunExpress partners primarily with InPost (both InPost Kurier home delivery and Paczkomat® lockers), DPD Poland, and Poczta Polska.

Why does InPost say 'W trakcie przygotowania' while my `YT...` parcel is still in China?

YunExpress registers the 24-digit InPost label electronically before departure; InPost updates to 'Przyjęta w oddziale' once the truck arrives in Poland.

YunExpress (yunexpress)→InPost (inpost)

YunExpress European Parcel Locker Linehaul to InPost Poland/UK/Italy Handoff

How YunExpress (YT…) cross-border parcels from Shenzhen link to 24-digit InPost Paczkomat® and Kurier barcodes across Poland and Europe.

Try a live tracking number:

Barcode transition: YunExpress to InPost

When YunExpress clears customs and hands off to InPost, lastscanned surfaces the secondary tracking number in the top-level message field.

YunExpress lookup →InPost lookup →Format & check-digit detector →

Origin / middle-mile carrier: YunExpress (yunexpress)
YunExpress Waybill (YT + 16 digits): YT… (18 chars)
Origin example: YT2429021272199901
Final-mile carrier: InPost (inpost)
InPost 24-Digit Barcode (620…): 620… (24 digits)
Final-mile example: 620192837461528391029901
Extracted in .message: Delivered to local carrier InPost - 620192837461528391029901

How the YunExpress → InPost handoff works

Follow the parcel across both networks without waiting on asynchronous webhooks or losing visibility at the handoff boundary.

1. Pre-allocation of the 24-digit InPost barcode in Shenzhen: YunExpress generates the target InPost (`620...`) barcode when the parcel is inducted in Shenzhen or Hong Kong.
2. EU customs clearance & Polish hub feeder: Parcels clear EU IOSS customs in Amsterdam, Liège, or Budapest and travel by overnight truck to InPost's Stryków hub in Poland.
3. Next-day InPost Kurier or Paczkomat® delivery: InPost delivers the parcel to the recipient's door or Paczkomat® locker the next working day.
YunExpress query: GET /v1/track/YT2429021272199901?carrier=yunexpress
InPost query: GET /v1/track/620192837461528391029901?carrier=inpost

Chain YunExpress → InPost in code or MCP

Resolve both legs synchronously in TypeScript, curl, or your AI support agent via Streamable HTTP MCP.

Get an API key WISMO agent guide

REST (Synchronous GET)

# 1. Query YunExpress origin waybill (extracts final-mile barcode in .message):
curl "https://api.lastscanned.com/v1/track/YT2429021272199901" \
  -H "Authorization: Bearer lsk_live_YOUR_API_KEY"

# 2. Query the extracted InPost barcode:
curl "https://api.lastscanned.com/v1/track/620192837461528391029901" \
  -H "Authorization: Bearer lsk_live_YOUR_API_KEY"

TypeScript (Automatic Handoff Chaining)

const headers = { Authorization: `Bearer ${process.env.LASTSCANNED_API_KEY}` };
const originRes = await fetch(`https://api.lastscanned.com/v1/track/${encodeURIComponent(number)}`, { headers });
const originPkg = await originRes.json();

// Extract secondary barcode from top-level message ("Delivered to local carrier InPost - 620192837461528391029901")
const handoff = originPkg.message?.match(/^Handed to (.+?) as ([A-Z0-9-]+)$/i);
if (handoff) {
  const [, , lastMileNumber] = handoff;
  const destRes = await fetch(`https://api.lastscanned.com/v1/track/${encodeURIComponent(lastMileNumber)}`, { headers });
  const destPkg = await destRes.json();
}

Remote MCP (Claude Code / Cursor / ChatGPT)

claude mcp add --transport http lastscanned https://mcp.lastscanned.com \
  --header "Authorization: Bearer lsk_live_YOUR_API_KEY"