Muebles San Francisco JYN: e-commerce in progress
An e-commerce project in progress for Muebles San Francisco JYN, built to extend the brand into real online sales. It includes authentication, cart, checkout, payments, and inventory control, plus dedicated rules for made-to-order products.
Challenge
Build the Muebles San Francisco JYN e-commerce with safe transactional flows, inventory logic by product type, and an internal operations layer that can handle orders and payments without state conflicts.
Solution
Implemented a modular domain-based architecture with transactional rules for checkout, cancellation, and payment confirmation. Added auth guards, rate limiting, and environment validation to harden day-to-day operations while the system continues to evolve.
Results
- Complete purchase flow from catalog to confirmed order
- Operational admin panel for day-to-day order/payment workflows
- Correct made-to-order behavior without hard stock blocking
- Monetary consistency by storing integer CRC values
- Scalable base for future catalog/shipping/promotion features
Technical details
Stack and technologies
- - Next.js 16 + React 19 + TypeScript
- - PostgreSQL + Prisma
- - better-auth (email/password plus optional Google)
- - Zustand for client state (cart, address, UI)
- - Zod validation
- - Tailwind + custom components + Radix
How it is organized
- - src/app: shop/auth/admin routes and layouts
- - src/features: domains (products, orders, payments, checkout, inventory, account)
- - src/shared: reusable UI and pure domain logic
- - src/lib: infrastructure (prisma, auth, env, email, rate limit)
- - Layering rules documented in ARCHITECTURE.md
Key modules
- - Orders: transactional place-order and cancel-order
- - Payments: confirmation/rejection with strict status guards
- - Inventory: product-level stock and made-to-order rules
- - Auth: requireAdmin/requireAdminAction guards
- - Checkout: address and verification step flow
Risks / technical debt
- - Status business rules may grow in complexity
- - External Redis dependency for auth rate limiting
- - Inventory concurrency needs continuous monitoring
- - Email/notification costs can scale with traffic
Need to build or improve a system?
I help turn the need into a clear technical direction and a clean execution plan.