What does a freight operating system actually do?
It connects the systems, inboxes and documents a freight operation already uses, and builds a single live reference for every movement. That reference becomes the source of truth that workflows automate against: quoting, scheduling and planning, documents, compliance and more.
The goal is not another system of record. It is to automate the work that currently happens by hand between your systems, so operators stop re-keying and start working from one consistent picture.
How is it different from a TMS or ERP?
A TMS or ERP is a system of record: it stores and manages structured data once that data exists. A freight operating system focuses on the messy work before and around those records: unstructured email, varied documents and disconnected tools, and turns it into structured action.
- A TMS/ERP records the shipment; the freight OS automates the work around it.
- It works with your existing systems instead of replacing them.
- It is built around one shipment, one live reference, not a database table.
- No rip and replace just connect, harmonise, and automate across your ecosystem.
Who is a freight operating system for?
It is for the operators who run movements day to day and lose hours to manual work between systems: freight forwarders, hauliers and heavy haulage operators, and the planning, quoting, documents and compliance teams around them.
- Freight forwarders quoting, emailing and producing documents around a TMS such as CargoWise.
- Hauliers planning jobs, tracking assets and trailers and lifting utilisation.
- Heavy haulage operators keeping routes, permits, asset builds and schedules aligned.
- Ops, planning and compliance teams who still re-key data between disconnected tools.
What workflows does a freight operating system cover?
It automates the operational work that happens around your systems of record, with every workflow acting on the same live reference per shipment.
- Quoting: turn inbound requests and rates into a draft quote in minutes.
- 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.
What systems does it connect to?
A freight operating system sits around your existing stack rather than replacing it. It connects to the systems of record, inboxes, rate sources and permit portals an operation already runs, and ties what it finds to one live reference.
- Your TMS or ERP, such as CargoWise, as the system of record.
- Email, including Outlook, for inbound requests and outbound replies.
- Rate and carrier sources through carrier APIs for live pricing.
- Tracking feeds such as Terminal49 for container milestones.
- Permit systems such as ESDAL for heavy haulage routing and permits.
- Legacy databases, so existing data is connected rather than ripped out.
Why does "one live reference" matter?
When every email, document, rate and asset assignment is tied to the same live reference, there is no drift between systems. A change in one place updates the picture everywhere, which is what makes reliable automation possible.
This is the core of the operating system for freight operations: a single, current view that both people and automations can trust.