marine-heroic

byM G
landing
landing

Comments (0)

No comments yet. Be the first!

System Requirements

System Requirements Document for marine-heroic

1. Introduction

1.1 PROJECT NAME: CafeDesk / PROJECT OVERVIEW

1.2 FINAL QUALITY REQUIREMENTS

FINAL GOAL:

Build CafeDesk as a premium, scalable, multi-tenant SaaS platform that any restaurant owner can use under their own brand.

A restaurant owner should be able to register, upload their logo, choose their preferred theme, customize their menu, generate table QR codes, and start accepting customer orders without needing technical knowledge.

The platform should connect Customers, Waiters, Kitchen Staff, Restaurant Owners, and Business Analytics into one intelligent restaurant management ecosystem.

CafeDesk – Every Table Connected. Every Order Simplified. Every Restaurant Smarter.# MASTER UPGRADE PROMPT

Page 1 of 99

1.3 FINAL QUALITY REQUIREMENTS / CafeDesk – White-Label Multi-Tenant Restaurant SaaS Architecture / FINAL INSTRUCTION

Build a production-oriented White-Label Multi-Tenant SaaS Platform.

The final system must allow hundreds of restaurant owners to operate independently under their own brands while the platform owner manages everything from one centralized Super Admin Dashboard.

CafeDesk – One Platform. Unlimited Restaurants. Every Brand Independent.# CAFEDESK – FINAL MASTER FOUNDATION PROMPT

1.4 FINAL QUALITY REQUIREMENTS / Enterprise White-Label Multi-Tenant Restaurant SaaS Platform / PROJECT OBJECTIVE

1.5 FINAL IMPLEMENTATION INSTRUCTIONS / FINAL VISION

CAFEDESK

"One Platform. Every Restaurant. Its Own Identity."

The project name selected by the user is “marine-heroic”.

2. System Overview

Page 2 of 99

2.1 PREMIUM WEBSITE DESIGN / Design Language

Create a professional landing page with:

  1. Premium Hero Section

  2. How It Works

  3. QR Ordering Demonstration

  4. Live Kitchen Dashboard Preview

  5. Restaurant Floor Management Preview

  6. Restaurant Customization Features

  7. Payment Management

  8. Business Analytics

  9. Pricing Plans

  10. FAQ

  11. Contact Section

Page 3 of 99

2.2 FINAL QUALITY REQUIREMENTS / CafeDesk – White-Label Multi-Tenant Restaurant SaaS Architecture / CORE OBJECTIVE

Upgrade the existing CafeDesk application into a fully functional, enterprise-grade, White-Label Multi-Tenant Restaurant SaaS Platform.

IMPORTANT:

CafeDesk must NOT operate as a single restaurant website.

It must work as a centralized SaaS platform where hundreds or thousands of independent restaurants, cafes, hotels, bakeries, and food businesses can register and operate using their own branding.

The platform owner (Super Admin) must have centralized control over all registered businesses.

Every restaurant must have its own independent digital identity, dashboard, menu, QR codes, customer interface, orders, payments, staff, analytics, and customization settings.

Page 4 of 99

2.3 FINAL QUALITY REQUIREMENTS / CafeDesk – White-Label Multi-Tenant Restaurant SaaS Architecture / DATABASE ARCHITECTURE

  • RestaurantDomains

  • MenuCategories

  • MenuItems

  • Tables

  • QR Codes

  • Orders

  • OrderItems

  • KitchenUpdates

  • ServiceRequests

  • Payments

  • Customers

  • Staff

  • Subscriptions

  • SubscriptionPlans

  • PaymentRequests

  • Notifications

Page 5 of 99

2.4 FINAL QUALITY REQUIREMENTS / Enterprise White-Label Multi-Tenant Restaurant SaaS Platform / PROJECT OBJECTIVE

Upgrade the existing CafeDesk application into a scalable, secure, enterprise-grade White-Label Multi-Tenant Restaurant SaaS Platform.

The entire architecture must be built around three critical foundations:

  1. Multi-Tenant Database Architecture

  2. White-Label Branding & Theme Engine

  3. Centralized Super Admin Control Center

IMPORTANT:

Do not build CafeDesk as a single restaurant website.

CafeDesk must support hundreds or thousands of independent restaurants using one centralized platform.

Every restaurant must operate under its own brand, with its own owner account, dashboard, menu, QR codes, orders, payments, customers, staff, and business settings.

The platform owner must have centralized control over the entire SaaS ecosystem.

2.5 FINAL IMPLEMENTATION INSTRUCTIONS / FINAL VISION

CafeDesk must become a centralized White-Label Restaurant SaaS Platform.

One platform.

Unlimited restaurants.

Independent databases and business operations.

Page 6 of 99

3. Functional Requirements

3.1 PROJECT NAME: CafeDesk / PROJECT OVERVIEW

Every restaurant must have its own:

  • Restaurant Name

  • Logo

  • Cover Image

  • Brand Colors

  • Custom Theme

  • Digital Menu

  • Food Categories

  • Food Images

  • Table QR Codes

  • Customer Orders

  • Kitchen Dashboard

  • Staff Management

  • Payment Settings

  • Business Analytics

3.2 PREMIUM WEBSITE DESIGN / Design Language

Page 7 of 99

3.3 MULTI-TENANT RESTAURANT REGISTRATION

Any restaurant owner must be able to create an account.

Registration fields:

  • Owner Full Name

  • Restaurant Name

  • Business Type

  • Email Address

  • Mobile Number

  • Password

  • Restaurant Address

  • City

  • Country

Business Types:

  • Cafe

  • Restaurant

  • Hotel

  • Bakery

  • Food Court

  • Cloud Kitchen

Page 8 of 99
  • Other

After registration, create a unique Restaurant ID.

Every restaurant must have an independent workspace.

Example:

Restaurant A → Restaurant ID: RES1001

Restaurant B → Restaurant ID: RES1002

Restaurant C → Restaurant ID: RES1003

Page 9 of 99

3.4 OWNER DASHBOARD

Create a powerful, premium restaurant owner dashboard.

Sidebar navigation:

  1. Overview

  2. Live Orders

  3. Menu Management

  4. Table Management

  5. QR Code Generator

  6. Live Floor Map

  7. Kitchen Management

  8. Staff Management

  9. Payment Management

  10. Customers

  11. Offers & Discounts

  12. Tips Management

  13. Split Bills

  14. Analytics & Reports

  15. Restaurant Customization

  16. Subscription

Page 10 of 99
  1. Settings
Page 11 of 99

3.5 OWNER DASHBOARD / Dashboard Overview

Display live information:

  • Today's Total Orders

  • Today's Revenue

  • Active Tables

  • Available Tables

  • Occupied Tables

  • Pending Orders

  • Preparing Orders

  • Ready Orders

  • Completed Orders

  • Pending Payments

  • Total Tips

Include:

  • Revenue Graph

  • Orders Graph

  • Popular Dishes

  • Recent Orders

  • Live Activity

Page 12 of 99
  • Table Occupancy

All dashboard statistics must come from actual database records.

Page 13 of 99

3.6 SMART DIGITAL MENU BUILDER

Create an advanced menu management system.

Restaurant owners can:

  • Add Food Items

  • Edit Food Items

  • Delete Food Items

  • Upload Food Images

  • Add Food Descriptions

  • Set Food Prices

  • Create Food Categories

Example categories:

  • Starters

  • Main Course

  • Pizza

  • Set Veg / Non-Veg Labels

  • Mark Items as Bestseller

  • Mark Items as Available / Unavailable

  • Add Special Offers

  • Set Preparation Time

Page 14 of 99

3.7 SMART DIGITAL MENU BUILDER / Advanced Customization

Include a LIVE PREVIEW button.

When an owner changes a menu design or food price, the changes must automatically appear on the existing customer QR menu.

No QR reprinting should be required.

3.8 RESTAURANT BRANDING & THEME CUSTOMIZATION

  1. Customize Typography

  2. Customize Menu Cards

  3. Customize Welcome Screen

  4. Customize Customer Ordering Page

Include:

  • Live Theme Preview

  • Save Changes

  • Publish Theme

  • Reset Theme

Every theme must dynamically update the restaurant's customer-facing QR menu.

