Flexiibook: Multi-Area Booking Platform

Most booking systems treat your entire location as one calendar. Flexiibook recognises that real businesses operate multiple services in the same physical spaces with different rules, capacities, and customer access levels.

Area-Level Service Assignment

Traditional booking: “Arena available 9-5pm, max 6 people”Flexiibook approach:

• Arena → Lunging Service: 2 people max, members get priority slots
• Arena → Schooling Service: 4 people max, different pricing tiers
• Arena → Private Lessons: 1 person max, premium member exclusive hours

Each service gets its own schedule within the same physical area. The system prevents double-booking while allowing different services to operate with completely different rules.

Intelligent Schedule Conflict Prevention

Multiple overlapping schedules don’t create chaos—they create flexibility:Schedule A: Lunging Mon/Wed/Fri 9am-3pm (capacity: 2)Schedule B: Schooling Tue/Thu 10am-4pm (capacity: 4)Schedule C: Private lessons daily 6pm-8pm (capacity: 1)The system automatically:

• Prevents conflicting bookings across services
• Applies correct capacity limits per service
• Enforces membership restrictions per schedule
• Calculates appropriate pricing based on service type

Multi-Tenant Architecture

Every business operates in complete data isolation. Your customers, bookings, schedules, and payment processing exist in a separate tenant space. Zero cross-contamination between businesses using the platform.

Dynamic Availability Engine

No pre-built calendar grids. Time slots generate on-demand from recurring patterns:

• Real-time capacity checking across all active schedules
• Membership tier validation
• Volume discount calculations
• Time-based pricing application
• Area-specific blocked time enforcement

Complex Booking Rules

Handle scenarios that break simpler systems:

• Sole use restrictions: When one member type books, block others even if capacity remains
• Mixed capacity: Members get 3 slots, non-members get 1 slot, same time period
• Cascading discounts: Volume pricing across multiple bookings or per individual slot
• Membership-exclusive windows: Certain hours only available to specific member tiers

Permission Granularity

Staff permissions operate at feature level, not role level:

• View schedules but not modify them
• Manage bookings but not access customer data
• Create services but not assign pricing
• Handle cancellations but not process refunds

Technical Implementation

Built on multi-schema PostgreSQL with tenant-isolated data stores. Stripe Connect handles payment processing with platform fee distribution. AJAX-based interfaces prevent page reloads during booking flows.