Sri Ayurvedic Vaidya Mitra

Sri Ayurvedic Vaidya Mitra is a registered Ayurvedic clinic and dispensary in Srirangam, Trichy, founded by Mrs. T. Mari Sri, with consultations given by Dr. R. Balamurgan, BAMS. The practice needed one system to do two jobs that are usually separate: sell classical Ayurvedic medicines online, and take bookings for clinical consultation.

The result is a single Next.js application backed by Supabase for database, file storage and authentication, with Resend for transactional email. It carries a 369-product catalogue imported from the practice's previous WordPress site, four consultation offerings, a manual UPI payment flow with admin verification, a gated content library, and an admin back office covering every one of those.

Checkout prices every line on the server, generates a UPI QR for the shop's own VPA, and takes the transaction reference back from the customer with an optional screenshot. Nothing is reserved until an administrator matches that reference against the bank statement.

Four consultation offerings, a seven-day booking lead time, and payment before confirmation. The lead time lives in the database rather than the form, because the booking endpoint is reachable without the interface.

One dashboard covers everything that needs attention: products, taxonomy, orders, bookings, articles, users and settings. Stock alerts, pending UPI verifications and unconfirmed consultations surface on the landing screen rather than waiting to be found.

Pages and route handlers call a service, and services map snake_case database rows onto the domain shapes components render. That boundary is what allowed the entire backend to be moved from MongoDB to Supabase mid-project without editing a single component.

Nineteen tables across nine migrations, every one with Row Level Security enabled. Access rules live in the database, so a query issued from anywhere — the application, a script, a leaked key — is subject to the same policy.

Type-checking and linting pass, but on this project they proved to mean very little on their own: every defect that mattered — storage permissions, a missing join modifier, cookies in a cached page, an unconfigured image host — passed both cleanly and appeared only against the real service.

Two habits followed from that. Database logic is exercised by npm run db:verify, which applies all nine migrations to an in-process Postgres and runs 36 checks over pricing, stock reservation, idempotency, authorisation and booking rules — it has caught real defects before deployment. Everything else is verified by exercising the actual endpoint against the live project and confirming the row or object exists, including a full customer journey from sign-up through payment.

The highest-intent queries for this practice are geographic. Pages carry MedicalClinic and Physician structured data with address, opening hours and credentials, which is what makes a clinic eligible for a local map result rather than appearing as an anonymous shop.

The sitemap covers 492 URLs and regenerates daily; robots rules exclude private and duplicate paths; product pages carry Product markup with images, price and availability. Analytics is wired through the Google tag, loaded after hydration so it never delays first paint.

The three-layer header collapses to a sheet, the product grid reflows to a single column, and checkout stays usable on a phone — where most of this catalogue's traffic lands.

Deployed on Vercel against the production Supabase project, with a verified sending domain for transactional mail. Eleven maintenance scripts cover the work that recurs: migration verification, seed regeneration, WooCommerce conversion, taxonomy seeding, icon and social-card generation, image optimisation and a live email delivery test.