Home / Documentation
Documentation
Written for the people who have to say yes: an operations lead deciding whether it fits how they work, and an IT function deciding whether it fits their estate. No sales call required to read any of it.
What Cargovate stores, where it physically lives, how one organisation's records are kept separate from another's, and how you get everything back out again. Answered first, because it is the question that decides whether the rest is worth reading.
Moving from spreadsheets, or from a system you intend to keep. What a first import looks like, how a nightly export becomes a running sync, and how the two systems are kept honest with each other while you run both.
What Cargovate connects to — handheld scanners, telematics, your ERP — and, just as usefully, what it deliberately does not do to systems you already depend on.
Managed cloud, inside your own estate, or fully air-gapped. What each option asks of your team, and what changes about the product in each.
How access is controlled, what the audit trail records and who can alter it, and how Cargovate behaves when a person or a device should no longer have access.
A realistic sequence from first import to daily use, what we need from you at each step, and the things that genuinely take time rather than the ones that sound like they should.
This documentation is for evaluating Cargovate. Day-to-day instructions — creating a shipment, scanning a checkpoint, issuing a device key — live inside the product, where they sit next to the screens they describe.
This documentation is for evaluating Cargovate — what it holds, how your data gets in, what it connects to and where it runs. If you are already using it and want to know how to do something, the day-to-day user guides live with the application at cargovate.io/docs.
