01
Purchasing workspace
Buyer
Inspect paid and unpaid orders, spend by currency, purchase history, support threads and notifications.
- Purchasing overview
- Orders and order detail
- Support and notification state
Role-based demoIllustrative fixtures
Walk the workflow, not a slide deck.
Enter as a buyer, seller or super administrator and inspect the same persisted application that powers discovery, commerce, review queues and operating dashboards.
Demo boundary
Demo entry appears only when the API reports that demo mode is enabled. The browser sends a role key; the server resolves it to a fixed demo account with an unusable password.
3 roles1 database0 shared passwords
Choose a vantage point
One workflow, three permission surfaces
Each role sees a different operational picture. Authorization is enforced by the API rather than by hiding links.
02
Operating workspace
Seller
Review the storefront, product inventory, seller-scoped order lines, payout position and support conversations.
- Store performance
- Products and orders
- Wallet and withdrawal queue
03
Control plane
Super admin
Open marketplace analytics, seller applications, store releases, order operations, payouts and support queues.
- Marketplace analytics
- Seller review and store release
- Commerce and support controls
01
Fixed identities
Demo identifiers are configured on the server. The browser cannot submit an email or choose another account.
02
Normal session controls
Demo sessions use the same HttpOnly cookie, CSRF checks, session rotation and revocation middleware as password login.
03
Repeatable reset
A scoped management command provisions or resets only the demo accounts and their workflow fixtures.
The demo is an evaluation environment, not a commercial marketplace. Products, suppliers, orders and support records are illustrative. No payment is taken, no supplier is contacted and no real fulfilment is created. Do not enable demo mode on a database containing production or personal data.