Separating a sales record from an active guest
A booking received through a channel in HotelRunner does not mean the guest is physically at the property. Netyum One integration defines the distinction between a sales record and an active stay, so future, cancelled or no-show bookings are not misinterpreted in access decisions.
Test cases should cover more than successful arrivals. Cancellations, no-shows, date changes and directly created reservations help establish consistency across different record sources.
Where does Netyum One fit?
The hotel management system remains the source for stay operations. Netyum One Cloud Hotspot addresses guest access, while Analyzer provides a separate layer of network-event visibility. PMS integration does not replace reservation or accounting software. The relationship between systems is scoped for the deployed versions and modules.
Pre-project checklist
- Booking versus active stay
- Cancellation and no-show cases
- Consistency across record sources
How is the rollout organized?
Start by identifying the deployed version, network design and responsible people. Select a limited pilot and document expected results for both successful and unsuccessful scenarios. Plan the wider rollout after acceptance checks. Repeating the same examples after an update makes changes in behavior easier to recognize.
Let’s assess your setup
Share the product version, number of locations and your main operational priority. Together, we can define the integration scope and pilot steps.