Every theme must dynamically update the restaurant's customer-facing QR menu.

Page 15 of 99

3.9 SMART TABLE MANAGEMENT & QR GENERATOR

Create an advanced table management system.

Owners can:

  • Add Tables

  • Edit Tables

  • Delete Tables

  • Set Table Numbers

  • Assign Table Capacity

  • View Table Status

  • Generate Individual QR Codes

Example:

Table 01

Table 02

Table 03

Table 04

Table 05

Every table must have its own unique QR code.

QR code must contain:

  • Unique Restaurant ID

  • Unique Table ID

Page 16 of 99
  • Secure Customer Menu URL

cafedesk.com/menu/RES1001/TABLE05

The system must automatically open Restaurant 1001's digital menu with Table 05 already selected.

QR Management Options:

  • Generate QR

  • Download PNG

  • Download PDF

  • Print QR

  • Copy QR Link

  • Test Scan

  • Regenerate QR

  • Deactivate QR

3.10 CUSTOMER QR ORDERING EXPERIENCE

Customer should NOT need to:

  • Create an account

  • Login

  • Enter a password

  • Download an application

Page 17 of 99

3.11 CUSTOMER QR ORDERING EXPERIENCE / Customer Journey

STEP 4:

Customer browses:

  • Food Images

  • Food Names

  • Prices

  • Descriptions

  • Categories

  • Special Offers

STEP 5:

Customer selects food items.

STEP 6:

Customer can:

  • Increase Quantity

  • Decrease Quantity

  • Customize Food

  • Add Special Instructions

  • Add Items to Cart

STEP 7:

Page 18 of 99

Customer reviews the cart.

STEP 8:

Customer enters:

  • Customer Name

  • Mobile Number (optional or configurable)

STEP 9:

Customer clicks PLACE ORDER.

STEP 10:

Show order confirmation to the customer.

Order automatically appears on:

  • Owner Dashboard

  • Kitchen Display Screen

  • Live Orders Dashboard

Page 19 of 99

3.12 LIVE KITCHEN DISPLAY SYSTEM (KDS)

Create a dedicated Kitchen Display System.

The kitchen screen should show incoming orders in real time.

Every order card should display:

  • Order Number

  • Table Number

  • Food Items

  • Item Quantities

  • Special Instructions

  • Order Time

  • Preparation Status

Order Status:

  1. New Order

  2. Accepted

  3. Preparing

  4. Ready

  5. Served

  6. Completed

  7. Cancelled

Page 20 of 99

Kitchen staff can update order status.

When the kitchen marks an order READY:

  • Owner dashboard updates.

  • Live floor map updates.

  • Customer receives an order status update.

Page 21 of 99

3.13 LIVE FLOOR MANAGEMENT

Create an interactive restaurant floor map.

Display all restaurant tables visually.

Table status indicators:

  • Green: Available

  • Orange: Occupied

  • Blue: Order Preparing

  • Purple: Order Ready

  • Red: Service Required

  • Yellow: Payment Pending

When the owner clicks a table, show:

  • Table Number

  • Current Order

  • Ordered Items

  • Total Amount

  • Payment Status

  • Customer Requests

  • Order Timeline

The floor map must update automatically.

Page 22 of 99

3.14 SMART CUSTOMER SERVICE REQUESTS

After placing an order, customers should see a Service Request section.

Buttons:

  • Request Water

  • Request Waiter

  • Request Extra Plate

  • Request Tissue

  • Request Assistance

  • Request Bill

When a customer clicks any button:

A live notification must appear on the owner/staff dashboard.

Display:

  • Table Number

  • Request Type

  • Request Time

  • Request Status

Staff can mark the request as:

  • Received

  • In Progress

Page 23 of 99
  • Completed

Highlight tables requiring assistance on the live floor map.

3.15 SMART BILLING & SPLIT BILL SYSTEM

Create an advanced billing module.

Customers can:

  • View Current Bill

  • View Food Breakdown

  • View Taxes

  • View Discounts

  • Add Tip

  • Split Bill

  • Pay Full Amount

3.16 SMART BILLING & SPLIT BILL SYSTEM / Split Bill Options

  • Split Equally

  • Split by Item

  • Custom Amount Split

Allow multiple customers to contribute toward the same table bill.

Automatically update remaining payable balance.

Never allow duplicate payment collection.

Page 24 of 99

3.17 MULTIPLE PAYMENT OPTIONS

Create a flexible payment management system.

Support:

  1. Google Pay

  2. PhonePe

  3. UPI ID

  4. UPI QR Code

  5. Debit / Credit Card

  6. Cash at Counter

  7. Cash at Table

Restaurant owners can configure their supported payment options.

Page 25 of 99

3.18 MULTIPLE PAYMENT OPTIONS / UPI Setup

Owner can:

  • Enter UPI ID

  • Upload Google Pay QR

  • Upload PhonePe QR

  • Upload Custom UPI QR

Customers can select their preferred payment option.

For online payments, implement payment verification using a supported payment provider or secure payment integration.

For manual UPI QR payments, provide payment confirmation and owner/staff verification.

For cash payments, staff must be able to mark payments as received.

Track:

  • Total Collected

  • Pending Payments

  • Online Payments

  • Cash Payments

  • Tips

  • Refunds

Never mark an unverified payment as successful.

Page 26 of 99

Never mark an unverified payment as successful.

3.19 STAFF MANAGEMENT

Owner can add staff members.

Roles:

  • Manager

  • Waiter

  • Kitchen Staff

  • Cashier

Each staff member gets role-based access.

Waiter:

  • View Assigned Tables

  • View Service Requests

  • Update Table Service Status

Kitchen:

  • View Kitchen Orders

  • Update Preparation Status

Cashier:

  • View Bills

  • Manage Payments

  • Confirm Cash Payments

Page 27 of 99

Manager:

  • Manage Operations
Page 28 of 99

3.20 CUSTOMER MANAGEMENT & ANALYTICS

Create a customer management module.

Display:

  • Total Customers

  • Repeat Customers

  • Total Orders

  • Average Order Value

  • Most Ordered Food

  • Customer Visit History

Analytics:

  • Daily Revenue

  • Weekly Revenue

  • Monthly Revenue

  • Yearly Revenue

  • Total Orders

  • Table Occupancy

  • Average Preparation Time

  • Payment Breakdown

  • Popular Food Categories

Page 29 of 99

Provide exportable reports in CSV and PDF.

3.21 SUPER ADMIN DASHBOARD

Create a completely separate Super Admin Dashboard.

Only the platform owner can access it.

Super Admin features:

  • Total Registered Restaurants

  • Active Restaurants

  • Pending Approvals

  • Expired Subscriptions

  • Total Platform Revenue

  • Monthly Revenue

  • Yearly Revenue

Super Admin features:

  • Restaurant Management

  • Subscription Management

  • Payment Request Management

  • Activate / Suspend Accounts

  • Manage Pricing Plans

  • Platform Settings

Page 30 of 99

3.22 SUBSCRIPTION MANAGEMENT

Create a flexible subscription module.

Allow platform admin to create and modify:

  • Monthly Plans

  • Yearly Plans

  • Free Trial

  • Premium Features

  • Subscription Expiry

  • Account Activation

Each restaurant should have its own subscription status.

Display:

  • Active

  • Pending

  • Expired

  • Suspended

Page 31 of 99

3.23 DATABASE & BACKEND ARCHITECTURE

Implement:

  • Secure Authentication

  • Database-Level Access Policies

  • Restaurant Data Isolation

  • Real-Time Updates

  • Server-Side Validation

  • Secure Payment Verification

  • Error Handling

  • Database Transactions

  • Audit Logging

Page 32 of 99

3.24 REAL-TIME SYSTEM REQUIREMENTS

The following operations must update in real time:

  • New Customer Orders

  • Kitchen Order Updates

  • Order Ready Notifications

  • Table Status

  • Service Requests

  • Payment Confirmation

  • Split Bill Updates

  • Owner Dashboard Analytics

Use a reliable real-time architecture.

Ensure the system works across multiple devices simultaneously.

Prevent duplicate orders and duplicate payment processing.

Page 33 of 99

