George Clinkscales Jr.

Booking & Payment Flow

The booking confirmation flow is webhook-driven — Stripe fires a checkout.session.completed event after payment clears, which writes the reservation to Supabase and triggers the confirmation email via Resend. A failed or abandoned payment never creates a booking record. After payment, the success page fetches live booking details using the Stripe session_id from the redirect URL and displays the confirmed room, dates, nights, and total paid — no polling, no waiting. Five email flows run through Resend: booking confirmation, cancellation receipt with refund status, pre-arrival reminder sent 2 days before check-in, post-stay review request sent the day after checkout, and contact form notifications routed to the owner.

Automated Email Scheduling

Pre-arrival reminders and post-stay review requests run on daily cron jobs via cron-job.org (free, no Vercel Pro required). Each job hits a protected endpoint on the server with a shared secret header. The server queries the shared booking API for check-ins or checkouts matching that day's target date, then sends the relevant email through Resend for each matching reservation.

Guest Experience

Each suite has its own SEO-optimized URL (/rooms/coastal-suite, /rooms/garden-room, etc.) served by a single dynamic Express route. Room data, meta tags, the Open Graph image, and the canonical URL are all populated client-side from a JavaScript data map. Guests can look up any reservation at /my-booking using just their email and check-in date — no account required. The booking form pre-selects the room when arriving from a room detail page.

Demo Mode

A read-only demo mode makes the admin dashboard accessible from this portfolio without exposing write endpoints or requiring a login. The page detects a ?demo=true URL param and renders pre-seeded reservation and room data client-side, skipping all API calls for data loading. Every mutating action — status changes, form submissions, adding blocks, deleting rooms, saving API keys — is intercepted before it reaches the server and replaced with a toast notification. No demo session ever touches the database.

Cancellation & Refunds

Each reservation is issued a UUID cancel token at insert time. The confirmation email carries that token in a link — no guest account required, and the URL cannot be guessed or enumerated. When a guest clicks the link, the server checks the check-in date: cancellations made more than 48 hours before check-in receive a full refund processed automatically through the Stripe API. Cancellations within 48 hours fall under the hotel's standard policy — no refund is issued and the booking is marked cancelled in the admin.

Auth & Multi-Tenancy

The admin dashboard is protected by Supabase Auth with a rate-limited login endpoint and JWT validation on every protected route. The architecture is multi-tenant from day one — a single middleware reads an X-Tenant-Slug request header and scopes every database query to that property. When an owner saves a Stripe or Resend key via the dashboard, it syncs to both the tenant's local settings table and the shared platform API so checkout sessions and webhooks both use the client's own keys. Onboarding a second hotel means inserting a row and deploying a new Vercel project — no schema changes, no code forks.

SEO

Schema.org Hotel JSON-LD structured data on the homepage enables Google rich results. GA4 is wired to all public pages. Individual room pages have unique <title>, meta description, Open Graph, and canonical tags set dynamically per room.