How can reception keep working when the internet or cloud PMS is unavailable?
A hotel PMS internet outage plan should give the evening team a clear route from the first failed connection to a checked, reconciled handover.
Reception can keep essential arrivals moving with a timestamped shift pack, verified room status and one controlled incident log. First distinguish a local connection problem from a suspected supplier outage. Use a tested backup connection for the former; follow supplier updates and your manual procedure for the latter. Confirm uncertain payments before retrying them, then reconcile every manual action when service returns. Do not assume offline PMS access.
Prepare the evening shift before a failure
Give the duty manager ownership of the fallback plan. Before handover, check that reception can access these essentials without the PMS:
- A timestamped arrivals and in-house list: booking reference, guest name, stay dates, party size, assigned room, recorded deposit and outstanding balance. Label balances “as at” the export time.
- Room occupancy, cleaning and out-of-order status, plus a working key-access procedure. Confirm later changes with housekeeping.
- One incident log with time, booking reference, action, staff initials, payment reference or uncertainty, and a reconciliation tick box.
- A charged duty phone, approved backup connection and contact details for the manager, internet provider, PMS support and lock supplier. Check access to authentication methods too.
Test the pack with Wi-Fi disconnected. A file saved only in cloud storage is not an accessible fallback unless it is also available on the approved device.
Identify which connection has failed
| Likely problem | Quick check | Next action |
|---|---|---|
| Local internet or Wi-Fi | Other websites fail locally; the PMS works over an independent mobile connection. | Use the approved backup connection and contact your network provider. |
| PMS or supplier service | Other websites work; the PMS fails on separate devices and connections. | Check supplier updates, report symptoms and start the manual procedure. |
| Device or account | Another authorised user or device can access the PMS. | Troubleshoot the affected access with support; do not share passwords. |
These checks guide triage; they do not prove the cause. Read the RoomRaccoon status page for component updates. A working booking engine does not establish that payments or reservation synchronisation are healthy.
Run the right reception procedure
If the hotel's internet is down
Move an authorised reception device onto the tested backup connection. Verify current reservations before continuing. Check the card terminal and door-key system separately: reconnecting a laptop does not reconnect every device. If backup access fails, use the shift pack and log below.
If the PMS supplier is unavailable
Use the pack to match arrivals to existing bookings, verify occupancy and readiness before issuing keys, and log changes in one place. Escalate missing reservations or disputed balances to the duty manager. Keep the duty phone reachable and give waiting guests a realistic next update time.
Hold new walk-in commitments when availability cannot be verified. The manager should check selling channels independently and, where necessary and accessible, pause affected inventory through approved channel controls. Record each change; never assume an instruction has reached every channel.
If payment status is uncertain
Use only a payment route approved for your terminal and integration. Adyen's offline-payment guidance shows that support depends on configuration and integration, with a risk of later failure. This does not establish offline capability for a particular RoomRaccoon setup.
For a timeout, log the amount, time and available reference. Check the provider's transaction status before retrying. If no approved route works, follow the manager's documented payment-deferral policy. Keep card numbers, security codes and PINs out of the incident log.
Reconcile the shift before returning to normal
A 12-room inn saves its shift pack at 16:00. The PMS becomes unavailable at 18:10. An arrival shows a £180 booking total and £60 deposit: the recorded balance is £120. A £120 terminal attempt times out. Reception records “status unknown” and does not retry. At 19:05, the provider confirms the payment succeeded. The team checks whether it has already appeared in the PMS and records it only if missing. The balance is then £0.
Fictional guest totals, including VAT where applicable; this is a reconciliation example, not a software quotation or tax calculation.
- Confirm service recovery and check bookings, amendments and cancellations received since the pack's timestamp, including the period before the outage.
- Match logged arrivals, room moves and charges to existing reservations. Check current PMS records before adding anything; do not overwrite newer information.
- Reconcile payments against provider records and receipts. Distinguish authorised, captured, failed and still-unknown transactions; investigate mismatches before collecting again.
- Check room status, channel inventory, paused sales, key access and queued guest messages. Assign every unresolved item to a named colleague before signing off.
Protect temporary guest information
Keep only what the shift needs. Use hotel-managed devices with encryption and screen locks, restrict staff access, and secure printed packs away from public view. Avoid personal email, messaging accounts and unnecessary identity-document copies.
Set a disposal trigger for temporary copies once reconciliation and any justified follow-up are complete. Preserve records still needed under the hotel's retention policy. The ICO's storage-limitation guidance requires justified retention, rather than a universal number of days.
Do not create a paper card vault: PCI SSC prohibits retaining card verification codes after authorisation, even when encrypted.
Make continuity part of your RoomRaccoon demo
When evaluating a hotel property management system, test how staff obtain usable fallback information. RoomRaccoon's UK PMS page describes reservation and payment-status views and a printable daily housekeeping list. Ask which reports supply your shift pack and what each timestamp represents.
RoomRaccoon onboarding includes managed setup and training. Ask whether your team can rehearse this scenario, which support routes your package includes, and what any read-only fallback can show. Confirm UK availability, data freshness and integration limits; do not assume an editable offline mode.
Bring an anonymised evening arrivals list, your terminal and lock details, and one timed-out payment scenario. Ask the demonstrator to walk through preparation, interruption and reconciliation.
Discuss operational continuity in your demoReception outage questions
How often should we refresh the fallback pack?
Refresh it at shift handover and after material changes, using a frequency suited to your booking activity. Always show its preparation time; even a recent copy can miss a new booking or payment.
Is read-only access the same as working offline?
No. A separate read-only service may still require internet access and may show delayed data. Confirm its current availability and limitations with the supplier; keep a separate log for actions it cannot save.
What if a guest's key cannot be issued?
Use the lock supplier's tested contingency procedure with authorised staff. Verify the guest and room allocation before granting access. Escalate immediately if safe access cannot be provided; a PMS printout cannot replace a working key procedure.
Sources and checks
Checked on 10 November 2026. RoomRaccoon's UK PMS and onboarding pages are linked above. Provider-specific payment guidance does not confirm your hotel's configuration. The ICO marks its storage-limitation guidance as under review following legislative changes.












