☕ Odoo Cafe POS - Smart Order Management

A modern, enterprise-grade Point of Sale system built with Next.js, Prisma, and PostgreSQL

Features • Tech Stack • Installation • Architecture • Screenshots

---

TEAM MEMBERS

• Hardagya Rajput
• Jagjeet Dangar
• Isha Patel

📖 Table of Contents

• Overview
• Features
• Tech Stack
• System Architecture
• Database Schema
• Order Lifecycle
• Installation
• Environment Variables
• Usage
• API Reference
• Project Structure
• Role-Based Access Control
• Screenshots
• Contributing
• License

---

🎯 Overview

Odoo Cafe POS is a comprehensive restaurant management system designed to streamline the ordering process, from table selection to kitchen preparation and final billing. It offers a synchronized ecosystem connecting Baristas, Kitchen Staff, and Managers through real-time updates.

Key Objectives

• 🏢 Centralized table and floor management
• ⚡ Fast, intuitive Point of Sale (POS) interface
• 👨‍🍳 Real-time Kitchen Display System (KDS)
• 💳 Integrated payments (Cash, UPI with QR, Digital)
• 📊 Detailed sales sessions and financial reporting
• 🔐 Secure role-based access control (Admin, Cashier, Kitchen)

System Overview Mindmap

mindmap
  root((Odoo Cafe POS))
    POS Terminal
      Table Selection
      Menu Browsing
      Cart Management
      Checkout
    Kitchen (KDS)
      Live Order Feed
      Status Updates
      Prep Tracking
    Management
      Floor Planning
      Product Inventory
      Staff Sessions
      Sales Reports
    Payments
      Cash Handling
      UPI Integration
      Receipt Generation
    Security
      JWT Auth
      Role Based Access
      Session Tracking

Loading

---

✨ Features

🖥️ POS Operations

• ✅ Table Management: Visual floor plan with real-time table status (Occupied, Free)
• ✅ Smart Menu: Categorized items, search, and variants (sizes, extras)
• ✅ Cart Operations: Hold orders, add notes, modify quantities
• ✅ Session Management: Opening/Closing cash tracking per terminal

👨‍🍳 Kitchen Display System (KDS)

• ✅ Real-time Feed: Orders appear instantly via Socket.io
• ✅ Status Workflow: PENDING → PREPARING → READY → COMPLETED
• ✅ Visual Cues: Distinct colors for different order states
• ✅ Item-level Control: Mark individual items as ready

🔧 Admin & Inventory

• ✅ Product Management: Create categories, products, and variants
• ✅ Floor Editor: Design restaurant layout (Floors, Tables, Seats)
• ✅ Staff Management: Create users and assign roles
• ✅ Sales Dashboard: Visualize revenue, popular items, and peak hours

📊 Views & Dashboards

• ✅ POS View: Optimized for touchscreens and fast entry
• ✅ Kitchen View: High-contrast, easy-to-read order tickets
• ✅ Manager Dashboard: Charts using Recharts/Nivo for insights
• ✅ Customer Display: Second screen view for customers (Planned)

🚀 Smart Automation

• ✅ Auto-Routing: 'Send to Kitchen' flag routes specific items to KDS
• ✅ Status Sync: KDS updates reflect instantly on POS
• ✅ Receipts: Auto-generated PDF receipts with QR codes
• ✅ Stock Logic: Basic availability toggles for menu items

Order Workflow Diagram

flowchart LR
    subgraph Cashier
        C1[Open Session]
        C2[Select Table]
        C3[Add Items]
        C4[Checkout]
    end
    
    subgraph Kitchen
        K1[Receive Ticket]
        K2[Start Prep]
        K3[Mark Ready]
    end
    
    C1 --> C2
    C2 --> C3
    C3 --> C4
    C4 -->|Socket.io| K1
    K1 --> K2
    K2 --> K3
    K3 -->|Notification| C4
    
    style C1 fill:#1A4D2E,color:#fff
    style C4 fill:#1A4D2E,color:#fff
    style K1 fill:#D97706,color:#fff
    style K3 fill:#10B981,color:#fff

Loading

🔐 Security & Tech

• ✅ JWT-based authentication
• ✅ Encrypted passwords (bcryptjs)
• ✅ Protected API routes (Middleware)
• ✅ Optimistic concurrency control on orders

---

🛠️ Tech Stack

Frontend

• Framework: Next.js 16.1.4 (App Router)
• Styling: Tailwind CSS 3.4
• State Management: Zustand + React Query
• Icons: Lucide React
• Charts: Recharts, Nivo, MUI X-Charts
• Realtime: Socket.io Client
• Animations: Framer Motion

