NAVHEALING HERBS
DESIGN · BUILD · SHIP
NEXT.JS · REACT · GSAP · NESTJS · POSTGRESQL · PRISMA
The website and admin panel for an Ayurvedic wellness brand from Nangal, Punjab — an online shop and teleconsult booking up front, and the system that runs orders, leads, patients and the team behind it.
A CLINIC-LED AYURVEDA BRAND NEEDED A SHOP — AND A BACK OFFICE TO RUN IT.
Nav Healing Herbs makes classical Ayurvedic formulations and offers teleconsultations with Dr Tanya Sharma, a gynaecologist and general physician.
They needed a site that feels as considered as the products, sells them online, and turns visitors into consultations — plus one place for the team to handle every order, lead and patient that follows.
STOREFRONT
A Next.js site for the formulary, treatment guides, journal and clinic story — editorial typography and GSAP motion, built to rank and to load fast on mobile.
CART → CHECKOUT
Cart, checkout with UPI (scan-to-pay QR) or cash on delivery, and an order page customers can come back to for live status.
CONSULT → LEAD
Teleconsult booking with a Prakriti (dosha) quiz. Every request lands in the admin panel as a lead, with WhatsApp and call shortcuts on every page.
ADMIN PANEL
A NestJS + PostgreSQL back office at admin.navhealingherbs.com that runs the business behind the site — from the first enquiry to the delivered parcel.
ONE ADMIN PANEL FOR THE WHOLE BUSINESS.
Every website order in one queue — approve or reject, then follow it through shipped, in transit, out for delivery, delivered or returned (RTO).
Shipments are tracked live through the Shipmozo courier API, and PDF invoices are generated straight from the order.
Consult requests become leads with a real calling pipeline — not picked, call back, follow-up 1–3, converted — and each patient keeps a history of every interaction.
Sales, product sales, expenses and daily reports roll up into charts, so the owners see the business at a glance.
Super admin, admin and team-member roles, email invites, and sign-in with a user code followed by a password or an email one-time code. Staff log their calls and work every day.
[ 200 OK ]
LIVE.
- [ LIVE AT NAVHEALINGHERBS.COM ]
- [ STOREFRONT + ADMIN PANEL ]
- [ UPI + CASH ON DELIVERY ]
- [ NEXT.JS · NESTJS · POSTGRESQL ]
- [ VISIT THE SITE ↗ ]
Ecommerce website and custom admin panel development
Nav Healing Herbs is a client project for an Ayurvedic wellness business in Punjab. GrowYourWebs designed and built the customer website and operational back office. The scope connects product browsing and consultation enquiries with the records staff need to manage afterwards.
From checkout to order management
The storefront provides a product catalogue, cart, UPI QR payment or cash-on-delivery checkout, and an order-status page. The admin workflow lets the team review an order and follow its delivery stages. The checkout uses a scan-to-pay QR flow, with order review handled in the admin panel.
From a consultation form to a lead
A consultation request becomes a lead in the back office. Staff can record calls and follow-ups, move the enquiry through defined stages, and maintain patient interaction history. This gives the public form a corresponding staff workflow instead of ending at an email notification.
Backend APIs and staff access
The Next.js and React website is paired with a NestJS backend, PostgreSQL and Prisma. The admin includes owner, administrator and team-member roles. Shipmozo supplies courier tracking through its API, while order records support PDF invoices. These are concrete examples of the integration and admin-panel work offered by GrowYourWebs.
Delivered scope and evidence
The public website and screenshots show the storefront, mobile consultation form and admin sign-in. The private back-office scope includes orders, leads, patient records, sales and expense reports, and team access. The customer and staff workflows are described together so a similar project can be scoped around its full operational requirements.
Questions before you start
Can a website and admin panel be built together?
Yes. Defining them together helps connect a customer action, such as an order or enquiry, with the staff action that follows it. The scope still needs to identify the records, roles, integrations and acceptance checks for your own business.
Can I see the private admin or patient records?
The public case study uses project screenshots and a description of the delivered modules. Customer, patient and staff records are private and are not part of a public demonstration.
Does a similar build include ecommerce and booking by default?
Only the functions agreed in your proposal are included. Product variants, payment handling, delivery providers, appointment rules and existing data can change the scope substantially. Bring those requirements when asking for an estimate.