Featured project
Back to workKhetiValah
Agriculture marketplace — booking and payments on the web
01 — Overview
Listings, stall booking, Razorpay checkout, and GST billing for vendors, sponsors, and participants.
KhetiValah on the web is the production platform for agricultural marketplace and event participation. Mobile is a separate client — this case study covers the web application.
02 — Problem
The product had to hold up as a connected workflow.
The business needed a web product where different roles could book, register, pay, and manage catalogs — with Razorpay and billing treated as part of the real workflow, not an afterthought.
03 — My role
What I owned.
Frontend Product Engineer — Frontend Product Engineer on the KhetiValah web application — marketplace UI, booking flows, payments, and API integration. Primary frontend and UI/UX engineer, with other developers also involved. Backend was handled separately; I contribute there when needed.
04 — Product flow
The path a user actually takes.
I built the web client around the business journeys that actually generate revenue and participation — discovery, booking, payment, billing, and post-payment visibility.
Conceptual product flow for this domain — not a literal system diagram.
05 — Engineering
Decisions worth explaining.
Keep booking, payments, and billing as connected workflows.
Use a shared API layer across marketplace and event modules.
Present role-specific UI without duplicating the entire application.
05.1 — Architecture
How the pieces sit together.
06 — Challenges
What shaped the build.
Multi-role booking and checkout
Vendors, sponsors, and participants follow different booking paths, but all converge on shared payment, billing, and order visibility requirements.
Razorpay and billing together
Payment success, GST-related billing, and order state had to stay aligned across the UI and multiple backend responses.
Marketplace data on the web
Listings, availability, early-bird offers, and stand types required transforming API-shaped data into usable booking and catalog interfaces.
Booking reconciliation
Returning users needed previously selected stalls and order lines reflected accurately when they resumed a booking flow.
07 — Outcome
What shipped.
Production
Production web application — marketplace, booking, and payment workflows
Qualitative — no performance or business metrics are claimed here.
A production web platform connecting agricultural marketplace discovery, booking, Razorpay payments, and billing workflows.
Production web application with real payment and booking integrations. Mobile companion app is documented separately under Khetivala App.
In the product
React and TypeScript web application
Role-aware routes and feature modules
REST API integration with marketplace and event services
Razorpay payment UI and status handling
GST billing and invoice-related screens
Stall booking and registration workflows
Catalog, Early Bird Offers, and Stand Types modules
OTP authentication on the web
Frontend integration with Spring Boot / AgriEvents REST APIs. Backend service ownership is not claimed.
08 — Learnings
I built the web client around the business journeys that actually generate revenue and participation — discovery, booking, payment, billing, and post-payment visibility.