Any tracking number, one that resolves everywhere.
dcx converts a carrier tracking number — UPS, USPS, FedEx, or Amazon Shipping — into a single dcx number with a public timeline. Same real events, one format, one page your buyer can actually open.
Numbers begin with DCX followed by 13 digits.
One number, whoever carries it.
Feed dcx a number from any network. It reads the real delivery events from the source and republishes them under one dcx number — the same status, the same timestamps, on a page and an API that anyone can reach.
Carrier tracking number
- Shipped
- At carrier facility
- Out for delivery
- Delivered
Real events only
dcx republishes what the source network actually reported. It never invents a scan, and never marks a package delivered on a projected date. If the source is quiet, the timeline is quiet.
Resolves in public
A dcx number has its own page and its own JSON endpoint, and is registered with the aggregators that marketplaces and tracking apps read from. The number works wherever a buyer pastes it.
One API for every source
Recognized carriers convert automatically. Sources dcx can't reach on its own — including Amazon multi-channel fulfillment — are fed by the client that holds the data. Both land as one dcx number in the same format, so your integration doesn't change.
Made for cross-border shipments.
A parcel from Asia to Europe can pass through an origin carrier, a line-haul consolidator, and a local final-mile carrier — and the tracking number often changes at each handoff, going dead in between. dcx keeps the whole route under one dcx number and shows the status in your buyer's own language.
Built to be read, by people and by machines
The buyer gets a plain-language page with real timestamps and no dead ends. Your systems get one JSON shape for every shipment, whatever carried it. Same source of truth, two audiences.
Running in demo mode with sample data. Try DCX4417829033556 for a shipment in transit, DCX8830174429664 for a delivered one, or DCX2065513378894 for an exception.