MT Dealerships | FiveM Player Owned Dealership | QBCore ESX

MT Dealerships is a free FiveM player owned dealership script that transforms vehicle sales into a fully player-driven economy loop for QBCore, qbx_core, and ESX servers. Spin up multiple showrooms across the map, hand them off to player jobs, or run them as state-owned outlets — every dealership behaves independently, with its own stock, catalogue, and sales flow. The clean TypeScript + React + Mantine interface keeps the entire experience modern and snappy, so buying a car finally feels like a real retail moment instead of a clunky NPC menu. Servers running a serious economy and casual roleplay communities alike will find this script slots in as a full ownership and sales backbone.

🎬 Script Showcase

Watch the routing-bucket test drives, catalogue purchase flow, and owner dashboard come together in this full walkthrough of MT Dealerships in action across a live FiveM lot.

🚗 Inside This FiveM Player Owned Dealership Script

Generic dealership scripts force one location, one job, one fixed flow. MT Dealerships flips that model on its head by letting you run as many dealerships as your map can hold, each tied to its own job, its own vehicle catalogue, and its own ownership state. Some can be player-owned franchises pulling in real economy revenue; others can run unowned as state-managed outlets for new players to grab entry-level rides. Pair that with the optional stock system and routing-bucket test drives, and you get a dealership ecosystem that actually feels like a working part of your city — not a placeholder shop. This QBCore car dealership script also runs seamlessly on ESX and qbx_core stacks, so framework choice never dictates the depth of the experience.

✨ Full Feature Breakdown

Every feature below is built to give server owners flexibility while keeping the player-facing experience clean, modern, and intuitive:

• Possibility of creating multiple dealerships with different jobs and vehicles — run luxury, used, and exotic outlets side by side under separate ownership
• Possibility of having owned or not owned dealerships — mix player-run franchises with state-managed shops on the same server
• Test drive system using Routing Bucket (optional) — players take cars for a real spin without disturbing other traffic on the map
• Stock system (optional) — finite inventory creates genuine supply, demand, and economy pressure
• Buy vehicles via catalogue or sell them at dashboard — flexible flows for both walk-in customers and active dealership owners
• List of sells — owners track every completed sale at a glance from the dashboard
• List of importations — owners track every imported vehicle that has been brought into stock
• Buy and test vehicles directly from showroom — interact with the physical car on the lot for a real retail feel
• Admin command to add or remove stock — staff manage inventory live without touching the database
• Clean UI made in TypeScript with React, Vite and Mantine — fast, responsive, and built to feel at home on a modern FiveM server

🔧 Compatibility & Requirements

This FiveM player owned dealership script is built for the most common modern FiveM stacks, so installation slots in cleanly alongside your existing framework. Make sure your server has the dependencies below installed and up to date before importing the resource — once they’re in place, the script is essentially drop-in.

• es_extended, qb-core or qbx_core
• ox_target or qb-target
• ox_lib

❓ Frequently Asked Questions

Q: Which frameworks does MT Dealerships support?

A: The script works with es_extended (ESX), qb-core (QBCore), and qbx_core (Qbox). You’ll also need ox_lib plus either ox_target or qb-target installed as targeting dependencies.

Q: Can I run more than one dealership at the same time?

A: Yes — multi-dealership support is a core feature. You can configure as many dealerships as your server needs, each with its own assigned job and its own vehicle catalogue, and each one can be set as player-owned or unowned independently.

Q: Do test drives interfere with other players on the map?

A: No. The optional test drive system uses Routing Buckets, which isolate the test driver into their own instance while they’re behind the wheel, so the rest of your server’s traffic and roleplay flow stays untouched.

Q: How is stock managed inside a dealership?

A: The optional stock system tracks vehicle inventory per dealership, and an admin command is included so staff can add or remove stock live without touching the database. Owners can also review every sale and every importation directly from the dashboard.

Q: How do players actually buy a car?

A: Players can browse and purchase vehicles through the in-game catalogue, or buy and test them directly from the physical showroom car on the lot. Dealership owners can also sell vehicles manually through the dashboard for negotiated deals.

🏁 Open Your City’s First Player-Run Dealership

MT Dealerships replaces the static NPC car shop with a real, player-run sales floor that drives economy activity at every layer of your server. With multi-dealership support, routing-bucket test drives, an optional stock system, and a polished React UI, it gives owners a real business to operate and buyers a real showroom to walk into. Drop it in once and your server gains a full automotive retail layer that practically runs itself.