Charter Booking, Payments & Marina Management

What I built

• Designed the data model covering vessels, availability, seasonal pricing rules and fee structures.
• Built the customer-facing web application and staff admin UI: availability search, multi-boat scheduling logic and analytics dashboards.
• Implemented Stripe Connect with refunds, commissions and multi-party payouts.
• Maintain and evolve the live Vue SaaS application, including CDN and cache-invalidation strategy.
• Ticketing module: passenger manifests with activity log and permissions, ticketing calendar, card payment on cash-only trips, captain check-in.
• Native captain app (Flutter): SMS/email login, auto-login, post-trip notifications and payment, mate tips.
• Charter rules engine: rule-builder wizard, conflict rules, multi-day charter types, make-up charters, booking cutoff overrides, auto-confirm, decline-to-reschedule notices.
• Payments: Payment Center redesign, manual payment types, refunds after payouts, payout reversal policy, deposit-forfeit payouts, Stripe Connect destination-charge dispute handling.
• Reservations & accounts: reservation edit/cancel/status fixes, minimum-advance-reservation settings, case-insensitive usernames across Company/Account/Client/Captain profiles (toward cross-marina customer accounts), admin fund-transfer UI with transfer log.
• Ops: recurring dependency audits, PostgreSQL 18 upgrade, RDS alerting, production outage root-cause work, Django 5.2 migration, notification worker → SQS microservice ADR, Twilio SMS compliance.