> For the complete documentation index, see [llms.txt](https://ambr4-scripts.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ambr4-scripts.gitbook.io/docs/scripts/vehicle-shop/add-vehicles-to-shop.md).

# Add Vehicles to Shop

1. Open **`config_vehicles.lua`** add your categories and vehicles.\
   Example structure:

```lua
return {
    categories = { "super", "motorcycles", "sports", "compacts", "sedans", "suvs", "offroad", "vans", "muscle", "cycles", "sportsclassics", "coupes", "commercial", "boat", "helicopter", "plane" },

    cars = {
        super = {
            { name = "Adder",   spawn_name = "adder",   rentPrice = 329, vehicleType = "car" },
            { name = "Autarch", spawn_name = "autarch", rentPrice = 203, vehicleType = "car" },
        },

        motorcycles = {
            { name = "Akuma",   spawn_name = "akuma",   rentPrice = 75,  vehicleType = "car" },
        },

        boat = {
            { name = "Dinghy",  spawn_name = "dinghy",  rentPrice = 120, vehicleType = "boat" },
        },

        helicopter = {
            { name = "Frogger", spawn_name = "frogger", rentPrice = 450, vehicleType = "plane" },
        },

        plane = {
            { name = "Besra",   spawn_name = "besra",   rentPrice = 520, vehicleType = "plane" },
        },
    }
}

```

Explanation:

* **`categories`** → every category must exist here if you want to use it in `cars`.
* **`cars`** → keys (`super`, `motorcycles`, etc.) must match the `categories`.
* **`name`** → displayed name in the UI.
* **`spawn_name`** → actual vehicle model code (lowercase, no spaces).
* **`rentPrice`** → used for preview/rental cost (can be ignored if not needed).
* **`vehicleType`** → values can be `car`, `boat`, `plane`.

2. Open **`vehicles.js`** and add an entry for each vehicle:

```lua
{
  "name": "Adder",
  "model": "adder",
  "category": "super",
  "price": "100",
  "brandimage": "Truffade.webp"
}

```

Explanation:

* **`name`** → display name.
* **`model`** → must match <kbd>spawn\_name</kbd> (`adder`).
* **`category`** → must match the category from `config_vehicles.lua`.
* **`price`** → base price shown in the management panel.
* **`brandimage`** → manufacturer logo file (e.g., `Truffade.webp`). Make sure this file exists in your `ambr4_vehicleshop/html/images/brand` image folder.
* Vehicles image should be in `ambr4_vehicleshop/html/images` folder, with same name like vehicles.


---

# 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://ambr4-scripts.gitbook.io/docs/scripts/vehicle-shop/add-vehicles-to-shop.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.