Overview
Blurkart sells prescription frames, sunglasses and blue-light glasses in Nepal. They needed a storefront that could actually take money from Nepali customers, which is the part that decides whether an online store in this market works at all. The catalogue is organised the way people shop for glasses rather than the way a database stores them: by frame shape, by collection, and by brand, with a wishlist so a customer can sit on a decision and come back. Product pages are server-rendered so they can be found in search rather than only through the shop's own navigation. Payment runs through a separate Fonepay service rather than being wired into the storefront. That separation is deliberate. Payment code has a different failure profile from the rest of a shop, and keeping it in its own process means a change to the catalogue cannot break checkout, and a payment provider changing its verification response is one file to edit rather than a hunt through the application. Two features exist because eyewear is not a normal e-commerce category. Buying glasses usually needs a prescription, so the site books an in-store eye test rather than pretending the whole journey can happen online. And because frames are a considered purchase with a real return rate, order tracking and the returns policy are first-class pages rather than links buried in a footer. The stack is Next.js 16 and React 19 with TypeScript and Tailwind, Prisma over PostgreSQL, NextAuth for customer accounts, and Zustand for cart state. The application, database and reverse proxy each run as their own container, and there is a Cypress end-to-end suite covering the paths that cost money when they break.
Results
Challenges
Our Solutions
Technologies Used
Tags
