Locus TMS in Action
From the seven tenets to reality: how an agentic-native TMS implements each capability in production, one decision at a time.
From the rubric to the running system.
The Seven Tenets gave a rubric. The Vendor Landscape placed Locus in the agentic-native quadrant. Both were arguments. This is the demonstration: the specific agents, the specific decisions, and the specific screens behind each tenet. Where a claim is Locus's own measurement rather than an independent benchmark, it is marked as such.
Locus runs as DiSCO, a set of specialist agents that share one operating picture: an Orchestrator that reasons across the network, and the Capacity, Carrier, Customer, Dispatch, Hub, and Settlement agents that act within it, with a Copilot that surfaces what the operator should look at next. Each can run at the autonomy level the operator sets. What follows is each tenet, demonstrated.
Source: Locus-reported figures. Independent verification recommended in any RFI.
The system in one view.
DiSCO covers the freight lifecycle on a single operating picture: procure, plan, execute, settle, analyse. The agents do not hand work to a planner and wait. They ingest real-time signals from the TMS, WMS, carrier APIs, and telematics, decide within the guardrails the operator has set, and act, logging every step. A global enterprise running Locus sees the same picture whether the load is an ocean leg out of a port or a final-mile drop in a dense urban grid.
The seven tenets, demonstrated.
- 01 Tenet 01
Decisions, not insights.
A contract carrier rejects a tendered load on a lane out of a regional DC. A dashboard-era TMS raises an alert and waits for a planner. In Locus, the rejection is the trigger. The Carrier agent re-tenders to vetted spot capacity inside the cost ceiling the operator set, generates the new AWB, and the Customer agent pushes a revised ETA to the channel, before anyone opens the alert. The planner sees a completed decision with its reasoning attached, not a task to start.
The difference is not that Locus has AI. It is that the agents hold the authority to act, and every action is recorded as an inspectable decision rather than a log line.
- 02 Tenet 02
Learning, not configuration.
Carrier performance scores improve over a deployment without anyone rewriting a rule. The Carrier agent scores every carrier and lane on what actually happened, on-time delivery, cost, and damage, and refreshes the scorecard continuously as outcomes arrive. A carrier that starts slipping on a specific lane is deprioritised and its volume re-balanced to stronger performers from observed outcomes, not from an administrator editing a routing guide. The Copilot surfaces these shifts to the operator: here is what changed, here is the evidence, here is the effect.
The signal is the operation's own execution history. The boundaries stay the operator's. The system gets better between runs; the planner does the same job with a sharper instrument.
- 03 Tenet 03
Events, not batches.
Hub throughput drops below the line during a morning sort. A batch-era system would surface the shortfall in the next reporting cycle, by which point the downstream routes are already late. The Hub agent reads the throughput event as it happens, triggers an additional sort wave, adjusts dock assignments, and coordinates with the Dispatch agent to re-sequence the affected routes. The decision is made against the state of the network now, not against the picture the overnight batch had.
For an operation running tight delivery windows, the gap between "the system found out at 09:00" and "the system found out at the geofence crossing" is the difference between a recovered slot and a missed one.
- 04 Tenet 04
Composable, not monolithic.
Locus does not require a rip-and-replace. Each agent can run on its own or alongside an existing TMS and ERP. A team can start with the Carrier agent against their incumbent system, prove the value on one lane group, and extend to Dispatch and Settlement later, without a platform migration in between. The agents connect through documented interfaces and deploy over the systems already in place, with region- and customer-specific logic configured rather than coded.
The point is the customer's optionality. The starting footprint can be one agent on one workflow; the path to more is additive, not another replatform.
- 05 Tenet 05
Governance, not goodwill.
An agent that can re-tender freight and approve an invoice holds real financial authority. Locus does not ask the operator to trust that on faith. Every agent runs at an autonomy level the operator sets per process: human approves each decision, auto-act within guardrails, or confidence-based, dialled independently for procurement, planning, execution, and settlement. The Settlement agent runs a four-way match across contract, shipment record, proof of delivery, and invoice, auto-approves the clean ones, and flags the anomalies, with the full reasoning chain available for any decision a CFO or auditor asks about.
Locus reports 100% audit coverage on settled invoices in deployments running the Settlement agent. The governance is a property of the system, not a promise in the contract.
- 06 Tenet 06
Ground-truth, not happy-path.
Real logistics data is messy: addresses without street numbers, carrier APIs that lag, documentation gaps, capacity that evaporates. Locus is built for that as the default condition, not the exception. The ingest layer pulls live state from the TMS, WMS, carrier APIs, and telematics; the geocoding engine resolves incomplete or landmark-based addresses into usable coordinates before a route is ever planned. When a contract carrier's capacity falls through, the Capacity agent books vetted spot capacity rather than letting the plan proceed on a number that is no longer true.
For an enterprise operating in markets where address quality and partner maturity vary widely, treating exceptions as normal is what keeps the plan matched to reality instead of drifting away from it.
- 07 Tenet 07
Network-aware, not lane-by-lane.
The Orchestrator is the agent that reasons across the whole network rather than one leg at a time. It weighs a transport decision against cost, route, load, and SLA together, and across modes: ocean, road, rail, air, and final mile on one picture. A cheaper individual leg that would strand a downstream delivery is not chosen, because the Orchestrator can see the downstream delivery. For an operation moving goods across multiple legs and borders, this is the difference between a plan that looks efficient per lane and one that is efficient end to end.
This is also where the architecture is doing the most work, and where Locus continues to extend coverage, which the next section is honest about.
An honest read.
No agentic TMS is finished, and this one is not either.
The seven tenets describe a destination. Locus clears most of them as live, production properties today, and is still extending coverage on the rest. Network-wide orchestration across every mode and border is the area under the most active development; the depth of autonomous decisioning is real on some workflows and maturing on others. The honest way to read any agentic-native vendor, including this one, is by trajectory: what shipped in the last year, against which capabilities, with evidence.
That is also why this article shows decision logs and screens rather than adjectives. The claim is not that the architecture is complete. The claim is that it is genuinely agentic where it runs, and that the gaps are named rather than papered over. Test it against the RFI questions from the previous piece, and against a proof-of-concept on your own network.
Product capabilities. Agent behaviours (Orchestrator, Capacity, Carrier, Customer, Dispatch, Hub, Settlement, Copilot), autonomy-level controls, the four-way-match settlement engine, the ingest layer, and the geocoding engine are described from Locus product documentation.
Locus-reported metrics. Scale figures (360+ clients across 30+ countries, 1.5 billion+ deliveries optimised, $320M+ logistics costs saved) and outcome figures (8 to 12% freight cost reduction, 40% planning-time reduction, 10 to 15% SLA-adherence improvement, 100% audit coverage, 15% emission reduction via optimised routing) are Locus-reported internal data, not independently audited benchmarks. Treat them as vendor claims to be verified in an RFI and proof-of-concept.
Customer references. Scenes reference anonymised, real Locus enterprise customers spanning multiple industries. No customer is named without permission.
If a capability here does not match what you see in a live evaluation, that gap is the most useful thing you can tell us. Write to us.
