> For the complete documentation index, see [llms.txt](https://help.tacinsight.com/fast-weigh-knowledge-base/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.tacinsight.com/fast-weigh-knowledge-base/references/web-portal/trucks/haulers.md). # Haulers ***Typically a Hauler is going to be a carrier, trucking company, or customer that owns that trucks in which you will be ticketing. You can also think of Haulers as a folder that one or multiple trucks belong to.*** Here you are able to create haulers, as well as edit, delete, and assign existing haulers.

Haulers screen

You can create a new hauler by clicking the **+ New Hauler** button in the top right of the hauler table. The following window will pop up:

New Hauler window

{% hint style="info" %} *Enable Dispatching* requires the Dispatching module add-on to be used. If you are interested in adding the Dispatching module please contact us at 865-219-2980 or . {% endhint %} The only required fields are the **Hauler ID** and **Name**. Below are brief descriptions of each of the fields: * **Hauler ID** - A shorthand ID for the Hauler * **Name** - Full name of the Hauler * **Address** - Fields for the Hauling Company's address. * **Contact Information** - Fields for the Hauling company's main contact * **Vendor AP Num** - Field to store Hauler's Vender AP number if one is to be used * **Hauler Type** - Field to differentiate Haulers as *External, Internal,* or *Other* * *External* - Outside company is hauling material * *Internal* - Your company is hauling the material * *Other* - * **Insurance #** - Field for Hauler's insurance policy number * **(Insurance) Expiration** - Set date for Hauler's insurance expiration * This applies to any truck within the Hauler * **Workers Comp #** - * **(Workers Comp) Expiration** - Set date for Workers Comp expiration * **Certification #** - * **(Certification) Expiration** - Set date for Certification expiration * **Enable Dispatching** - Allow trucks within the Hauler to be used for the ***Dispatching*** feature * **All Regions** - If checked, Hauler can be ticketed on in any region. If unchecked you are able to pick specific regions you would like the Hauler to be able to be ticketed on. * **Active** - If checked, Hauler is available to be ticketed on. If unchecked, Hauler will be unavailable and not populate in ticketing app. * **Allow Overloaded Trucks** - Future use in newest ticketing app * **Use Tare on Inbound** - Future use in newest ticketing app * **Days Tare Valid** - Future use in newest ticketing app Once you have filled out the relevant fields you can click **Update** to add the Hauler. *** ## Assigning Haulers to Customers
Haulers can be assigned to specific customers by clicking on the **\[✔️Assign]** button under the *Customer* column of the Haulers menu.\ \ In the new pop-up window, you can use the filters to search for customers, then click the checkbox on the left to assign them. This will prevent the Hauler from being able to have tickets created on orders for customers that are not selected from this menu.
{% hint style="info" %} You **do not** have to assign a Hauler to a Customer to create tickets. If the Hauler does not have any Customers marked on the assignment list, they are available to be selected for ALL customers. Adding an assignment for a specific customer will restrict their availability to that specific customers orders only. {% endhint %} --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://help.tacinsight.com/fast-weigh-knowledge-base/references/web-portal/trucks/haulers.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.