← Back to Projects
ONGOING PROJECT

Magilam Foods — Admin Web Platform

An end-to-end business management platform built for Magilam Foods, covering menu management, recipe costing, stock control, order processing, and billing. The system serves two user roles — customers via a mobile app and administrators via a Next.js web dashboard. I contribute across both frontend development and QA for the admin website, building features and owning the full quality assurance pipeline.

Next.js TypeScript Tailwind CSS REST APIs JWT Auth Axios QA & Testing GitHub Issues

Project Status

This project is currently under active development for a real client organization. An 11-member team is working across backend, mobile frontend, admin frontend, and DevOps tracks simultaneously. The admin website is being built in Next.js with TypeScript, consuming a centralized backend API that handles all business logic including costing, stock deduction, and billing.

My Role

I contribute to the Admin Website across both frontend implementation and QA — building features alongside the primary frontend developer and independently owning the quality assurance pipeline for the admin interface.

Frontend Implementation — Key Contributions

  • Building admin interface pages and components in Next.js with TypeScript alongside Venkata Krishnan
  • Implementing UI using Tailwind CSS, ensuring responsive layout and consistent design across all admin views
  • Integrating frontend with backend REST APIs via Axios for data fetching, form submission, and state management
  • Handling loading states, error states, and empty states across all async operations
  • Contributing to the overall admin dashboard, management pages, and billing views as the team assigns scope

Admin Website QA & Support — Key Responsibilities

  • Testing all admin authentication flows — login, logout, protected route enforcement, and role-based access control
  • Validating all CRUD forms across menus, recipes, stock, orders, and billing for correct input handling, error messaging, and edge case behavior
  • Verifying API response handling — correct loading states, error states, and data rendering across all admin pages
  • Performing regression testing after each fix cycle to ensure no previously working functionality breaks
  • Reporting bugs through GitHub Issues with full reproduction steps, expected versus actual behavior, and attached screenshots or recordings
  • Re-testing resolved issues and confirming fixes before they are marked closed

System Overview

The platform is structured around a strict separation of concerns — the frontend holds no business logic, all computation (costing, stock deduction, billing) happens server-side, and the frontend consumes clean REST APIs.

Backend Modules

  • Authentication Service — JWT-based login with role-based access (Admin / Customer)
  • Menu & Recipe Engine — Menu items mapped to recipes, recipes mapped to ingredients
  • Costing Engine — Ingredient quantity multiplied by current price, plus labor cost, overheads, and profit margin to generate accurate quotations
  • Order Management — Order creation, status tracking, and confirmation workflows
  • Stock Management — Automatic stock deduction on order confirmation, with low-stock alerts
  • Billing System — Quotation generation, invoice creation, and payment status tracking

Admin Website — Frontend Modules

  • Dashboard — Summary metrics (orders, revenue, low stock), recent orders table, real-time API data
  • Menu & Recipe Management — Full CRUD for menu items, recipe mapping, and ingredient associations
  • Stock Management — Ingredient quantity updates, low-stock highlighting
  • Orders & Billing Views — Order lifecycle visualization, quotation and invoice display, read-only pricing
  • Auth & Navigation — JWT storage, protected routes, token expiration handling, persistent sidebar layout

Tech Stack

  • Next.js with TypeScript for the admin web interface
  • Tailwind CSS for consistent, responsive styling
  • Axios with a configured base client for all API communication
  • JWT for session management and route protection
  • GitHub Issues for structured bug tracking and lifecycle management

QA Scope & Testing Areas

  • Admin login, logout, session persistence, and token expiration handling
  • Protected route enforcement and role-based access control verification
  • All CRUD form flows — empty inputs, invalid data, boundary values, and error message accuracy
  • API integration correctness — verifying response data renders accurately across dashboard, orders, stock, and billing views
  • Loading and error state handling across all async operations
  • Regression testing after each round of bug fixes
  • UI consistency — spacing, typography, and responsive behavior across screen sizes

Current Progress

  • Project architecture, folder structure, API contracts, and ER diagram finalized
  • Next.js project initialized with TypeScript, Tailwind CSS, Axios base client, and environment configuration
  • Admin authentication UI and JWT session handling implemented
  • Global layout with sidebar navigation and header scaffolded
  • Menu, recipe, and stock management pages under active development
  • QA testing initiated for completed auth and navigation flows

Future Roadmap

  • Complete orders and billing view implementation and QA
  • Full integration testing across mobile app, admin website, and backend
  • End-to-end flow testing — order creation through stock deduction through invoice generation
  • Performance and concurrency testing for simultaneous order handling
  • Cloud deployment of backend and admin website with CI/CD pipeline
  • Mobile app APK build and distribution for customer-side testing