> For the complete documentation index, see [llms.txt](https://daddy-studios.gitbook.io/daddy-studios-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://daddy-studios.gitbook.io/daddy-studios-docs/scripts/daddy-marketplace.md).

# Daddy Marketplace

A player-driven item marketplace, auction house and buy-order board for FiveM.

![Daddy Marketplace](https://2487709298-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FqcEXX242M9YYHjASblGi%2Fuploads%2Fgit-blob-e1215478adcd9738a07ed50fb516176695dc2fbb%2Fdaddy-marketplace-thumbnail.jpg?alt=media)

Daddy Marketplace turns player-to-player trading into a real in-game economy. Players list items at a fixed price, bid on auctions, make offers, or post buy orders telling the server what they want and what they will pay for it — all from one NPC, with every transfer validated on the server.

## Features

* **Fixed-price listings** with a shopping cart, partial purchases, per-item payment restrictions and an optional listing fee
* **Offers and counter-offers** with escrow, so offered money is held until the seller answers
* **Auctions** with buyout, configurable bid increments, anti-snipe extension and an optional bid money hold that refunds automatically when a bidder is outbid
* **Buy orders** — post "I want 50 iron at $80 each", sellers fill it from their inventory, partially or in full, and the escrow is settled per fulfilment
* **Featured listings and auctions**: a paid, time-limited highlight at the top of the list
* **Seller ratings and profiles**, price history charts and a watchlist with price-drop alerts
* **Dashboard** with market pulse, sales chart, top items, ending-soon auctions, your open buy orders and a one-click claim for stored items
* **Delivery depot**: anything that cannot be handed over right now (full inventory, player offline) is stored and claimed later — items are never lost
* **Discord logs** for listings, purchases, bids, auction results, offers, buy orders and admin actions, sent through a queue so busy servers do not hit Discord's rate limit
* **Multiple market locations**, each with its own listings, job restrictions, allowed categories and allowed items
* **5 languages**: English, Turkish, German, Spanish, French

## Supported frameworks and inventories

| Type          | Supported                                                                                                                                               |
| ------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Framework     | `qbx_core`, `qb-core`, `es_extended` — auto-detected                                                                                                    |
| Inventory     | `ox_inventory` (recommended, required on QBX), `qb-inventory`, `ps-inventory`, `lj-inventory`, `qs-inventory`, `codem-inventory`, default ESX inventory |
| Target        | `ox_target`, `qb-target`, any custom interaction resource, or a marker + **E**                                                                          |
| Notifications | `ox_lib` when running, otherwise the framework's own, or your own resource                                                                              |

`Config.Framework`, `Config.Inventory.system`, `Config.TargetSystem` and `Config.Notify.type` are all set to `auto` by default and detect what your server runs.

## Editions

|                                                   | Escrow edition | Open-source edition |
| ------------------------------------------------- | -------------- | ------------------- |
| Runs out of the box                               | ✅              | ✅                   |
| `config.lua`, `locales/`                          | Editable       | Editable            |
| Framework bridge (`modules/framework/*.lua`)      | Editable       | Editable            |
| Inventory bridge (`modules/inventory/bridge.lua`) | Editable       | Editable            |
| Core Lua (`server/`, `client/`)                   | Encrypted      | Editable            |
| Vue source of the UI (`web/src/`)                 | Not included   | Included            |

Both editions have the same features. The open-source edition is for developers who want to change the core logic or the interface itself — see [Building the UI](/daddy-studios-docs/scripts/daddy-marketplace/building-the-ui.md).

## Safety

* Every record is claimed atomically in SQL *before* money or items move, so two players buying the same listing at the same moment cannot both succeed
* Prices, quantities, item metadata, categories and the market location all come from the server — never from the client
* Item metadata (durability, serial numbers) survives every trade
* Actions require the player to still be at the market they opened
* Players never receive each other's real identifiers (citizenid / license)

## Next steps

* [Installation](/daddy-studios-docs/scripts/daddy-marketplace/installation.md)
* [Configuration](/daddy-studios-docs/scripts/daddy-marketplace/configuration.md)
* [Commands & Permissions](/daddy-studios-docs/scripts/daddy-marketplace/commands-and-permissions.md)

***

[🛒 Escrow on Tebex](https://daddy-studio.tebex.io/package/7673855) | [🔓 Open Source on Tebex](https://daddy-studio.tebex.io/package/7684728) | [💬 Get Support](https://discord.gg/NFKjbN9s2q)


---

# 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://daddy-studios.gitbook.io/daddy-studios-docs/scripts/daddy-marketplace.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.