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

# Envi-ChopShop

***

## Prerequisites

{% hint style="info" %}

* A working FiveM Server
* Basic understanding of FiveM server setup and resource management
* An up-to-date version of [ox\_lib](https://github.com/CommunityOx/ox_lib)
* Followed the [First Steps](/documentation/premium-scripts/first-steps-read-first.md) guide
* Envi-Bridge (added to your CFX Portal automatically when Chopshop is purchased)
* Inventory items matching your chop, loot, and contract config
* Database support for ownable business data
  {% endhint %}

***

## [Tebex](https://envi-scripts.tebex.io/package/5639403)

***

## Features

* multi-stage vehicle chop workflow
* tool-based door and wheel removal
* battery, gearbox, radiator, and scrap stages
* loot and optional car-part item rewards
* ownable chop shop businesses
* worker permissions and machine purchases
* special contract flow
* optional dispatch integration
* optional hardcore mode for player-owned vehicles
* payout tuning by vehicle class and damage state

### How vehicle contracts work

Contracts are only useful for player-owned chop shops.

Flow:

1. the shop owner generates a contract
2. the owner gives that contract item to another player
3. that player finds the matching vehicle in the world
4. when the chop is completed, the contract is removed and both sides get the configured rewards

The script does not spawn the contract vehicle for you.

The owner cannot complete their own contract.

### How player-owned vehicles work

By default, player-owned vehicles cannot be chopped.

If you enable hardcore mode, player-owned vehicles can be chopped, but the default behavior is destructive.

{% hint style="warning" %}
Hardcore mode can permanently remove owned vehicles from the database unless you adjust your editable server logic.
{% endhint %}

That behavior is intended to be customized in your editable server files if your garage flow needs something different.

### Install

{% stepper %}
{% step %}

### Start the dependencies

Start `envi-bridge`, `ox_lib`, your inventory, and any target dependency before ChopShop.
{% endstep %}

{% step %}

### Keep the resource name intact

The resource expects to run as `envi-chopshop`.
{% endstep %}

{% step %}

### Add database and item setup

Apply the chopshop database setup and register the install items in your inventory.
{% endstep %}

{% step %}

### Test one shop first

Test a default shop before adding your own locations or enabling hardcore mode.
{% endstep %}
{% endstepper %}

Use [Quick Start](/documentation/premium-scripts/envi-chopshop/quick-start.md) for the first full setup flow.

### Where you edit things

Most owners will work in:

* `shared/config.lua`
* `client/client_edit.lua`
* `server/server_edit.lua`
* `install/items.txt`

### Docs in this section

* [Quick Start](/documentation/premium-scripts/envi-chopshop/quick-start.md)
* [How to Chop](/documentation/premium-scripts/envi-chopshop/how-to-chop.md)
* [Business Ownership and Contracts](/documentation/premium-scripts/envi-chopshop/business-ownership-and-contracts.md)
* [Hardcore Mode](/documentation/premium-scripts/envi-chopshop/hardcore-mode.md)
* [Config Reference](/documentation/premium-scripts/envi-chopshop/config-reference.md)
* [Inventory Setup](/documentation/premium-scripts/envi-chopshop/inventory-setup.md)
* [Props for AntiCheats](/documentation/premium-scripts/envi-chopshop/props-for-anticheats.md)
* [Editable Functionality](/documentation/premium-scripts/envi-chopshop/editable-functionality.md)
* [Common Issues](/documentation/premium-scripts/envi-chopshop/common-issues.md)
* [FAQ and Operations](/documentation/premium-scripts/envi-chopshop/faq-and-operations.md)

***

## Preview

{% embed url="<https://youtu.be/AAjMJ0PvFoA>" %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://envi-scripts-organization.gitbook.io/documentation/premium-scripts/envi-chopshop.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.