3.25 FINAL QUALITY REQUIREMENTS

Build a complete functional application.

Every button must perform its intended action.

Every form must validate and save actual data.

Every dashboard must display real database information.

Every QR code must open the correct restaurant and table.

  1. Staff Permissions

  2. Super Admin Security

  3. Multi-Restaurant Data Isolation

Page 34 of 99

3.26 FINAL QUALITY REQUIREMENTS / CafeDesk – White-Label Multi-Tenant Restaurant SaaS Architecture / WHITE-LABEL BRANDING SYSTEM

Create a dedicated White-Label Branding Engine.

Every restaurant owner must be able to customize their restaurant's digital experience.

Customization options:

  • Restaurant Name

  • Restaurant Logo

  • Restaurant Cover Image

  • Brand Colors

  • Primary Color

  • Secondary Color

  • Background Color

  • Font Family

  • Button Styles

  • Menu Card Design

  • Header Design

  • Footer Design

  • Customer Menu Layout

  • Welcome Screen

Page 35 of 99
  • Restaurant Contact Information

  • Social Media Links

  • Live Preview

  • Save Theme

  • Publish Theme

  • Reset Customization

All changes must instantly reflect on that restaurant's customer-facing QR menu.

Page 36 of 99

3.27 FINAL QUALITY REQUIREMENTS / CafeDesk – White-Label Multi-Tenant Restaurant SaaS Architecture / INDEPENDENT RESTAURANT WORKSPACES

Create a separate workspace for every registered business.

Example:

RESTAURANT 01:

Business Name: Mayur Cafe

Restaurant ID: RES1001

RESTAURANT 02:

Business Name: ABC Restaurant

Restaurant ID: RES1002

RESTAURANT 03:

Business Name: XYZ Hotel

Restaurant ID: RES1003

Each business must have:

  • Independent Owner Account

  • Independent Dashboard

  • Independent Restaurant Settings

  • Independent Branding

  • Independent Menu

  • Independent Categories

  • Independent Food Images

Page 37 of 99
  • Independent Tables

  • Independent QR Codes

  • Independent Orders

  • Independent Kitchen Dashboard

  • Independent Staff Accounts

  • Independent Payments

  • Independent Customers

  • Independent Reports

  • Independent Subscription

NEVER share restaurant data between businesses.

Page 38 of 99

3.28 FINAL QUALITY REQUIREMENTS / CafeDesk – White-Label Multi-Tenant Restaurant SaaS Architecture / DYNAMIC RESTAURANT URL SYSTEM

Create dynamic branded customer menu URLs.

Example:

cafedesk.com/menu/mayur-cafe

cafedesk.com/menu/abc-restaurant

cafedesk.com/menu/xyz-hotel

Also support unique table URLs:

cafedesk.com/menu/mayur-cafe/table-01

cafedesk.com/menu/mayur-cafe/table-02

cafedesk.com/menu/abc-restaurant/table-01

Each URL must dynamically load the correct restaurant's branding, menu, and table information.

Restaurant slug must be unique.

Validate every URL against the restaurant database.

Never use hardcoded restaurant names or sample restaurant data in production.

Page 39 of 99

3.29 FINAL QUALITY REQUIREMENTS / CafeDesk – White-Label Multi-Tenant Restaurant SaaS Architecture / WHITE-LABEL QR CODE ENGINE

Create a completely independent QR generation system.

Every restaurant can create unlimited or plan-based table QR codes.

Each QR must contain:

  • Restaurant ID

  • Table ID

  • Restaurant Slug

  • Unique QR Token

QR features:

  • Generate QR

QR features:

  • Download PNG

QR features:

  • Download PDF

QR features:

  • Print QR

QR features:

  • Copy Link

QR features:

Page 40 of 99
  • Test Scan

QR features:

  • Regenerate QR

QR features:

  • Deactivate QR

When a customer scans a QR code:

  1. Identify the restaurant.

  2. Identify the correct table.

  3. Load the restaurant's own branding.

  4. Load its live menu.

  5. Allow customer ordering.

  6. Send the order to the correct owner and kitchen.

CRITICAL SECURITY:

A QR code belonging to Restaurant A must never display Restaurant B's menu or orders.

Page 41 of 99

3.30 FINAL QUALITY REQUIREMENTS / CafeDesk – White-Label Multi-Tenant Restaurant SaaS Architecture / CENTRALIZED SUPER ADMIN CONTROL

Create a private Super Admin Control Center.

Only the authorized platform owner can access this area.

Super Admin must be able to:

  • View All Restaurants

  • Search Restaurants

  • Add Restaurants

  • Edit Restaurant Details

  • Approve New Owners

  • Activate Accounts

  • Suspend Accounts

  • Delete Accounts with appropriate safeguards

  • View Subscription Status

  • Manage Pricing Plans

  • View Payment Requests

  • Approve / Reject Payment Requests

  • Monitor Platform Revenue

  • View Platform Analytics

  • Manage Platform Settings

Page 42 of 99

Super Admin can inspect business-level information when authorized, but must not accidentally modify individual restaurant data.

3.31 FINAL QUALITY REQUIREMENTS / CafeDesk – White-Label Multi-Tenant Restaurant SaaS Architecture / RESTAURANT OWNER ACCESS CONTROL

Each restaurant owner can access only their own workspace.

Example:

Mayur Cafe Owner:

Can manage RES1001 only.

ABC Restaurant Owner:

Can manage RES1002 only.

XYZ Hotel Owner:

Can manage RES1003 only.

Restaurant owners must never be able to:

  • View Other Restaurant Dashboards

  • View Other Restaurant Orders

  • Access Other Restaurant Menus

  • Modify Other Restaurant Branding

  • Access Other Restaurant Payments

  • View Other Restaurant Customers

  • Access Super Admin Dashboard

Page 43 of 99

3.32 FINAL QUALITY REQUIREMENTS / CafeDesk – White-Label Multi-Tenant Restaurant SaaS Architecture / WHITE-LABEL CUSTOMER EXPERIENCE

The customer must see the restaurant's own identity.

For example:

When a customer scans Mayur Cafe's QR:

  • Mayur Cafe Logo

  • Mayur Cafe Name

  • Mayur Cafe Theme

  • Mayur Cafe Menu

  • Mayur Cafe Food Images

  • Mayur Cafe Prices

When a customer scans ABC Restaurant's QR:

  • ABC Restaurant Logo

  • ABC Restaurant Name

  • ABC Restaurant Theme

  • ABC Restaurant Menu

  • ABC Restaurant Food Images

  • ABC Restaurant Prices

Page 44 of 99

3.33 FINAL QUALITY REQUIREMENTS / CafeDesk – White-Label Multi-Tenant Restaurant SaaS Architecture / SAAS SUBSCRIPTION & FEATURE CONTROL

Create a flexible subscription engine.

Super Admin can create plans and assign features.

Example plans:

BASIC:

  • Digital Menu

  • Table QR Generation

  • Customer Ordering

  • Basic Dashboard

PRO:

  • All Basic Features

  • Kitchen Display

  • Live Floor Map

  • Customer Service Requests

  • Advanced Menu Themes

  • Analytics

PREMIUM:

  • All Pro Features

  • Split Bills

Page 45 of 99
  • Staff Management

  • Advanced Reports

  • Premium Branding

  • Advanced Business Analytics

Super Admin must be able to change plan prices, durations, limits, and features without modifying application code.

3.34 FINAL QUALITY REQUIREMENTS / CafeDesk – White-Label Multi-Tenant Restaurant SaaS Architecture / OPTIONAL CUSTOM DOMAIN SUPPORT

www.abcrestaurant.com

www.xyzhotel.com

Each custom domain should connect to the correct restaurant workspace and customer menu.

Include domain verification and ownership validation.

Do not allow one restaurant to claim another restaurant's domain.

Page 46 of 99

3.35 FINAL QUALITY REQUIREMENTS / CafeDesk – White-Label Multi-Tenant Restaurant SaaS Architecture / FINAL TESTING REQUIREMENTS

  1. Separate Kitchen Screens

  2. Separate Payments

  3. Separate Customers

  4. Separate Analytics

  5. Subscription Restrictions

  6. Super Admin Access

  7. Cross-Tenant Access Prevention

  8. Customer QR Scanning

