Track OSM Worldwide parcels before and after USPS handoff—even when USPS says 'Currently Awaiting Package'.

OSM Worldwide moves millions of domestic e-commerce parcels across its regional sort network (Glendale Heights IL, York PA, Atlanta GA, Las Vegas NV, Dallas TX) using a single 22-digit 92… (or 30-digit 420+ZIP+92…) USPS IMpb barcode. While OSM transports the package middle-mile for 3–7 days, USPS shows 'Pre-Shipment: Picked Up by Shipping Partner, USPS Awaiting Item'. Pass ?carrier=osm to lastscanned on that same 92… number to see every middle-mile hub scan.

Barcode transition: OSM Worldwide to USPS

Domestic OSM Worldwide parcels keep the same 92… / 420… barcode from pickup to mailbox. Pass ?carrier=osm to inspect middle-mile sort scans before USPS induction.

Origin / middle-mile carrier
OSM Worldwide (osm)
Shared USPS IMpb / OSM ID
92… (22 digits), 420+ZIP+92… (30 digits), or OSM + 14 chars
Origin example
92612903029511573030094531
Final-mile carrier
USPS (usps)
USPS Domestic IMpb
Same 92… / 420+ZIP+92… barcode inducted at local DDU post office
Final-mile example
92612903029511573030094531
Middle-mile resolution
Arrived at OSM Facility — Glendale Heights, IL (via ?carrier=osm)

How the OSM Worldwide → USPS handoff works

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

1. Merchant prints a single 92… USPS IMpb label
Unlike international shipments that switch tracking numbers at customs, domestic OSM Worldwide parcels use a single 22–26 digit 92… (or 30-digit 420+ZIP+92…) barcode from warehouse pickup all the way to the recipient's mailbox.
2. Middle-mile transit through OSM sort hubs (Days 1–5)
OSM Worldwide picks up the parcel and moves it through regional hubs (Glendale Heights IL, York PA, Atlanta GA, Las Vegas NV). During this entire window, querying USPS returns 'Pre-Shipment: Picked Up by Shipping Partner, USPS Awaiting Item'.
3. Query ?carrier=osm for middle-mile scans, then USPS for final delivery
Because 92… numbers auto-detect as USPS in Pass 1, calling GET /v1/track/:number?carrier=osm queries OSM Worldwide directly and returns every intermediate hub arrival, departure, and estimatedDelivery date before USPS acceptance.
Default auto-detection behavior
GET /v1/track/926129... routes to usps in Pass 1 (/^(420\d{5})?9[2345]\d{18,24}$/).
Middle-mile override parameter
GET /v1/track/926129...?carrier=osm routes the exact same barcode to OSM Worldwide and returns regional hub events.
Native OSM formats auto-detected
OSM[0-9A-Z]{14} (Pass 1) and A\d{10}[A-Z]{3}\d{8} (Pass 2) route to osm automatically without ?carrier=osm.

Chain OSM Worldwide → USPS 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 OSM Worldwide middle-mile scans on the 92… barcode:
curl "https://api.lastscanned.com/v1/track/92612903029511573030094531?carrier=osm" \
  -H "Authorization: Bearer lsk_live_YOUR_API_KEY"

# 2. Query USPS final-mile scans on the same barcode:
curl "https://api.lastscanned.com/v1/track/92612903029511573030094531" \
  -H "Authorization: Bearer lsk_live_YOUR_API_KEY"

TypeScript (Automatic Handoff Chaining)

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

// If USPS is still waiting on the consolidator parcel, query OSM Worldwide middle-mile hubs:
if (pkg.carrier === "usps" && pkg.status === "label_created" && /^(420\d{5})?9[2345]/.test(number)) {
  const mid = await fetch(`https://api.lastscanned.com/v1/track/${encodeURIComponent(number)}?carrier=osm`, { headers });
  if (mid.ok) pkg = await mid.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"

OSM Worldwide to USPS Handoff Tracking FAQ

Why does my USPS tracking number say 'Picked Up by Shipping Partner, USPS Awaiting Item' (OSM Worldwide)?
OSM Worldwide is a postal consolidator that picks up packages from merchants, sorts them across its own regional hubs, and drops them directly at your local destination post office (DDU). USPS does not scan the package until OSM hands it over at your local post office 3–7 days after shipment.
Does an OSM Worldwide package get a new USPS tracking number upon handoff?
Usually no—the 22-digit 92… (or 30-digit 420+ZIP+92…) number on the label is already a valid USPS IMpb tracking number. You can query that exact same number with ?carrier=osm on lastscanned to see OSM's internal hub scans while USPS still says 'Currently Awaiting Package'.
How do I automate OSM-to-USPS fallback in my WISMO agent or backend?
Call GET /v1/track/:number first. If carrier === 'usps', status === 'label_created', and the tracking number starts with 92 or 420, fire a second synchronous call to GET /v1/track/:number?carrier=osm to surface the live middle-mile sort scans.

All 31 supported carriers