Verticals · Logistics & distribution
Shipments, carriers, contracts — the network as a system of record.
Shipments move through staged workflows with real locations, carrier contracts run as deals with terms and renewals, and every dispatcher and depot contact is one person in the graph.
Why one system
The TMS sees shipments, the contract folder sees rates, dispatch sees today — and nobody sees the lane whole.
One system where the shipment, the carrier, and the contract share one record of the network.
The objects you’d define
shipments
workflow · locations · activity
Staged from booked to delivered, geocoded at both ends, with the exceptions on a timeline.
carrier contracts
deal · attachments · workflow
RFQ to signature: rates offered, rates agreed, contract start and end — a deal with a renewal built in.
carriers
contacts · website · phone
The companies and dispatchers behind every lane, one directory across contracts and shipments.
lanes
locations · hierarchy · activity
Origin to destination as a first-class record, with the shipments that ran it nested beneath.
- RFQ
- Rates
- Terms
- Signed
A carrier contracts pipeline — shipper ↔ carrier — same deal primitive, your labels.
How it runs.
A carrier contract is a deal: rates proposed, rates agreed, terms with a start and an end. When the contract signs, the lane knows its carrier; when it nears its end, the renewal is a pipeline record, not a surprise.
Shipments run as staged workflows — booked, picked up, in transit, delivered — with rules that hold: a shipment doesn’t close without a proof-of-delivery attached.
Every exception lands on the shipment’s timeline, so the story of a late delivery is already written when the customer calls.
By the time the customer calls about a late delivery, Nomi has already put the exception on the shipment’s timeline, chased the contract stuck in Terms, and answered ‘which lanes lose money this month?’ from the graph.
Nothing here is an industry edition — it’s the same primitives, named by the people who run the business.