> For the complete documentation index, see [llms.txt](https://tg-dev.gitbook.io/tg-dev-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://tg-dev.gitbook.io/tg-dev-docs/tg-vehicleshop/troubleshooting.md).

# Troubleshooting

#### The shop does not open

Check:

* The resource is started
* Dependencies are started first
* The shop coordinates are correct
* Your job matches the shop job requirement
* Target or TextUI mode is configured correctly

#### No vehicles show in the shop

Check:

* The vehicle has the correct `shop` name
* The vehicle category exists in `Config.Categories`
* The vehicle model exists in GTA or your add-on pack
* The stock system is not hiding unavailable vehicles

#### Stock does not update

Check:

* `Config.General.StockSystem` is enabled
* `oxmysql` is running
* The stock table exists
* The vehicle model exists in `Config.Vehicles`
* You restarted after major config changes

#### Keys are not given after purchase

Check:

* `config/bridge.lua`
* `TGBridge.Settings.VehicleKeys`
* The key resource is started
* The selected key system matches your server

#### Fuel is wrong after purchase

Check:

* `config/bridge.lua`
* `TGBridge.Settings.Fuel`
* The fuel resource is started
* The selected fuel system matches your server

#### Custom plate says unavailable

Check:

* The plate already exists in the database
* The plate is too long
* The plate contains unsupported characters
* Custom plate is enabled in config

#### Admin menu does not open

Check:

* `Config.AdminMenu.Enabled`
* The admin command name
* ACE permissions
* Framework group permissions

### Recommended Setup Flow

1. Configure `config/bridge.lua` first.
2. Configure `Config.General`.
3. Add or edit shops in `Config.Shops`.
4. Add categories in `Config.Categories`.
5. Add vehicles in `Config.Vehicles`.
6. Test a normal purchase.
7. Test custom plate.
8. Test trade-in.
9. Test test drive.
10. Test vehicle keys and fuel.
11. Test admin stock changes.
12. Enable logs if needed.

### Notes

* Keep vehicle model names lowercase when possible.
* Use real GTA or valid add-on spawn names.
* If a vehicle has no preview image, the UI uses the fallback image.
* If a vehicle brand cannot be detected, the UI uses the custom brand fallback.
* Restart the resource after changing config files.