Workspace signup
Create an operator account and protected workspace.
Capability map
Every capability has a status. Every available claim needs a working route, acceptance coverage, and release evidence.
01 · Operator foundation
Secure account creation, tenant isolation, catalog setup, booking inspection, and role-aware operations are working locally. Team expansion remains later.
Create an operator account and protected workspace.
Sign in and recover access through the existing authentication foundation.
Account context fails closed before domain data is introduced.
Invite staff and select the active operating account explicitly.
02 · Inventory and pricing
Accommodation, activities, sessions, services, and add-ons share one authoritative availability and pricing foundation.
Venues, operating timezone, currency, contacts, policies, and controlled publication.
Sellable accommodation categories, optional physical-unit identity, and nightly capacity.
Reusable activities with one-off or scheduled local-time capacity.
Transfers, equipment, meals, treatments, and other optional booking items.
Server-authoritative prices, seasonal rules, restrictions, holds, and operational calendar evidence.
Required and optional items composed into one bookable experience; sequenced after the core.
03 · Direct booking
The isolated BookingBreeze iframe now supports local availability, authoritative quotes, capacity holds, booking creation, and a production-gated payment handoff.
Calculate the valid price and capacity on the server.
Protect the final place while checkout is active, then release it safely.
Use a responsive iframe with an optional resizing loader.
Stop at a production-gated boundary until verified provider events are available.
04 · Payments and guest journey
Payment, reservation, and fulfillment stay separate so operators can trust the status they see.
Secure account setup, obligations, attempts, financial facts, and provider-event inbox foundations exist; the real provider contract remains gated.
Local confirmation communications and deterministic previews use the same booking-status projection as the portal and backoffice.
A secure read-only guest booking status portal works locally; guest writes remain future work.
Append-only financial-event and payment-obligation foundations keep money separate from reservation state.
Expand the lifecycle after direct booking is proven.
Keep IDR authoritative while helping international guests understand an indicative value.
05 · Insight and ecosystem
Reporting and operational reliability come before channel breadth, public APIs, and advanced automation.
Revenue, occupancy, capacity, exports, audit trail, privacy, monitoring, and production hardening.
Packages, waiting lists, group pricing, transfers, applications, partner access, and gift cards.
Channel management, OTA synchronization, public API, webhooks, and external automation.
Early access
Create an operator workspace today. Live booking tools will be enabled as each workflow clears its release gate.
Create your workspace