Built to order

Wedding Vendor Discovery and Booking Platform

This project is a complete web application for discovering and booking wedding vendors — photographers, venues, decorators, makeup artists, caterers and planners — with verified profiles, transparent package pricing, reviews and a one-click enquiry system. Couples can shortlist vendors, track enquiry responses, and plan their spend with a budget-splitter tool. The vendor side manages enquiries and packages. It models a real two-sided marketplace for the wedding industry. Suitable for B.E./B.Tech final-year projects in Computer Science, IT and Web Development.

Wedding Vendor Discovery and Booking Platform — project thumbnail preview
More project photos (2)

The problem

Planning an Indian wedding means coordinating half a dozen vendors — photographer, venue, decorator, makeup, catering, planner — usually found through relatives' recommendations and negotiated over phone calls with no written quotes. Couples can't compare prices, reviews are word-of-mouth, and there's no record of what was promised. This project builds the marketplace that fixes it: vendor profiles with verified badges, package-wise transparent pricing, ratings from verified bookings, and an enquiry system where every conversation is tracked. A budget planner splits the total wedding budget across categories using standard industry ratios so couples see where the money goes. The build is a genuine two-sided platform — couple-facing discovery plus vendor-facing enquiry management — scoped to one region's vendor base so the data model stays explainable.

How it works

  1. Vendors are onboarded with a profile: category, city, description, packages with prices, and portfolio details.
  2. A couple searches by need ("wedding photographer in Pune"), filters by category and budget, and browses vendor cards with ratings.
  3. Opening a profile shows packages, inclusions, reviews and response-time stats.
  4. The couple sends an enquiry with event date, guest count and a message — free, no advance needed.
  5. The vendor replies through the tracked thread; the enquiry status moves from sent to viewed to replied.
  6. When terms are agreed, the enquiry is marked booked and joins the couple's shortlist.
  7. The budget planner keeps total spend visible across categories as decisions accumulate.

Tech stack:

  • HTML5 · CSS3 · JavaScript (ES6)
  • Node.js · Express
  • MySQL · relational schema design
  • REST API architecture
  • Responsive mobile-first UI
  • Full-text search indexing
  • Review aggregation logic
  • Git · version control
Parameter Value
User roles Couple, vendor and admin (design target)
Vendors supported Thousands per region (expected)
Categories 6 core wedding categories (extensible)
Search Keyword + category + budget filters (design target)
Page load Under ~2 s on broadband (design target)
Database MySQL with migration scripts and seed data
Deployment Shared hosting or VPS; no special hardware needed
Browsers Modern Chrome, Firefox, Edge, Safari (expected)

Project features

  • [Vendor discovery] Search vendors by keyword, filter by category (photography, venue, makeup, decor, catering, planning) and budget band.
  • [Verified vendor profiles] Profiles with ratings, review counts, city, service description and a verified badge for checked businesses.
  • [Transparent package pricing] Every vendor lists packages with inclusions and prices — no "call for quote" black boxes.
  • [Reviews from verified bookings] Star ratings and written reviews tied to actual enquiries, keeping feedback trustworthy.
  • [Enquiry management] Couples send enquiries with event date, guest count and message; every enquiry is tracked as sent, viewed, replied or booked.
  • [Budget planner] Enter a total budget and watch it split across categories by standard ratios, alongside the shortlisted vendors.
  • [Vendor response tracking] Median response-time stats per vendor set honest expectations before the first message.
  • [Shortlist dashboard] All enquired vendors in one table with their latest status — the couple's whole wedding in one view.

What is included

  • Complete source code: couple frontend, vendor dashboard, backend API and database schema
  • Database migration scripts with realistic seed data (vendors, packages, reviews, enquiries)
  • Setup and deployment guide (local + shared hosting/VPS)
  • Vendor onboarding guide
  • Project report PDF (problem, design, schema, testing)
  • PPT presentation for final review
  • Viva Q&A preparation document

Limitations & prerequisites

  • Payments between couples and vendors happen outside the platform; no escrow or payment gateway is included.
  • Vendor "verification" in the demo is a badge workflow — real-world GST/document checks are an operational process, not code.
  • Reviews are seeded as realistic samples; a production launch would need anti-fake-review moderation.
  • Availability calendars are per-enquiry rather than a live shared calendar.
  • The budget ratios are standard industry splits, adjustable — not financial advice.
  • One region per deployment; multi-city scaling is future scope.

Frequently Asked Questions

How is this different from a listing website?

Listings show names and numbers. This is a transaction platform: packages with prices, tracked enquiries with statuses, verified reviews and a budget planner — the whole decision loop, not just discovery.

How do enquiries work?

The couple fills event date, guest count and a message. The enquiry is stored with a status (sent → viewed → replied → booked) visible to both sides, so nobody's message disappears into WhatsApp.

Are the reviews trustworthy?

Reviews can only be left against a completed enquiry thread, which the schema enforces. The demo ships with realistic seeded reviews to show the feature working.

Does money change hands on the platform?

No — deliberately. Wedding bookings involve site visits and negotiations; the platform handles discovery-to-agreement, and payment integration is documented as future scope.

Is this project suitable for a final-year project?

Yes — for Computer Science, IT and Web Development programs. It demonstrates two-sided marketplace design, search and filtering, review systems and enquiry state machines — strong, modern web-development concepts. Suitable for B.E./B.Tech final-year projects in Computer Science, IT and Web Development.

Components & software requirements
  • HTML5 · CSS3 · JavaScript (ES6)
  • Node.js · Express
  • MySQL · relational schema design
  • REST API architecture
  • Responsive mobile-first UI
  • Full-text search indexing
  • Review aggregation logic
  • Git · version control
Delivery information

Built-to-order project. Delivery timeline is shared after order confirmation based on current queue.

Support terms

Complete documentation, setup guide, and viva preparation included. Support for setup and explanation provided.

Download abstract (PDF)

Related guides

All guides
Technical illustration of a cloud server pushing event envelopes outward to web application endpoints for payments, dashboards and chat.Web development and IoT students who have built a REST API or an ESP32 project and now need external services (payments, GitHub, messaging) to notify their app when things happen

Webhooks Explained: Receive Data from Payments, GitHub and IoT

A webhook lets a service call your server the moment an event happens — payments, code pushes, form submissions. This guide explains the event anatomy, HMAC signature verification, the fast-acknowledge reliability pattern, local testing, and how webhooks compare with polling, WebSockets and SSE.

Read guide
Illustration of Docker Compose orchestrating a full-stack application with frontend, API, database, and cache containers connected in one network.B.E./B.Tech Computer Science and IT students whose full-stack projects need a frontend, backend, and database running together and are tired of setup instructions that only work

Docker Compose for Full-Stack Projects

Stop juggling four terminals and setup docs that only work on your laptop. This guide builds a complete Docker Compose stack — frontend, API, database, cache — with annotated config, healthchecks, persistent volumes, and a dev/prod split that survives demo day.

Read guide
Illustration of a web page with a comment section: a shield filtering user input so scripts are neutralized into harmless text before rendering in visitors' browsers.B.E./B.Tech Computer Science, IT and Web Development students building web applications with user-generated content: comments, profiles, forums, dashboards

XSS Attacks Explained for Students

Cross-site scripting turns your comment section into code running in visitors' browsers. Learn the three XSS types conceptually, why browsers execute injected input, what it enables, and the defender's toolkit: output encoding, Content Security Policy, safe DOM handling, and hardened cookies. No payloads — prevention only.

Read guide
Get a quotation