You keep CXT. StatVault is built to ride alongside it, not to rip it out. Your order numbers and the people who know CXT inside out stay where they are.
How the two fit together
CXT stays your system of record for orders and accounts. The biggest thing StatVault adds is what no dispatch system has: hardware in the field. The SmartBox connected pickup box reports lid events, contents, photos and temperature from the clinic itself, and temperature tags ride in vehicles and bags, so cold chain is measured at the box and in transit instead of assumed. Around that, StatVault adds NFC tap proof at every box, a hash-chained chain of custody record, a modern driver app, customer portals and a dispatch board with a live map.
A zero-credit feed in
StatVault reads CXT through its scheduled export feed: orders, route stops, drivers, contract stops, driver pay and order items. That feed costs no API credits. Changes made in CXT show up in StatVault within about half a minute. There is no screen-scraping and no polling that runs up a bill.
Every driver action pushed back
When a driver acts in the StatVault app, the action goes back to CXT: confirm, pickup, deliver, proof of delivery, cancel a delivery, unconfirm, piece edits, NFC scans at origin and destination, route stop completions and scans, driver assignment, dispatch edits and route assignment. Each update is labelled as coming from StatVault and the driver who did it, so anyone reading CXT can tell where a change came from. Echo protection keeps an update from bouncing back and forth between the two systems.
The same order numbers
An order keeps its CXT number everywhere: on the dispatch board, on the driver's phone, in the client's portal and on the custody record. Nobody learns a second numbering scheme.
Verified numbers stay in step
StatVault prices, verifies and pays from its own billing engine. Price, pay and reference corrections made there are mirrored to CXT automatically, so whatever CXT still produces for you reflects what was verified.
Grows with the way you work
StatVault already creates orders in CXT from its own order entry and client portals, and runs dispatch, drivers, custody and portals on top of the CXT feed. New capabilities land as additions to that setup, surface by surface, at the pace your team chooses. CXT stays the system your billing and your people know; StatVault is the layer that sees, proves and remembers.
What switching on looks like
Turning on the feed is a configuration step on the CXT side and ours. Drivers install the app on their own phones. Dispatchers keep working the same orders with the same numbers. Your clients can stay on CXT ordering or move to a StatVault portal, account by account.
Related
Further reading: orders and routes, explained.
Questions couriers ask
- Do I have to stop using CXT?
- No. StatVault runs alongside CXT. Your team can keep working in CXT while dispatch, drivers and clients gain what StatVault adds.
- Does it cost CXT API credits?
- Reading the feed does not. StatVault takes CXT's scheduled export feed, which costs no credits, instead of polling the API.
- Do driver actions reach CXT?
- Yes. Confirms, pickups, deliveries, proof of delivery, NFC scans, route stop completions and assignments are pushed back to CXT, labelled as coming from StatVault.
- Will my order numbers change?
- No. Orders keep their CXT numbers in StatVault, on the driver's phone and in the client portal.
- Can I leave CXT later?
- That door stays open. Today StatVault already creates orders in CXT and runs dispatch, drivers, custody and portals on top of it. Whether you ever go further is your call.