The challenge
The brand needed a store that feels like a luxury boutique and that the owner can run without a developer, including launching and renaming seasonal collections.
- Checkout failed for real products: Stripe rejected the image URLs, and order totals showed 100 times too high
- The admin portal was unreachable because of a login redirect loop
- A compromised starter template injected hidden code into the build
- Customer order data and product images were not protected from public access
What I built
I normalised image URLs and moved all prices to consistent handling in pence (GBP), so Stripe Checkout accepts every product and totals are correct. Orders are confirmed by Stripe webhooks, not by the browser.
I restructured the admin routes so the login page sits outside the protected area, which ended the redirect loop. I then built database-driven collections (“drops”) and categories that the owner manages herself, with an editable homepage banner and collection pages generated automatically. The admin dashboard covers products, collections, categories, orders, enquiries, bespoke commissions and analytics, plus discount codes.
Security was part of the build, not an afterthought. I removed the injected code and the auto-run trigger that came with the starter template and audited every changed file. The admin is locked to a single verified account, customer order lookups are scoped to the signed-in user with Supabase row-level security, and public write access to storage is closed.
Architecture and stack
- Frontend
- Next.js 16 (App Router) · React 19 · TypeScript · Tailwind CSS 4 · Zustand · Framer Motion
- Backend
- Next.js API routes and Server Actions · Supabase (PostgreSQL, Auth, Storage, row-level security)
- Payments
- Stripe Checkout Sessions · Stripe webhooks
- Hosting
- Vercel · Custom domain with SSL
Outcome
The store takes real payments with correct totals, and the owner launches and renames collections, edits the homepage banner and handles orders, enquiries and bespoke requests without a developer. Customers get a wishlist, cart and a Patron Portal with their order history on any device.
The supply-chain lesson matters as much as the store: a starter template can carry hidden code that runs on build. Checking every file a template brings in is now a standard step in every project I start.
Last updated