Core
Shipments, legs and checkpoints. A journey is modelled as a sequence of movements, not a single location field.
Supply chain & asset lifecycle
Cargovate gives freight forwarders, shippers and operators a single operational record of where goods are, who holds them, and what happened on the way — across carriers, systems and borders that were never designed to agree with each other.

The problem
Carrier portals, spreadsheets, scanned paperwork, a WhatsApp thread with the driver. When a consignment is disputed weeks later, reconstructing what actually happened costs days of somebody's time — and the answer is still contestable.
Platform
Nothing is bundled to inflate a contract. Five capabilities are on from the first day; the rest are switched on when a need is demonstrated, not assumed. What each one includes, and what it connects to →
Shipments, legs and checkpoints. A journey is modelled as a sequence of movements, not a single location field.
Who held the goods, when responsibility transferred, and on whose authority. The chain survives a client leaving.
Documentation and evidence held against each movement, retrievable long after the shipment closed.
Ingest from the systems you already run. Repeated imports are idempotent, so a re-run never duplicates history.
Positions from your own devices or the telematics you already run, each carrying the age of its fix.
Locations, pallets, lots and reservations — stock at rest, and what is already promised.
Cost baselines and measured operational savings against them.
Asset and fleet lifecycle — service intervals, due dates and history per vehicle or unit.
Parts, routings, units and genealogy — who built each serial, from what material, and the evidence that it was done right.
Act on behalf of client organisations without merging their data or exposing one to another.
Commit a tamper-evident fingerprint of the custody record to an independent ledger, when a record needs to be provable to someone who does not trust you.
Solutions
A forwarder that never owns the freight has different problems from a manufacturer that does. Each operating model starts with the capabilities that model needs.
You move other people's goods and answer to their clients as well as your own.
You own the freight and need one account of where it is and who has it.
You make goods and ship them, with finished stock sitting between the two.
You run vehicles rather than consignments, and downtime is the cost that matters.
You hold other people's goods and must be able to prove the condition you held them in.
Capabilities are licensed individually, so an operating model that isn't listed is a configuration question rather than a bespoke build.
Deployment
Some clients cannot put freight data in a shared cloud — for contractual, jurisdictional or security reasons. That is a deployment decision, not a reason to lose the deal.
We run it. Fastest to start, no infrastructure on your side.
Runs inside your own estate under licence, with your own database and backups.
Installed with no outbound network path at all, for environments where egress is prohibited outright.
Design partner
Built with a working freight forwarder, not in a vacuum.
Cargovate was designed against the operating reality of a third-party logistics provider — an organisation that moves goods it does not own, for clients who each expect a complete and private record of their own consignments.
That constraint shaped the platform: a client's operational history belongs to the client from the first row written, and leaves with them intact if they go elsewhere.
A short session with your shipment data, not a slide deck.