How to Install a FiveM Inventory Script (Step-by-Step)

The inventory is one of the first premium systems most server owners install — and one of the most common sources of “it won’t start” errors. This tutorial walks through a clean install that works the first time, whether you run ESX, QBCore or Qbox.

Step 1 — Check the requirements

Every inventory lists dependencies. The near-universal ones today are:

• oxmysql — the database layer.
• ox_lib — shared UI/utility library used by most modern resources.
• Your framework (es_extended, qb-core, or qbx_core).

Install and confirm those start cleanly before adding the inventory. You can verify how common they are on our resource metrics page — oxmysql and ox_lib sit near the very top of the ecosystem.

Step 2 — Add the resource files

1. Drop the inventory folder into your resources/ directory (keep the exact folder name the developer shipped).
2. If it came in a [inventory] bracket folder, keep that structure — brackets group resources and can affect load order.

Step 3 — Import the database

Most inventories ship a .sql file that adds item tables, stashes or metadata columns.

1. Back up your database first. Non-negotiable.
2. Import the provided .sql via HeidiSQL, phpMyAdmin or the CLI.
3. If the script uses an items table, make sure your items are seeded (many premium inventories include a starter item list).

Step 4 — Set the load order in server.cfg

Order is where most installs break. Dependencies must start before the inventory:

# Core first
ensure oxmysql
ensure ox_lib
ensure es_extended      # or qb-core / qbx_core

# Then the inventory
ensure my-inventory

If the inventory replaces your framework’s default inventory, disable the old one (comment out its ensure line) so they don’t fight over the same events.

Step 5 — Configure it

Open the resource’s config.lua (or config/ folder) and set the essentials:

• Framework — some products auto-detect; others need a Config.Framework = 'esx' line.
• Slots / weight — pick a system and stick with it server-wide.
• Keybind to open the inventory.
• Stashes, shops, trunks — enable the features you actually use; disable the rest to save performance.

Step 6 — Test before you announce

Boot the server and watch the txAdmin console on first load. Then in-game, verify the core loop:

• Open/close the inventory.
• Pick up and drop an item.
• Move items between hotbar and bag.
• Open a stash / trunk / shop.
• Reconnect and confirm items persist (database is saving).

Which inventory should you install?

If you want a free, dependable base, ox_inventory is the community benchmark. If inventory is central to your server’s identity — crafting, progression, deep storage and a polished UI — a premium system is worth it. In our testing the standout all-rounder is Quasar Inventory, which supports ESX, QB, QBCore and Qbox from a single product and is engineered to keep its per-frame cost low even in a full city. You can see it on the Quasar Store inventory page, and we compare it against the field in our best FiveM inventory scripts guide.

Common install errors (and fixes)

Once your inventory is stable, pair it with a clean HUD — see our HUD customization guide — and make sure the whole thing stays fast with our optimization guide.