The problem
The business needed a way to understand what was selling, what was trending, and how inventory was moving without exporting spreadsheets or relying on generic analytics tools that did not understand the domain.
Operations surface
Admin Dashboard
Analytics, inventory, and catalog management
Next.jsTypeScriptSupabaseReporting
A backend interface giving the business owner real-time visibility into sales, product performance, and catalog management.
Technical narrative
This is where the archive goes deeper than the homepage: architecture choices, operating constraints, and the decisions that make the product maintainable over time.
What it does
The dashboard surfaces sales trends, popular products, category breakdowns, and inventory alerts. The owner can manage products, update pricing, control featured collections, and configure seasonal promotions. Everything is designed around the questions a business owner actually asks.
Technical approach
Data flows from Supabase PostgreSQL through server-side queries that aggregate and shape metrics before reaching the client. The dashboard lives in the same Next.js application as the storefront, sharing data contracts and types rather than acting like a disconnected side tool.
Design philosophy
I prioritized information density without clutter. Key metrics are surfaced first, with drill-down available where it matters. The interface uses the same design system as the storefront, but the hierarchy is tuned for operational speed rather than browse-first storytelling.