Shop by occasion
The catalogue is organised the way a wedding is: bridal, festive, haldi, reception, mehendi ceremony and sangeet, plus a stock-clearing rail. Navigation follows the event, not the garment type.
400E-commerce
Vinny's Vogue
Online store for Indian bridal and festive couture.
- Role
- Sole developer.
- Year
- 2026
- Status
- Live at vinnysvogue.in.
- Stack
- Next.js, TypeScript, Supabase, PostgreSQL, Tailwind CSS
- collections by occasion, bridal to stock clearing
- 7
- role-based access enforced in Postgres
- RLS
(57) Abstract
A production storefront with catalogue, cart, checkout and order tracking, run from a role-based admin dashboard by the boutique itself.
Background
A family boutique selling bridal and festive wear needed to sell online without losing the feel of the shop. Customers shop by occasion, not by category, and the owners wanted to run products and orders themselves.
Detailed description
Stock that holds under concurrent checkout
Cart changes run as single atomic database operations and inventory is tracked through checkout, so two customers buying the last piece at once can't both succeed.
Roles in the database
Customers and admins are separated by Supabase row-level security, not only by what the UI hides. Order tracking, product management and checkout all sit behind the same policies.
An admin the owners actually use
The dashboard covers products, orders, abandoned carts, reviews and analytics such as revenue and orders by status, with weekly sales exports, so the shop runs without a developer in the loop.
What is claimed is:
- 1.
A storefront whose catalogue is organised by occasion.
- 2.
The storefront of claim 1, wherein cart changes are single atomic database operations.
- 3.
The storefront of claim 1, wherein roles are enforced by row-level security in the database.