Build Secure Euphoria Ticketing Platform

₹600-1500 INR

Posted 1 minute ago

•

Ends in 6 days

₹600-1500 INR

Paid on delivery

# PROJECT REQUIREMENT — EUPHORIA 2027 **Project:** Event Ticket Booking & Management Website **Event Name:** EUPHORIA 2027 **Theme:** Luxury Black & Gold **Languages:** English + Hindi **Platform:** Responsive Website (Mobile + Desktop) ## 1. Project Overview We want to develop a premium event ticket booking website for our New Year's event, EUPHORIA 2027. The website should allow customers to explore event details, select ticket categories, book tickets online, make secure payments, receive digital tickets with QR codes, and enter the event through QR scanning. Along with the customer-facing website, we need a complete Admin Dashboard to manage bookings, payments, ticket inventory, offline sales, staff and event entry. ## 2. Existing Project We already have a basic React prototype featuring: - Luxury black-and-gold design. - English and Hindi language toggle. - Event landing page. - Ticket category selection. - Demo booking modal. - Starter Supabase database schema. This is only a prototype. We need a developer to complete the backend and convert it into a secure, production-ready platform. ## 3. Customer Website Features - Premium, modern and responsive UI. - Event information, venue, date and timings. - Artist/performer details and event gallery. - Ticket categories: - General - VIP - Couple - Group - Early Bird - Live ticket availability and pricing. - Customer details form. - Secure Razorpay payment integration. - Booking confirmation. - Unique QR-based digital tickets. - Downloadable PDF tickets. - Automatic email delivery. - FAQ, Terms & Conditions, Privacy Policy and Refund Policy. ## 4. Admin Dashboard We need a complete admin panel with: - Total bookings. - Total tickets sold. - Total revenue and payment status. - Category-wise sales. - Remaining ticket inventory. - Customer and booking management. - Refund and cancellation management. - QR check-in statistics. - Staff management and permissions. - Sales reports and CSV/Excel export. ## 5. Offline Ticket Sales System We also sell tickets physically at counters. Admin/counter staff should be able to: - Create offline bookings. - Enter customer name and mobile number. - Select ticket category and quantity. - Record payment method and amount. - Generate tickets with unique QR codes. - Track which staff member made each sale. Online and offline sales must use the same database and inventory so that tickets cannot be oversold. ## 6. QR Scanner & Entry Management This is a very important feature. - Mobile camera-based QR scanner. - Individual QR code for every admission ticket. - Server-side QR validation. - One-time entry validation. - Prevent duplicate entry. - Show clear VALID, ALREADY USED and INVALID statuses. - Record entry time and staff member. - Admin can view all check-in records. ## 7. Technical Requirements Preferred technology stack: - Frontend: React / [login to view URL] + TypeScript. - Styling: Tailwind CSS. - Backend: [login to view URL] server-side APIs. - Database: Supabase PostgreSQL. - Authentication: Supabase Auth. - Payments: Razorpay. - QR generation and scanning: QR library / ZXing. - PDF generation: Server-side PDF generation. - Email: Resend or equivalent. - Hosting: Vercel or equivalent. Developer can suggest a better architecture if it meets all requirements. ## 8. Security Requirements - Server-side payment signature verification. - Razorpay webhook verification. - Secure database permissions and RLS. - Role-based admin and staff access. - Unique, unpredictable QR tokens. - Atomic one-time QR check-in. - Prevent duplicate bookings and overselling. - Keep API keys and secrets on the server. - Maintain payment, booking and check-in audit logs. ## 9. Important Deliverables We expect: 1. Complete responsive website. 2. Working customer booking system. 3. Razorpay integration. 4. Complete admin dashboard. 5. Offline counter sales module. 6. QR ticket generation and scanning. 7. PDF ticket generation. 8. Email confirmation and resend functionality. 9. Secure database and backend. 10. Production deployment. 11. Source code and setup documentation. 12. Testing and bug fixing before launch. ## 10. Developer Proposal Please share: - Your experience with React/[login to view URL] and Supabase. - Examples of similar projects you have built. - Estimated development timeline. - Total development cost with milestone-wise breakdown. - Hosting and third-party service costs separately. - Post-launch maintenance and support details. **Important:** We already have a starter project. We want to build on it rather than unnecessarily redesign everything from scratch. The final product must be a fully functional, secure and production-ready event ticketing platform, not just a frontend design or demo website.

Project ID: 40830445

About the project

1 proposal

Open for bidding

Remote project

Active 34 secs ago

Place your bid

Bid amount Email address

Benefits of bidding on Freelancer

Set your budget and timeframe

It's free to sign up and bid on jobs

1 freelancer is bidding on average ₹890 INR for this job

User Avatar
Flag of INDIA

The main challenge in EUPHORIA 2027 is keeping online bookings, counter sales, payments and event entry consistent: every flow must respect the same ticket inventory, and each issued ticket must remain uniquely verifiable. The existing React prototype and Supabase starter schema provide a foundation, but the booking and check-in workflows need secure server-side handling before they can support real sales. I’d build on the current prototype rather than replace its black-and-gold experience or English/Hindi toggle. Booking and offline sales should both reserve and decrement inventory through trusted backend operations, with payment confirmation verified server-side before tickets are issued. Each ticket would have a unique QR value, and check-in should validate it against booking status to prevent duplicate entry. Razorpay webhooks, booking states and failure cases need clear handling so a delayed or unsuccessful payment does not create an apparently valid ticket. Admin access should follow staff permissions, with reporting and exports based on the same booking records. I’d connect the customer pages and dashboard to reusable UI components and a consistent data layer, keeping server-owned booking/payment data separate from temporary interface state. Responsive layouts, loading and error feedback, PDF/email delivery, and the mobile camera scanning flow all need to work across the complete customer and staff journey. I’d also keep the bilingual interface coherent as event details, policies and booking confirmations are added, and deliver the implementation with readable, maintainable code and clean Git changes. Can you share the current Supabase schema and confirm whether the Razorpay webhook configuration is already available?

内容来自 Freelancer News,版权归原作者所有。

阅读原文 ↗

用 HomepageTab 新标签页关注 RSS,打开浏览器就能看到更新。

安装 HomepageTab