What is ox_inventory in FiveM?

An inventory resource owns items: what a player carries, what a vehicle's trunk holds, what a stash contains, and what a shop sells. Because so many other scripts give, take, or check items, the inventory becomes a dependency for half the server, and choosing one is a stack decision rather than a feature choice. ox_inventory earned its position by handling items on the server, supporting rich per-item metadata (a specific serial number, a durability, an owner name), and exposing exports that other resources build against.

It replaces rather than extends. Installing ox_inventory means disabling the framework's own inventory (qb-inventory on QBCore, the ESX default inventory) and letting ox_inventory own the items table and the item definitions. Scripts that call the old inventory's exports directly will need their inventory calls bridged or changed, which is exactly the kind of coupling worth checking before buying a script: ask which inventories it supports by name.

ox_inventory's maintenance lineage is the same as ox_lib's — Overextended originally, then a successor organisation — and its current stewardship is worth verifying on GitHub before adopting it for a new project. Its dependence on ox_lib and oxmysql also means it inherits their update cadence. Because it sits under so much else, treat an inventory update the way you would a framework update: read the changelog, test on staging, back up the items and stashes tables first.