Skip to main content
AA
Back to selected work

Case study 02 · Independent product

Triplex E-commerce

An independently developed commerce platform combining a polished storefront with dependable content, identity, cart, payment, and inventory workflows.

Triplex E-commerce product interface
Role
Solo full-stack product engineer
Primary outcome
End-to-end commerce · Catalog, cart, checkout, and order history
Core stack
Next.js, TypeScript, Sanity

A premium wearable-commerce experience built as a complete product system


Product Goal

Triplex was built to demonstrate more than a storefront UI. The goal was to create a dependable commerce flow where content editors can manage products, customers can keep their carts across devices, and orders remain consistent through authentication, payment, and inventory changes.


My Role

Sole product and engineering ownership

  • Product and interaction design
  • Next.js application architecture
  • Commerce data modelling and Sanity Studio configuration
  • Authentication, cart, checkout, and order-history implementation
  • Stripe payment and webhook integration
  • Deployment, error handling, and production hardening

Engineering Approach

Content and Identity

  • Sanity manages products, categories, collections, and order content
  • Clerk provides authentication and protected customer order history
  • Dynamic metadata supports product discovery and shareable pages

Cart and Checkout

  • Zustand and local storage provide immediate client-side cart state
  • Upstash Redis persists carts across authenticated devices
  • Stripe handles checkout, with signed webhooks used to confirm payment events

Order and Inventory Reliability

  • Prices and stock are revalidated on the server before checkout
  • Duplicate-order protection prevents repeated payment events from creating multiple orders
  • Inventory updates are handled as part of the confirmed order workflow

Why This Project Matters

Triplex demonstrates full-stack product judgment: joining interface quality with content operations, secure identity, payment processing, persistent state, and defensive server-side validation.


Links