You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A self-service ordering kiosk + complete bakery management platform — built for real shop operations.
📖 About
The Bakery Inventory & Kiosk System is a production-ready, full-stack web application that digitalises both the front-of-house and back-office operations of a small-to-mid-sized bakery. On the customer side, a large-screen self-service kiosk — styled like the ordering terminals at fast food chains — lets walk-in customers browse the menu, build their cart, and walk away with a token number in seconds, no cashier needed. On the owner side, a secure, JWT-protected dashboard gives complete control over the business: a live three-stage order pipeline, daily stock management that auto-disables sold-out products, custom wedding-cake orders with advance-payment tracking, raw material purchase logging, full price history records, and profit reports that calculate net income by subtracting daily expenses from completed-order revenue. Every price change is stored as a historical record rather than overwriting the old one, and every order permanently captures the price at time of sale — so financial reports are always accurate no matter how many times prices change in the future.
Owner needs to buy ingredients / packaging supplies
│
▼
┌─────────────────────────┐
│ Ensure material exists │ ← POST /api/raw-materials (if new)
│ in catalogue │ e.g. "Refined Flour", "Butter"
│ (RawMaterials page) │
└────────────┬────────────┘
│
▼
┌─────────────────────────┐
│ Log the purchase │ ← POST /api/raw-purchases
│ (AddRawPurchase page) │ Stores: material(ref), qty,
│ │ unitPrice, totalCost,
│ │ purchaseDate, status = PENDING
└────────────┬────────────┘
│
▼
┌─────────────┐
│ PENDING │ ← Ordered, not yet received
└──────┬──────┘
│ Goods arrive → PATCH /api/raw-purchases/:id/done
▼
┌─────────────┐
│ DONE │ ← Confirmed received
│ │ ✓ Cost recorded as expense for that date
│ │ ✓ Feeds into daily expense report
└─────────────┘
7. Reporting Workflow
Owner opens Reports page → /reports
│
├── Daily Profit Report ─────────────────────────────────────┐
│ GET /api/reports/profit?date=YYYY-MM-DD │
│ │
│ Revenue = SUM of priceAtSale × qty (completed orders) │
│ Expenses = SUM of totalCost (confirmed raw purchases) │
│ ───────────────────────────────────────────────────── │
│ Net Profit = Revenue − Expenses │
│ │
├── Date Range Profit Report ────────────────────────────────┤
│ GET /api/reports/profit/range?start=...&end=... │
│ │
│ Same calculation across every day in the range │
│ Useful for weekly / monthly / custom period reviews │
│ │
└── Daily Expense Report ────────────────────────────────────┘
GET /api/reports/expense?date=YYYY-MM-DD
Full breakdown of every confirmed raw purchase for the day
✨ Features — All 18 Pages
🧍 Customer-Facing Pages (Public — No Login Required)
#
Route
What It Does
1
/menu
Large-screen kiosk product grid. Shows all active products with Cloudinary images, current prices, and live stock status. Products with zero stock are hidden. Customers browse by category and add items to the cart.
2
/checkout
Cart review screen with quantity controls and a live running total. Customer enters their name and phone number. On confirmation, the order is submitted to the backend with priceAtSale locked per item.
3
Token number receipt screen displayed after a successful order. The large token number tells the customer what to quote at the counter when their order is ready. Also used by the owner as a read-only order summary list.
🔐 Auth
#
Route
What It Does
4
/login
Owner login form. Sends credentials to POST /api/auth/login, receives a JWT token, stores it in localStorage, and redirects to the dashboard. All subsequent protected routes read this token from storage.
📋 Order Management
#
Route
What It Does
5
/dashboard
The owner's primary working view. Displays three live columns — Pending, Done, Completed — with action buttons on each order card. Completing an order triggers automatic stock deduction.
6
/orders
Full searchable and filterable history of all orders across all statuses. Useful for resolving disputes and reviewing past activity.
📦 Product Management
#
Route
What It Does
7
/products
Active product catalogue. Each product card shows its image, name, category, current price, and enable/disable toggle. Soft-delete sends the product to the deleted list without breaking order history.
8
/add-product
Form to add a new product. The owner fills in name, category, and price, then uploads an image which passes through the image cropper for consistent aspect-ratio cropping before being sent to Cloudinary.
9
/deleted-products
Lists all soft-deleted products. Each entry has a Restore button that sets isDeleted: false and makes the product visible on the kiosk again. Order history referencing the product is always preserved.
🥦 Raw Material Management
#
Route
What It Does
10
/raw-materials
Full catalogue of all active raw materials used in the bakery. Shows name, unit of measure, and category. Links to add new entries and view deleted ones.
11
/add-raw-material
Form to register a new raw material in the catalogue before purchases can be logged against it. Captures name, unit (kg, litres, etc.), and category.
12
/deleted-raw-materials
Lists all soft-deleted raw materials with a restore button. Prevents orphaned purchase records by never hard-deleting materials that have purchase history.
🛒 Raw Purchase Tracking
#
Route
What It Does
13
/raw-purchases
All logged raw material purchases with Pending/Done status, quantities, unit price, total cost, and purchase date. Confirmed (Done) purchases feed the daily expense report.
14
/add-raw-purchase
Form to log a new raw material purchase. The owner selects the material from the catalogue, enters quantity and unit price, and the total cost is calculated automatically.
👥 Customer Management
#
Route
What It Does
15
/customers
All customers who have ever placed an order, grouped by phone number. Shows order count and total spend per customer. Useful for identifying loyal repeat customers.
16
/customers/:phone
Full order history for one specific phone number — every order placed, with date, items ordered, and amount paid. Useful for resolving customer queries.
📈 Reports & Custom Orders
#
Route
What It Does
17
/reports
Daily and date-range profit reports (revenue minus expenses) and daily expense breakdowns. Revenue figures use priceAtSale values from completed orders so historical reports are always accurate.
18
/add-custom-order
Form to create a bespoke order (wedding cakes, bulk event orders). Records customer details, order description, total agreed price, advance payment received, and outstanding balance due.
🛠 Tech Stack
Technology
Purpose
Why Chosen
React.js 18
Frontend UI
Component model cleanly separates kiosk and dashboard into independent trees; hooks make cart state and form logic simple
React Router v6
Client-side routing
Declarative protected-route wrappers let /menu stay fully public while /dashboard and beyond require a valid JWT
Node.js 18
Backend runtime
Non-blocking I/O handles simultaneous order POSTs from the kiosk without queuing or blocking the owner's dashboard requests
Express.js 4
HTTP server and API
Minimal, unopinionated; thin route files delegate to controller files — concerns are cleanly separated throughout
MongoDB Atlas
Primary database
Document model accommodates the varied shapes of orders, custom orders, stock entries, and price history without schema migrations
Mongoose
MongoDB ODM
Schema validation, pre-save hooks (e.g. auto-disable on zero stock), and clean query syntax over the raw MongoDB driver
JWT
Owner authentication
Stateless token auth is ideal for a single-admin system; no session table needed, works seamlessly across Vercel + Render
Cloudinary
Image storage & CDN
Handles upload, optimisation, resizing, and global delivery — the Node server never serves a single static asset
ImageCropper
In-browser image crop
Ensures all product images are cropped to a consistent aspect ratio before upload, keeping the kiosk grid visually uniform
Vercel
Frontend hosting
Zero-config React deployment with automatic HTTPS and global edge CDN
Render
Backend hosting
Free-tier Node.js hosting with persistent environment variables and straightforward MongoDB Atlas connectivity
📁 Project Structure
INVENTORYSYSTEM/
│
├── backend/
│ │
│ ├── controllers/ # Business logic — 12 files, one per domain
│ │ ├── authController.js # Validate credentials, issue JWT
│ │ ├── categoryController.js # Product category CRUD
│ │ ├── customerController.js # Aggregate orders grouped by phone number
│ │ ├── customOrderController.js # Create + Pending→Done→Completed flow for custom orders
│ │ ├── expenseReportController.js # Sum confirmed raw-purchase costs per date
│ │ ├── orderController.js # Place order (priceAtSale), status transitions, stock deduction
│ │ ├── productController.js # CRUD + Cloudinary upload + soft-delete + enable/disable
│ │ ├── productPriceController.js # Close old price record, open new; current-price query
│ │ ├── profitReportController.js # Revenue − expenses for day or date range
│ │ ├── rawMaterialController.js # Catalogue CRUD + soft-delete
│ │ ├── rawPurchaseController.js # Log purchase, confirm receipt → records as expense
│ │ └── stockController.js # Daily stock entry, today's query, zero-stock disabling
│ │
│ ├── models/ # Mongoose schemas — shape of every MongoDB document
│ │ ├── Category.js # { name, description }
│ │ ├── CustomOrder.js # { customerName, phone, description, totalPrice, advancePaid, balanceDue, status }
│ │ ├── Order.js # { customerName, phone, tokenNumber, items[{product, name, qty, priceAtSale}], status }
│ │ ├── Product.js # { name, category, imageUrl, cloudinaryId, isEnabled, isDeleted }
│ │ ├── ProductPrice.js # { product, price, fromDate, toDate } — append-only history
│ │ ├── RawMaterial.js # { name, unit, category, isDeleted }
│ │ ├── RawPurchase.js # { material(ref), qty, unitPrice, totalCost, purchaseDate, status }
│ │ ├── StockEntry.js # { product(ref), date, quantityAdded, quantityRemaining }
│ │ └── User.js # { email, password(hashed) } — single owner account
│ │
│ ├── routes/ # Express route definitions — thin, delegates to controllers
│ │ ├── authRoutes.js # POST /api/auth/login
│ │ ├── categoryRoutes.js # CRUD /api/categories
│ │ ├── customerRoutes.js # GET /api/customers GET /api/customers/:phone
│ │ ├── customOrderRoutes.js # CRUD + status /api/custom-orders
│ │ ├── expenseReportRoutes.js # GET /api/reports/expense
│ │ ├── orderRoutes.js # POST + GET + status PATCH /api/orders
│ │ ├── productPriceRoutes.js # POST + GET /api/prices
│ │ ├── productRoutes.js # Full product management /api/products
│ │ ├── profitReportRoutes.js # GET /api/reports/profit /api/reports/profit/range
│ │ ├── rawMaterialRoutes.js # CRUD /api/raw-materials
│ │ ├── rawPurchaseRoutes.js # CRUD + confirm /api/raw-purchases
│ │ └── stockRoutes.js # GET today + POST update /api/stock
│ │
│ ├── middleware/
│ │ ├── authMiddleware.js # Verify JWT on every protected route, attach owner to req
│ │ └── cloudinaryConfig.js # Initialise Cloudinary SDK + multer/upload config
│ │
│ ├── setup.js # One-time seed: creates default owner account
│ ├── server.js # Entry point: connect MongoDB, mount routes, listen
│ └── package.json
│
├── frontend/
│ └── src/
│ │
│ ├── pages/ # 18 full-page route components
│ │ │
│ │ │ ── CUSTOMER KIOSK (PUBLIC) ──────────────────────────
│ │ ├── CustomerMenu.js # Product grid kiosk — browse, filter by category, add to cart
│ │ ├── Checkout.js # Cart review + name/phone entry + submit order
│ │ ├── OrdersSummary.js # Token number receipt (public) + order summary (owner)
│ │ │
│ │ │ ── AUTH ───────────────────────────────────────────────
│ │ ├── Login.js # Owner login form + JWT storage
│ │ │
│ │ │ ── ORDERS ─────────────────────────────────────────────
│ │ ├── Dashboard.js # Live pipeline: Pending → Done → Completed
│ │ ├── Orders.js # Full historical order list, all statuses, searchable
│ │ │
│ │ │ ── PRODUCTS ────────────────────────────────────────────
│ │ ├── Products.js # Active catalogue with enable/disable/soft-delete
│ │ ├── AddProduct.js # Add product form — ImageCropper → Cloudinary upload
│ │ ├── DeletedProducts.js # Soft-deleted products with restore
│ │ │
│ │ │ ── RAW MATERIALS ──────────────────────────────────────
│ │ ├── RawMaterials.js # Active raw material catalogue
│ │ ├── AddRawMaterial.js # Add new raw material to catalogue
│ │ ├── DeletedRawMaterials.js # Soft-deleted materials with restore
│ │ │
│ │ │ ── RAW PURCHASES ──────────────────────────────────────
│ │ ├── RawPurchases.js # All logged purchases with Pending/Done status
│ │ ├── AddRawPurchase.js # Log a new raw material purchase
│ │ │
│ │ │ ── CUSTOMERS ─────────────────────────────────────────
│ │ ├── Customers.js # All customers grouped by phone, order count, spend
│ │ ├── CustomerDetails.js # Full order history for one phone number
│ │ │
│ │ │ ── REPORTS & CUSTOM ORDERS ────────────────────────────
│ │ ├── Reports.js # Profit + expense reports, daily and date-range
│ │ └── AddCustomOrder.js # Bespoke order with advance payment tracking
│ │
│ ├── components/ # Reusable UI components
│ │ ├── Header.js # Owner dashboard nav bar with active route highlighting
│ │ └── ImageCropper.js # In-browser aspect-ratio crop before Cloudinary upload
│ │
│ ├── App.js # Route table, JWT auth context, protected route logic
│ └── index.js # React DOM render entry point
│
├── assets/
│ └── screenshots/ # Screenshot images (add yours here)
│
└── .gitignore
# 1. Clone the repository
git clone https://github.com/iit2023271/INVENTORYSYSTEM.git
cd INVENTORYSYSTEM
# 2. Enter the backend directorycd backend
# 3. Install dependencies
npm install
# 4. Create your environment file and fill in values (see below)
cp .env.example .env
# 5. Start the development server
npm run dev
# API running at http://localhost:5000
Backend .env
Create backend/.env — every variable is required.
# ── DATABASE ─────────────────────────────────────────────────────────# MongoDB Atlas: mongodb+srv://<user>:<pass>@cluster.mongodb.net/<db># Local: mongodb://localhost:27017/bakeryMONGO_URI=mongodb+srv://your_user:your_password@cluster.mongodb.net/bakery# ── AUTH ─────────────────────────────────────────────────────────────# Long random string used to sign JWTs — never commit this# Generate: node -e "console.log(require('crypto').randomBytes(64).toString('hex'))"JWT_SECRET=your_super_secret_jwt_key_minimum_32_characters# ── OWNER SETUP ──────────────────────────────────────────────────────# Passphrase checked by setup.js when seeding the owner accountOWNER_SECRET=your_owner_setup_passphrase# ── SERVER ───────────────────────────────────────────────────────────PORT=5000# ── CLOUDINARY ───────────────────────────────────────────────────────# Found at cloudinary.com → Dashboard → Settings → API KeysCLOUDINARY_CLOUD_NAME=your_cloud_nameCLOUDINARY_API_KEY=your_api_keyCLOUDINARY_API_SECRET=your_api_secret
Frontend Setup
# From the project rootcd frontend
# Install dependencies
npm install
# Create environment file and fill in your backend URL
cp .env.example .env
# Start React dev server
npm start
# App opens at http://localhost:3000
Frontend .env
Create frontend/.env:
# ── API URL ───────────────────────────────────────────────────────────# Local development:REACT_APP_API_URL=http://localhost:5000# Production (replace with your Render URL after deploying the backend):# REACT_APP_API_URL=https://your-backend-name.onrender.com
First-Time Owner Account
The system enforces exactly one owner. Before logging into the dashboard, run the setup script once:
# From the backend/ directory
npm run setup
Default credentials created by the script:
Field
Value
Email
admin@shop.com
Password
admin123
⚠️Change the password immediately after first login. The script refuses to run a second time if an owner already exists — this prevents accidental overwrites in production.
1. Single Owner Account — Enforced at Architecture Level
The system is designed for one bakery operator, not a multi-tenant SaaS product. Rather than building role management and team-access features that would triple complexity without any business value here, the architecture enforces a hard constraint: setup.js refuses to create a second owner account if one already exists, and the login endpoint only ever issues tokens against that single record. This keeps authentication down to a standard JWT flow with no refresh tokens, no session tables, and no permission checks beyond "is this a valid owner token." If the business grows to need a team, the only change required is adding a role field to the User schema and a single middleware check — the foundation is already correct.
2. Daily Stock Entries Instead of a Running Inventory Counter
Most inventory systems maintain a running counter and decrement it on every sale. A bakery does not work that way — croissants are baked fresh every morning in specific quantities, and yesterday's unsold stock is written off or repurposed, not carried forward. The system models this reality by requiring the owner to enter fresh quantities each morning. If the owner forgets to enter stock, no product is shown as available with a stale count from a previous day. This also makes the stock entry ritual meaningful — it is the owner's daily signal to the system about what is available today, not a ledger correction.
3. Price History as Immutable Append-Only Records
When a price changes, the system closes the current ProductPrice record by setting its toDate to today, then creates a new record with fromDate set to today and toDate as null (signalling "currently active"). The old record is never updated or deleted. This means the full pricing timeline for every product is always queryable — you can find exactly what a product cost on any date in the past. It provides an automatic audit trail, makes the priceAtSale pattern reliable (below), and costs virtually nothing in storage since price changes are infrequent relative to orders.
4. priceAtSale Stored Directly on Every Order Line Item
When an order is placed, the backend looks up the currently active price for each product and stores it directly on the order document as priceAtSale. This makes every order a self-contained financial record — it knows what was sold, how many units, and exactly what was charged at that moment in time. Without this, any profit calculation for a past period would silently recalculate using today's prices rather than the prices actually charged, making historical reports unreliable. This is standard practice in every serious commerce system and is just as important for a small bakery as it is for a large e-commerce platform.
5. Soft Delete for Products and Raw Materials
Deleting a product or raw material sets an isDeleted: true flag rather than removing the document. This is essential for referential integrity: every Order references product IDs in its line items, and every RawPurchase references a raw material ID. A hard delete would orphan those references and make historical records unreadable. Soft delete preserves the full history, allows the owner to restore an item deleted by mistake, and costs nothing in query performance because all normal listing queries simply filter on isDeleted: false. The dedicated Deleted Products and Deleted Raw Materials pages give the owner complete visibility and control.
6.Everything is Mobile Friendl
Everyting can be controlled in the mobile itself.so this is the biggest advantage. assuming owner doesnt know any technical knowledge, this website is made for them.
Built this system to solve a real operational problem: replacing the paper-and-shouting workflow of a busy bakery counter with a clean digital kiosk and owner dashboard — from customer token to end-of-day profit report.
📄 License
This project is licensed under the MIT License.
MIT License
Copyright (c) 2025 iit2023271
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
THE SOFTWARE.
Made with ☕, flour, and way too many console.log statements.
⭐ Star this repo if it helped you — it takes one click and means a lot.
