TravelnFlex
A trust-first travel marketplace for discovering, comparing, and booking packages from verified travel agencies.
Project / travelnflexLive productThe problem and product context.
Travel planning in India often depends on WhatsApp messages, Instagram pages, phone calls, and fragmented agency information. That makes it difficult for travellers to assess agency trust, compare packages, understand pricing, confirm availability, and find reliable support.
TravelnFlex centralizes discovery, comparison, booking, payment processing, verification, and customer-support technology in one trust-focused marketplace.
TravelnFlex provides the marketplace and supporting technology; verified agencies remain responsible for delivering the trips.
- Travellers and families searching for Uttarakhand packages
- Solo and group travellers
- Verified travel agencies and agency administrators
- Travel guides
- TravelnFlex operations and support teams
What I contributed.
Full-stack Product Engineer
I contributed across the customer marketplace and operations platform. This was a collaborative project, so these areas represent my work rather than sole ownership of the complete platform.
- 01
Improved the customer homepage and travel-discovery experience.
- 02
Built and refined destination, activity, search, filtering, pricing, and responsive booking interfaces.
- 03
Improved customer login, registration, password recovery, and account-reactivation experiences.
- 04
Enhanced package booking, confirmation, booking-detail, receipt, and invoice flows.
- 05
Integrated optional activities as package add-ons instead of a separate booking path.
- 06
Strengthened booking expiry, payment status, notification, and customer-communication flows.
- 07
Implemented and hardened contact, support inquiry, cancellation, refund, and activity-issue workflows.
- 08
Improved agency onboarding, validation, departure, guide, and booking-management experiences.
- 09
Improved mobile responsiveness, accessibility, error handling, loading states, and design consistency.
- 10
Implemented the blog content model, listing experience, article interface, and supporting content tools.
- 11
Maintained architecture, workflow, testing, and product documentation.
How the system is shaped.
Product surfaces
- Customer website for public discovery, booking, payment, profiles, wishlists, reviews, and notifications
- Operations platform for admin, agency/vendor, and guide workflows
- Independent server APIs for each Next.js application
- A shared PostgreSQL database for common marketplace records
Technology
- Next.js 15 App Router, React 19, and TypeScript
- PostgreSQL with pg and server-side API validation
- NextAuth with JWT-based sessions and role-based authorization
- Razorpay for payments and refunds
- Cloudinary for image storage and Pusher for real-time notifications
- Nodemailer for transactional email and React PDF for receipts and invoices
- Tailwind CSS, Material UI, Headless UI, and Radix UI
System boundaries
- Customer and operations applications have separate interfaces, routes, sessions, and responsibilities.
- Browsers access business data through server APIs rather than connecting directly to the database.
- Authorization is enforced on the backend, not only through hidden controls or client-side checks.
- Confirmed bookings preserve a booking-time snapshot of prices, taxes, discounts, activities, inclusions, and cancellation terms.
Challenges and engineering decisions.
Trust versus marketplace growth
Agencies needed a practical route to publication without weakening customer confidence.
Make verification status, transparent package information, and responsible publishing core product principles.
Two applications sharing business data
Customer and operations teams require the same booking records but have very different workflows.
Use two independent full-stack applications with explicit boundaries and a shared PostgreSQL database.
Booking and inventory complexity
Shared travellers consume seats, while private groups may reserve an entire departure.
Support shared-seat and exclusive-departure allocation with temporary holds, payment confirmation, expiry, and cancellation release.
Financial consistency
Package pricing may change after a customer has confirmed a booking.
Preserve booking-time financial snapshots so the confirmed customer agreement remains stable.
Payment reliability
Webhook retries, late payments, and duplicate requests can create inconsistent booking states.
Use idempotent payment records and explicit booking and payment lifecycle states.
Optional activities
A separate activity date and checkout introduced unnecessary complexity.
Treat activities as package add-ons that inherit the selected package travel date.
Security and privacy
Customer records, booking codes, agency access, and support cases contain sensitive information.
Apply server-side ownership checks, scoped sessions, rate limiting, safe redirects, and role-based access controls.
Current outcome.
The current result is a production-facing foundation for a trust-focused travel marketplace.
- Responsive public website and trust-focused brand positioning
- Package and activity discovery interfaces
- Customer authentication and account workflows
- Booking, payment, receipt, and invoice infrastructure
- Customer support and issue-management workflows
- Agency, guide, and internal operations platform
- Editorial travel blog and SEO-oriented content system
- Documented architecture and business boundaries
The source repositories are private, and no verified conversion, revenue, booking-volume, or active-user metrics are available for publication.
Public evidence and links.