01
Reservations & active stays
Reservation code, arrival/departure dates, status, property and essential stay details.
Connected guest journey
Helios does not replace the PMS. It makes it more useful.
The integration transfers the necessary stay context from the PMS to Helios so the guest experience, services and automations work with less manual entry.
Integration architecture
From the reservation to the right experience.
The technical method is selected according to the PMS's real capabilities: an official cloud API, a secure local connector or a controlled import as fallback.
PMS
Reservations · Stays · Rooms
→
API / Connector
Secure mapping & sync
→
Helios
Guest context & automation
→
Guest & Teams
PWA · Admin · Operations
Important:
The exact scope of an integration depends on the endpoints, permissions and technical constraints of each PMS. This page presents an integration-ready architecture, not a supposed universal connection to every system.
Data flows
The data with real operational value.
The entire PMS does not need to be copied. Only the data required to activate guest journeys and services correctly is transferred.
02
Guest & companion context
Name, contact details, party size and permitted profile fields, with privacy and mapping rules.
03
Room assignment
Room number, room changes and property context for My Stay, requests, orders and internal routing.
04
Check-in / check-out events
Access activation or expiry, automated invitations and a clear lifecycle for each stay session.
05
Optional write-backs
Where supported by the PMS, notes, charges or operational statuses can be assessed under strict rules.
06
Group-level mappings
Mapping multiple hotels/properties, room codes, rate plans or source systems into one integration layer.
Deployment models
Cloud where possible. A connector where necessary.
Hotel PMS platforms do not all share the same architecture. Helios supports different integration patterns without exposing the hotel's internal network.
Direct connection through an official API.
OAuth/API credentials, webhooks or secure polling, with rate limits, mapping and retry policies.
A small service inside the hotel.
A Windows service or container that reads permitted data and communicates outbound with Helios without an inbound VPN.
A fallback without false promises.
Scheduled CSV/SFTP import when the PMS has no suitable API, with clear limits on frequency and data.
Reliability & security
An integration that can be monitored and supported.
- Idempotent sync to prevent duplicate stays or events
- Audit logs and monitoring of the latest successful synchronisation
- Retry queue and temporary storage when the connection is unavailable
- Mapping layer by PMS, property and room code
- Least-privilege credentials and encrypted transport
Health monitoring
Visibility into connector status, latency and failed records.
Data minimisation
Only the necessary dataset is transferred.
Safe rollout
A read-only sync pilot before any write-back.
Vendor-aware scope
The final scope is defined after an API assessment.
PMS assessment
First we assess the PMS. Then we promise an integration.
Technical discovery, access review, data mapping and a pilot plan before production integration.