Eyvro: optical e-commerce built from zero

The business had a physical presence but no effective digital storefront. Customers had no simple way to:

From the business side there was another problem: even after products were online, there was no reliable way to know when an order had been placed.

My first approach was heavily focused on the visual side. I believed a polished UI and a premium-looking landing page would be enough to create a useful online presence.

It wasn't. The first version looked more like a digital showcase than an actual commerce product.

I introduced a CMS-based product catalog using Sanity CMS, so product information and content could be managed separately from the frontend, with structured product data in place of hardcoded markup.

But having products online did not automatically create a usable buying experience. The site still lacked the underlying flow commerce needs, which pushed me to focus less on individual visual sections and more on the complete user journey.

The project then grew from a mostly frontend experiment into a proper web application. I learned how APIs work, how frontend and backend communicate, how databases store application data, how server-side logic handles requests and how e-commerce systems process orders.

I explored PostgreSQL for persistent storage and later moved to a Node.js backend using Express.js.

With the technical side understood, I rebuilt the experience around the customer's journey and rebranded the project as Eyvro, an optical e-commerce brand. Instead of a landing page, it became a complete shopping experience, designed to reduce friction between discovering a product and completing a purchase.

The redesign focused on making product discovery useful. A customer can:

It follows familiar e-commerce patterns while keeping the visual identity of the optical brand.

A new operational problem appeared: if someone places an order, how does the owner know? The CMS could store the order, but storage alone is not a notification workflow.

I added an email service that fires whenever an order is submitted, which connected the customer-facing site to the business's day-to-day operations.

The last gap was closing the commerce loop. Customers needed to pay digitally rather than just submit an order request, so I evaluated Indian payment gateway options and integrated one into the application.

The biggest value was not the website itself. Over several iterations I solved a chain of connected problems, each one discovered only after the last was fixed:

This project was my move from "I can create a website" to "I can understand a business problem and gradually build the system required to solve it." It taught me to think across UX, frontend, backend, data, integrations and business operations, and that mindset became the foundation for the projects that followed.