3.36 FINAL QUALITY REQUIREMENTS / CafeDesk – White-Label Multi-Tenant Restaurant SaaS Architecture / FINAL INSTRUCTION

Upgrade and integrate this architecture into the existing project.

Preserve existing working features while correcting structural problems.

3.37 FOUNDATION 01: MULTI-TENANT DATABASE ARCHITECTURE

Build a secure, scalable multi-tenant database.

Page 47 of 99

3.38 FOUNDATION 01: MULTI-TENANT DATABASE ARCHITECTURE / A. Independent Restaurant Identity

Every registered restaurant must receive:

  • Unique Restaurant ID

  • Unique Restaurant Name

  • Unique Restaurant Slug

  • Unique Owner Account

  • Unique Restaurant Workspace

  • Independent Settings

  • Independent Subscription

Example:

Restaurant A:

Mayur Cafe – RES1001

Restaurant B:

ABC Restaurant – RES1002

Restaurant C:

XYZ Hotel – RES1003

3.39 FOUNDATION 01: MULTI-TENANT DATABASE ARCHITECTURE / B. Complete Data Isolation

Every restaurant must have independent:

  • Owner Profile
Page 48 of 99

3.40 FOUNDATION 01: MULTI-TENANT DATABASE ARCHITECTURE / D. Independent Restaurant URLs

Create dynamic restaurant URLs.

Examples:

cafedesk.com/menu/mayur-cafe

cafedesk.com/menu/abc-restaurant

cafedesk.com/menu/xyz-hotel

Each restaurant must have its own unique table QR URLs.

The system must automatically identify the correct restaurant and table.

3.41 FOUNDATION 02: WHITE-LABEL BRANDING & THEME ENGINE

Build a powerful White-Label Customization Engine.

Every restaurant owner must be able to create a unique digital identity without needing technical knowledge.

3.42 FOUNDATION 02: WHITE-LABEL BRANDING & THEME ENGINE / A. Restaurant Branding

Allow owners to customize:

  1. Restaurant Name

  2. Restaurant Logo

  3. Restaurant Cover Image

  4. Brand Identity

Page 49 of 99

3.43 FOUNDATION 02: WHITE-LABEL BRANDING & THEME ENGINE / C. Live Customization

Include:

  • Live Preview

  • Save Changes

  • Publish Theme

  • Reset Theme

When an owner changes the theme, the existing customer QR menu must automatically display the updated design.

No QR reprinting should be necessary.

Page 50 of 99

3.44 FOUNDATION 02: WHITE-LABEL BRANDING & THEME ENGINE / D. Complete White-Label Experience

ABC Restaurant:

  • ABC Restaurant Logo

  • ABC Restaurant Theme

  • ABC Restaurant Menu

  • ABC Restaurant Branding

XYZ Hotel:

  • XYZ Hotel Logo

  • XYZ Hotel Theme

  • XYZ Hotel Menu

  • XYZ Hotel Branding

Each restaurant must have a completely independent customer-facing experience.

Do not hardcode any restaurant name, logo, colors, or menu.

Load all branding dynamically from the restaurant database.

3.45 FOUNDATION 03: CENTRALIZED SUPER ADMIN CONTROL CENTER

Build a separate, secure Super Admin Dashboard.

Only the authorized platform owner, Mayur Gorule, can access the Super Admin area.

Page 51 of 99

3.46 FOUNDATION 03: CENTRALIZED SUPER ADMIN CONTROL CENTER / A. Super Admin Overview

Display:

  • Total Registered Restaurants

  • Active Restaurants

  • Pending Approvals

  • Suspended Restaurants

  • Expired Subscriptions

  • Total Owners

  • Monthly Revenue

  • Yearly Revenue

  • Total Subscription Revenue

  • Recent Registrations

All statistics must come from actual database records.

Page 52 of 99

3.47 FOUNDATION 03: CENTRALIZED SUPER ADMIN CONTROL CENTER / B. Restaurant Management

Super Admin must be able to:

  • View All Restaurants

  • Search Restaurants

  • Filter Restaurants

  • View Restaurant Details

  • Approve Registrations

  • Activate Accounts

  • Suspend Accounts

  • Reactivate Accounts

  • Manage Restaurant Status

  • View Subscription Information

Page 53 of 99

3.48 FOUNDATION 03: CENTRALIZED SUPER ADMIN CONTROL CENTER / C. Owner Management

Manage all restaurant owners.

Features:

  • View Owner Profiles

  • View Registered Businesses

  • View Account Status

  • Approve Owner Accounts

  • Activate / Suspend Owners

  • View Registration Date

Page 54 of 99

3.49 FOUNDATION 03: CENTRALIZED SUPER ADMIN CONTROL CENTER / D. Subscription Management

Create a flexible subscription management system.

Super Admin can:

  • Create Plans

  • Edit Plans

  • Delete Plans

  • Set Monthly Pricing

  • Set Yearly Pricing

  • Configure Trial Periods

Super Admin can:

  • Assign Plans

  • Extend Subscriptions

  • Activate Subscriptions

  • Suspend Subscriptions

  • View Expiry Dates

Page 55 of 99

3.50 FOUNDATION 03: CENTRALIZED SUPER ADMIN CONTROL CENTER / E. Payment Management

Create a Payment Request Management section.

Features:

  • View Payment Requests

  • View Payment Screenshots

  • Approve Payments

  • Reject Payments

  • View Payment History

  • Track Subscription Payments

  • View Total Collected Revenue

Page 56 of 99

3.51 FOUNDATION 03: CENTRALIZED SUPER ADMIN CONTROL CENTER / F. Super Admin Security

Implement:

  • Mandatory Two-Factor Authentication

  • Server-Side Admin Authorization

  • Protected Admin Routes

  • Secure Authentication Sessions

  • Login Activity Logs

  • Admin Action Audit Logs

Restaurant owners must never access Super Admin pages or APIs.

Hiding admin buttons in the frontend is not sufficient.

Page 57 of 99

3.52 FOUNDATION 04: OWNER DASHBOARD INTEGRATION

Every restaurant owner must receive a separate dashboard.

Sidebar:

  1. Overview

  2. Live Orders

  3. Menu Management

  4. Table Management

  5. QR Generator

  6. Kitchen Display

  7. Live Floor Map

  8. Customer Requests

  9. Payment Management

  10. Staff Management

  11. Customer Management

  12. Analytics

  13. Branding & Themes

  14. Subscription

  15. Settings

All features must operate within the authenticated owner's Restaurant ID.

Page 58 of 99

3.53 FOUNDATION 05: QR & CUSTOMER ORDERING INTEGRATION

Every restaurant must be able to generate unique QR codes for its tables.

Each QR code must securely identify its restaurant and table.

Customer workflow:

  1. Customer scans the table QR.

  2. Correct restaurant menu opens.

  3. Restaurant logo and theme appear.

  4. Customer selects food items.

  5. Customer places the order.

  6. Order reaches the correct kitchen.

  7. Owner dashboard updates in real time.

  8. Table status updates automatically.

Customers must not need to register or log in.

3.54 FOUNDATION 06: SCALABILITY & PERFORMANCE

Page 59 of 99

3.55 FOUNDATION 07: MANDATORY SECURITY TESTING

Create three independent test restaurants:

  1. Mayur Cafe – RES1001

  2. ABC Restaurant – RES1002

  3. XYZ Hotel – RES1003

Test the following:

MULTI-TENANT TESTS:

  • Separate Owner Login

  • Separate Dashboards

  • Separate Menus

  • Separate Orders

  • Separate QR Codes

  • Separate Customer Data

  • Cross-Restaurant Access Prevention

Test the following:

WHITE-LABEL TESTS:

  • Independent Logo Upload

  • Independent Theme Selection

  • Independent Brand Colors

Page 60 of 99
  • Independent Menu Customization

  • Live QR Menu Updates

SUPER ADMIN TESTS:

  • Super Admin Login

SUPER ADMIN TESTS:

  • Mandatory 2FA

SUPER ADMIN TESTS:

  • View All Restaurants

SUPER ADMIN TESTS:

  • Approve Owners

