One storefront for cars, boats, and aircraft.
This QR Vehicle Shop fork supports Qbox and QBCore dealerships for cars, boats, helicopters, and planes. It uses ox_lib and oxmysql, requires a target provider for normal shop access, and can write the garage, type, stored, and state columns used by the compatible Lunar Garage build.
Back up the player_vehicles table and existing dealership configuration.
Place qr-vehicleshop in your resources without renaming it.
For an existing Qbox/Lunar database, review and import qbox_lunar_vehicle_columns.sql rather than replacing the table.
Configure the framework, target, shops, garage identifiers, fuel, keys, payment account, and test-drive behavior before starting the resource.
ensure oxmysql
ensure ox_lib
ensure qbx_core # or qb-core
ensure ox_target # or qb-target
ensure ox_fuel # default; configure another provider if needed
ensure qbx_vehiclekeys # optional; or qb-vehiclekeys
ensure lunar_garage # recommended, not a hard dependency
ensure qr-vehicleshopSet Config.Framework to auto, qbox, or qb and Config.Target to auto, ox_target, or qb-target. For predictable startup, explicitly select the resources installed on the server.
Config.Framework = 'qbox'
Config.Target = 'ox_target'Configure each shop's label, vehicle type, categories, ped, target, blip, test-drive location, purchase spawn, and default garage. Garage identifiers must exactly match the installed garage configuration.
Back up player_vehicles before importing qbox_lunar_vehicle_columns.sql. The insert always requires license, citizenid, vehicle, hash, mods, and plate; only the extra garage, type, state, stored, job, fuel, engine, and body fields are conditionally detected. Do not replace a live framework table with the full base SQL file.
The default fuel setting is ox_fuel. Choose auto, native, LegacyFuel, ps-fuel, or cdn-fuel when appropriate. KeySystem none does not fully suppress key grants when qbx_vehiclekeys or qb-vehiclekeys is running, so use it only after correcting or validating that server helper.
Review the payment account, maximum purchase distance, purchase cooldown, plate format, test-drive duration, cancel-on-exit setting, and player or vehicle invincibility before opening the shops.
The success handler still spawns a purchased vehicle outside even when PurchasedVehicleState and PurchasedVehicleStored are set to 1. Those values do not create a true buy-direct-to-garage flow; keep them consistent with an outside vehicle unless the client spawn path is also customized.
Use the configured target on the auto, boat, and air dealership peds. Browse categories, search, start and end a test drive, then purchase one vehicle from each enabled shop.
Confirm the purchased plate appears once in player_vehicles with the intended type, garage, stored, and state values, then park and retrieve it through the selected garage system.
Test the server's insufficient-funds, excessive-distance, invalid-model, and database-failure paths, then manually keep each configured purchase spawn point clear and test it. The purchase is charged and inserted before the client spawn attempt, so a client spawn failure does not trigger an automatic refund.
Start the selected target before qr-vehicleshop, confirm Config.Target matches it, and verify the shop ped model and target coordinates.
Confirm qbx_core or qb-core was running before the shop, the payment account exists, and the server console shows no validation or player_vehicles insert error. The internal fallback is not a standalone economy adapter.
Verify the shop's garage identifier exists, the vehicle type matches that garage, and the columns expected by the selected garage integration are present and synchronized.
Start the configured fuel and key resources before the shop. KeySystem none may still grant keys through a running supported key resource in the current server helper. Vehicle models without bundled images use a remote FiveM documentation image fallback, which requires client network access.