> For the complete documentation index, see [llms.txt](https://docs.av-scripts.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.av-scripts.com/guides/dealerships/admin-panel/import-vehicles.md).

# Import Vehicles

{% hint style="success" %}
To start importing vehicles place yourself in an open zone because the script will start spawning vehicles in order to retrieve their specs.
{% endhint %}

## Addon Vehicles

> If you're importing addon vehicles, make sure FiveM knows how they're named. To do this, go to `client/editable/vehnames.lua` and add each vehicle's spawn name and label to the `myAddonVehicles` table.

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

{% hint style="danger" %}
If you skip this step, all your addon vehicles names will be saved as **"NULL"**.
{% endhint %}

## Import Panel

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

* **Model Name:** Use this field to specify the exact vehicle model to import when adding new vehicles to your server.
* **Import All Vehicles:** Imports all vehicles from your server. This process may take a few minutes, depending on your PC's performance.

{% hint style="warning" %}
If you want to import your vehicles from your Framework set **Config.UseFrameworkVehicles = true** in `config/_config.lua` / This option **only works with QBCore and Qbox**.
{% endhint %}

<figure><img src="/files/NhA3fswdIvxzeYcVn6Lw" alt=""><figcaption><p>Process starting..</p></figcaption></figure>

<figure><img src="/files/VA7MC3vMnK7pchbu4TOC" alt=""><figcaption><p>Process ended.</p></figcaption></figure>

## Missing Assets

```lua
"[ERROR] "..vehmodel.." asset couldn't be loaded, is either corrupted or it doesn't exist in qb/shared/vehicles.lua"
```

> **This print can mean the following:**
>
> * You have some addon vehicles folder where one of the **vehicles.meta** file have registered vehicles that does **NOT exist in your server**, meaning the **.yft files are missing**.
> * If importing a single vehicle, you entered one that does not exist in your server files.
>
> **Solution:**
>
> * You can either ignore the warning and continue, or edit your `vehicles.meta` file to find and remove the missing vehicle entry.

## Custom Imports

{% hint style="info" %}
This import functions can be found in **client/editable/\_framework.lua**
{% endhint %}

> The following functions allow you to import vehicle lists from any external script or database table:

#### getFrameworkVehicles()

> This function retrieves all vehicles from your Framework. To import from a custom script or database, you must generate and return a table where each vehicle adheres to the following structure:
>
> * **model:**`hash` The vehicle model hash
> * **name:**`string` Vehicle model name
> * **class?:**`string` Vehicle class
> * **brand?:**`string` Vehicle brand name
> * **category?:**`string` Vehicle category (suv, sports, super....)
> * **price?:**`number` Vehicle base price

#### getVehicleInfo()

> This function retrieves data for a single vehicle from the Framework. For custom integrations, you must return a single table (not an array) matching the structure below:
>
> * **model:**`hash` The vehicle model hash
> * **name:**`string` Vehicle model name
> * **class?:**`string` Vehicle class
> * **brand?:**`string` Vehicle brand name
> * **category?:**`string` Vehicle category (suv, sports, super....)
> * **price?:**`number` Vehicle base price


---

# 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://docs.av-scripts.com/guides/dealerships/admin-panel/import-vehicles.md?ask=<question>&goal=<endgoal>
```

`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.