Qtrax 360 Premium Retail App Guide

Best Buy quietly removed all Qtrax kiosks by mid-2014. HMV (already struggling) terminated the contract. Retailers realized they were complicit in copyright infringement.

Qtrax 360 empowers sales associates to act as personal stylists. When a customer enters the store (either via app check-in or recognition), the associate’s device receives a "Client Card." qtrax 360 premium retail app

| Competitor | Weakness That Qtrax 360 Exploits | |------------|----------------------------------| | Shazam | No retail loyalty integration; no store employee view; no licensed in-store playback. | | Soundtrack Your Brand | Strong on licensed playlists, but zero customer song identification or purchase path. | | Rockbot | Has retail + music, but requires proprietary hardware; Qtrax 360 works with existing phone as identifier. | | Apple Music for Business | No customer-facing recognition layer; B2B only. | Best Buy quietly removed all Qtrax kiosks by mid-2014

Unique differentiator: Qtrax 360 is the only platform that closes the loop between hearing a song in a store, identifying it, purchasing it, and rewarding the store – all within one app. Qtrax 360 empowers sales associates to act as

The Client: "Urban Threads" (4 locations in Chicago) The Problem: Staff were playing their personal Spotify playlists. Volume and genre varied wildly. Legal risk was high. The Solution: The Qtrax 360 Premium Retail App across all 4 stores, centralized under one account. The Implementation: They used the voice-over feature to announce a "Flash Sale" every 20 minutes. The Result:

The owner notes: "The voice-over feature pays for the subscription on the first day of each month. We don't have to yell 'sale' anymore; the music system does it for us."

Retail is moving away from stationary Point of Sale (POS) terminals. Qtrax 360 Premium enables "Endless Aisle" capabilities.

Back
Top
Chat commands start with a /, while console commands can be entered directly in the F1 console or server console. Use find <keyword> in console to search for available commands related to the plugin. Parameters in < > are required, while [ ] are optional.
This plugin uses Oxide's permission system. Grant or revoke permissions using oxide.grant and oxide.revoke. You can assign them to individual players or groups using their Steam id or group name.
Settings are stored in the config file found under the config/ directory. You can edit this file manually, then reload the plugin to apply your changes.
Persistent data is saved in the data/ directory. This includes things like saved settings, usage stats, or player progress depending on the plugin. Deleting a data file will reset stored progress or customizations.
Language files are located in the lang/ folder. To translate messages, copy the en.json file into your target language folder (e.g. fr, de) and edit the values. Reload the plugin after changes to apply new messages.
This section lists public methods exposed by the plugin for use in other plugins. You can call these via the CallHook method. Ensure the plugin is loaded before calling its API to avoid null reference errors.
These are custom hooks that other plugins can listen for. Simply define a method with the same name and expected parameters in your plugin to handle the event. Hooks are triggered at key moments and are useful for extending or reacting to plugin behavior.
These hooks are injected into the game's code using Harmony. They let the plugin run code at key points in the game's internal logic. You can return values to block or modify behavior. Use with caution — these are powerful and can affect core mechanics.
Cart

Cart

Total -