What is a freight operating system in plain English?
A freight operating system is the automation layer that connects the data, email, documents, rates, assets, permits, compliance and exceptions around the systems an operation already runs. It is not a TMS replacement; it is the layer that builds one live reference per shipment and automates the manual work in between.
Its architecture is best understood as three layers working together: the live reference at the centre, the connectors that feed it, and the workflows that run on it.
Who is freight operating system architecture for?
It matters to anyone evaluating how a freight automation layer fits their existing stack, not just developers.
- Ops and IT leaders mapping how a freight OS sits around a TMS such as CargoWise.
- Freight forwarders, hauliers and heavy haulage operators planning what to automate first.
- Teams that need automation to act on accurate, live data rather than stale copies.
Layer one: the live reference (digital twin)
At the centre is one live reference per shipment, a digital twin that mirrors the real state of the movement: lanes and equipment, rates, assets and trailer configuration, permits, documents and the email thread.
Because every input is tied to the same reference, there is no drift between systems, and both people and automations can act on it with confidence.
Layer two: the connectors to your systems
Connectors link the live reference to the systems an operation already uses, reading from and writing back to them so the reference reflects reality.
- Systems of record: your TMS or ERP, such as CargoWise, stay the source of structured shipment data.
- Email: inboxes such as Outlook feed inbound requests and carry outbound replies.
- Rates and capacity: carrier APIs pull live pricing into quoting.
- Tracking: feeds such as Terminal49 add container milestones to the reference.
- Permits: systems such as ESDAL keep heavy haulage routing and permits aligned.
- Legacy data: legacy databases are connected, not ripped out.
Layer three: the automation workflows
On top of the live reference sit the workflows that automate operational work. Each reads and updates the same reference, so the workflows stay consistent with each other.
- Quoting: assemble a draft quote from inbound requests and live rates.
- Email-to-ops: turn inbound and outbound email into structured actions.
- Documents: extract, generate and reconcile paperwork against the reference.
- Scheduling and planning: plan jobs and assets against real capacity.
- Compliance: keep checks and documents aligned as a movement changes.
- Exceptions: surface clashes, gaps and changes early, in the workflow.
How does it sit around systems of record?
A TMS or ERP records shipments once they exist as structured data. The freight operating system focuses on the messy work before and around those records, then writes structured results back. The system of record stays in place; the freight OS automates the work around it.
This is why there is no rip and replace: the architecture is additive, connecting and harmonising your ecosystem rather than competing with it.