Cloud PMS Offline — What the Desk Can Actually Do
Quick answer
A cloud PMS cannot run fully offline. It can support a documented fallback for arrivals, folios, keys and reconciliation when the connection drops. If the desk must keep working through an outage without a fallback, hybrid or on-premise is the honest answer.
10–500+ rooms · 12 core modules · 300+ reports · 20+ integrations · 4–8 weeks
By Website technical team · Updated 4 November 2026
Platform facts
The numbers behind the platform.
The platform runs 10–500+ room properties on 12 core modules, with 300+ report templates and 20+ integration points across 8 interface categories. Deployment comes in 3 models; a typical single-property implementation takes 4–8 weeks. Four product lines cover PMS, POS, membership and procurement; 5 property types are configured; the site is published in 10 languages with 6 knowledge hubs and 24 guides. One guest record and one ledger run the property, with 1 database, 1 folio and 1 audit trail. Reports are available in 2 languages; 4 role groups are supported; quotes reply within 1 business day. A quote has 3 room-count tiers, 5 preparation inputs and 3 implementation phases; cutover is planned in 3 phases. Use these figures to size the evaluation; the quote confirms rooms, modules, interfaces and deployment for your property.
| Fact | Figure |
|---|---|
| Property range | 10–500+ rooms |
| Core modules | 12 |
| Report templates | 300+ |
| Integration points | 20+ |
| Integration categories | 8 |
| Deployment models | 3 — cloud, on-premise, hybrid |
| Typical implementation | 4–8 weeks |
| Product lines | 4 — PMS, POS, membership, procurement |
| Property types | 5 |
| Site languages | 10 |
| Knowledge hubs | 6 |
| Published guides | 24 |
| Guest record | 1 |
| Ledger | 1 |
| Report languages | 2 — English and Chinese |
| Quote response | 1 business day |
| Role groups | 4 — front office, housekeeping, F&B, finance |
At a glance
Offline capability by deployment
| Function | Cloud with fallback | Hybrid | On-premise |
|---|---|---|---|
| Check-in | Manual list and procedure | Local system | Local system |
| Check-out | Manual folio | Local system | Local system |
| Folio posting | Manual log | Local system | Local system |
| Key issue | Lock may be local | Local system | Local system |
| Housekeeping status | Paper or mobile cache | Local system | Local system |
| Night audit | Delayed | Local system | Local system |
| Payments | Terminal may work offline | Local or terminal | Local or terminal |
| Channel sync | Paused | Paused or local | Paused |
| Reservations | Manual list | Local system | Local system |
| Reports | Delayed | Local reports | Local reports |
| Guest profiles | Limited cache | Local database | Local database |
| Outlet charge | Manual log | Local system | Local system |
| Reconciliation | Manual after reconnect | Automatic or manual | Manual or automatic |
| Recovery | Vendor | Property plus vendor | Property |
| Best fit | Short outages, reliable network | Unreliable WAN | Local control |
What does offline actually mean?
It means the desk can complete a defined set of tasks while the connection to the vendor is down. It does not mean the full system with no network. The set of tasks should be written down and tested.
What is a cloud fallback?
A local arrival list, a manual folio, a key procedure and a reconciliation sheet. The property uses paper or a local device, then enters the transactions when the link returns. The procedure must be exercised, not just documented.
When is hybrid the answer?
When the desk must keep working through a WAN outage without a manual fallback. A property server keeps the local operation running; the centre receives the reporting data when the link returns.
How do you test it?
Disconnect the link during a quiet period, check in a guest, post a charge, issue a key and reconnect. Measure the time and the reconciliation effort. Repeat at peak if the property can tolerate it.
How do you reconcile after an outage?
Compare the manual log with the system, post the missing charges, correct the room states and verify the payments. The reconciliation should be owned by a named person, not left to the next shift.
What should the contract say?
The offline procedure, the support during an outage, the recovery objectives and the reconciliation responsibility. A cloud contract without an outage procedure is incomplete.
What does an outage drill look like?
Choose a quiet period and announce the drill to the team. Disconnect the WAN, then run a standard arrival, a room move and a departure using the fallback procedure.
Record the time, the missing information and the workarounds. The point is not to prove the fallback is perfect; it is to find where it breaks before a real outage does.
Reconnect and reconcile the manual log with the system. Check the folios, the room states and the payments. Measure how long the reconciliation takes.
Review the drill with the desk and update the procedure. Repeat at least annually and after a major release.
What should the offline procedure contain?
The trigger, the roles, the tasks the desk can complete, the paper or local forms, the key procedure and the reconciliation steps.
It should name the person who declares an outage, the person who reconciles and the person who communicates with guests. A procedure without names is a document, not a plan.
Keep a printed copy at the desk. A procedure stored only in the system that is down is not available when it is needed.
Frequently asked questions
Frequently asked questions
Can a cloud PMS check in a guest with no internet?
Is a mobile hotspot enough?
Do door locks work offline?
How long can an outage last?
Who owns the reconciliation?
Is hybrid automatically resilient?
What should we monitor?
How often should we drill?
Who should join the drill?
What is a successful drill?
Where should the procedure live?
Next step
See the platform on your own workflows.
A 30-minute walkthrough, built around your property type and the systems you already run. No slide deck — we work through arrivals, folios, night audit and reporting live.
Typical reply within one business day.