← All guidesHOTEL INTEGRATIONS

Hotel PMS and guest WiFi integration checklist

Plan hotel WiFi integration with your PMS: check-in, checkout, stay extensions, room changes, OTP verification and recovery testing.

Define what the hotel wants to automate

Hotel PMS integration connects the stay recorded in the hotel management system to guest WiFi entitlement. The first decision is which event should create, extend or end access. A booking being created may not mean the guest has arrived; confirm whether actual check-in is the trigger.

Write the intended reception workflow before choosing an interface. For example: an eligible check-in creates access until the planned checkout time; an approved extension updates that entitlement; checkout ends it according to the hotel’s agreed policy. These are acceptance criteria to configure and verify, not behaviours to assume for every connector.

Identify the product, version and access route

Record the PMS vendor, exact product and version, cloud or on-site deployment, property identifiers and the available API or interface licence. Confirm whether the hotel can authorise access directly or needs a vendor or partner onboarding process.

Hotels may use products such as eZee/Yanolja Cloud Solution, Hotelogix, IDS Next, Oracle OPERA, Cloudbeds or Mews. These names identify systems to discuss during a compatibility assessment; they do not establish that every product edition has the same interface or that a particular WiFiMitra connector is enabled at your property.

For example, Oracle’s hospitality integration platform exposes OPERA Cloud APIs and business events, while Cloudbeds documents reservation webhooks. Access conditions and event meanings must be checked against the installed product.

Map the stay lifecycle

Events to agree with reception and the integration team
EventDecision to record
Check-inWhich stay becomes eligible, when access starts and how guests receive it.
ExtensionHow expiry changes and how quickly that reaches the access system.
Room changeHow the same stay is tracked without accidentally creating duplicate access.
Checkout / cancellationWhen entitlement ends and whether existing sessions must be disconnected.
Shared or group bookingWhich occupants and devices share an allowance and who may request changes.

Use stable reservation and property identifiers where the interface provides them. Room numbers can be reused, so they should not be treated as permanent guest identifiers. Agree time zones, expiry boundaries and what happens when a late update arrives.

Connect the PMS, network and messaging layers

The PMS establishes the stay entitlement. The guest login verifies the selected access credential or phone channel. The controller or gateway applies the network policy. Test the whole chain, because a successful message or PMS event alone does not prove that guest browsing works.

WiFiMitra offers SMS OTP through a configured SMS integration and WhatsApp verification through a supported business messaging integration. Confirm provider access, template setup, country coverage, expiry, retry behaviour and message costs during configuration. A phone OTP verifies control of the number at that moment; it does not, by itself, prove that someone is entitled to a hotel stay.

For supported Omada, MikroTik, Ruijie/Reyee, UniFi and OpenWrt installations, or WiFiMitra Gateway, confirm that access updates and session termination are enforced as intended. See all integration categories and the hotel login-method comparison.

Plan for delayed events and outages

Agree how missed, duplicate or out-of-order events are handled and how the systems reconcile after reconnection. Define the maximum acceptable delay before checkout changes take effect. Reception needs a visible way to recognise a sync problem and an agreed manual fallback.

A local voucher workflow can help staff when a cloud service is unavailable, provided local services remain operational. External PMS calls and message delivery still need their own working connections. Avoid promising fresh stay validation when the system cannot reach the authoritative source.

Approve a complete handover test

  • Create a test stay and confirm access starts at the agreed trigger.
  • Extend it and verify the new expiry on a guest device.
  • Move the guest to another room and check the original entitlement.
  • Check out and measure how quickly access changes.
  • Test a duplicate event, a missed update and recovery after interruption.
  • Verify staff permissions, audit records and manual overrides.
  • Record vendor support contacts, update ownership and recovery steps.

Limit exchanged data to the fields the workflow needs and agree access and retention responsibilities. Keep API credentials out of reception notes and public pages. WiFiMitra and SI partners can help scope configuration and on-site work; the final integration and support responsibilities are agreed per property.