TOVRConcepts

Matching layer

TOVR is a matching layer on top of the freight exchanges a carrier already uses — it pairs loads ingested from those platforms against the carrier's live vehicle capacity, producing scored candidate matches that feed chain building.

TOVR does not replace the freight exchanges, TMS, or marketplaces a carrier already uses — it inserts a matching layer on top of them. It reads the loads posted across those platforms and the carrier's own live capacity, and finds which trucks can serve which loads. Those matches are the raw material the platform builds freight chains from.

Insert on top, don't replace

A carrier's freight already arrives through Transporeon, TimoCom, Trans.eu, and others, and its trucks already report positions through telematics. TOVR sits above both: it ingests that demand and capacity and adds the decision layer — matching, pricing, compliance — without asking the carrier to move off the tools it runs on. The exchanges remain the source of loads; TOVR is what turns them into profitable, legal action.

The two sides being matched

  • Demand — shipments ingested from connected freight exchanges, continuously synced in.
  • Supply — the carrier's vehicle availability: where and when each truck is free, kept current from telematics.

How candidates are generated

Matching pairs the two sides on two axes:

  • Spatial — proximity between a truck's location and a load's pickup, using the locations' geospatial index so nearby candidates are found efficiently.
  • Temporal — the truck's availability window against the load's pickup/delivery timing.

Each candidate pairing is scored by what it would actually cost to serve — chiefly the deadhead (empty kilometres to reach the load) and the wait time before pickup. The results are written as match records:

  • vehicle_shipment_matches — candidate vehicle↔shipment pairings, each with deadhead_km, wait_time_hours, and a score.
  • shipment_matches — shipment→shipment linkability (how well one shipment chains onto another): origin_shipment_id, match_shipment_id, deadhead_km, wait_time_hours, score, match_type.

Matches are candidates, not decisions

A match says "this truck could serve this load, and here's the empty distance it implies." It is not yet a costed plan. The chain builder takes these candidates, assembles them into ordered routes, and prices them with the cost engine — where deadhead becomes real cost and the profitable, legal chains rise to the top. Matching is the funnel; chains are the decision.

On this page