Cargovate Request a demo

Home  /  Solutions

Solutions

Configured to how you actually operate.

A forwarder that never owns the freight has fundamentally different problems from a manufacturer that does. Each operating model below starts with the capabilities that model needs — and none of the ones it doesn't.

Operating modelAgency

Freight forwarder / 3PL

This is you if you move goods you do not own, and answer to your clients' customers as well as your own.

The hard problem is not tracking — it is separation. You need a view across every client you act for, while each of those clients sees only their own consignments and cannot infer anything about the others. Most platforms solve one half and quietly break the other.

Cargovate treats the principal as the owner of its own operational record from the first row written. Your cross-client reporting stays yours. A departing client leaves with a complete history and takes none of anyone else's.

Starts with
Core, Custody, Compliance, Import, Agency
Often adds
Anchoring, for consignments that end up contested
Operating model

Shipper

This is you if you own the freight and need one account of where it is and who is holding it.

Your goods cross several carriers, each with its own portal, format and definition of "delivered". The cost is not the tracking — it is the reconciliation afterwards, and the fact that a disputed consignment takes days to reconstruct from six sources.

Starts with
Core, Custody, Compliance, Import
Often adds
Finance, to put a number on what the reconciliation costs
Operating modelManufacturing

Manufacturer

This is you if you make goods and ship them, and you are asked to prove how they were built as well as where they went.

The gap is usually between the production record and the shipping record — two systems describing the same physical object that do not reconcile. Cargovate covers both, and the serial number is what joins them: a unit's build history, the material consumed into it and the evidence behind each operation stay attached when it becomes freight.

Production is a gate rather than a status field. A unit is not released while an operation is incomplete, evidence is missing, a nonconformance is open, or a contract flow-down is unresolved — and an operation will not complete on an uncertified operator or an out-of-calibration tool.

Starts with
Core, Compliance, Import, Warehouse, Manufacturing
Includes
A customer portal — your clients submit and track their own orders, and see nothing else
Often adds
Anchoring, where provenance is a contractual requirement
Operating modelMaintenance

Fleet operator

This is you if you run vehicles rather than consignments, and downtime is the cost that actually matters.

The unit of work is the asset, not the shipment. Service intervals, due dates and history per vehicle, held so that a maintenance record is a defensible document rather than a folder of receipts.

Starts with
Core, Maintenance
Operating modelWarehouse

Warehouse operator

This is you if you hold other people's goods and must be able to prove the condition you held them in.

Custody and storage are the same question asked twice: who was responsible, and for how long. Disputes here are almost always about the boundary — the moment responsibility passed to or from you.

Starts with
Core, Custody, Warehouse
Often adds
Anchoring, where the handover boundary is disputed
Not listed

Something else

Capabilities are licensed individually, so an operating model that isn't listed here is a configuration question rather than a bespoke build. If your operation doesn't map cleanly onto any of the five above, that is worth a conversation rather than a compromise.

See it against your own operation.

A working session with your shipment data, not a slide deck.