Butik

Context

Independent merchants and small multi-brand operators needed a way to run several storefronts from one account—catalog, branding, and orders—without bolting together a custom admin and a separate shop for every brand. Most “dashboard” demos stop at CRUD; real operators need publication controls, inventory-aware checkout, and APIs their own clients can consume.

My role

• Sole builder: product shape, data model, admin UX, public storefront, and commerce rules
• End-to-end ownership from auth/onboarding through order lifecycle
• Stack selection, schema/migrations, and production-minded API design (/v1 store-scoped routes)

What I shipped

• Business onboarding with Kinde auth and multi-store management under one business
• Per-store admin for products, variants, categories, colors, sizes, billboards, orders, and settings
• Public storefronts by slug: browse, cart, checkout, and themed appearance (themes, fonts, light/dark)
• Store-scoped REST APIs for catalog and orders so storefronts are not locked to a single UI
• Commerce policy layer: cart limits, stock handling, order confirm/cancel/expire transitions, and a cron path for expired orders
• Media uploads via Cloudinary; dashboard metrics with charts for ops visibility

Stack & architecture

Next.js 16 (App Router) + React 19 + TypeScript on the UI; PostgreSQL on Neon with Prisma 7 for the domain model (User → Business → Store → catalog/orders). Auth is Kinde; client data fetching uses Redux Toolkit; forms use React Hook Form + Zod. Admin lives under /business and /store/[storeId]; public shops under /[storeSlug]; APIs under /api/.../v1 keyed by store.

Outcomes

• End-to-end commerce path: onboard → create stores → publish catalog → themed storefront → place and manage orders
• Multi-tenant isolation at the store boundary (admin + API + public slug)
• Recruiter-facing signal: full-stack product work—schema, auth, admin UX, storefront UX, and defensive commerce rules—not a thin CRUD wrapper

Screenshot

Screenshot