Track Winit parcels through customs clearance and Correos final-mile delivery.

Winit consolidates cross-border e-commerce parcels under an origin waybill (ID18049204CN) and injects them into Correos (PQ4F830492819200128001P) via Madrid Barajas customs clearance to Correos CTA. Querying lastscanned with ?carrier=winit returns origin export and linehaul events, while querying the Correos tracking number returns domestic final-mile delivery scans.

Try a live tracking number:

Barcode transition: Winit to Correos

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

Origin / middle-mile carrier
Winit (winit)
Winit Waybill
ID1… alphanumeric waybill
Origin example
ID18049204CN
Final-mile carrier
Correos (correos)
Correos Barcode
PQ4F… domestic barcode
Final-mile example
PQ4F830492819200128001P
Extracted in .message
Handed over to final-mile carrier Correos (PQ4F830492819200128001P) — Madrid Barajas customs clearance to Correos CTA

How the Winit → Correos handoff works

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

1. Origin induction (Winit)
The merchant inducts the parcel into Winit under origin tracking ID ID18049204CN.
2. Linehaul & customs (Madrid Barajas customs clearance to Correos CTA)
The shipment clears customs at Madrid Barajas customs clearance to Correos CTA and receives domestic Correos barcode PQ4F830492819200128001P.
3. Final-mile delivery (Correos)
Correos completes local sorting and doorstep or parcel locker delivery.
Origin Carrier Slug
winit
Destination Carrier Slug
correos
Primary Injection Gateway
Madrid Barajas customs clearance to Correos CTA

Chain Winit → Correos in code or MCP

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

REST (Synchronous GET)

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

# 2. Query the extracted Correos barcode:
curl "https://api.lastscanned.com/v1/track/PQ4F830492819200128001P" \
  -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 ("Handed over to final-mile carrier Correos (PQ4F830492819200128001P) — Madrid Barajas customs clearance to Correos CTA")
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"

Winit to Correos Handoff Tracking FAQ

How do I track a Winit parcel handed off to Correos?
Query GET /v1/track/ID18049204CN?carrier=winit for origin and customs milestones, and GET /v1/track/PQ4F830492819200128001P?carrier=correos for final-mile delivery scans.
When does the Correos tracking number become active?
Correos pre-advises the label at dispatch, and live hub scans begin within 24–48 hours after customs release at Madrid Barajas customs clearance to Correos CTA.

Other carrier handoff guides

Explore cross-border last-mile barcode extraction and domestic USPS consolidator overrides across all 542 carriers.

All 542 supported carriers

Regional and last mile (241)

+231 more regional and last mile

International posts and couriers (176)

+166 more international posts and couriers

Cross-border (116)

+106 more cross-border