Skip to content
Back to all projects
Freelancing Project

Orchid Boutique — E-commerce Storefront

A custom Shopify-alternative storefront for a boutique fashion brand, with headless CMS and Razorpay checkout.

Demo & repo links coming soon
Role
Freelance full stack developer (client engagement)
Timeline
2024
Status
Delivered — freelance engagement
Team
Freelance client engagement, 1 client stakeholder

Tools

Next.jsSanity CMSRazorpayTailwind CSSVercel
Orchid Boutique — E-commerce Storefront cover image

Overview

Dummy placeholder — freelance engagement to build a fast, custom storefront for a boutique fashion client who wanted more design control than Shopify themes allowed. Delivered a headless commerce setup with a CMS for the client to manage products and a streamlined checkout flow integrated with Razorpay for the Indian market.

The Problem

Dummy placeholder — the client's existing theme couldn't support the layout and content flexibility their brand needed, and they were paying for extra apps to patch gaps a custom build could handle natively.

Architecture

Frontend

Next.js storefront with ISR for product pages, styled with Tailwind CSS.

Content

Sanity CMS as the headless content source for products, collections, and marketing pages.

Checkout

Razorpay integration for payments, with webhook-driven order confirmation.

Hosting

Deployed on Vercel with edge caching for static product pages.

Key Features & My Role

  • Headless CMS integration so the client can manage the full catalog
  • Custom checkout flow with Razorpay payment integration
  • Sub-1s page loads via ISR and image optimization
  • SEO-tuned product pages driving a 3x increase in organic traffic

Video Walkthrough

Video walkthrough coming soon

Outcomes & Results

  • Dummy placeholder — sub-1s page loads on product pages, versus 3-4s on the previous theme.
  • Client went from editing theme code to managing the entire catalog through Sanity Studio.
  • Organic traffic grew roughly 3x within the first two months post-launch.

Reflection

Dummy placeholder — coordinating content modeling with a non-technical client was as much of the job as writing code. Getting the content schema right early saved a lot of back-and-forth later.