Who delivers 4PX parcels in Poland?

4PX hands off Polish e-commerce deliveries to InPost (Paczkomat® and InPost Kurier) and Poczta Polska (Pocztex).

How do I find my 24-digit InPost number from a `4PX...` tracking code?

Query `GET /v1/track/{number}` with your `4PX...` code and `lastscanned` returns the linked 24-digit InPost tracking number.

4PX (4px)→InPost (inpost)

4PX Worldwide Express to InPost Paczkomat & Courier Handoff

How 4PX cross-border shipments from China clear European customs and hand off to InPost in Poland, the UK, and Italy.

Try a live tracking number:

Barcode transition: 4PX to InPost

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

4PX lookup →InPost lookup →Format & check-digit detector →

Origin / middle-mile carrier: 4PX (4px)
4PX Tracking Number (4PX… / LP…): 4PX300…
Origin example: 4PX3000918273645CN
Final-mile carrier: InPost (inpost)
InPost 24-Digit Barcode (620…): 620… (24 digits)
Final-mile example: 620192837461528391029902
Extracted in .message: Arrived at destination hub - Handed over to InPost

How the 4PX → InPost handoff works

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

1. 4PX Shenzhen/Dongguan export processing: 4PX processes the parcel at its South China super-hub and attaches the dual 4PX + InPost shipping label.
2. Liège / Słubice customs & linehaul: After clearing EU customs at Liège or Frankfurt/Słubice, 4PX trucks the pallet into InPost's Polish sorting network.
3. InPost final delivery: InPost delivers to the recipient's Paczkomat® locker or home address.
4PX query: GET /v1/track/4PX3000918273645CN?carrier=4px
InPost query: GET /v1/track/620192837461528391029902?carrier=inpost

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

# 2. Query the extracted InPost barcode:
curl "https://api.lastscanned.com/v1/track/620192837461528391029902" \
  -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 ("Arrived at destination hub - Handed over to 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"