Padel Booking Platform

Problem

The club needed more than a marketing website: players had to book courts, pay online, receive invoices and record match results, while operators needed reliable administration and visibility into day-to-day club activity.

Approach

I built a full-stack platform with a React frontend, a NestJS backend, PostgreSQL data model, payment and invoicing integrations, transactional email, admin workflows and Docker-based deployment.

Result

The platform runs as the club's live booking and management system, covering the customer booking journey, online payment, invoicing, match results, rankings and daily administration.

Decisions and trade-offs

• Built a custom booking product instead of forcing the club into a generic tool, because court availability, Hungarian invoicing and ranking workflows needed to fit the business.
• Kept frontend and backend separated behind an explicit API boundary so public booking flows and admin operations can evolve independently.
• Used PostgreSQL and Prisma for relational booking, payment, invoice and ranking data where consistency matters more than schema flexibility.
• Added admin surfaces for bookings, courts, users, invoices, gifts, statistics and ranking so operational work could live inside the product.