Vehicle Shops

Most QBCore servers piece together dealership functionality from two or three separate resources — one for test drives, another for financing, a third cobbled-in for player-owned shops. This script replaces the stack with a single resource that handles both public dealerships and player-owned operations, built specifically for QBCore with oxmysql and ox_lib as the foundation.

Public Dealerships: What Your Players Expect

Standard public showrooms cover test drives, license verification, and financing. Financing is not a UI stub — it connects to your existing banking (renewed-banking, okokBanking, and qb-banking are all tested; fd_banking, tgg-banking, and wasabi_banking run experimentally). Payment accepts cash, bank transfers, or configurable item-based payment for servers running barter economies. License checks gate purchases behind whatever conditions you configure — driving license, clean record, or custom logic.

Player-Owned Dealerships: Full Business Loop

The player-owned side is where the depth is. Ownership management, employee rosters with individual commission rates, stock ordering through configurable delivery missions, and sell-back pricing for vehicles the business buys back from players. A well-run player dealership becomes a server institution — it gives players a reason to stay invested in an economy role beyond flat NPC transactions.

• Public showrooms with test drives, financing, and license verification

• Player-owned dealership ownership and management

• Stock ordering via delivery missions

• Employee commission structures and roster management

• Vehicle sell-back from players to dealership

• Cash, bank, and item-based payment methods (configurable)

• Targeting: ox_target and qb-target both supported

• Vehicle keys: qb-vehiclekeys and cd_garage tested; jacksam, qs-vehiclekeys, okokgarage experimental

• Inventories: ox_inventory and qb-inventory tested; qs-inventory experimental

• Dependencies: oxmysql, ox_lib, qb-core

Honest Comparison with Premium Alternatives

JG Dealerships v2 costs £48 and ships an in-game dealership creator — you can build and configure dealerships live without a server restart. This script does not do that. Dealership locations are configured in the resource files, which means a restart when you add or move a showroom. That is the practical trade-off at £15 versus £48.

What you get at this price point is a production-ready system that covers every mechanic a QBCore server actually runs day-to-day: functional public showrooms, player-owned business operations, tested banking and inventory compatibility, and two targeting systems. If your server layout is set and you are not redesigning your map quarterly, the configuration overhead is a one-time cost and the feature set covers the gap.

QBCore-Only — By Design

This resource is QBCore-exclusive. There is no ESX port and no standalone mode. If you are running ESX, this is not the right script. If you are on QBCore and want dealership infrastructure without paying premium pricing for features you will not use, this covers the functional requirements.

Installation

1. Place the resource folder in resources alongside your other dealership resources.
2. Confirm qb-core, oxmysql and ox_lib are running, and add this resource's ensure line after them in server.cfg.
3. Choose ox_target or qb-target for the interaction points and set that in the config.
4. Point the financing side at the banking resource you already run, then restart the server.
5. Test one public sale and one player-owned sale before opening the dealerships up.

Requirements and Dependencies

Built for QBCore on qb-core, with oxmysql and ox_lib as the foundation. Interaction runs through ox_target or qb-target, item-based payment through ox_inventory or qs-inventory, and renewed-banking is among the tested financing integrations.