Backend

• Runtime: Node.js
• Framework: Express.js 5.2
• Database: PostgreSQL (NeonDB Serverless)
• ORM: Prisma 5.10
• Authentication: JWT + bcryptjs
• Realtime: Socket.io Server
• Email: Nodemailer

Technology Stack Visualization

graph LR
    subgraph Frontend
        A[Next.js 16] --> B[React Components]
        B --> C[Tailwind CSS]
        B --> D[Zustand]
        B --> E[Socket.io Client]
    end
    
    subgraph Backend
        F[Express API] --> G[Prisma ORM]
        F --> H[JWT Auth]
        F --> I[Socket.io Server]
        G --> J[(PostgreSQL)]
    end
    
    E <--> I
    
    style A fill:#000,color:#fff
    style C fill:#38B2AC,color:#fff
    style G fill:#2D3748,color:#fff
    style J fill:#336791,color:#fff
    style F fill:#000,color:#fff

Loading

---

🏗️ System Architecture

graph TB
    subgraph "Client Layer"
        POS[POS Terminal]
        KDS[Kitchen Display]
        Admin[Admin Dashboard]
    end

    subgraph "API Layer"
        Express[Express Server]
        Socket[Socket.io Service]
        Auth[Auth Middleware]
    end

    subgraph "Data Layer"
        Prisma[Prisma Client]
        DB[(PostgreSQL)]
    end

    POS -->|HTTP| Express
    POS <-->|WebSocket| Socket
    KDS <-->|WebSocket| Socket
    Admin -->|HTTP| Express
    
    Express --> Auth
    Auth --> Prisma
    Prisma --> DB

    style POS fill:#1A4D2E,color:#fff
    style KDS fill:#D97706,color:#fff
    style Express fill:#000,color:#fff
    style Prisma fill:#2D3748,color:#fff

Loading

---

🗄️ Database Schema

