Dwaar System connects table service, kitchen operations, billing, delivery, staff responsibilities, and restaurant oversight inside one shared operational model. Instead of forcing each department to work through disconnected tools and conflicting order states, every role works from the same order lifecycle and source of truth.
SELECTED PRODUCT AREAS
The main parts of the system.
Tables & QR
Kitchen & service
Billing & settlement
Online & delivery
PEOPLE & ACCESS
Who uses it.
Owner
Whole-restaurant visibility, staff access, reporting, plans, and operational controls.
Manager
Coordinates service, kitchen, reservations, delivery, and daily exceptions.
Counter
Handles billing, payments, online orders, delivery collections, and customer records.
Waiter
Manages table orders, service requests, ready items, and guest-facing actions.
KEY WORKFLOW
How the work moves.
Guest scans table QRJoins the active table sessionPlaces one or more ordersKitchen receives accepted itemsStaff serves ready items
CURRENT PHASE
Live testing
Core architecture and workflow rules are defined. Current work is completing operational workspaces, production data, and live restaurant testing.
BUILDS / Active build / Platform / 2026
Dwaar System
One operating layer for restaurants, cafés, and cloud kitchens.
Dwaar is being designed as an end-to-end operating layer for cafés, restaurants, and cloud kitchens. Instead of forcing teams to stitch together unrelated tools, it brings customer ordering, staff workflows, billing, delivery, and operational intelligence into one coherent system.
Dwaar System connects table service, kitchen operations, billing, delivery, staff responsibilities, and restaurant oversight inside one shared operational model. Instead of forcing each department to work through disconnected tools and conflicting order states, every role works from the same order lifecycle and source of truth.
BUILT BYKaran Soni / product, system & developmentIndependent product work designed and built under Karan Soni.
Restaurant operationsShared order lifecycleStaff workflows
PRODUCT AREAS
The parts that make the whole.
Move across the areas to see the role each one plays.
Tables & QR
Table sessions, guest ordering, repeat orders, and live service state.
Kitchen & service
Accepted items move into preparation and service handoffs.
Billing & settlement
Bills, payment methods, cash handling, and settlement remain connected to the session.
Online & delivery
Online orders, delivery tasks, collection, and settlement stay operationally separate.
Reservations
Pending, confirmed, cancelled, and no-show states are managed in one operational view.
Analytics
Operational reporting, customer intelligence, and restaurant-level performance.
ACTIVE MODULE
Tables & QR
Table sessions, guest ordering, repeat orders, and live service state.
PEOPLE & ACCESS
Built around the people who use it.
Each role sees the information and actions relevant to its responsibility.
ACTIVE ROLE
Owner
Whole-restaurant visibility, staff access, reporting, plans, and operational controls.
AnalyticsTeam & rolesPlans & settings
KEY WORKFLOW
How the work moves.
Guest scans table QRJoins the active table sessionPlaces one or more ordersKitchen receives accepted itemsStaff serves ready itemsBilling locks the sessionSettlement closes the table
PRODUCT DECISIONS
The rules behind the experience.
The decisions that keep the system coherent as the work becomes more complex.
Table and online orders stay separate
Table service accumulates against one live session. Online orders remain individual bills and workflows.
Realtime does not depend on browser focus
Operational queues keep updating while teams move between tabs, devices, and workspaces.
Permissions follow role and plan
Visibility and actions stay scoped to restaurant, role, plan, and explicit owner permissions.
Delivery collections are their own operation
Settlement and collection reconciliation do not disappear inside the delivery task queue.
BUILD STATUS
Where the build stands now.
Core architecture and workflow rules are defined. Current work is completing operational workspaces, production data, and live restaurant testing.
CURRENT PHASE
Live testing
Production Supabase, restaurant onboarding, plan controls, and operational trials.
CURRENT PHASELive testing
Production Supabase, restaurant onboarding, plan controls, and operational trials.
