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

The Connected Ecosystem is how four roles chain together on every job: the Customer who buys the work, the Primary Co (the Tread account running the job), the Vendor who supplies trucks, and the Driver who hauls the load. Each link is a real record in Tread, not a label.

​
Why it matters

Each link controls a different slice of the workflow. The Customer link drives invoicing. The Vendor link drives payables and truck sharing. The Driver link drives dispatch and pay. Break any link and the data downstream breaks with it.

​
How Tread models it

  • Customer — who you bill. Created in your Primary Co. If the Customer also runs Tread, they appear as a Connected Customer (a link between two Tread accounts).
  • Primary Co — your Tread account. The hub. Owns projects, orders, dispatch, and the books.
  • Vendor — a trucking partner. Their drivers and trucks come into your dispatch board through a Company Share (a one-way link letting a Vendor see jobs you assign them).
  • Driver — the person hauling the load. Either an internal driver in your Primary Co or a vendor driver shared in.
  • Owner-Operator (O&O) — a one-truck vendor. Set up as a Vendor so they can be dispatched directly.

​
Common pitfalls

Drivers added as vendors. When master data is built at the wrong company level, internal drivers can land as vendor records by mistake. Result: dispatchers cannot assign them, the mobile app rejects their login, and pay reports come up empty. Fix before go-live by reviewing the driver list in Settings.
If a partner drives only their own truck, set them up as a Vendor with O&O type. That keeps direct dispatch working without creating a fake company hierarchy.