Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.tread.ai/llms.txt

Use this file to discover all available pages before exploring further.

What it is

A Rate is the price for a unit of work — per hour, per ton, per load, per mile. An Add-On is an extra line on the invoice or pay statement (toll, demurrage, layover, truck commission). A Fuel Surcharge is a Rate that adjusts to fuel prices on a schedule.

Why it matters

Rates flow into every invoice and every pay statement. A misapplied rate is a billing dispute. A missing add-on is unbilled revenue. A broken fuel surcharge is the same mistake repeated across hundreds of loads.

How Tread models it

Rates apply by Customer, by Material, by Site, by Equipment Type, or globally. Tread looks up the most specific match. Fuel surcharge has three components. This is the part first-time admins get wrong.
  1. Price index — the fuel price source you key off (DOE national average, regional, custom).
  2. Schedule — the table mapping fuel price bands to a surcharge percentage or per-mile rate.
  3. Application — where the surcharge applies (which Customers, which lanes, on top of what base rate).
ComponentLives onExample
RateCustomer / Material / Lane$4.25 per ton, Pit A → Site B
Add-OnCustomer or Vendor$50 demurrage after 30 min
Fuel surcharge — indexPlatformDOE West Coast
Fuel surcharge — scheduleCustomer3.503.50–3.75 = 4%
Fuel surcharge — applicationCustomerApply on freight only

Common pitfalls

Fuel surcharge complexity bites first-time admins. Skipping any one of the three components — index, schedule, application — quietly removes the surcharge from invoices. Test on a sample Settlement before go-live and reconcile against your existing fuel matrix.
Add-Ons go missing at go-live. Auto-adding customer fuel rates, material rates, and settlement add-ons all need explicit setup. If line items are missing from your first invoice cycle, audit Add-On config first.