Project Overview The Beach Chair Operator System (OS) is a digital platform for managing daily operations of a beachfront seating service. It enables operators to assign, move, combine, and release beach chair sets, manage reservations, prioritise VIP/Owner guests, and generate occupancy and revenue reports. The OS will integrate with Clover POS terminals for payment processing. 2. Functional Summary The Operator OS must include the following key functions: interactive chair map, seat assignment and combination up to 10 sets, VIP priority logic, geofenced change enforcement, reporting dashboard with date filters, and integration with Clover POS. 3. Layout & Capacity • Two Sides: East and West • Five Rows per side • 25 Sets per row (each set includes 2 chairs and 1 umbrella) • Up to 10 contiguous sets can be combined per booking • Each set has a unique ID in format {Side}-{Row}-{Set} (e.g., E-1-07) 4. User Roles • Owner/Manager – full access, reporting, configuration. • Lead – operational control, refunds, and end-of-day close. • Operator – daily seating, combining, cancelling, marking OOS. • Auditor – read-only access for review and compliance. 5. Operator Interface The OS should be optimised for tablet use with large, high-contrast controls suitable for outdoor operation. Main map colours: Green (Available), Blue (Reserved/Checked-in), Orange (Seated), Red (Out of Service). VIP/Owner seats show a gold overlay. Primary operator actions: Scan, Assign, Seat, Move, Combine, Split, Cancel, Mark OOS, and Send Message. 6. Daily Workflow • Morning: log in, unlock Change Mode at Beach Hut (geofence or QR), reset all seats to Available, pre-stage VIP reservations. • During the Day: scan barcodes, seat guests, combine sets, move guests, cancel, mark OOS. • End of Day: release seats, sync Clover report, generate daily summary PDF, lock system until next open. 7. POS Integration The system integrates with Clover POS for payments. Operators can trigger a 'Charge in Clover' action, complete the payment on the terminal, and record the transaction ID in the system. The OS will store payment type, amount, tax, and tips for reporting purposes. Refunds and comps can be logged without requiring override pins. 8. Reporting and Analytics Reports must include filters for date range, side/row, booking source (Online, Walk-up, Concierge), and customer type (VIP vs Guest). Core KPIs: Occupancy percentage, Revenue per set per day, VIP share, Source mix, and Checked-in dwell time. Exports should support CSV and PDF formats for Daily and Weekly summaries.