SAKZIN

A complete e-commerce experience for SAKZIN, combining product discovery, wishlist, cart, checkout, customer accounts, and operational tools for managing products and orders.

A branded storefront connected to the everyday operations of a single-store commerce business.

SAKZIN brings a home-and-lifestyle brand online through a complete shopping experience. I approached it as two connected products: the storefront a customer uses to discover and buy an item, and the operational workspace a store owner uses to keep products, stock, payments, and orders understandable.

The live storefront includes category discovery, new arrivals, best sellers, product search, wishlist access, a cart drawer, and customer-account navigation. The broader project scope connects these pages with checkout and store administration.

An e-commerce site is more than a grid of product cards. The choices a customer makes must still make sense when an operator reviews the order. Product variants, available quantities, guest orders, registered customers, manual orders, and payment review all affect that continuity.

The challenge was to keep the shopping interface approachable while retaining enough structure for practical store operations.

1. Browse catalog.
2. Choose product and variant.
3. Cart and checkout.
4. Order and payment review.
5. Fulfillment and tracking.

The flow above describes the product journey. The following sections explain the implementation and the boundaries of this case study.

The project uses a Next.js application with Supabase as the backend foundation. The associated commerce implementation documents Server Components as the default, server-side handling for sensitive business rules, migration-based schema changes, and inventory ownership at the variant level.

The single-store model keeps each deployment focused on one business. It is a reusable architecture for individual stores rather than a shared multi-tenant marketplace. This matters because catalog ownership, staff permissions, and operational configuration stay within one store boundary.

A useful domain distinction is the difference between a person and an order: an authenticated order can link to a customer, while guest and manually entered orders still need a valid operational lifecycle.

Technology stack

A manually operated commerce MVP can provide useful business workflows without immediately adding automated courier integration, accounting, or a marketplace model. Those are separate concerns with their own operational cost.

The live homepage was verified during this review. The portfolio review did not place a real order or execute a real payment. Feature breadth should therefore be distinguished from a fresh end-to-end transaction audit.

Commerce quality depends on the continuity between the storefront and the order desk. A polished shopping page matters, but the operator must be able to understand what was purchased, which variant it refers to, and what still needs attention.

Open the application