# How to Import Tickets

***

## Setting up your Import <a href="#setting_up_your_import" id="setting_up_your_import"></a>

{% hint style="warning" %}
You must be logged into an **Admin** account the access the Import Format page
{% endhint %}

{% stepper %}
{% step %}

### Navigate to \[ Settings > Import Format ]

<figure><img src="/files/svyjVPOtow51QHGZa5TK" alt=""><figcaption></figcaption></figure>

{% endstep %}

{% step %}

### Click on \[ + New Format ]

<figure><img src="/files/TKyOpBeMDv7XVo7XB8GM" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Fill the Required Fields

The minimum required fields are the **\[** **Format Name ]** and all fields with a **\[ 0 ]**

<figure><img src="/files/thyjychUoUIzQJHq4vvt" alt=""><figcaption><p>If you are importing Orderless Tickets, fields with a * are also required</p></figcaption></figure>

Match your fields to the corresponding number of the column in your export with the column containing that information on your CSV

{% hint style="info" %}
Numbers will replace the letter of the column in your export:\
**A** = **1**, **B** = **2**, **C** = **3**, **D** = **4**, etc.
{% endhint %}

<figure><img src="/files/420zUm6hhGtD9lAtLJ0v" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/8xXUDs1JOZgS3UmvB6LI" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
"**Header Row**" is checked because the CSV in the above example does have a header row, this can be left unchecked if your columns do not have headers.
{% endhint %}
{% endstep %}

{% step %}

### Click \[ **✓** Update ]

The Import Format should now be created! Follow the **Importing Ticket Data** steps below to see how to use it.
{% endstep %}
{% endstepper %}

***

## Importing Ticket Data

{% stepper %}
{% step %}

### Navigate to \[ Tickets > Ticket Import ]

<figure><img src="/files/4RLhmB4Mniz98rI4YrJn" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Fill the required fields

Select the ticket import **Format**, **Import File** (CSV), **Region**, **Location** and **Yard**

<figure><img src="/files/MSpLGUefJeGvyeVeBOlr" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
*Overwrite Date*: Will overwrite all dates on tickets being imported\
\&#xNAN;*Overwrite Hauler*: Will overwrite all haulers on tickets being imported\
\&#xNAN;*Add New Trucks*: Will add trucks on tickets being imported, if they are not in Fast-Weigh
{% endhint %}

{% endstep %}

{% step %}

### Click \[ Upload ]

<figure><img src="/files/sL43eLMD5u6RUjpk0bkv" alt=""><figcaption></figcaption></figure>

• Go over the import and the CSV to correct any errors if present

{% hint style="info" %}
Errors are shown in the right most column. This error is stating that the order being applied is not valid
{% endhint %}

<figure><img src="/files/mFzKKNUCaam7pajXiTgV" alt=""><figcaption></figcaption></figure>

• Once all errors are cleared, the tickets will have green check marks next to them

<figure><img src="/files/67rBuW5CEbsn6Im3Sj15" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Click the \[ Save ] Button

<figure><img src="/files/l1UATWmjXC8eeHx5OSfU" alt=""><figcaption></figcaption></figure>

The tickets should now be imported and viewable from the **Ticket Query**

<figure><img src="/files/I7tPobPdziMvUmzi4WoB" alt=""><figcaption></figcaption></figure>
{% endstep %}
{% endstepper %}

***

## References

{% content-ref url="/pages/AFskNfymo4DE97mNAijM" %}
[Ticket Import](/fast-weigh-knowledge-base/references/web-portal/tickets/ticket-import.md)
{% endcontent-ref %}


---

# Agent Instructions: 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:

```
GET https://help.tacinsight.com/fast-weigh-knowledge-base/how-to-guides/how-to-import-records/how-to-import-tickets.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.