Checkout & Delivery

Set up factory options, test drives, and delivery, and see how the server checks each purchase.

Resource
drs_vehicleshop
Version
v1.0.1-drs.8
Updated
Aug 30, 2026
View drs_vehicleshop resource View files on GitHub
Guide navigationCheckout & Delivery
Sections
01 / FACTORY CHECKOUT & DELIVERY

Factory checkout & delivery

Configure factory checkout

Checkout entries use stable option ids. The server resolves their GTA indexes, prices, availability, plate restrictions, and delivery support when creating a quote. Prefixes accept one to three uppercase letters or numbers and apply only to road vehicles.

config.lualua
Config.PaymentAccount = 'cash'
Config.DeliverPurchasedVehicles = true
Config.Checkout.quoteLifetime = 30000
Config.Checkout.platePrefix.enabled = true

Align delivery and garage identifiers

Default car, boat, and air garage ids must exist in the selected garage configuration. Drive-away is removed when delivery is disabled or a shop lacks a spawn point; garage delivery remains the safe fallback. Keep the acknowledgement and handoff timeouts long enough for the configured fade and streaming transition.

02 / TEST DRIVES

Test drives

Tune server-managed test drives

Review test-drive duration, geofence, handoff timeout, return fallback, and cleanup settings. The server creates, tracks, expires, and removes test vehicles; clients cannot grant keys or turn a test entity into an owned purchase.

03 / HOW PURCHASES ARE CHECKED AND SAVED

How purchases are checked and saved

The server controls and checks every purchase step. If another system gives an uncertain result, the order can be recovered or held for review.

How prices and options are checked

The player's game requests a quote with the chosen option IDs, shop ID, model, and plate prefix. The server looks up the price, access rules, plate options, garage, spawn point, and delivery rules. It rejects a quote if any of those details changed before purchase.

How a personal purchase is saved

The plate reservation and order are saved together. The order log then records payment, player_vehicles ownership, vehicle creation, garage registration, saved state, keys, and the player's one-time delivery confirmation.

What happens when delivery fails

If the spawn is blocked, saving or keys fail, the player disconnects, the resource stops, or confirmation times out, the purchased vehicle is stored in the garage. An uncertain payment or refund is held for review instead of risking a duplicate credit.

04 / TEST PURCHASES & FIX DELIVERY

Test purchases & fix delivery

Validate every dealership path

Open each enabled road, marine, and aviation shop. Test category access, search, one successful and one rejected quote, test-drive expiry, drive-away delivery, garage delivery, keys, ownership, storage, and retrieval.

A purchase is stored instead of delivered

Verify the selected garage is started and compatible, its identifier exists, the delivery spawn is clear, and persistence and key providers are healthy. Stored state is the intended safe result when delivery cannot be proven.