SUPER ADMIN TESTS:

  • Activate / Suspend Accounts

SUPER ADMIN TESTS:

  • Manage Subscriptions

SUPER ADMIN TESTS:

  • View Payment Requests

SUPER ADMIN TESTS:

  • Access Control Verification
Page 61 of 99

3.56 FINAL IMPLEMENTATION INSTRUCTIONS

  1. First inspect the existing CafeDesk application and database.

  2. Identify existing features and preserve everything that works.

  3. Upgrade the database architecture for multi-tenancy.

  4. Implement strict tenant-level security.

  5. Build the White-Label Branding Engine.

  6. Build the centralized Super Admin Control Center.

  7. Connect all existing restaurant modules to the new architecture.

  8. Test with three independent restaurant accounts.

3.57 FINAL IMPLEMENTATION INSTRUCTIONS / FINAL VISION

Centralized Super Admin control.

Page 62 of 99

4. User Personas

CafeDesk serves active human roles across independent restaurant workspaces. Each restaurant owner manages only their own restaurant; only the platform owner, Mayur Gorule, reaches the Super Admin Control Center.

RoleResponsibilitiesAccess
Restaurant OwnerRegisters the restaurant (owner full name, restaurant name, business type, email); customizes white-label branding (name, logo, cover image, brand identity, brand colors, font family, button styles, menu card design); builds the menu (items, images, descriptions, prices, categories, veg/non-veg labels, bestseller and availability flags, special offers); manages tables (numbers, capacity); configures payment options (UPI ID, Google Pay/PhonePe/custom UPI QR uploads); adds staff with roles; monitors dashboard (preparing/ready/completed orders, pending payments, total tips, revenue and orders graphs, popular dishes, recent orders, live activity, table occupancy)Own restaurant workspace only; sensitive restaurant settings are owner-only
ManagerManages operationsOwn restaurant, role-based
WaiterViews assigned tables and service requests; marks requests Received, In Progress, CompletedOwn restaurant, role-based
Kitchen StaffViews kitchen orders on the KDS and updates preparation statusOwn restaurant, role-based
CashierViews bills, manages payments, confirms cash paymentsOwn restaurant, role-based
Super Admin (platform owner)Views, searches and filters all restaurants; manages all restaurant owners; creates, edits and deletes plans with monthly and yearly pricing and trial periods; assigns, extends, activates and suspends subscriptions and views expiry dates; reviews payment requests and screenshots, approves or rejects payments, views payment history, tracks subscription payments and total collected revenue; inspects business-level information without accidentally modifying restaurant dataPrivate Super Admin Control Center only

Customers are not account holders: they scan a table QR, order, view their bill and raise service requests without registering, logging in, entering a password or downloading an app.

Owner journey: register → brand the digital experience → build the menu → add tables and generate QR codes → configure payments → add staff → run service from the live dashboard.

Customer journey: scan the table QR → the correct restaurant menu opens with that restaurant's logo and theme → select food items → place the order → the order reaches the correct kitchen, the owner dashboard updates in real time and table status updates automatically.

Page 63 of 99

Service journey: the QR identifies the restaurant and table and loads that restaurant's branding and live menu; the kitchen updates status; the customer views the bill breakdown, taxes and discounts and pays by a supported option; staff verify manual UPI payments or mark cash received; service requests appear live on the owner/staff dashboard with table number, request type, time and status.

Platform journey: the Super Admin approves owners, activates or suspends accounts, and governs plans, subscriptions and payments centrally.

5. Core User Flows

5.1 Restaurant Onboarding and Tenant Creation

Actor: Restaurant owner. Trigger: Owner decides to join CafeDesk.

  1. Owner opens registration and submits Owner Full Name, Restaurant Name, Business Type (Cafe, Restaurant, Hotel, Bakery, Food Court, Cloud Kitchen, Other), Email Address, Mobile Number, Password, Restaurant Address, City, Country.
  2. System creates the tenant and issues a unique Restaurant ID.
  3. Owner lands in the Owner Dashboard (Overview) and proceeds to configure menu, tables, branding, payments, and staff.

Result: A branded, isolated restaurant workspace keyed by its Restaurant ID. Continuation: Owner may configure any dashboard area in any order; no mandatory sequence is imposed.

Page 64 of 99

5.2 Menu and Branding Publication

Actor: Owner. Trigger: Menu or theme needs to change.

  1. Owner opens Menu Management and adds, edits, or deletes food items with images, descriptions, prices, categories (e.g., Starters, Main Course, Pizza), Veg/Non-Veg labels, Bestseller flags, availability, special offers, and preparation time.
  2. Owner opens Restaurant Customization, adjusts typography, menu cards, welcome screen, and ordering page, reviews the Live Theme Preview, then Save Changes and Publish Theme (or Reset Theme).
  3. Changes propagate automatically to the existing customer QR menu; no QR reprinting is required.

Result: Published menu and theme visible to customers on the same QR links.

5.3 Table Setup and QR Generation

Actor: Owner. Trigger: New or changed seating.

  1. Owner adds, edits, or deletes tables, setting table numbers and capacity, and views table status.
  2. Owner generates an individual QR per table. Each QR encodes the unique Restaurant ID, unique Table ID, and secure customer menu URL (e.g., cafedesk.com/menu/RES1001/TABLE05).
  3. Owner uses QR options: Generate QR, Download PNG, Download PDF, Print QR, Copy QR Link, Test Scan, Regenerate QR, Deactivate QR.

Result: Every table has its own active QR. Failure/recovery: A deactivated or regenerated QR is replaced by reprinting or re-sharing the new code; Test Scan verifies the link before printing.

Page 65 of 99

5.4 Customer QR Ordering

Actor: Customer (no account, login, password, or app download). Trigger: Customer sits at a table and scans its QR.

  1. Branded digital menu opens automatically with that table already selected (e.g., Table 05 of Restaurant 1001).
  2. Customer browses images, names, prices, descriptions, categories, and special offers.
  3. Customer selects items, adjusts quantity, customizes food, adds special instructions, and adds to cart.
  4. Customer reviews the cart and enters Customer Name and Mobile Number (optional or configurable).
  5. Customer clicks PLACE ORDER and sees an order confirmation.

Result: Order appears automatically on the Owner Dashboard, Kitchen Display Screen, and Live Orders Dashboard, tied to the scanned table. Continuation: Customer may raise service requests or view the bill.

5.5 Kitchen Preparation and Status Propagation

Actor: Kitchen staff. Trigger: New order on the Kitchen Display System.

  1. Kitchen staff view kitchen orders and update preparation status through the workflow.
  2. On marking an order READY, the Owner Dashboard updates, the Live Floor Map updates, and the customer receives an order status update.

Result: Synchronized order state across kitchen, owner, floor, and customer views.

Page 66 of 99

5.6 Live Floor Monitoring and Table Service

Actors: Waiter, owner, or manager. Trigger: Ongoing service; table status changes.

  1. Floor Map shows all tables visually with color states (e.g., Yellow: Payment Pending) and updates automatically.
  2. Clicking a table reveals Table Number, Current Order, Ordered Items, Total Amount, Payment Status, Customer Requests, and Order Timeline.
  3. When a customer taps a Service Request button (Water, Waiter, Extra Plate, Tissue, Assistance, Bill), a live notification shows Table Number, Request Type, Request Time, and Request Status on the owner/staff dashboard; the table is highlighted on the floor map.
  4. Waiters view their assigned tables and service requests, update table service status, and mark requests Received, In Progress, then Completed.

Result: Requests are tracked to completion and assistance-needing tables are visually flagged.

Page 67 of 99

5.7 Billing, Tipping, and Split Payment

Actors: Customer, cashier, owner/staff verification. Trigger: Customer requests the bill or opens billing.

  1. Customer views Current Bill with food breakdown, taxes, and discounts, and may add a tip.
  2. Customer chooses Pay Full Amount or Split Bill via Split Equally, Split by Item, or Custom Amount Split.
  3. Multiple customers contribute toward the same table bill; the remaining payable balance updates automatically.
  4. Customer selects a configured payment option (Google Pay, PhonePe, UPI ID, UPI QR Code). For manual UPI QR payments, the customer provides payment confirmation and owner/staff verify it.
  5. Cashier views bills, manages payments, and confirms cash payments; staff mark cash payments as received.

