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 this solves

Pricing is where billing mistakes start. A producer might quote a customer per ton on the haul, per load on the material, plus a fuel surcharge that recalculates weekly — all of which need to land cleanly on the invoice without a billing lead double-checking each line. Tread separates pricing into three layers — the price index, the schedule, and the application — so you change one piece without breaking the others. This workflow walks through setting up customer rates, vendor pay rates, add-ons, and fuel surcharge.

​
Walkthrough

1

Open Rates

Go to Settings → Rates. The page splits into Customer Rates (what you charge), Vendor Rates (what you pay), and Driver Rates (what your own drivers earn). Each rate has its own UoM, schedule, and effective dates.
2

Build a rate sheet

Click New Rate Sheet. Pick the customer (or vendor/driver), then add line items: material, origin, destination, UoM (per ton, per load, per hour), and the price. Save as a template if you’ll reuse it.
3

Configure add-ons

Add-ons are line items that apply on top of base rate — standby time, tarping fees, demurrage, equipment surcharges. Set the trigger (per load, per hour, conditional) and the amount. Add-ons attach to specific rate sheets or to all of them.
4

Set up fuel surcharge

Go to Settings → Fuel Surcharge. Pick the index (e.g., DOE national diesel average), the schedule (weekly, biweekly), and the application rule (per mile, percentage of haul, fixed escalator). Tread re-rates open loads on the schedule.
5

Assign rates to a Project or Order

When you create a Project or Order, Tread auto-assigns the customer’s default rate sheet. Override at the Project or Order level if a specific job uses a different rate.
6

Preview before you bill

From any approved load, click Preview Invoice Line. Tread shows exactly which rate, add-ons, and fuel surcharge will apply. Catch the misconfigurations before they hit the customer’s PDF.

​
Rate Precedence

When a load is rated, Tread checks for a matching rate in a fixed order. The first match wins. Everything below it is ignored — even if it has a more recent effective date.
OrderRate sourceScopeWins when
1Site rate scheduleSpecific origin/destination pair on a SiteA rate row exists for the load’s exact site pair
2Project rateOverride set on the ProjectThe Project has a rate sheet attached and no Site rate matches
3Customer rate cardDefault for the CustomerNo Site or Project rate matches
4Default rateFallback per UoMNone of the above match — used to keep the load from going un-rated
When a rate “disappears” or “reappears” between billing runs, it is almost always precedence plus an unset field falling through. A blank UoM, a missing destination, or a Site row that does not match the load’s actual route causes Tread to skip to the next layer. Check the load’s Site, Project, and Customer in that order — find the first level where a field is blank or wrong, fix it there.

​
Watch it

​
Common pitfalls

Rate effective dates matter — past loads use past rates. Editing a rate sheet without setting an effective date will re-rate historical loads and break already-sent invoices. Always create a new rate row with a forward-dated effective date when prices change.
Drivers must never see customer rates. A driver-facing screen built off the wrong rate field can leak customer-facing pricing. Tread separates customer, vendor, and driver rates by design — confirm Roles & Permissions gate driver views to driver-rate fields only.
Fuel surcharge complexity bites first-time admins. A producer setting up surcharge as both a per-load fee and a percentage rolled it twice and overcharged. Pick one application rule per customer and stay there.