by Intelliverse X

The Operator Console, visually

One console for your whole fleet โ€” machines, money, ads, and play.

This guide is a plain-language, picture-first tour of the Kiosk-X Operator Console (operator.kiosk-x.ai, plus the native Android app from the downloads hub) and how it connects to everything else in the Kiosk-X family.

The big picture

Your kiosk is more than a vending machine: its screen earns ad money, its QR codes start games and quests, and every one of those loops reports back to the same operator console.

flowchart LR subgraph shopper [At the machine] VA["๐Ÿช Vending app
(kiosk screen)"] QR["๐Ÿ“ฑ QR codes
(play ยท advertise here)"] end subgraph cloud [Kiosk-X Cloud] API["Partner API
api.kiosk-x.ai"] end subgraph products [Product family] QX["๐ŸŽฎ QuestX
free-product quests"] GW["๐ŸŒ GameWorld
multiplayer at the kiosk"] CX["๐Ÿ“บ ContentX Ads
sponsorships + programmatic"] end OC["๐Ÿ–ฅ๏ธ Operator Console
operator.kiosk-x.ai
+ Android app"] VA -- "sales, faults, stock" --> API QR -- "scan-to-play / scan-to-buy-ads" --> QX & CX QX -- "giveaway + credit reports" --> API GW -- "session & reward stats" --> API CX -- "proof-of-play, eCPM, approvals" --> API API -- "one login, every number" --> OC

Everything below is one section per console area: what it shows, where the data comes from, and the one thing to check daily.

๐Ÿ  Dashboard โ€” your morning glance

Route: / ยท Check daily: Today's Sales + the alert bell.

Tile What it means
Today's Sales Delivered product sales since local midnight (server-computed)
Last 7 / 30 days ยท All time The same, over longer windows, net of refunds
Ad Income Estimated screen-ad revenue โ€” direct sponsorships + programmatic fill
Machine Fleet How many kiosks are online right now
Notifications Offline machines and low-stock aisles

The bell in the top bar mirrors the notifications; the avatar menu holds Change Password and sign-out. Every screen you visit becomes a workspace tab so you can flip between, say, a machine detail and its sales.

๐Ÿช Machines & inventory

Routes: /machines, /machines/{serial}, /faults, /products.

Register a machine by the serial inside its door, watch its aisles (planogram, prices, stock), re-enable faulted aisles, and bind the Nayax card reader so card takings settle to your merchant account.

๐Ÿ’ณ Sales & money

Routes: /playbook, /sales, /reports, /pnl, /tax, /venues, /warehouse, /payouts.

The first hour is /playbook โ€” six steps in this order: confirm the fleet, put a tax rate on file, receive open purchase orders, record each site and its host deal, add crew rates, open the P&L once. Tax and inventory affect every later number; skip them and the first P&L looks too good.

Orders stream in from the machines (cash, card, wallet). Reports slice revenue by period, machine, and product, and reconcile card settlement against your Nayax accounts. Refunds are one tap from any order. /pnl is the identity (gross โˆ’ tax = net โˆ’ FIFO โˆ’ host โˆ’ โ€ฆ); /venues is the only place host commission is defined โ€” name the serial when you create the venue if the cabinet has already been selling, or the host is owed nothing for that history. /tax schedules do not reprice stamped sales; a cabinet's own jurisdiction rate does, except for a period already remitted or paid out (/api/v1/tax/restatements-blocked).

๐Ÿ“‹ Subscriptions & billing

Route: /subscriptions โ€” four tabs, mirroring the classic operator portal:

flowchart LR S["Subscribe
plans + Renew Equipment"] --> R["Recharge Record
wallet top-ups"] R --> A["Account Information
available / frozen / cumulative"] A --> B["Billing Detail
every line + summation + CSV"]

๐Ÿ“บ Ad revenue โ€” your screens earn while idle

Route: /ads (summary also on /reports and the dashboard).

flowchart TD LOOP["Kiosk attract loop
(screen between sales)"] D["Direct sponsorships
you sell โ€” local business, stocked-brand co-op"] P["Programmatic fill
SSP auction, net CPM"] H["House ads
your own promos ($0)"] SS["Self-serve buyers
scan 'advertise here' QR โ†’ pay via Stripe"] APPR{"You approve
every self-serve ad"} D --> LOOP P --> LOOP H --> LOOP SS --> APPR -- approved --> LOOP LOOP -- "proof-of-play ledger" --> REV["๐Ÿ’ฐ Ad income in your reports
split by source + eCPM"]

The mediation engine ranks fill sources by eCPM under your floor price; every play lands in the proof-of-play ledger, so the revenue split you see is counted from actual plays, not estimates of estimates.

๐ŸŽฎ Play โ€” QuestX & GameWorld

Where: Reports โ†’ Player engagement; per-machine toggles on the machine detail page.

Both are demand generators: the machine gets foot traffic, the play loop gets players, and you see it all next to the sales it drives.

๐Ÿ†˜ Support, in the corner of every screen

The floating bubble opens a five-tab widget: Home (quick actions), Messages (your ticket threads), Tickets (open + track), Help (article library), and Tasks โ€” a setup checklist that checks itself off as your account reaches each milestone, with a QR to grab the Android operator app.

๐ŸŽจ One design language

The console, the Android app, the kiosk screen, and the buyer-facing pages all share the Kiosk-X design system: deep-space surfaces, purple #a855f7 + cyan #06d0f9, Poppins type, and the same motion vocabulary. If a surface looks different, that's a bug โ€” the tokens ship from one file.

Where to go next