Nandiniz'Aura

This one is probably the cleanest example of me building software for an actual business instead of for a portfolio checkbox.

Nandiniz'Aura needed an e-commerce platform for selling handcrafted candles and home decor. On paper, that sounds straightforward enough: product pages, cart, checkout, orders, admin. But the moment payments, inventory, customer accounts, transactional emails, and real fulfilment workflows enter the picture, it stops being a nice frontend exercise and becomes a real product.

Which is exactly what made it worth building properly.

The Product

The customer-facing side is the part people see first: a storefront, product catalogue, product detail pages, cart, checkout, account pages, order history, and the basic brand pages a real business needs to feel complete.

But the more important part, honestly, was the operational side.

I built the admin dashboard for managing products, categories, users, orders, stock, featured products, analytics, and the everyday work of running the store. That's the part that turns a site from "people can buy something" into "the business can actually operate from this system".

The goal was to make something the business could actively use, not just a simple demo.

The Engineering

The stack is Next.js, TypeScript, PostgreSQL, Prisma, NextAuth, Razorpay, and Resend. Fairly standard tools, but the interesting work was in making all the pieces hold together.

Payments go through Razorpay, with webhook verification handling the real payment state rather than trusting the browser. Authentication is role-based, with admin-only routes and protected API surfaces. Orders create the right records, trigger the right emails, and show up in the admin flow where they can actually be acted on.

I also wired up CSRF handling, middleware-level protection, product image uploads, category management, order status updates, customer account flows, and the kind of boring-but-crucial edge cases that usually decide whether a product feels trustworthy.

And because commerce systems are exactly the wrong place to guess, I built a proper test suite around the API routes, middleware, auth, payment verification, order emails, products, users, categories, analytics, and the rest of the system surface.

The Value

This project taught me that full-stack product work is less about knowing a framework and more about respecting the whole chain of consequences.

If the cart is weird, the user loses trust. If the payment flow is flaky, the business loses money. If the admin dashboard is unclear, someone has to compensate manually. If the tests are missing, every change becomes a tiny gamble.

The satisfying part here was watching the whole thing become a coherent operating system for a small business.

Practical, visible, shipped and just complicated enough that it forces one to care about both the user experience and the backend truth underneath it, just the exact sort of work that I like.