# Inventory Systems

Start with [upstream qb-inventory](https://github.com/qbcore-framework/qb-inventory) for a QBCore server. Before replacing it, identify the exact repository and commit, check every calling resource, and test saved inventories on a staging copy. An inventory's appearance does not establish API compatibility or safe persistence.

## Available Inventory Systems

###

### QBCore Inventory

    Upstream API reference, configuration and server-side inventory operations.

### LJ Inventory

    Archived community inventory: inspect legacy APIs and storage before migration.

### QB Inventory V2

    Identify the exact project behind this ambiguous label before installing a fork.

## Features Comparison

Compare the implementation you actually plan to install rather than an unversioned feature checklist:

| Resource | Source baseline | Compatibility decision |
| --- | --- | --- |
| Upstream qb-inventory | [Commit dc3d07fc](https://github.com/qbcore-framework/qb-inventory/tree/dc3d07fc60139de569df38c5ac178ed4cada4577) | Check exports and the `inventories` schema against existing callers/storage. |
| LJ Inventory | [Commit 86ec0d84](https://github.com/loljoshie/lj-inventory/tree/86ec0d8425cdc980c4dc4541841deb381f24e1e5); README marks it archived | Uses legacy storage tables and an inventory-open event; not a drop-in replacement for the current server export. |
| “QB Inventory V2” | No single upstream project established by this documentation | Require a repository, commit, API documentation and schema before evaluating it. |

These are source-review baselines, not in-game compatibility certifications. Mobile layout, performance and controller support require evidence for the specific implementation; they cannot be inferred from a name or screenshot.

## Installation Guide

### Prerequisites

- Record the core, inventory and dependent resource commits and local changes.
- Back up the database, item definitions, images and resource files.
- Restore a staging copy before testing an inventory replacement.

### General Installation Steps

1. Review the target README, `fxmanifest.lua`, exports and SQL at the recorded commit.
2. Check prerequisites and [resource load order](/docs/troubleshooting/resource-load-order). Inventory consumers must start after their provider.
3. Disable the competing inventory on staging. Keep the resource name expected by its consumers, or explicitly migrate those consumers.
4. Review storage changes before importing SQL; `CREATE TABLE IF NOT EXISTS` does not migrate existing columns or move inventory contents.
5. Test player, shop, stash, trunk and glovebox operations, including reconnect, inventory-full rejection and unauthorized access. See the [inventory acceptance matrix](/docs/troubleshooting/inventory-updates#manual-acceptance-matrix).

### Configuration

Keep shared item names, weights, slot limits and image filenames consistent with the target implementation. The [config validator](/tools/config-validator) can identify supported static configuration problems; it cannot prove inventory runtime compatibility. Use the [resource compatibility checklist](/docs/migration/tools/compatibility-checker) for manifests, callers, schemas and runtime checks.

## Choosing the Right Inventory

### For Beginners: QBCore Inventory

Use the upstream resource and its [API reference](/docs/resources/qb-inventory) as a reproducible starting point. Keep related resources at explicitly recorded compatible revisions rather than mixing downloads described only as “latest”.

### For Advanced Servers: LJ Inventory

An existing LJ installation requires a legacy API and storage audit. The project README states that support is no longer offered. Read the [LJ migration notes](/resources/inventory/lj-inventory) before updating core or inventory consumers.

### For Custom Setups: QB Inventory V2

Treat “V2” as a label until the supplier identifies the source. Follow the [fork evaluation checklist](/resources/inventory/qb-inventory-v2#migration-checklist); do not assume an optional compatibility wrapper or a particular UI framework exists.

## Common Issues & Solutions

### Inventory Not Opening

Capture the first server/F8 error. Check resource state, expected client/server export and execution side. A missing `OpenInventory` export can indicate an old inventory paired with a new caller; restarting or renaming it does not add that export.

### Items Not Showing

Check `QBCore.Shared.Items` keys first, then image paths and failed NUI requests. Missing images and missing saved item definitions are different failures. See [missing shared items and UI diagnostics](/docs/troubleshooting/inventory-updates#missing-shared-items-and-the-ui-are-different-problems).

### Weight Issues

Compare the configured capacity and shared item weights with the actual `AddItem`/`RemoveItem` results. Test the full-inventory rejection path before blaming the UI.

## Support & Resources

- [Inventory update troubleshooting](/docs/troubleshooting/inventory-updates): APIs, shared items, persistence and rollback.
- [Official inventory documentation](https://docs.qbcore.org/qbcore-documentation/qbcore-resources/qb-inventory) and [upstream issues](https://github.com/qbcore-framework/qb-inventory/issues).
- [Independent community documentation](/docs): this site is not the official QBCore project.
