Skip to content
Selected work

Case study 03 / 04

YUCA

Independent contract · built and maintained by me

An e-commerce platform for handcrafted, sustainable home objects — built and maintained end to end.

Role
Independent Contractor — full-stack engineering and product ownership
Timeline
February 2025 – Present
Stack & tools
MongoDB · Express · React · Node.js · Razorpay · Cloud infrastructure
YUCA home page: the ‘New for you’ carousel of coconut-shell bowls and candles

I build and maintain YUCA's commerce platform on the MERN stack: catalogue, shopping experience, checkout, payments, logistics integration, infrastructure and performance.

01

Overview

YUCA is a lifestyle brand making mindful objects from natural and discarded materials — coconut-shell bowls, hand-poured candles — rooted in Indian craft. The brand's language is quiet: “for those who chose slow over speed, meaning over noise.”

I'm the engineer behind the store. I built the platform and continue to maintain it: the backend, the frontend, the catalogue and shopping experience, billing and payments, the logistics integration, infrastructure and deployment, and ongoing performance work.

02

Context

A small brand selling a small, carefully photographed catalogue. The products are tactile and photographic, so the store has to feel like the brand — dark, warm, editorial — while still behaving like a dependable shop: accurate prices and stock, a checkout people trust, and orders that reach a courier.

There is no engineering team behind it. Whatever gets built has to be maintainable by one person and cheap to run.

03

Problem

Off-the-shelf themes either looked generic or fought the brand's visual direction. The business needed its own storefront and back office: a catalogue it controls, a checkout with Indian payment methods, and a dependable path from a paid order to a shipment.

  • Present a premium, image-led brand without making pages slow.
  • Keep the shopping flow short and familiar: discover → product → cart → checkout → pay.
  • Connect payments and logistics so an order moves through the business without manual re-entry.
  • Build something a single engineer can run, deploy and improve.

04

My role

Independent contractor, responsible end to end. I own the technical decisions and the implementation, and work directly with the brand on what the store needs next.

  • Backend development — Node.js / Express APIs and MongoDB data models.
  • Frontend development — the React storefront, product catalogue and shopping experience.
  • Billing and payment integration (Razorpay checkout).
  • Logistics partner integration for order fulfilment.
  • Infrastructure, deployment and ongoing maintenance.
  • Frontend performance optimisation and database query optimisation.

05

Approach

I treated the store as a product rather than a website: start from the purchase journey, keep each step doing one job, and let the photography carry the brand. The interface stays restrained — serif display type, warm neutrals, generous imagery — and the commerce mechanics underneath stay conventional so nothing about buying feels unfamiliar.

06

User experience

The journey is deliberately short. Every screen below is the live store.

Browsing and discovery

The home page opens on a full-bleed film of the product, then the brand statement, then a ‘New for you’ carousel and category stories for Bowls and Candles. Category pages lead with a single hero object and a simple grid — the catalogue is small, so curation matters more than filters.

YUCA home page hero: a coconut-shell bowl with honey, and the line ‘For those who chose slow over speed, meaning over noise’
YUCA home page hero: a coconut-shell bowl with honey, and the line ‘For those who chose slow over speed, meaning over noise’
YUCA mobile home page with the YUCA Lifestyle wordmark
Mobile

Product detail

A split layout: photography on the left, decision-making on the right — name, price with the original price struck through, a stock signal when inventory is low, a one-line description, quantity, and two clear actions (Add to cart, Buy now). Shipping and secure-checkout reassurance sit just below.

YUCA product page for the Mahapatra bowl showing price, stock notice and add-to-cart
YUCA product page for the Mahapatra bowl showing price, stock notice and add-to-cart
YUCA product page on mobile
Mobile

Cart and checkout

The cart (‘Your selection’) keeps quantity editing and an order summary — subtotal, savings, shipping — side by side. Checkout is a single page: contact, shipping address and payment method on the left, the order summary and one ‘Pay’ action on the right, with the accepted methods (UPI, cards, RuPay, net banking) shown before the customer commits.

YUCA secure checkout page with contact form and order summary
YUCA secure checkout page with contact form and order summary
YUCA cart on mobile
Mobile
YUCA cart page with order summary and proceed-to-checkout action
YUCA cart page with order summary and proceed-to-checkout action

07

Design decisions

  • Let photography lead. Product imagery is large and dark-backed so the objects glow; interface chrome stays small and quiet.
  • Keep commerce conventions intact. Cart icon top-right, price under the name, one primary action per step — the brand is distinctive, the mechanics are not.
  • Show trust before payment. Accepted methods, free-shipping threshold and secure-payment notes appear before the customer reaches the payment step.
  • Use honest urgency. The low-stock notice only appears when stock is actually low, because it reads directly from inventory.
  • Make mobile first-class. Navigation collapses to search, account, cart and menu; product imagery stays full-width.

08

Technical implementation

A MERN application: a React storefront talking to a Node.js / Express API backed by MongoDB, deployed on cloud infrastructure. Razorpay handles payment collection (UPI, cards, net banking, wallets); a logistics partner integration hands paid orders on for fulfilment.

  • Catalogue, categories, inventory and orders modelled in MongoDB and served through REST endpoints.
  • Checkout creates an order server-side before payment and confirms it only after the payment is verified — the client is never the source of truth for price or payment status.
  • Inventory is tracked per product and surfaces on product pages as a low-stock notice.
  • Paid orders are passed to the logistics partner so shipping doesn't depend on manual re-entry.
  • Frontend performance work on an image-heavy storefront, and query/index optimisation on the database side.
  1. 01

    React storefront

    Catalogue, product, cart, checkout

  2. 02

    Node.js / Express API

    Products, inventory, orders

  3. 03

    MongoDB

    Catalogue, stock, customers, orders

  4. 04

    Razorpay

    UPI, cards, net banking, wallets

  5. 05

    Logistics partner

    Paid orders handed on for shipping

Request path for a purchase — simplified.

09

Key challenges

  • Image-heavy pages that still load quickly — the brand depends on large photography and film.
  • Keeping cart, stock, order and payment state consistent between browser, server and payment gateway.
  • Integrating third-party payment and logistics services so failures are recoverable rather than silent.
  • Running production as a one-person team: deployment, monitoring and fixes all sit with me.

10

Outcome

YUCA is live at yucalifestyle.com and takes real orders through its own catalogue, cart, checkout and Razorpay payment flow. I continue to maintain and improve it. I haven't included sales or traffic figures here — the case study focuses on what was built and how.

11

What I learned

  • Owning every layer changes how you prioritise: a small UX fix and a slow query can matter equally to the business.
  • A brand-led interface and a conventional commerce flow aren't in tension — the restraint is what makes the photography land.
  • Payment and logistics integrations deserve more design time than they look like they need; edge cases live there.

Next case study

NKNZ Studio