Smart Order and TTLock: A Hotel Self Check-In Checklist

Smart Order is a documented PMS option for hotels using TTLock: it publishes a specific TTLock setup guide. Its 2025 integration update also names GO+, Haas Cloud, Sciener and Nations. If you already use Cloudbeds, its Guest Experience–RemoteLock connection is another documented path. Compare the exact integration and arrival workflow before replacing a working PMS.

For Smart Order, the useful buying boundary is concrete: the TTLock guide treats the connection as a paid add-on outside the standard Professional Edition, requires the main TTLock account, and distinguishes locks with and without a gateway. Hardware fit and regional terms still need confirmation; these documents are not a universal certification for every lock sold with the same app.

Two documented PMS-to-lock routes

Route	What the official documentation establishes	When to shortlist it
Smart Order → TTLock	A dedicated account-and-room setup workflow; separate add-on and gateway conditions	You want reservation, room and access work coordinated in Smart Order
Existing Cloudbeds → Guest Experience → RemoteLock	Documented PIN delivery and room mapping; the exact PMS room name matters	You already operate Cloudbeds and want to retain it while adding a supported access layer
Existing PMS with a separate check-in tool	Scope depends on that exact connector; it is not verified merely by an API logo	Keep it only after demonstrating your required reservation and access events

The Smart Order, Cloudbeds and TTLock links below are primary documentation, not an independent speed or reliability ranking. Neither integration is declared cheaper without comparable property quotes.

The TTLock constraints to confirm before buying

The official TTLock connection guide establishes five important boundaries: use the main account, one TTLock account per PMS property, map the locks to rooms, buy the relevant add-on, and check gateway requirements for remote operations. In particular, a lock without a gateway does not provide remote unlocking through this documented workflow.

This makes the first demo request specific: provide your TTLock account arrangement, physical lock and gateway details, property and room list. Have the supplier demonstrate the intended configuration instead of simply saying that “smart locks are supported.” TTLock’s own app documentation is a separate upstream reference for its account and device environment; it does not certify your PMS installation.

Midnight failure handoff: test more than the happy path

Scenario	Controlled test	Acceptance evidence
Ordinary arrival	Use an authorized test booking with the intended room and door	The correct guest receives usable access for the intended stay
Date change	Change the test stay and inspect the resulting access state	The team can identify the current access and handle the old instruction
Payment incomplete	Inspect the staff-visible payment state without charging a real guest	A named operator knows whether to collect payment or authorize entry
Phone, network or lock unavailable	Demonstrate the property-approved alternative with staff present	A reachable night responder and a usable fallback
Room not ready	Move the test booking using the agreed process	The next shift understands the room change and access handoff

These are proposed acceptance tests, not claimed results from a customer installation. Never remove the staffed fallback during a trial or create unauthorized bookings, charges or access changes to make a demonstration look complete.

An illustrative two-room planning example

Suppose a small property has Room A, Room B and a shared entrance. This is a planning example, not a customer case study. List the room-to-door assignment, who owns the TTLock main account, whether a gateway is present and the night contact. Run the arrival and room-change tests on an authorized test booking. Keep expected and observed results separate, then give the record to a second staff member to take over without verbal coaching.

The practical advantage of an integrated route is a shorter documented operational handoff when it actually passes this test. If an existing PMS and access layer already do so reliably, replacing them may add migration work rather than remove it.

Price the service scope without guessing the fee

Ask for separate lines for the PMS plan, lock add-on, supplied hardware/gateways, installation, training and support. Smart Order’s public pricing presentation does not establish the final account-specific total. A free module label does not override the TTLock guide’s add-on requirement. For a 20-room quote, record which charges scale with rooms or doors and which are fixed; do not multiply an unverified unit price.

For the Cloudbeds–RemoteLock route, ask for the applicable Guest Experience and RemoteLock commercial scope as well as hardware. Compare the same period and the same required doors. Neither a generic subscription price nor a one-off successful demo is a total operating-cost guarantee.

A reusable night-duty escalation record

For the illustrative two-room trial, record booking reference, room/door, arrival time, payment-checking role, current access, gateway state, primary night-duty role/contact channel, backup role if unanswered, and the property-approved alternative entry method. Populate names and telephone numbers inside the property's controlled operating record. These are planning fields, not a promised response time or a claim that an actual team has accepted the duty. Give the next shift only this record and observe whether they can continue the authorized test.

The purchase decision

Shortlist Smart Order when the documented TTLock route fits your hardware and you want the PMS workflow integrated. Retain Cloudbeds with a supported access layer when preserving the current PMS is the better operational choice. In either case, accept the setup only after the actual room mapping, arrival exception and night-duty handoff work for your property. Confirm precise lock model, firmware, installation and local service terms before commitment.

Verified product facts

Parameter	Documented value / condition
Documented lock route	TTLock; exact model and gateway conditions must be checked
Commercial boundary	TTLock connection is a separate add-on outside standard Professional Edition
Account boundary	Main TTLock account; one TTLock account per PMS property
Remote operation	Remote unlock requires a gateway in the documented TTLock workflow

These are manufacturer-documented specifications, not independent performance measurements. Verify the exact model, source device and local purchase terms. A product photograph does not demonstrate compatibility or test results.

Frequently asked questions

Which PMS has a documented TTLock integration?

Smart Order publishes a TTLock connection guide. Cloudbeds also documents a Guest Experience–RemoteLock path. Confirm the exact account, hardware and commercial scope rather than choosing from a brand logo.

Is the TTLock connection included in standard Smart Order Professional?

The cited Smart Order support guide says it is a separate add-on. Confirm the current account-specific offer rather than assuming that all Professional functions are included.

Can a TTLock sub-administrator connect the PMS property?

The Smart Order guide requires the main TTLock account and limits a PMS property to one linked TTLock account.

Can the night team remotely unlock a lock without a gateway?

Not through the gateway-free workflow described by that Smart Order guide. Include the actual gateway and an approved fallback in the trial.

What proves the hotel is ready for self check-in?

An authorized end-to-end trial with room mapping, an ordinary arrival, changed dates, incomplete payment and a failed-device handoff. A Connected label alone is not that proof.

Sources and scope

Check the exact model and connection options