Merky FC HQ

Merky FC HQ required a booking engine that could handle fundamentally different venue types — football pitches with shared-pitch configurations, music studios with session-based pricing, and game rooms with capacity controls — within a single unified system. The complexity is not just in the variety of venue types but in the interaction between them: membership tiers that apply discount rules differently across venue categories, booking windows that vary by venue type and member status, and queue logic that must account for both priority access and capacity constraints simultaneously.

The shared-pitch configuration was the most technically involved aspect of the booking engine. A football pitch can be booked as a full pitch or as two half-pitches simultaneously by different groups — which means the availability model must track bookings at the sub-venue level and aggregate them correctly when checking full-pitch availability. A half-pitch booking affects full-pitch availability; a full-pitch booking blocks both half-pitch slots. Getting this constraint logic right required careful data modelling and thorough testing against edge cases where partial bookings overlap in time.

The membership and pricing system was built to be fully configurable from the admin panel without requiring code changes. Each membership tier can have custom pricing multipliers per venue category, priority booking windows that open earlier than standard availability, and capacity reservations that hold slots for members before they become visible to general users. Holiday blocking and admin override scheduling were built as first-class features rather than workarounds — administrators can block specific dates, time slots, or entire venue categories across the calendar, with those blocks immediately reflected in booking availability.

Savyasachi Infotech's relationship with Merky FC goes beyond the initial build. We handle ongoing maintenance for both Merky FC and Merky FC HQ as connected platforms, managing updates, feature additions, and infrastructure stability as the initiative grows. This long-term partnership model is how we approach most of our client relationships — staying involved through the full lifecycle of the product rather than handing over code and stepping away.