Integration

Opening the storefront (client)

Call from any client script (e.g. a qb-target/legacy-lib Target interaction, a command, etc.):

-- client-side, e.g. client/main.lua
exports['legacy-shops']:OpenStore(3) -- shopId

This awaits the legacy-shops:getInitData and legacy-shops:openStore server callbacks and opens the store NUI. It no-ops if the UI is already open, or shows an lib.notify error if the server returns no data (e.g. job-locked).

Opening the admin creator (client)

-- client-side
exports['legacy-shops']:OpenCreator()

Requires initData.isAdmin (from the cached legacy-shops:getInitData result) to be true, otherwise shows an lib.notify error. Note this admin check is client-side only after the initial fetch — the server-side legacy-shops:getInitData callback is the real enforcement point.

Opening the creator from the server

-- server-side, e.g. server/main.lua
TriggerClientEvent('legacy-shops:openCreator', src)

This triggers the local OpenCreator() function on that client, instead of relying on the client to call the export directly. This is what Config.CreatorCommand uses internally.

Reacting to shop list changes (client)

-- client-side
AddEventHandler('legacy-shops:syncShops', function()
    -- re-fetch and respawn shop peds/blips automatically (handled internally)
end)

Broadcast server-side (to all clients, -1) after any shop is created, updated, deleted, or after a preset re-sync propagates to its linked shops. You don't need to trigger this yourself in normal usage — the server callbacks below already broadcast it.

legacy-shops:stockUpdated is also broadcast to all clients after restock/fluctuation ticks, but its client-side handler is currently an empty stub — do not rely on it to refresh an open store UI.

Server callbacks (ox_lib lib.callback)

All of the following are registered server-side and consumed via lib.callback.await(...) from the client, or can be called from other server scripts via the export syntax exports['legacy-shops']:<name>(...) where applicable. Admin-gated ones return an empty result for non-admins.

-- server-side example: fetch a shop's items from another resource
local items = exports['legacy-shops']:getItems(shopId)

Key callbacks:

Example: purchase flow trigger from the storefront NUI

-- this happens internally via lib.callback from the NUI; shown here as a
-- reference for what a purchase payload looks like
local result = lib.callback.await('legacy-shops:purchase', false, {
    shopId = 3,
    paymentMethod = 'cash', -- or 'bank'
    lines = {
        { id = 12, quantity = 2 },
    },
})