Project overview
What this project is and why it exists.
Built as a production storefront for a fragrance brand specializing in alcohol-free attar oils, combining a premium editorial feel with real commerce infrastructure.
A fragrance brand needing a fast, premium storefront with a checkout flow built for the Indian market.
End-to-end ecommerce platform covering catalogue management, cart and wishlist, checkout, and order fulfillment.
Business challenge
Balancing an immersive, animation-driven storefront experience with server-rendered performance, SEO, and a secure checkout flow.
Solution approach
Implemented server-side Razorpay order creation with HMAC-SHA256 signature verification, persistent cart and wishlist state synced across tabs, automatic pincode-to-address lookup, and full shipping address management at checkout.
Technical architecture
Next.js App Router with Server Components for product and category data, Prisma on Neon Postgres for orders, carts, and addresses, and Sanity CMS for catalogue and editorial content via GROQ with short-interval ISR.
Project gallery
A closer look at MS Signature Scents.
- Deliver fast, SEO-ready product and category pages
- Let the brand manage products and content without a redeploy
- Support a full Razorpay checkout with verified payments
- Payment flow needed to be signature-verified before order confirmation
- Product catalogue needed to stay editable by non-technical staff
- Full-stack architecture
- CMS and data modeling
- Payment integration
- UI and interaction design
Key features
- CMS-managed product catalogue with ISR revalidation
- Razorpay checkout with signature-verified payments
- Persistent cart and wishlist across sessions
- Real-time pincode lookup for address entry
- Full shipping address CRUD with default-address handling
Technical highlights
- Server Components for product/category data-fetching
- Prisma-modeled orders, carts, reviews, and addresses on Neon Postgres
- HMAC-verified payment confirmation
- Framer Motion scroll-driven product storytelling
Lessons learned
A premium storefront feel and a maintainable content layer are not in tension when the CMS and commerce data are modeled separately from the start.
Services connected
Solutions connected
Technologies connected
Case studies connected
CMS Integration: Building Flexible Content Management Systems for Modern Websites
How CMS choice — Sanity, Payload, or WordPress — is matched to a project's content complexity and technical requirements instead of defaulted to one platform for every build.
- Sanity CMS
- Payload CMS
- WordPress
Payment Gateway Integration: Creating Secure, Reliable, and Frictionless Online Payment Experiences
How Razorpay and Stripe checkout flows are built around server-side signature verification and webhook handling, so payment confirmation never depends on trusting the client alone.
- Razorpay
- Stripe
- Node.js
Transparency note
This page intentionally avoids fabricated metrics, testimonials, and timeline claims. If data is private or unavailable, it is not guessed.
Need a similar outcome?
Tell us your current challenge and we will map a practical path using the most relevant services and implementation approach.