> For the complete documentation index, see [llms.txt](https://drfx-store.gitbook.io/drfx-store-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://drfx-store.gitbook.io/drfx-store-docs/documentation/products/qb-pawn-shop-script/installation.md).

# Installation

Install the QBCore Pawn Shop resource correctly.

### 1. Install dependencies

Confirm QBCore, ox\_lib, and qb-inventory are installed and start without errors.

### 2. Download the script

Get the package from Tebex using the CFX account connected to the checkout. Extract the download and keep the original resource folder name.

### 3. Upload the resource

Place the resource folder inside your FiveM server's resources directory.

### 4. Review the included README

Follow any version-specific setup included with the download before starting the script.

### 5. Configure the start order

Start QBCore, ox\_lib, and qb-inventory before the Pawn Shop resource in server.cfg.

### 6. Restart and test

Restart the server completely. Test displaying an item, purchasing an item, retrieving an item, and persistence after a server restart.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://drfx-store.gitbook.io/drfx-store-docs/documentation/products/qb-pawn-shop-script/installation.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
