Terra — Freight and logistics

Before the next load misses.

Terra keeps one live model of every shipment, carrier and lane across the systems you already run: your TMS, your ELD, your customers’ EDI. It sees a load running late before it misses, traces every appointment and customer it will hit, and names the move that matters now.

For brokers, 3PLs, warehouses, carriers and fleet operators. Your TMS does its job. Terra works across what it produces.

In the Command center

Watch it work.

Synthetic data
  1. 01 SeeMemphis is running over capacity, and the map shows it in its place in the network.
  2. 02 RelieveTerra ranks the sites with room to spare, by distance and spare capacity a day.
  3. 03 PlanThe move is planned with its volume, duration and handling guidance.
  4. 04 SearchOne question returns the late shipments behind it, record by record.

Two questions

What tells you today?

When a load starts running late, does anything tell you which appointments and customers it will hit before the miss?

Terra does. It sees the delay forming, from the carrier slipping on the lane to the dock filling up, and traces every load, appointment and customer it reaches while there is still time to re-plan.

If a carrier you rely on dropped out for a week, could you see today what that would cost you?

Terra does. It runs that week across the whole operation before it happens: the lanes left uncovered, the loads at risk, the detention and chargebacks that follow, and where to move the freight first.

The gap

Tracking tells you where a load is. Not what it is about to run into.

The dock filling up by Thursday. The carrier that has been slipping on this lane for six weeks. The four other loads for the same customer riding the same connection. Each fact sits in a different system, so the first sign is usually a missed appointment, a detention bill or a chargeback.

Joined up

The same load, with everything around it.

One shipment in the PrincipiaA synthetic shipment drawn as a graph: the carrier, lane, order, hub, trailer and customer it is connected to, each with its own state, and the finding the graph produces.carried byruns onfulfilsroutes throughhauled indelivers toShipmentLoad 4471Chicago → Atlanta · due Thu 06:00CarrierC-17On time, but 20 min later each weekLaneCHI – ATL212 loads in ninety daysOrderPO-8821311 loads to one customer this fortnightHubAtlanta cross-dock91% of capacity on ThursdaysTrailerUnit 5310Dry van · position every 15 minCustomerGrocery DC98% OTIF · 3% deduction per missFinding6 of the next 11 loads to this customer will miss, from three causes no single system shows.
  • ShipmentLoad 4471Chicago → Atlanta · due Thu 06:00
  • CarrierC-17On time, but 20 min later each week
  • LaneCHI – ATL212 loads in ninety days
  • OrderPO-8821311 loads to one customer this fortnight
  • HubAtlanta cross-dock91% of capacity on Thursdays
  • TrailerUnit 5310Dry van · position every 15 min
  • CustomerGrocery DC98% OTIF · 3% deduction per miss
  • Finding6 of the next 11 loads to this customer will missFrom three causes no single system shows.

One shipment, as the Principia holds it. A synthetic example: the figures are realistic, not real.

What Terra flags

In your words, before it costs you.

  • Carriers slipping.

    Still inside the window, but later every week on this lane. Terra sees the trend before on-time falls and tenders start coming back.

  • Docks filling up.

    Inbound volume against dock capacity, so Thursday's congestion shows on Monday, before the detention and the missed appointments.

  • Customers at risk.

    One late linehaul, and every order and appointment it reaches, ranked by what each customer will charge back.

  • Records that disagree.

    When your TMS, your WMS and a customer's EDI disagree, Terra reconciles them and shows the source of each, so a shortage arrives as data, not as a deduction.

A worked example

One carrier. One lane. Six weeks.

An illustrative operation, not a customer account. The figures are realistic, not real.

