Who delivers Yanwen packages in Poland?

Yanwen partners with InPost (InPost Kurier & Paczkomat®) and Poczta Polska (Pocztex) for final-mile delivery in Poland.

How do I find the Polish InPost tracking number for a Yanwen `VR...YP` parcel?

Enter your Yanwen tracking code into `GET /v1/track/{number}` to extract the linked 24-digit `620...` InPost barcode.

Yanwen Logistics Poland Linehaul to InPost Paczkomat & Poczta Polska Handoff

How Yanwen (YW… / UJ… / VR…YP) cross-border shipments from China convert into 24-digit InPost Poland or Pocztex tracking numbers.

Try a live tracking number:

Barcode transition: Yanwen to InPost

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

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

Origin / middle-mile carrier: Yanwen (yanwen)
Yanwen Waybill (VR…YP / UJ… / YW…): VR…YP / UJ…CN
Origin example: VR519283746YP
Final-mile carrier: InPost (inpost)
InPost 24-Digit Barcode (620…): 620… (24 digits)
Final-mile example: 620192837461528391029903
Extracted in .message: Last mile tracking number assigned: 620192837461528391029903 (InPost)

How the Yanwen → InPost handoff works

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

1. Yanwen origin sorting & exchange number generation: Yanwen scans the parcel in Shenzhen, Yiwu, or Dongguan and assigns a 24-digit `620...` InPost Poland exchange number (`exchangeNumber`).
2. European air arrival & customs release: The air shipment lands in Liège, Budapest, or Warsaw, clears EU IOSS customs, and trucks to InPost's central sorting hub.
3. InPost Kurier or Paczkomat® delivery: InPost delivers the parcel to the Polish buyer within 24 hours of hub induction.
Yanwen query: GET /v1/track/VR519283746YP?carrier=yanwen
InPost query: GET /v1/track/620192837461528391029903?carrier=inpost

Chain Yanwen → 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 Yanwen origin waybill (extracts final-mile barcode in .message):
curl "https://api.lastscanned.com/v1/track/VR519283746YP" \
  -H "Authorization: Bearer lsk_live_YOUR_API_KEY"

# 2. Query the extracted InPost barcode:
curl "https://api.lastscanned.com/v1/track/620192837461528391029903" \
  -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 ("Last mile tracking number assigned: 620192837461528391029903 (InPost)")
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"