​

Dashboard Architecture Overview

​

High-Level Split

• Landing / storefront: Next.js public app
• Dashboard: Vite SPA for authenticated operations
• Backend: shared API/auth origin on marketplace-backend.digitizweb.com

​

Core Functional Domains

1. Public commerce layer
   • listing discovery
   • category browsing
   • pricing
   • registration/login
2. Seller workspace
   • own listings
   • create listing
   • watchlist
   • invoices
   • messaging
   • profile
   • promotions
3. Admin operations
   • moderation
   • users
   • subscriptions
   • invoices
   • categories
   • CMS/content settings
   • promotion package administration

​

API Patterns Observed

• session identity: api/spa/user
• login shortcut: api/dev/spa-login
• notifications: api/notifications*
• seller listings: api/my-listings
• watchlist: api/watchlist
• chat threads: api/threads
• listing attributes/categories: api/attributes, api/categories?role=...
• subscriptions: api/subscriptions/*
• promotions: api/promotions/*
• admin modules: api/admin/*

​

Realtime / Background Services

• Pusher/WebSocket connection attempts were observed for notifications/chat presence.
• Some headless runs reported socket-close warnings before full connection establishment.

​

Role Model

• Super Admin: full admin + seller surface
• Private: self-service marketplace user with upgrade CTAs
• Business: seller account with business identity/profile layer
• Business Pro: premium seller tier with billing evidence and same visible seller nav as Business in tested demo

​

Visual Architecture References