Result: Bill settled with no duplicate payment collection. Failure/recovery: Unverified manual payments remain pending until staff confirm and are never marked successful unverified; the remaining balance stays visible until fully covered.

5.8 Payment Configuration

Actor: Owner. Trigger: Enabling or changing accepted payments.

  1. Owner opens Payment Management and selects supported options.
  2. Owner enters UPI ID and uploads Google Pay QR, PhonePe QR, and/or Custom UPI QR.

Result: Customers see and can choose only the owner's configured payment options at checkout.

Page 68 of 99

5.9 Subscription and Platform Administration

Actor: Super Admin (platform owner only). Trigger: New owner approval, subscription change, or payment request.

  1. Super Admin reviews new owner registrations and approves them, then activates or suspends accounts.
  2. Super Admin creates and modifies monthly plans, yearly plans, free trials, premium features, subscription expiry, and account activation.
  3. Super Admin reviews payment requests and approves or rejects them, manages pricing plans, monitors platform revenue and analytics, and manages platform settings.

Result: Tenant lifecycle and subscriptions centrally controlled. Continuation: Restaurant owners operate only within their own workspace (e.g., Mayur Cafe manages RES1001 only).

5.10 Real-Time Consistency Across Devices

Trigger: Any order, status, request, or payment event.

  1. New customer orders, kitchen order updates, order ready notifications, table status, service requests, payment confirmation, split bill updates, and owner dashboard analytics update in real time across multiple simultaneous devices.
  2. The system prevents duplicate orders and duplicate payment processing.

Result: All connected roles see a single consistent state; every QR opens the correct restaurant and table.

5.11 SMART TABLE MANAGEMENT & QR GENERATOR

When a customer scans Table 05 QR:

Page 69 of 99

5.12 CUSTOMER QR ORDERING EXPERIENCE / Customer Journey

STEP 1:

Customer sits at a restaurant table.

STEP 2:

Scans the QR code placed on the table.

STEP 3:

The restaurant's branded digital menu opens automatically.

Page 70 of 99

6. Visuals Colors and Theme

[Design proposal; unspecified choices are defaults.]

Muse: Peter Saville. Headline: “One platform. Every restaurant. Its own identity.”

The system reads as quiet luxury and calm operational control, not startup noise. Light-mode tokens by role: background warm cream #F4EFE6 (about 60% of each screen), surface #FFFDF9, text #221F1C, primary coffee brown #3A2A1E for type and dark panels, accent gold #B08A3E, muted #8C8378. Gold marks one element per section or a thin 1px divider rule. No blue or indigo accents, gradient blobs, saturated colour fields, or glassmorphism panels.

Headings: Cormorant Garamond Light 300, large with tight tracking. Body and small-caps labels: Jost; labels 12px at 0.18em tracking. Modular scale 96/64/40/28/18/16px; mobile headline starts at 40px and scales with clamp() so headlines, wordmarks, labels, numbers, card text and controls stay whole inside the viewport and their container at 375px, 768px and 1280px.

Shape: sharp corners on type blocks and image frames; soft 16px radius only on dashboard cards and buttons. Layout: one centred artefact per section on a wide cream field, asymmetric metadata block low-left, hairline grid rules visible at 1280px, stacked at 375px. Imagery: warm-light macro food and table photography, one coded colour plate per restaurant example, small scientific-style diagrams for the QR and kitchen flow.

Page 71 of 99

The public entry hero: full-width cream field, 96px coffee-brown Cormorant headline across the top, a single gold rule beneath it, one centred white table-QR card with a gold code frame on a charcoal plinth, and the CTA low-left as a small-caps label — no rounded pill buttons in the hero.

Restaurant branding is white-label and dynamic: name, logo, cover image, primary/secondary/background colours, font family, button styles, menu card design, header, footer, food-image layout, welcome screen, customer ordering page, contact information and social links all load from the restaurant database per tenant. The theme library offers at least 8 professionally designed themes — Luxury Black & Gold, Premium Coffee Brown, Modern Minimal White, Elegant Beige, Royal Dark, Italian Restaurant, Modern Glassmorphism, Premium Food Experience — each shown with one coded colour swatch beside its name. No restaurant name, logo, colour or menu is hardcoded; CafeDesk platform branding must not interfere with the restaurant's own customer-facing identity.

Defaults (unspecified by source): the exact hex values, font families, type scale and radii above are the creative direction's tokens; the source specifies the palette names (premium coffee brown, warm cream, beige, white, deep charcoal, subtle gold) and the theme list, not their hex codes.

Page 72 of 99

6.1 PREMIUM WEBSITE DESIGN / Design Language

Use:

  • Premium Coffee Brown

  • Warm Cream

  • Beige

  • White

  • Deep Charcoal

  • Subtle Gold Accents

  1. Professional Footer

Hero headline:

"Your Restaurant. Your Brand. One Smart System."

Subheading:

"Transform your restaurant operations with smart QR ordering, live kitchen management, digital menus, seamless payments, and complete business control."

CTA Buttons:

  • Get Started

  • Explore Demo

Page 73 of 99

6.2 SMART DIGITAL MENU BUILDER / Advanced Customization

Allow owners to customize:

  • Menu Layout

  • Menu Background

  • Card Design

  • Font Style

  • Primary Colors

  • Secondary Colors

  • Button Styles

  • Category Layout

  • Food Image Shape

Provide multiple premium menu templates.

Page 74 of 99

6.3 RESTAURANT BRANDING & THEME CUSTOMIZATION

THIS IS ONE OF THE MOST IMPORTANT FEATURES.

Every restaurant owner must be able to create a unique branded digital experience.

Create a dedicated section:

"MY RESTAURANT BRANDING"

Customization options:

  1. Upload Restaurant Logo

  2. Upload Cover Photo

  3. Change Restaurant Name

  4. Change Brand Colors

  5. Change Menu Background

  6. Select Premium Themes

  7. Customize Buttons

Provide at least 8 professionally designed themes.

Theme examples:

  • Luxury Black & Gold

  • Premium Coffee Brown

  • Minimal White

  • Modern Dark

Page 75 of 99
  • Elegant Beige

  • Italian Restaurant

  • Modern Glass

  • Royal Luxury

6.4 CUSTOMER QR ORDERING EXPERIENCE

Create a beautiful mobile-first customer interface.

6.5 FINAL QUALITY REQUIREMENTS / CafeDesk – White-Label Multi-Tenant Restaurant SaaS Architecture / WHITE-LABEL BRANDING SYSTEM

Provide professionally designed themes:

  1. Luxury Black & Gold

  2. Premium Coffee Brown

  3. Modern Minimal White

  4. Elegant Beige

  5. Royal Dark

  6. Italian Restaurant

  7. Modern Glassmorphism

  8. Premium Food Experience

Include:

Page 76 of 99

6.6 FOUNDATION 02: WHITE-LABEL BRANDING & THEME ENGINE / A. Restaurant Branding

  1. Primary Color

  2. Secondary Color

  3. Background Color

  4. Typography

  5. Button Styles

  6. Menu Card Design

  7. Header Design

  8. Footer Design

  9. Food Image Layout

  10. Customer Menu Appearance

Page 77 of 99

6.7 FOUNDATION 02: WHITE-LABEL BRANDING & THEME ENGINE / B. Premium Theme Library

Provide at least 8 professional themes:

  • Luxury Black & Gold

  • Premium Coffee Brown

  • Elegant Beige

  • Modern Minimal White

  • Royal Dark

  • Italian Restaurant

  • Glassmorphism

  • Premium Food Experience

6.8 FOUNDATION 02: WHITE-LABEL BRANDING & THEME ENGINE / D. Complete White-Label Experience

Example:

Mayur Cafe:

  • Mayur Cafe Logo

  • Mayur Cafe Theme

  • Mayur Cafe Menu

  • Mayur Cafe Branding

Page 78 of 99

6.9 FINAL IMPLEMENTATION INSTRUCTIONS / FINAL VISION

Independent branding.

Page 79 of 99

7. Signature Design Concept

[Design proposal; unspecified choices are defaults.]

