Farm Equipment Rental Platform

Small and marginal farmers rarely own the full set of machines their cropping calendar needs — a combine harvester is used a few weeks a year, a laser leveller even less — yet hiring one still runs on phone calls, middlemen and word of mouth. The result is familiar: machines sit idle in one village while a farmer ten kilometres away misses a sowing window, with no written record of the rate, dates or handover condition. This project builds the missing marketplace: a web platform where equipment owners list machines with per-day rates, photos and availability, and renting farmers search by machine type and location, check a live calendar, book, and pay online. Owners approve requests and track earnings from a dashboard; an admin verifies owner documents, approves listings and resolves disputes. The scope is deliberately bounded to what one student team can build and defend: relational data modelling, role-based access, a booking state machine, calendar logic and a real payment-gateway integration — the core of any marketplace product, applied to an agricultural problem the examiners will recognise instantly.

1. The renter opens the portal, signs up with a phone number and OTP, and searches equipment by machine type, location and date range; the frontend queries the backend's listing API with availability computed from existing bookings.
2. The backend (Node.js + Express) checks the requested dates against the bookings table — any overlap with a confirmed booking marks the machine unavailable — and returns only rentable machines with live per-day pricing.
3. The renter picks start and end dates on the availability calendar; the frontend totals rental days × rate + delivery fee + 5% platform commission and shows the bill before payment.
4. On "Pay", the backend creates a Razorpay order, the renter completes UPI/card payment in the checkout widget, and a webhook verifies the payment before the booking row flips from pending to confirmed.
5. The owner sees the request in their dashboard with renter details and rating, accepts it, and the dates are locked on the calendar so no second renter can book the same machine.
6. At handover both parties confirm machine condition with notes/photos in the app; on return the renter marks completion, the security deposit hold is released, and both sides leave ratings.
7. The admin monitors everything: new listings wait in the verification queue until owner ID and machine documents are approved, disputes are resolved against the handover evidence, and weekly payouts settle owner earnings minus commission.

Tech stack:

• React + Vite (responsive frontend)
• Node.js + Express (REST backend API)
• MySQL (relational database)
• JWT + OTP (phone-based authentication)
• Razorpay (payment gateway, test mode)
• Prisma ORM (schema & migrations)
• Redis (session & availability caching)
• Nginx + VPS deployment

• [Equipment listings with availability calendar] Owners create listings with machine type, power rating, per-day rate, photos, delivery radius and terms; a month-view calendar marks each date available, booked or blocked, so renters never request a machine that is already out.
• [Search and filters] Renters search by keyword, machine category (tractors, harvesters, tillage, sowing, sprayers, threshing) and location, with distance, price and rating sort — results update live without page reloads.
• [Booking flow with online payment] Date selection computes the rental total with delivery fee and platform commission; checkout runs through Razorpay (UPI, cards, netbanking) in test mode, and each confirmed booking gets an ID, receipt and cancellation window.
• [Owner dashboard] Pending booking requests with accept/decline, a listings table with live/paused status, booking history, an earnings chart and weekly payout summary after the platform fee.
• [Admin panel] Platform stats (users, listings, bookings, GMV), a verification queue where owner ID and machine documents are approved before a listing goes live, dispute tickets, and commission settings.
• [Ratings and reviews] Both sides rate each other after return; handover condition notes and photos are attached to the booking record to settle damage disputes with evidence.
• [Notifications and receipts] Booking confirmation, owner acceptance and payment receipts are generated for every transaction, with SMS/WhatsApp hooks kept as a documented extension point.
• Optional customization: UPI-intent or manual cash/UPI payment recording instead of Razorpay, multi-language (Marathi/Hindi) UI, per-hour pricing for harvesters.
• Future scope: native mobile app, GPS tracking of delivered machines, automated deposit release, crop-calendar demand forecasting.

• Complete full-stack source code (frontend + backend API)
• MySQL schema with migrations and realistic seed data
• Razorpay payment flow implemented in test mode with webhook verification
• Owner dashboard and admin panel as specified above
• Project report PDF (background, ER design, API documentation, booking state machine, testing)
• PPT presentation for final review
• Viva Q&A preparation document (auth, payments, concurrency, schema design)
• Deployment guide for VPS hosting