Back to Works
Works / 08Academic

Rupali Beauty Point

Rupali Beauty Point was built for a sixth-semester e-commerce practical. Yumesh Ban and Rupesh Acharya chose a beauty-product storefront as their shared project, using it to practise a full MERN customer-to-admin commerce flow rather than stopping at a static product catalogue.

Role

Full-stack Developer

Association

Tribhuvan University

Rupali Beauty Point logo
Project evidence / 0816:10 view

01

The context

The problem, people, and outcome in view.

Rupali Beauty Point was built for a sixth-semester e-commerce practical. Yumesh Ban and Rupesh Acharya chose a beauty-product storefront as their shared project, using it to practise a full MERN customer-to-admin commerce flow rather than stopping at a static product catalogue.

The project includes customer/admin access, product and category management, image upload, cart persistence, checkout/order creation, and MongoDB-backed API workflows. It is an academic implementation, not a deployed commercial store; payment, delivery tracking, and production-operation claims must remain out of the case study.

02

The contribution

A clear view of what I owned.

Full-stack Developer

Responsibilities

Showing 10 of 18
  • Vite/React frontend with customer and admin contexts
  • routing
  • product pages
  • cart
  • checkout
  • and an administration surface.
  • Node.js/Express backend with MongoDB/Mongoose data models and REST-style route/controller layers.
  • JWT-protected customer and admin flows.
  • Product/category CRUD
  • stock fields

Capabilities applied

ReactCommerce & Inventory DataPayments, Webhooks & IntegrationsCollaboration & Problem SolvingViteExpress.jsMongoDB & MongooseAuthentication & AuthorizationAdmin & Dashboard DesignCloudinary & MulterState Management & Local Persistence

03

The work

From decisions to the working product.

Process

Rupali Beauty Point was built for a sixth-semester e-commerce practical. Yumesh Ban and Rupesh Acharya chose a beauty-product storefront as their shared project, using it to practise a full MERN customer-to-admin commerce flow rather than stopping at a static product catalogue.

The project includes customer/admin access, product and category management, image upload, cart persistence, checkout/order creation, and MongoDB-backed API workflows. It is an academic implementation, not a deployed commercial store; payment, delivery tracking, and production-operation claims must remain out of the case study.

Solution

Vite/React frontend with customer and admin contexts, routing, product pages, cart, checkout, and an administration surface. Node.js/Express backend with MongoDB/Mongoose data models and REST-style route/controller layers. JWT-protected customer and admin flows. Product/category CRUD, stock fields, image upload handling, and Cloudinary-ready media integration. Cart quantity, total, order, and product reference logic in MongoDB. Order creation and payment-request preparation, including delivery charge calculation.

04

The result

Proof over promises.

The project was built for an academic practical and is repository-only. Do not claim commercial deployment, live payment success, delivery tracking, sales, or client adoption.

05

Build notes

The tools and details that carried it through.

Technology

Showing 10 of 12
React frontend engineeringVite development workflowExpress API developmentMongoDB data modellingJWT authenticationRole-based administrationProduct/catalogue managementImage upload integrationCart modellingOrder workflow

Selected product details

  • Vite/React frontend with customer and admin contexts, routing, product pages, cart, checkout, and an administration surface.
  • Node.js/Express backend with MongoDB/Mongoose data models and REST-style route/controller layers.
  • JWT-protected customer and admin flows.
  • Product/category CRUD, stock fields, image upload handling, and Cloudinary-ready media integration.
  • Cart quantity, total, order, and product reference logic in MongoDB.
  • Order creation and payment-request preparation, including delivery charge calculation.

Explore further

Project document

Rupali Beauty Point PDF

06

Connected work

Proof and writing from this project.

Project proof

Showing 5 of 12

Frontend / React

Rupali Beauty Point: React frontend engineering

Built customer and admin React views for the shared Rupali Beauty Point e-commerce project with Rupesh Acharya. Component-based screens and context-driven state supported browsing, cart, and administration journeys.

Customer and admin viewsComponent-based interfaceCart-related state

Tools / Vite

Rupali Beauty Point: Vite development workflow

Used Vite to run and bundle the React frontend during development of the academic e-commerce project. Its fast local feedback loop supported iterative work on customer and admin screens.

Vite React setupFast local developmentFrontend build workflow

Backend / Express.js

Rupali Beauty Point: Express API development

Built Express route and controller layers for authentication, products, categories, carts, and orders. The API structure separated request handling from application logic for the MERN project.

Route and controller layersCatalogue API endpointsCart and order endpoints

Database / MongoDB & Mongoose

Rupali Beauty Point: MongoDB data modelling

Modelled users, products, categories, carts, and orders with MongoDB and Mongoose. These collections supported the customer journey and the application’s administration features.

User and product schemasCategory and cart recordsOrder data relationships

Backend / Authentication & Authorization

Rupali Beauty Point: JWT authentication

Protected customer and admin routes through bearer-token verification in the MERN application. The access rules kept administrative actions separate from ordinary customer journeys.

Bearer-token checksCustomer route protectionAdmin access boundaries

Works / 08 of 08

Have a similar problem to solve? Let's talk.