logo

Architecture and Panel Structure

This page explains how the system is divided into parts, and what each part is used for.

Main parts of the system

  • Public Website: for visitors who are learning about your product
  • Authentication Module: login and register pages for staff/users
  • Admin Panel: central control for top-level users
  • Store Dashboard (/dashboard/[storeSlug]/*): daily operations for one selected store
  • Legacy Store Panel (/store/*): older fast-action interface for heavy execution users

Why there are two store interfaces

The dashboard interface is easier to read and better for visibility and reports.

The legacy interface is faster for teams who prefer a compact, action-heavy screen.

You can keep both if different staff types work differently.

How data separation works

Admin pages can see global data across stores.

Store pages show only the selected store data.

This prevents one branch from accidentally editing another branch records.

It also keeps accountability clean and improves operational discipline.

Recommended practical usage

Use Admin Panel for oversight, policy checks, and performance comparison.

Use Store Dashboard for daily order handling and team execution.