How dcx works
dcx is a tracking conversion service. It takes a tracking number from any network and republishes that shipment's real delivery events under one dcx number that resolves in public. We don't carry the package — we make the carrier's data legible and reachable under a single, stable number.
- 01
Submit a tracking number
Send dcx a shipment through the API or the dashboard, with the source tracking number attached. dcx mints one dcx number and binds it to that shipment for the life of the delivery.
- 02
dcx reads the source
For a recognized carrier — UPS, USPS, FedEx, Amazon Shipping and others — dcx subscribes to the carrier's own updates and pulls each scan as it happens. For a source dcx can't reach on its own, the client that holds the data pushes events in as it sees them. Either way, the events are the real ones the source reported.
- 03
The timeline is published
Events are normalized into one plain vocabulary and published on the dcx tracking page and the API within minutes. The dcx number resolves in public, so a buyer can open it wherever they paste it.
Two ways a shipment is fed
Managed
The source is a recognized carrier. dcx handles the subscription and the updates arrive on their own. You submit the number once and the timeline fills itself in.
Push
The source is one only the client can see — for example, orders moving through Amazon multi-channel fulfillment. That client posts events to dcx as they happen, and dcx publishes exactly what it receives, attributed to that client.
What we don't do
We don't mark a package delivered because a projected date passed. We don't invent intermediate scans to fill a timeline, and we reject events dated in the future. A dcx number carries the real events of one shipment — nothing borrowed from another package, nothing manufactured. If a source goes quiet, the timeline goes quiet, and the page says so.