Questions users actually ask before they register.

King Sparkon Tracker™ is the trademark platform of Sizolwakhe Leonard Mthimunye, known as King Sparkon, an Oracle-verified developer. The About page shows the founder card and credential link to Credly. The platform is not a white-label marketplace skin; it has custom business workspaces, scan protocols and audit logs backed by the Spring Boot backend leonard1thecoder/king-sparkon-tracker-backend.

It replaces spreadsheet chaos with one auditable ledger for: barcode inventory (unit-level tracking), QR ticket sales and gate verification, cart checkout and collection, job postings and applications, worker tips and withdrawals, affiliate referrals and promotions, billing and audit-ready reports. Each job maps to a role-safe dashboard.

SELL requires barcodes.length to equal total quantity — the API enforces it so every sold unit is traceable. BUY must not send barcodes. Stock quantity and barcode count are separate fields; remainingBarcodeSlots = stockQuantity − barcodeCount is computed server-side and shown in the product screens.

Owners create events with ticket classes (quantity, price, sold, checkedIn). Users buy and keep QR tickets in My Tickets. Workers scan at the gate via /dashboard/worker/tickets/scan. The backend marks tickets fulfilled and prevents reuse. Capacity dashboards aggregate tickets, workers, jobs, stock and platform totals.

Yes. Transactions support CASH, SWIPE_MACHINE and WEBSITE_PAYMENT. Website payments return paymentUrl, paymentStatus and referenceEmail. Tips expose grossAmount, feeAmount and netAmount — never computed in the browser. Withdrawals show gross/fee/net and status before the owner approves. No hidden rounding.

FREE_TRIAL allows up to 2 workers, PLUS up to 5, PRO is unlimited. Pro unlocks WORKER_TIPS_PLATFORM, BUSINESS_ANALYSIS_AI and WORKER_CLOCKER. The UI respects backend feature locks and shows a coherent upsell rather than a dead button. Billing is managed via /dashboard/owner/billing and Stripe checkout sessions.

Owner: products, workers, transactions, tips, promotions, reports, audit logs, billing. Worker: scan terminal, barcodes, transactions, tips, claims. Affiliate: referrals, commissions, payouts, assets. User: shop, tickets, jobs, carts. Admin: users, businesses, promotions, scan logs, settings. Each has its own layout and nav component; the proxy guards role access server-side.

Auth tokens are stored as httpOnly cookies via /api/auth/* route handlers; the browser never handles backend secrets. Backend contact handling for WEBSITE_PAYMENT can create a CLIENT subscriber via the API, but CASH/SWIPE_MACHINE flows never subscribe customers. See the Privacy page for the full inquiry, subscriber and cookie policy.