Know the supplier cost before you sell the seat.
Per-run and per-kilometre rates by subcontractor and vehicle type, route-specific where the route matters, versioned so a mid-season price change never rewrites last month's numbers.
A rate table that survives a real supplier relationship
A subcontractor rate carries a calculation basis — per run, or per kilometre on a monthly basis — along with a vehicle type, a currency and a validity window. The basis is enforced: a per-run rate cannot also carry a kilometre figure, so no row is ambiguous about how it prices.
Rates can be global to the supplier or specific to a route, and the route-specific rate takes priority. When the system falls back to the supplier's base rate it says so on the resolved cost, rather than silently pricing a run off the wrong number. Rates are versioned with their own valid-from date, so a run costed in June still reads June's rate in September.
Per run or per kilometre
One basis per rate, enforced at the API. A per-run rate holds a run price; a per-km rate holds a monthly kilometre rate. Neither can carry the other's figure.
Route-specific overrides
Set a rate for a specific origin and destination and it beats the supplier's base rate. The resolved cost reports which of the two was actually used.
Gross to net, with the VAT split
Suppliers quote gross. The cost breakdown reverse-calculates net cost and deductible input VAT at the agency's rate, so margin is computed on what the run actually costs you.
Straight into run margin
Resolved supplier cost meets booked revenue on the per-run margin surface, both normalised to the agency base currency when the two sides are quoted in different ones.
The rest of the operation
See it on your own operation.
No open signup — a short manual review, then a demo populated for your region.