qb-inventory
Why it does not matter which of the two you run
The reason our resources do not ship a version per inventory is a design decision: device state is stored in the database against your identifier, not in item metadata. Cube Radio is the clear example (serial, battery, volume, presets and scan list live in their own table), and that is what makes it behave the same on qb-inventory as on ox_inventory.
When the object does have to be an item, like the signed paper in Cube Documents, it is created as a normal item of whatever inventory you run and handed over like any other.
The case that breaks the rule, on purpose
Cube Prison contraband is in no inventory. It hides in body and cell stash spots, it is invisible to an inspection and it only surfaces if somebody searches. That is not a compatibility limitation: it is the mechanic of the resource, and it is why all four search types resolve on the server.
Before you buy
Check the supported frameworks on the page of the product you are interested in. Eleven of our fifteen resources cover ESX, QBCore, Qbox and standalone, and some add vRP.
If you are on a very old qb-inventory build or your own fork, ask us on Discord with the resource name before paying.
Frequently asked questions
Do I need ox_inventory or is qb-inventory enough?
qb-inventory is enough. Device state is stored in the database rather than in item metadata, so behaviour does not change between supported inventories.
Does it work on a qb-inventory fork?
Usually yes, but with forks it is worth confirming before you buy. Message us on Discord with the exact resource name.