What Terra read
Ninety days of loads exported from a mid-size broker's TMS: 3,640 loads, 41 carriers and 212 lanes, with promised and actual pickup and delivery times, and carrier status messages over EDI.
The signal
Carrier C-17 on Chicago to Atlanta is still inside its delivery window, but arriving about twenty minutes later every week for six weeks. On-time has not moved yet. On this trend it breaks the window in about two weeks.
What it reaches
C-17 carries 38% of the lane. Eleven loads in the next fortnight deliver to one grocery customer with a 98% OTIF programme and a 3% invoice deduction for every miss. Two of them cross a dock that already runs at 91% of capacity on Thursdays.
What is at stake
Six projected late deliveries: about $10,800 in OTIF deductions and $2,400 in detention and redelivery, $13,200 in all, and a scorecard the customer reviews every quarter.
The move
Move the four highest-exposure loads to carrier C-04, which has run the lane 97% on time, for $45 more a load in carrier rate. Keep C-17 on the rest and raise the trend at its next review. Projected late deliveries fall from six to one, for $180 in extra freight cost. The recommendation arrives with the loads, the six-week trend and the customer's terms attached.
What follows
The decision is kept with its evidence. When the loads deliver, the outcome is checked against the prediction, and C-17's record on the lane carries into the next decision.

$13,200 at stake. Four loads moved, for $180 more in carrier rates.

Works with what you run

Nothing to replace.

Your TMS runs the loads. Your ELD tracks the trucks. Your WMS runs the dock. Terra works across what they produce, and across your partners’ EDI, to see what they mean together. Exports, spreadsheets and EDI work as readily as APIs.

Reads from

  • TMS
  • WMS
  • ELD and telematics
  • EDI
  • Spreadsheets and exports
  • APIs
Freight networks that see around corners →

How to start

See it on your lanes.

Show us where the operation breaks down. We build Terra around the systems you already run, show you what it sees on your own loads, and you compare it with what you run today.

You bring
The problem, and the loads around it: carrier, lane, customer, promised and actual pickup and delivery. A TMS export or a spreadsheet is fine, with EDI status messages if you have them.
We bring
Terra, built around your data, your systems and how you actually operate, and a walkthrough of what it sees on your own carriers, lanes and customers.
Cost
There's no cost while we work with you, for the foreseeable future. You see what the software does on your own operation before it costs you anything.
Then
Terms are agreed only once you have seen what the software does on your operation. They are sized to what you run, not to us, and nothing becomes a contract until you agree to it.

Your data

  • Used only for your operation. It is never shared with, or used for, anyone else.
  • No third-party models. Your data is never sent to an outside model provider.
  • An NDA first, before you send anything, if you want one.
  • Where it is processed is named before any data moves, and access is limited to the people working on your operation.
  • Deleted on request.

Questions

What operators ask first.

Do I have to replace my TMS?

No. Your TMS does its job. Terra works across what it and your other systems produce, and nothing you depend on is touched.

What do you need from me?

The problem, someone who knows how the operation runs, and the loads around it. A TMS export or a spreadsheet of recent loads is enough to start. Imperfect data is fine.

Is this built for an operation my size?

Yes. We build around the operation in front of us, at whatever size it is, and it costs nothing while we work together.

What does it cost?

Nothing while we work with you, for the foreseeable future. You see what the software does on your own operation first. When it has shown its value there, we agree terms with you, sized to what you run, and nothing becomes a contract until you agree to it.

Why is there no cost?

Because the software is best judged on your own operation, not on our word. It isn't a trial or a pilot: you see what it does on your own data first, and when it has shown its value there, we agree terms with you.

What does it cost once the software has shown its value?

Terms are agreed only after you have seen what the software does on your own operation. They are sized to what you run: how much of the operation the software covers, the volume and the number of sites, not the size of Theralon. You start with the product that fits the problem in front of you and add the rest when it has earned it. Nothing becomes a paid contract until you agree to it. The same software runs owner-led operations and large ones alike.

Who sees my data?

Only the people working on your operation. It is never shared with or used for anyone else, never sent to a third-party model, covered by an NDA if you want one, and deleted on request.

Before the next load misses

See it on your lanes.

Show us where the operation breaks down. We build around the systems you already run. Then compare it with what you run today.

Get in touch →