Hospitality Architecture
Hospitality is organized into 11 subsystems sharing one database with the rest of Aeion. Availability tracking is the consistency boundary — every channel reads through it; every reservation writes through it. Channel sync orchestrates 18 OTA + GDS adapters with automatic failure detection and safe retries. Night audit runs the 12-step end-of-day close. The pricing engine, AI revenue forecasting, and demand scoring together power deterministic rule-based yield management.
System Map
`
Availability — the Consistency Boundary
Hospitality's central invariant: every booking path reads and writes through one shared availability check, so inventory never drifts between direct bookings and channel-sourced ones.
Channel Sync — 18-Adapter Orchestration
When a reservation is created, modified, or cancelled:
Night Audit — 12-Step Close
Each business day's close runs in strict sequence:
Pricing Engine + Yield Management
Three components work together:
Event Flow — Cross-Module Integration
`
AI Agent Layer
Three purpose-built AI agents:
FAQ
Each property has its own availability tracking and its own set of channel connections; reports aggregate cross-property. One tenant = one property group; multi-tenant for separate ownership groups.
Bookings for different room types or dates are processed independently and never block each other. We haven't published a specific simultaneous-bookings-per-second benchmark; talk to sales about load testing against your expected flash-sale traffic.
Pricing rules are evaluated instantly with no external calls on the booking path. The resolved rate is cached per room-type and date, refreshing automatically whenever occupancy changes — so flash-sale traffic reads a cached rate instead of recomputing on every request.
Via the Bridge module. Digital key issuance connects to your lock vendor; minibar sensors push events through Bridge; ID scanners feed guest profiles. If a device can't be reached, Aeion reports that plainly rather than pretending it worked.
Availability tracking is the single source of truth that every channel reads through, and a broken channel connection is automatically isolated (circuit breaker) so it can't affect the others. Same-room concurrent-booking races on the availability check itself aren't currently serialized with a lock — talk to your Aeion contact if you need a specific concurrency guarantee for high-contention inventory.
Rates in property's base currency; channel-specific currency conversion at OTA push time using configured FX rates (default ECB + OpenExchangeRates). Folio in property's base currency; guest payment in any currency.
All timestamps stored UTC; per-property timezone for display + business-day boundary. Night audit runs at property's local business-day-end.