Fit
Does it fit how we operate?
Cargovate starts from your operating model. A freight forwarder, a shipper, a manufacturer, a
fleet operator and a warehouse operator each begin with the capabilities that model needs, and
anything else is licensed only when you need it.
Solutions by operating model →
Your references
Do we have to learn new shipment numbers?
No. Your own identifiers are kept as they are. A shipment you call JOB-4417 stays JOB-4417
throughout, so your people search the way they already think.
What is held, and how →
Getting data in
How does our existing data get in?
Upload an export from a spreadsheet or your current system. Cargovate proposes a column mapping
and shows exactly what would be created or changed before anything is written. After that your
nightly export can arrive on its own, and re-sending the same rows updates them instead of
duplicating them, so both systems can run side by side.
Migration →
Tracking
Where do the positions come from?
From the telematics your vehicles already report to (Motive today), from air waybill and flight
tracking, and from your own scanners and devices, which only need to make an HTTPS request. Each
position carries the age of its fix, so an old reading is never shown as a current one.
What it connects to →
People
Who on the team can use it?
Everyone who touches the freight. Nothing is charged per user, so the warehouse crew, the drivers
and your customers' receiving desks can all have accounts without changing the price.
Pricing →
Time
How long before it is running for real?
A first session with your own export takes about an hour. Running one trade lane or one site
for real takes days to set up and a few weeks to be confident in. The slow part is rarely the
software: it is two departments agreeing what "delivered" means.
What adoption looks like →