Commerce beyond a landing page
The project connects product discovery, cart, checkout, orders, tracking, cancellation, and reviews into a believable customer commerce loop instead of stopping at a hero section.
Back to projects
Commerce case study
Mushdelight
Premium food commerce system with customer auth, order lifecycle, reviews, subscribers, and admin operations
Mushdelight is a premium food-commerce website designed as a complete customer and business system rather than only a storefront landing page. The project includes customer signup and login, OTP verification, forgot and reset password flows, product catalog browsing, cart and checkout screens, order placement, tracking, cancellation handling, product reviews, contact flows, subscriber capture, and admin-side product operations. Under the hood it uses Next.js, React 19, MongoDB, Mongoose data models, JWT-based auth patterns, Brevo-powered communication flows, and operational APIs for products, settings, reviews, contacts, and customer orders.
I built this as a commerce product with both customer-side polish and business-side usefulness in mind, covering auth, orders, reviews, subscriber communication, admin operations, and database-backed product flows end to end.
Customer auth stack
Signup, login, OTP verification, forgot password, and reset password flows are part of the product
Order lifecycle
Customers can place orders, track them, and interact with order state instead of seeing a static checkout only
Mongo-backed catalog
Products, reviews, carts, settings, contacts, subscribers, and orders are modeled in the backend
Brevo communication
Transactional and subscriber communication make the project more business-ready than a frontend-only demo
Admin operations
Product management, reorder handling, and settings flows add an operational surface behind the storefront
Brand-first commerce UX
The interface is designed to feel premium, conversion-focused, and commercially presentable
System proof
What makes the commerce system feel complete
Customer account lifecycle
Login, signup, OTP verification, forgotten-password recovery, and profile-linked order visibility give the product a fuller account system than many demo storefronts.
Business communication layer
Contact submission, subscriber collection, and email-oriented workflows make the website useful for ongoing brand communication as well as order capture.
Operational backend thinking
Models and APIs for products, orders, reviews, settings, contacts, and subscribers show backend structure that supports day-to-day business operations.
Customer storefront flow
The website supports product discovery, product detail exploration, cart building, checkout progression, and order completion as a connected purchase journey.
Authentication and recovery
Signup, login, OTP verification, forgot password, and reset password screens turn the project into a fuller customer-account product instead of a guest-only demo.
Order management
Customers can view their orders, inspect status, track progress, and cancel where the flow allows, which makes post-purchase behavior part of the system.
Review and reputation system
Product reviews and rating-oriented data models add social proof and customer feedback loops to the commerce experience.
Subscriber and contact flows
Subscriber capture, contact messaging, and email delivery infrastructure make the product more realistic for a brand that wants retention and communication, not only one-time orders.
Admin-side control surface
Admin APIs for product management, reorder behavior, settings, and protected access prove there is an operations layer behind the public storefront.
Frontend commerce layer
The customer-facing site is built with modern Next.js and React, with route-level flows for auth, cart, checkout, orders, reviews, and profile-connected shopping behavior.
Next.js 15React 19TypeScriptTailwind CSSFramer Motionapp router
Backend data and API layer
MongoDB-backed APIs support products, orders, carts, reviews, subscribers, contacts, settings, and authenticated customer interactions.
MongoDBMongooseAPI routesproduct modelorder modelreview model
Auth and account flows
The product uses JWT-style auth patterns plus OTP and reset-password support so customer access behaves more like a production commerce app.
JWT patternsOTP verificationforgot passwordreset passwordprofile-linked orders
Communication systems
Brand and customer communication is handled through subscriber flows, contact handling, and email infrastructure rather than being left out entirely.
BrevoNodemailersubscriber APIscontact flowemail dispatch
Ownership
What I personally handled
Commerce information architecture for catalog, cart, checkout, and post-purchase experience
MongoDB and Mongoose data modeling for products, orders, reviews, contacts, subscribers, carts, and settings
Authentication, OTP verification, password recovery, and customer-order account flows
Admin-side operational APIs for product control, reorder handling, and settings management
Subscriber and email communication wiring through Brevo and mail-oriented workflows
Premium customer-facing UI direction for a polished food-commerce brand presentation
Technology index
Core technologies used
Next.js 15React 19TypeScriptMongoDBMongooseJWT auth patternsBrevoNodemailerTailwind CSSFramer MotionOrder lifecycle UXReview systemSubscriber workflowsAdmin product controls