FULL STACK / E-COMMERCE
Building the storefront and the operations behind it.
A premium scarf e-commerce platform built with Next.js 16, React 19, TypeScript, and Supabase, connecting product discovery and Cash on Delivery checkout with catalog, inventory, orders, and administration.
- CONTEXT
- MODEYA / MODÉYA SCARF
- CONTRIBUTION
- Freelance Full-Stack Developer
- PERIOD
- Mar 2026 – Jun 2026
- Next.js 16
- React 19
- TypeScript
- Tailwind CSS 4
- Supabase
- PostgreSQL
- Zustand
- Zod
The system behind the interface.
A storefront is one part of a commerce system. Customers need product discovery, a cart, and checkout; administrators need a consistent way to manage products, inventory, orders, and content. MODEYA connects these experiences through a shared database and authenticated access.
What I worked on.
- Developed a premium e-commerce storefront with product discovery, collections, product pages, a cart, and checkout.
- Designed the documented 18-table PostgreSQL schema and implemented role-based authentication with Supabase.
- Implemented Cash on Delivery checkout alongside inventory and order management.
- Built an admin analytics dashboard and management interfaces for store operations.
How the pieces connect.
An original diagram of the documented stack and application boundaries.
- 01Next.js + React
Storefront, customer account pages, and a role-protected administration area.
- 02Application layer
Server actions and route handlers support commerce and management workflows.
- 03Supabase
Authentication and PostgreSQL-backed data access connect the application to stored records.
- 04Commerce records
Products, variants, orders, order items, customer profiles, and related content.
Decisions and their tradeoffs.
Use a relational model for commerce.
Products, variants, orders, and order items have distinct responsibilities in the schema. Their relationships support both customer-facing flows and administrative work. The 18-table figure describes the documented project scope; the current source has expanded since that scope was recorded.
Make Cash on Delivery the checkout model.
The documented implementation uses Cash on Delivery instead of an online card-payment flow. This makes order capture and the subsequent operational workflow central to checkout, without implying that a payment gateway has processed a transaction.
Protect administration alongside customer access.
Supabase authentication and role-protected administration distinguish customer account features from store management. Authorization needs to be enforced where data is accessed, in addition to controlling which interface a user can see.
A clear review checklist.
- Product and variant selection, cart changes, checkout validation, and order confirmation.
- Customer authentication, authorization for administration, and access to customer-specific records.
- Inventory changes, order management, and consistency between storefront information and administrative updates.
What the project demonstrates.
The customer experience and operational data model need to agree on products, inventory, and orders.
A clear checkout model and explicit access boundaries make the system easier to reason about as storefront and administration features grow.