erDiagram
    User ||--o{ Session : "opens"
    User ||--o{ Order : "manages"
    Terminal ||--o{ Session : "hosts"
    Session ||--o{ Order : "contains"
    Floor ||--o{ Table : "contains"
    Table ||--o{ Order : "assigned"
    Category ||--o{ Product : "classifies"
    Product ||--o{ Variant : "has"
    Product ||--o{ OrderItem : "sold as"
    Order ||--o{ OrderItem : "contains"
    Order ||--o{ Payment : "paid by"

    User {
        string id PK
        string email UK
        string name
        enum role "ADMIN, CASHIER, KITCHEN"
    }

    Session {
        string id PK
        timestamp startAt
        timestamp endAt
        decimal openingCash
        decimal closingCash
        enum status "OPEN, CLOSED"
    }

    Product {
        string id PK
        string name
        decimal price
        boolean isAvailable
        boolean sendToKitchen
    }

    Order {
        string id PK
        string orderNumber
        enum status "DRAFT, PREPARING, COMPLETED"
        decimal totalAmount
    }

Loading

Key Enums

Enum	Values
Role	ADMIN, CASHIER, KITCHEN
OrderStatus	DRAFT, SENT, PREPARING, COMPLETED, PAID, CANCELLED
PaymentMethod	CASH, DIGITAL, UPI
SessionStatus	OPEN, CLOSED

---

🔄 Order Lifecycle

stateDiagram-v2
    [*] --> DRAFT: Order Created
    DRAFT --> SENT: Send to Kitchen
    SENT --> PREPARING: Kitchen Starts
    PREPARING --> COMPLETED: Kitchen Finishes
    COMPLETED --> PAID: Payment Received
    PAID --> [*]
    
    DRAFT: 📝 Draft\n(Adding Items)
    SENT: 📨 Sent\n(Awaiting Kitchen)
    PREPARING: 👨‍🍳 Cooking\n(In Progress)
    COMPLETED: ✅ Ready\n(Serve to Customer)

Loading

---

📥 Installation

Prerequisites

• Node.js 18+
• PostgreSQL database
• npm or yarn

Step 1: Clone Repository

git clone https://github.com/Hardagya12/Odoo-Cafe-Pos.git
cd odoo-cafe-pos

Step 2: Backend Setup

cd backend
npm install
# Setup .env file
# Run migrations
npx prisma generate
npx prisma migrate dev
# Seed data
npm run seed
# Start Server
npm run dev

Step 3: Frontend Setup

cd frontend
npm install
# Setup .env.local file
# Start Client
npm run dev

Open http://localhost:3000 for Frontend and http://localhost:5000 for Backend API.

---

🔐 Environment Variables

Backend (.env)

Variable	Description	Required
DATABASE_URL	PostgreSQL connection string	✅ Yes
JWT_SECRET	Secret key for auth tokens	✅ Yes
PORT	API Port (default 5000)	❌ No

Frontend (.env.local)

Variable	Description	Required	Default
NEXT_PUBLIC_API_URL	Boolean	✅ Yes	http://localhost:5000/api

---

🚀 Usage

Default Accounts (from Seed)

Email	Password	Role	Usage
admin@odoo.com	admin123	ADMIN	Full Access, Manage Users/Products
cashier@odoo.com	cashier123	CASHIER	POS Main, Orders, Payments
kitchen@odoo.com	kitchen123	KITCHEN	KDS View Only

Standard Workflow

1. Login as Cashier.
2. Select Terminal and Open Session (Enter opening float).
3. Select Table from the floor plan.
4. Add Items to cart. Add variants/notes if needed.
5. Send to Kitchen (Order appears on KDS).
6. Kitchen Staff marks items as Ready.
7. Payment: Select Cash/UPI, confirm payment.
8. Close Session at end of day (Enter closing cash).

---

📡 API Reference

🔐 Authentication

Base URL: /api/auth

• POST /signup - Register new user
• POST /login - Authenticate user
• GET /me - Get current user profile

📦 Products & Inventory

Base URL: /api/products

• GET / - List all products
• POST / - Create product
• PUT /:id - Update product
• DELETE /:id - Delete product
• GET /categories - List categories
• POST /categories - Create category
• DELETE /categories/:id - Delete category

📝 Orders

Base URL: /api/orders

• POST / - Create new order
• GET / - List all orders
• GET /:id - Get order details
• PUT /:id/status - Update order status
• POST /:id/pay - Process payment
• POST /:id/email - Send receipt email

👨‍🍳 Kitchen

Base URL: /api/kitchen

• GET /active - Get active kitchen tickets
• PUT /:id/status - Update ticket status

🏢 Floor & Tables

Base URL: /api

• GET /floors - List floors
• POST /floors - Create floor
• POST /floors/:id/tables - Add table to floor
• PUT /tables/:id - Update table details
• DELETE /tables/:id - Remove table

🖥️ Sessions & Terminals

Base URL: /api

• POST /sessions/open - Open POS session
• PUT /sessions/:id/close - Close session
• GET /sessions/active - Get active session
• GET /sessions/:id - Get session details
• GET /terminals - List terminals
• POST /terminals - Create terminal
• DELETE /terminals/:id - Delete terminal

📊 Dashboard

Base URL: /api/dashboard

• GET /stats - Summary statistics
• GET /recent-orders - Recent activity
• GET /sales-chart - Sales visualization data
• GET /sales-trends - Trend analysis
• GET /top-products - Best selling items
• GET /heatmap-data - Busy hours heatmap

⚙️ Settings & Users

Base URL: /api

• GET /settings - Get store config
• PUT /settings - Update store config
• GET /users - List users
• POST /users - Create user
• PUT /users/:id - Update user
• DELETE /users/:id - Delete user

---

📁 Project Structure

odoo-cafe-pos/
├── backend/
│   ├── src/
│   │   ├── controllers/    # Route controllers
│   │   ├── routes/         # API routes
│   │   ├── middlewares/    # Auth & Validation
│   │   ├── services/       # Business logic
│   │   └── app.js          # Express entry point
│   ├── prisma/
│   │   └── schema.prisma   # Database Schema
│   └── package.json
├── frontend/
│   ├── src/
│   │   ├── app/            # Next.js App Router Pages
│   │   ├── components/     # UI Components
│   │   ├── lib/            # Utilities & API client
│   │   └── stores/         # Zustand Stores
│   └── package.json
└── README.md

---

🔐 Role-Based Access Control

• ADMIN: Access to Dashboard, Settings, User Management, Menu Editing.
• CASHIER: Access to POS, Orders, Payments, Sessions.
• KITCHEN: Access restricted to Kitchen Display System (KDS).

---

📸 Screenshots

(Placeholders)

POS Interface

Kitchen Display

Analytics Dashboard

---

🤝 Contributing

1. Fork the repo
2. Create feature branch (git checkout -b feature/NewFeature)
3. Commit changes
4. Push to branch
5. Create Pull Request

---

📄 License

This project is licensed under the MIT License.

---

Built with ❤️ for Coffee Lovers

⭐ Star this repo if you find it helpful! ⭐