CafeDesk is a premium white-label, multi-tenant restaurant SaaS: every restaurant runs on one calm system for digital menus, food categories and images, table QR codes, live kitchen and floor management, ordering, payments and business control, while presenting a completely independent customer-facing identity. The design treats each restaurant theme as a coded identity rather than a generic template.

The signature composition is an editorial operating artefact: cream space, one centred QR/menu object, charcoal dashboard panels with gold numerals for live stats, soft shadows, and thin gold rules carrying small-caps section labels. The interface should read as a premium international SaaS product, drawing on Stripe, Linear, Shopify, Square POS and Toast POS.

Owners shape their identity through the dedicated My Restaurant Branding section: upload logo and cover photo, change restaurant name, brand colours, menu background, select premium themes, customize buttons, typography, menu cards, welcome screen and customer ordering page, with a Live Theme Preview. The Smart Digital Menu Builder adds menu layout, card design, font style, primary and secondary colours, button styles, category layout and food image shape, with multiple premium templates and a Live Preview button. Changes flow through Live Preview → Save Changes → Publish Theme (or Reset Theme) and instantly reflect on that restaurant's customer-facing QR menu.

White-label examples: scanning Mayur Cafe's QR shows Mayur Cafe's logo, name, theme, menu, food images and prices; ABC Restaurant's QR shows ABC Restaurant's identity; XYZ Hotel likewise. Each restaurant has a completely independent customer-facing experience, and the customer ordering experience stays mobile-first and extremely simple.

Page 80 of 99

The public entry copy: headline “One platform. Every restaurant. Its own identity.”; subline “CafeDesk gives each restaurant its own brand, menu, table QR codes and live kitchen, on one warm, quiet system.”; CTA Get Started (with Explore Demo available as the secondary hero action).

7.1 PREMIUM WEBSITE DESIGN

Create a visually stunning, modern SaaS website.

Design inspiration:

  • Stripe

  • Linear

  • Shopify

  • Square POS

  • Toast POS

7.2 PREMIUM WEBSITE DESIGN / Design Language

The interface should look like a premium international SaaS product.

8. Interaction Model & Motion Direction

[Design proposal; unspecified choices are defaults.]

Interaction Model: Static (direction) Motion Tempo: still Hero Dimensionality: flat

Page 81 of 99

8.1 Landing Hero Motion Brief

Focal subject: one restaurant-branded table QR card — white with a gold code frame — centred on a charcoal plinth over the warm-cream field.

Input → transformation → outcome thesis: the visitor hovers the QR card; it rotates slowly to reveal the branded menu on its back; the outcome is a felt understanding that each restaurant's QR carries its own brand, menu and identity. The Get Started CTA leads into the accepted onboarding/product-entry flow. No new behaviour or destination is introduced.

Motion vocabulary: slow 600ms fades on scroll; one colour-code swatch cycles on hover; the hero QR card rotates slowly on hover. Nothing bounces; no springs, no identical hover-lift card grids.

Composed first frame: the 96px Cormorant headline spans the cream field without overflow, a single gold rule runs beneath it, the QR artefact sits centred below on its plinth, and the small-caps CTA rests low-left.

Reduced-motion state: with prefers-reduced-motion, the hero stays static — no rotation, no colour cycling — with the QR card, headline, CTA and all controls fully readable and contained; content wraps or scrolls horizontally where needed so every item can be brought fully into view.

No 3D scene is required: the direction specifies flat hero dimensionality and no WebGL request was made.

Page 82 of 99

8.2 PREMIUM WEBSITE DESIGN / Design Language

Visual effects:

  • Modern Glassmorphism

  • Smooth Animations

  • Premium Dashboard Cards

  • Soft Shadows

  • Rounded Corners

  • Elegant Gradients

  • Interactive Hover Effects

  • Beautiful Typography

9. Non-Functional Requirements

9.1 PROJECT NAME: CafeDesk / PROJECT OVERVIEW

Each restaurant must have completely isolated data.

Page 83 of 99

9.2 PREMIUM WEBSITE DESIGN / Design Language

Make everything responsive for:

  • Desktop

  • Laptop

  • Tablet

  • Android

  • iPhone

9.3 MULTI-TENANT RESTAURANT REGISTRATION

Never allow one restaurant owner to access another restaurant's information.

Use secure authentication and server-side authorization.

9.4 SMART TABLE MANAGEMENT & QR GENERATOR

Never allow one restaurant's QR code to open another restaurant's menu.

Page 84 of 99

9.5 SUPER ADMIN DASHBOARD

Security requirements:

  • Mandatory Super Admin 2FA

  • Server-side authorization

  • Protected admin routes

  • Secure session management

  • Role-based permissions

Restaurant owners must NEVER access Super Admin pages or APIs.

9.6 SUBSCRIPTION MANAGEMENT

Plan restrictions must be enforced server-side.

9.7 DATABASE & BACKEND ARCHITECTURE

Never trust frontend-only authorization.

9.8 REAL-TIME SYSTEM REQUIREMENTS

Page 85 of 99

9.9 FINAL QUALITY REQUIREMENTS

Every restaurant must have independent branding and customization.

Every owner must manage only their own restaurant.

The customer experience must be extremely simple and mobile-friendly.

The owner experience must be professional and easy to operate.

The kitchen experience must be fast and distraction-free.

The Super Admin experience must provide complete platform control.

Before completing the project, test:

  1. Restaurant Registration

  2. Owner Login

  3. Restaurant Branding

  4. Menu Creation

  5. Menu Customization

  6. QR Code Generation

  7. QR Scanning

  8. Customer Ordering

  9. Kitchen Order Reception

  10. Live Floor Map

  11. Customer Service Requests

Page 86 of 99
  1. Split Bills

  2. Payment Management

  3. Mobile Responsiveness

9.10 FINAL QUALITY REQUIREMENTS / CafeDesk – White-Label Multi-Tenant Restaurant SaaS Architecture / CENTRALIZED SUPER ADMIN CONTROL

Implement strict role-based permissions.

9.11 FINAL QUALITY REQUIREMENTS / CafeDesk – White-Label Multi-Tenant Restaurant SaaS Architecture / RESTAURANT OWNER ACCESS CONTROL

Enforce access restrictions on the backend and database level.

Do not depend on frontend route hiding alone.

9.12 FINAL QUALITY REQUIREMENTS / CafeDesk – White-Label Multi-Tenant Restaurant SaaS Architecture / WHITE-LABEL CUSTOMER EXPERIENCE

The customer ordering experience must remain mobile-first and simple.

9.13 FINAL QUALITY REQUIREMENTS / CafeDesk – White-Label Multi-Tenant Restaurant SaaS Architecture / SAAS SUBSCRIPTION & FEATURE CONTROL

Enforce subscription restrictions server-side.

Page 87 of 99

9.14 FINAL QUALITY REQUIREMENTS / CafeDesk – White-Label Multi-Tenant Restaurant SaaS Architecture / DATABASE ARCHITECTURE

Create a secure multi-tenant database architecture.

  • AuditLogs

Every restaurant-specific record must contain a valid Restaurant ID.

Implement:

  • Database-Level Tenant Isolation

  • Row-Level Security

  • Role-Based Access Control

  • Server-Side Authorization

  • Secure Authentication

  • Input Validation

  • Secure File Uploads

  • Audit Logs

  • Database Transactions

Never trust a Restaurant ID supplied by the frontend without validating the authenticated user's access.

Page 88 of 99

9.15 FINAL QUALITY REQUIREMENTS / CafeDesk – White-Label Multi-Tenant Restaurant SaaS Architecture / FINAL TESTING REQUIREMENTS

Before completing the upgrade, test with at least three independent demo tenants:

Tenant A: Mayur Cafe

Tenant B: ABC Restaurant

Tenant C: XYZ Hotel

Test the following:

  1. Independent Registration

  2. Independent Login

  3. Separate Owner Dashboards

  4. Separate Logos

  5. Separate Themes

  6. Separate Menus

  7. Separate QR Codes

  8. Separate Table Management

  9. Separate Customer Orders

  10. Mobile Responsiveness

Page 89 of 99

