Skip to archive
Abhay Rohit
Back to archiveSelected study / 03

Vastraveda

A storefront for customers. A workspace for family.

My role

Product and engineering builder for the family saree business.

Project status

Public storefront · shop operations and live payments under review.

Concept poster for Vastraveda with vermilion and indigo fabric folded through a clear display form. The headline reads “Craft, carried into commerce.” It identifies storefront and family operations work. The fabric is illustrative campaign artwork, not exact catalogue photography or proof of stock.
Original conceptual campaign artwork · October 2026. A visual metaphor for this study; project evidence follows below.
01 / Context

The idea behind the work.

Vastraveda is a family saree business, and the product work starts with everyday use. I built an editorial storefront alongside a family panel for catalogue and shop operations. Reusing a previous product as a starting point, ordering photographs and seeing what still needs review make repeat entry easier to understand. On the customer side, cart persistence keeps the journey coherent. The source also records payment attempts, inventory holds and recovery states separately. The story I can show today is the design and implementation of those workflows, supported by dated captures and a public storefront. Real sales, exact catalogue readiness and live payment acceptance require their own evidence.

02 / Engineering & design

What I chose.
And why.

Moving a home-run saree business online creates work on both sides of the screen: shoppers need clear products and a consistent cart, while family members need a practical way to add pieces, order photographs and manage shop work.

  1. Design the editorial storefront together with a phone-first family operations panel.

  2. Support repeatable catalogue entry through templates, ordered photos and distinct review/publish steps.

  3. Use persistent cart state and source-backed payment/inventory records, keeping hosted release, catalogue review and live payment acceptance distinct.

03 / Supporting media

Closer to the source.

Dates and capture context are preserved with the media.

Dated Vastraveda family dashboard product-entry capture, with reusable product templates, photo ordering, blank catalogue fields and a storefront preview.
Supporting image 1: family product entry, 19 September 2026.Historical live-production admin capture; no customer details
Dated Vastraveda family product list showing six Live catalogue rows with thumbnails, prices and stock indicators. This is an interface snapshot, not a claim of current stock accuracy.
Supporting image 2: family catalogue interface, 19 September 2026; current stock not asserted.Historical live-production catalogue interface capture
04 / Evidence

What the work shows.

The public storefront returned HTTP 200 on 9 October. The September launch checkpoint records cart-persistence, build and live-header checks; the newer September 19 portal audit shows six Live products and 28 gallery images. Source includes server-priced quotes, purchase intents, inventory holds and separate financial state. No sales results or live payment/refund acceptance is asserted.

05 / Boundaries

Where I keep the distinction.

Product imagery needs exact-product review: AI-assisted views cannot establish material, stock or quality. Source implementation, the hosted storefront and live payment/refund acceptance are separate states. No sales outcome is claimed.

Implementation / Independent project

From interface
to infrastructure.

Role
UI design & frontend engineering
Core stack
React · TypeScript · Vinext
Platform
Cloudflare Workers · D1 · R2
Payment integration
Razorpay checkout & verification

Behind the interface

A clear path
to an order.

Customer actions and server responsibilities meet at explicit states.

  1. 01 / CustomerChoose a saree

    Responsive gallery, availability and a bag saved when browser storage is available.

  2. 02 / ServerConfirm the quote

    Current prices, delivery checks and availability.

  3. 03 / Server & payment providerComplete payment

    Stock reserved before Razorpay opens, with the existing order retained for recovery.

  4. 04 / Server & familyVerify, then fulfil

    Verified payment, guarded stock changes and an order dashboard.

The browser’s bag is a convenience. The server confirms the amount and availability before payment.

Engineering evidence

Built to be
examined.

  • Image delivery: original uploads are retained, with WebP derivatives for product cards and galleries. Older uploads use their originals until reprocessed.
  • Resilient state: local tests cover storage failures, checkout recovery, stock concurrency and refund rules, including out-of-order provider updates. When browser storage is blocked or full, bag changes remain usable on the current page; persistence across reloads or navigation requires available storage.
  • Publishing controls: draft products, explicit factual confirmation and revision checks protect shared edits and active checkout holds.
  • Search readiness: product metadata, structured data, sitemap and merchant feed share a deliberate publication gate.
  • Optional measurement: a consent-based, first-party event ledger counts shopping actions without customer or order information.

The supporting images on this page are historical captures. Automated tests cover the commerce and recovery rules; physical-device and live-payment verification remain separate checks. I do not claim measured conversion or Core Web Vitals improvements.

Contact Me

Abhay Rohit — portfolio index