Case study
HappiBuys / ZCOM
Full commerce stack: customer site, admin, Node API, payments, and catalog ingest.
Live (store and admin); collector Scaffold- Next.js
- Express/TypeScript
- Prisma
- MySQL
- FastAPI
- PostgreSQL
- Celery
- Redis
- Razorpay
- AWS S3
Problem
A store needs products, variants, orders, and admin — plus a way to fill the catalog from live shop pages instead of typing SKUs by hand.
What exists
- Customer web app: Next.js
- Admin: Next.js — product tools including background removal
- API: Node 18, Express, TypeScript, Prisma, MySQL, AWS S3, Razorpay
- Catalog collector: Next.js + FastAPI + PostgreSQL + Celery + Redis — root URL → discover products → images → user JSON schema → PostgreSQL / JSON / Google Sheets. Design principle: Access → Extract → Transform → Store → Sync. Never Bypass.
- Sheet mapping is the real HappiBuys catalog shape: zcom_stock + zcom_stock_variants (SKU, productName, brand, category tree, prices, images)
Architecture
Animated diagram of the system from documented facts.
Stack
- Next.js
- Express/TypeScript
- Prisma
- MySQL
- FastAPI
- PostgreSQL
- Celery
- Redis
- Razorpay
- AWS S3
Status
Live (store and admin); collector Scaffold
Customer and admin frontends are live on Vercel (Ready). Collector Phase 1 is scaffolded — not claimed as any-site fully automated production crawl.
Catalog in. Store live. Schema yours.