Premium fashion commerce platform. Launches as Sri Vartali Sarees; the underlying system stays category-generic so dresses, kurtis, lehengas, blouses, dupattas and accessories can be added without rebuilding the core.
Three areas:
| Area | Purpose |
|---|---|
| Customer storefront | Browse, search, cart, multi-product checkout, order tracking |
| Client dashboard | Products, images, stock, orders, payment verification, shipping |
| Super admin | Users/roles, integrations, webhook logs, audit, diagnostics |
Invariants (from the build spec — non-negotiable):
- Database (Supabase PostgreSQL) is the source of truth; WhatsApp is a communication and payment-coordination layer, never the database.
- Orders are created before WhatsApp opens; all money math is authoritative on the server; browser-supplied prices are never trusted.
- A customer typing "PAID" only sets
CUSTOMER_CLAIMS_PAID— payment is verified manually by an authorized client user. - Money is stored as integer paise. UUIDs internally, readable codes externally
(
SVS-P-000121,SVS-ORD-20261002-00129).
Phase 1 (foundation) complete — app scaffold, design tokens, Supabase client layer,
auth with role gates, database schema v1 (RLS on every table), CI. Phases 2-11 per
the build spec: Sri_Vartali_AI_Agent_Build_Spec.md.
Phase 16 (2026-10-10, local-only): cart "Buy via WhatsApp" handoff (server-quoted
cart prefilled into a wa.me chat — lib/cart/whatsapp.ts), persistent supplier
contact dock + footer contacts (components/storefront/contact-dock.tsx,
lib/store/contact.ts; number resolves from store_settings.whatsapp_store_number
→ NEXT_PUBLIC_WHATSAPP_STORE_NUMBER). Fresh Supabase project
sri-vartali-commerce (all six migrations + sample catalog seed +
[email protected] SUPER_ADMIN), created and verified from this machine — see
.env.local for credentials. A Vercel production deploy was made the same day and
taken down at the owner's request (project deleted; only Supabase remains).
Run locally with npm run dev. Outbound Postgres (5432/6543) is blocked on this
network; apply one-off SQL via the dashboard SQL editor or a temporary Edge
Function (precedent: the sql-runner used today, deleted after use).
Phase 17 (2026-10-11, local-only): storefront UX pass at the owner's request —
(1) header rail highlights the active route (components/storefront/header-nav.tsx);
(2) Track Order removed everywhere (page, sitemap entry, getTrackOrderView;
the public /order/<n> page and the client dashboard remain the status views);
(3) Buy Now removed (button, svs_buy_now cookie, checkout buy-now mode) and
replaced on the product page by Buy via WhatsApp — the deep link prefills the
selected product, variant and live quantity (buildProductWhatsAppMessage); the
mobile contact dock yields its bottom bar to the product's sticky purchase bar;
(4) containers widened max-w-6xl → max-w-[1440px] across storefront, client
and admin shells; (5) brand logo (public/brand/logo.svg, SV monogram placeholder
until the owner's artwork lands) in header and footer.
Next.js (App Router) · TypeScript · Tailwind CSS · Supabase (PostgreSQL, Auth, RLS) · Cloudinary (media) · WhatsApp Business Cloud API.
app/
(storefront)/ public storefront (Phase 4)
account/ customer auth + profile
client/ client/seller dashboard (Phase 3/6; role-gated)
admin/ super admin panel (Phase 10; SUPER_ADMIN-gated)
api/ route handlers
components/ ui · commerce · product · checkout · client · admin
lib/
db/ Supabase browser/server/admin clients (service-role: server-only)
auth/ roles, permissions, session
env.ts typed env access with clear guards
docs/db/ schema.sql (v1) + README
tests/ unit · integration · e2e (suites land with Phase 2+)
npm install
cp .env.example .env.local # fill in Supabase credentials first
npm run devScripts: dev · build · start · lint · typecheck (CI runs typecheck →
lint → build on every PR and on main).
First-time setup: create a Supabase project, fill .env.local, then apply
supabase/migrations/20261002150000_init_schema.sql (SQL editor or supabase db push).
Until then, pages degrade to setup notices instead of crashing.
Org: manohar-test123 (Stonebridge). Operating rules: AGENTS.md, GOVERNANCE.md,
REPORUNBOOK.md in the operator workspace.