Skip to content
Lodgcore Hotel Management System

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

Guest room window with city skyline

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

FunctionCloud with fallbackHybridOn-premise
Check-inManual list and procedureLocal systemLocal system
Check-outManual folioLocal systemLocal system
Folio postingManual logLocal systemLocal system
Key issueLock may be localLocal systemLocal system
Housekeeping statusPaper or mobile cacheLocal systemLocal system
Night auditDelayedLocal systemLocal system
PaymentsTerminal may work offlineLocal or terminalLocal or terminal
Channel syncPausedPaused or localPaused
ReservationsManual listLocal systemLocal system
ReportsDelayedLocal reportsLocal reports
Guest profilesLimited cacheLocal databaseLocal database
Outlet chargeManual logLocal systemLocal system
ReconciliationManual after reconnectAutomatic or manualManual or automatic
RecoveryVendorProperty plus vendorProperty
Best fitShort outages, reliable networkUnreliable WANLocal 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?
Only through a documented fallback or a local cache. It is not the full system; it is a procedure with a reconciliation step.
Is a mobile hotspot enough?
It can be a backup path, but it is not a guarantee. Test it at the property and include it in the procedure.
Do door locks work offline?
Often the lock or encoder can issue a key locally, but the PMS may not record it until the link returns. Confirm the exact model.
How long can an outage last?
It depends on the fallback. A manual procedure can cover hours; a multi-day outage needs a local system.
Who owns the reconciliation?
The property, with vendor support. The procedure should name the person and the deadline.
Is hybrid automatically resilient?
No. It needs a reconciliation design and a tested local server. Hybrid without design is two systems.
What should we monitor?
Link availability, sync failures, manual postings and the time to reconcile after an outage.
How often should we drill?
At least annually, and after a major upgrade or a change of network provider.
Who should join the drill?
Front office, housekeeping, finance and the person who owns the network. The vendor can observe remotely.
What is a successful drill?
A guest can arrive, a charge can be posted and the reconciliation can be completed without inventing a new procedure on the spot.
Where should the procedure live?
At the desk, printed and in the operations folder. It should not depend on the PMS being available.

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.