Brick Shops installation

Brick Shops ships as one provider-neutral runtime for QBCore, Qbox, and ESX.

Requirements

• OneSync and server-side player ped access
• ox_lib
• A compatible Brick Bridge release
• a supported framework, inventory provider, and oxmysql
• optional target and notification providers

Use a selected inventory provider that supports item catalogs, inventory reads, image paths, capacity checks, adding items, and removing items through Brick Bridge.

Database

Brick Shops creates and additively repairs its eight owned tables during startup. The database account needs access to information_schema plus permission to create and alter those tables. Importing sql/install.sql is optional.

Startup never changes existing column definitions, drops data, or runs destructive migrations.

Start order

ensure oxmysql
ensure ox_lib

# Start one framework and the selected inventory/target/notify resources.
ensure qb-core

ensure brick_bridge
ensure brick_shops

This is normal server startup configuration. Do not reload ox_lib on a running server. If a selected provider changes, restart the provider, then Brick Bridge, then Brick Shops.

Create the first store

1. Join with a configured administrator grant.
2. Stand where the shopkeeper should be placed.
3. Run /shopcreator.
4. Choose New store.
5. Configure identity, owner, hours, presentation, access, and optional loyalty overrides.
6. Add categories and products if desired. A store can be saved with an empty catalog.
7. Leave products visible unless you intend to hide them. Use -1 for unlimited stock or maximum stock.
8. Save and enable the store.

The first save creates the store and synchronizes it to connected clients immediately. No resource restart is required.

Note

Brick Shops has no /myshops command. Owners and permitted workers manage a store through the shopkeeper’s Manage interaction or the configured marker fallback.

Verify before production

On a test server, open a published shop, complete a low-value purchase, and confirm that inventory, stock, and the shop balance update correctly before moving the resource to production.