9.16 FOUNDATION 01: MULTI-TENANT DATABASE ARCHITECTURE / B. Complete Data Isolation

  • Menu Categories

  • Food Items

  • Food Images

  • Food Prices

  • Table Records

  • QR Codes

  • Customer Orders

  • Kitchen Orders

  • Service Requests

  • Payments

  • Tips

  • Bills

  • Staff Members

  • Customer Records

  • Analytics

  • Reports

  • Restaurant Branding

  • Subscription Details

Page 90 of 99

Every tenant-specific database record must contain a valid Restaurant ID.

9.17 FOUNDATION 01: MULTI-TENANT DATABASE ARCHITECTURE / C. Security Rules

Implement:

  • Database-Level Row-Level Security

  • Server-Side Authorization

  • Role-Based Access Control

  • Tenant-Level Data Isolation

  • Secure Authentication

  • Protected API Endpoints

  • Input Validation

  • Audit Logs

  • Secure Session Management

CRITICAL:

Never trust Restaurant IDs supplied by frontend requests.

Always verify the authenticated user's restaurant membership and permissions on the backend.

Restaurant A must never access Restaurant B's data, even by manually changing URLs, API parameters, or database requests.

9.18 FOUNDATION 03: CENTRALIZED SUPER ADMIN CONTROL CENTER / D. Subscription Management

Subscription restrictions must be enforced on the backend.

Page 91 of 99

9.19 FOUNDATION 06: SCALABILITY & PERFORMANCE

Build the architecture to support hundreds or thousands of restaurants.

Ensure that activity in one restaurant does not negatively affect another restaurant.

Implement:

  • Efficient Database Indexing

  • Optimized Database Queries

  • Pagination

Implement:

  • Image Optimization

  • Secure File Storage

Implement:

  • Real-Time Updates

  • Background Processing Where Required

Implement:

  • API Rate Limiting

  • Error Monitoring

Implement:

  • Database Backups

  • Reliable Session Handling

Page 92 of 99

Keep the system modular so future features can be added without rebuilding the entire application.

9.20 FINAL IMPLEMENTATION INSTRUCTIONS

  1. Fix all security and functionality issues.

  2. Verify the entire application on desktop and mobile.

10. Tech Stack

10.1 LIVE KITCHEN DISPLAY SYSTEM (KDS)

Use real-time database subscriptions or WebSockets.

Page 93 of 99

10.2 DATABASE & BACKEND ARCHITECTURE

Build a fully functional backend.

Suggested database entities:

  1. Users

  2. Restaurants

  3. RestaurantSettings

  4. RestaurantThemes

  5. MenuCategories

  6. MenuItems

  7. Tables

  8. QR Codes

  9. Orders

  10. OrderItems

  11. KitchenUpdates

  12. ServiceRequests

  13. Bills

  14. BillSplits

  15. Payments

  16. Tips

Page 94 of 99
  1. Staff

  2. Customers

  3. Subscriptions

  4. PaymentRequests

  5. Notifications

  6. AuditLogs

10.3 FINAL QUALITY REQUIREMENTS / CafeDesk – White-Label Multi-Tenant Restaurant SaaS Architecture / DATABASE ARCHITECTURE

Core database tables:

  • Users

  • Restaurants

  • RestaurantMemberships

  • RestaurantSettings

  • RestaurantBranding

  • RestaurantThemes

11. Assumptions and Constraints

Page 95 of 99

11.1 PROJECT NAME: CafeDesk / PROJECT OVERVIEW

Superseded by explicit chat:

Build a world-class, premium, fully responsive, multi-tenant Restaurant QR Ordering and Management SaaS Platform called "CafeDesk".

This must be a complete restaurant operating system, not just a QR menu website.

The platform should allow any Cafe, Restaurant, Hotel, Food Court, or Dining Business to register, create its own branded restaurant environment, customize its design, generate table-specific QR codes, accept customer orders, manage kitchen operations, monitor tables, process payments, and track business performance.

The entire system must work in real time.

IMPORTANT:

This platform is designed for multiple independent restaurant businesses. It must never be restricted to one particular cafe or restaurant.

11.2 RESTAURANT BRANDING & THEME CUSTOMIZATION

IMPORTANT:

Restaurant A must only see and manage Restaurant A branding.

Restaurant B must only see and manage Restaurant B branding.

Never use a fixed restaurant name, logo, or theme for all businesses.

11.3 LIVE KITCHEN DISPLAY SYSTEM (KDS)

Do not rely on static demo data.

Page 96 of 99

11.4 STAFF MANAGEMENT

Only the owner can access sensitive restaurant settings.

11.5 DATABASE & BACKEND ARCHITECTURE

Every restaurant-related database record must include a Restaurant ID.

11.6 FINAL QUALITY REQUIREMENTS

IMPORTANT: Do not create a static UI prototype.

11.7 FINAL QUALITY REQUIREMENTS / CafeDesk – White-Label Multi-Tenant Restaurant SaaS Architecture / WHITE-LABEL CUSTOMER EXPERIENCE

The CafeDesk platform branding should not interfere with the restaurant's own customer-facing brand identity.

11.8 FINAL QUALITY REQUIREMENTS / CafeDesk – White-Label Multi-Tenant Restaurant SaaS Architecture / OPTIONAL CUSTOM DOMAIN SUPPORT

Prepare the architecture for future custom domain support.

Example:

www.mayurcafe.com

11.9 FINAL QUALITY REQUIREMENTS / CafeDesk – White-Label Multi-Tenant Restaurant SaaS Architecture / FINAL TESTING REQUIREMENTS

Use demo tenants only for testing. Do not show fake businesses or fake analytics in the live production environment.

Page 97 of 99

11.10 FINAL QUALITY REQUIREMENTS / CafeDesk – White-Label Multi-Tenant Restaurant SaaS Architecture / FINAL INSTRUCTION

Do not rebuild the existing CafeDesk application unnecessarily.

11.11 FOUNDATION 03: CENTRALIZED SUPER ADMIN CONTROL CENTER / E. Payment Management

Never activate a paid subscription based only on an unverified payment claim.

11.12 FOUNDATION 07: MANDATORY SECURITY TESTING

Do not use fake production data or static dashboard statistics.

11.13 FINAL IMPLEMENTATION INSTRUCTIONS

Do not create only frontend designs or dummy dashboards.

Every button, form, setting, and management feature must be connected to real backend functionality.

Do not claim a feature is complete unless it has been implemented and tested.

If a required integration or backend capability is unavailable, clearly identify it instead of simulating successful functionality.

12. Glossary

Page 98 of 99

12.1 SMART DIGITAL MENU BUILDER

  • Burgers

  • Sandwiches

  • Chinese

  • Beverages

  • Desserts

Page 99 of 99
Live
landing design preview
Cashier chooses staff sign-in
Credentials valid for own restaurant
Bill requested for a table
Customer chooses equal split
Customer chooses item split
Customer chooses custom amount
Contributions recorded
Contributions recorded
Contributions recorded
Cash paid at counter or table
Manual UPI confirmation provided
Cash received confirmed
Payment verified by staff
Balance remains until fully covered
landing: Open staff sign-in
Login: Sign in as cashier
Live Orders Dashboard: Review live orders
Live Orders: Open table bill
Split Bills: Split bill equally
Split Bills: Split bill by item
Split Bills: Enter custom split amount
Split Bills: 1. Track remaining balance
Split Bills: Confirm cash payment received
Split Bills: Verify manual UPI payment
Live Orders: Mark bill settled
Live
landing design preview
Cashier chooses staff sign-in
Credentials valid for own restaurant
Bill requested for a table
Customer chooses equal split
Customer chooses item split
Customer chooses custom amount
Contributions recorded
Contributions recorded
Contributions recorded
Cash paid at counter or table
Manual UPI confirmation provided
Cash received confirmed
Payment verified by staff
Balance remains until fully covered
landing: Open staff sign-in
Login: Sign in as cashier
Live Orders Dashboard: Review live orders
Live Orders: Open table bill
Split Bills: Split bill equally
Split Bills: Split bill by item
Split Bills: Enter custom split amount
Split Bills: 1. Track remaining balance
Split Bills: Confirm cash payment received
Split Bills: Verify manual UPI payment
Live Orders: Mark bill settled