Skip to content
Back to all features

Smart locks · TTLock

TTLock locks and PIN management

Superhostem supports two guest-access approaches: an automatic TTLock PIN tied to a reservation, or a permanent property code managed manually. Connect a compatible lock and manage access validity and PIN changes directly in the app.

Each stay has its own PIN. Superhostem creates and manages automatic TTLock PINs based on the reservation. Save a manual code for the property or an individual stay when needed.

Automatic optionOne stay. Its own access.
Automatic PIN

Valid only during the stay

TTLock lock
Check-inCheck-out
The reservation defines the access window. Each stay has its own PIN.

Two ways to manage PINs

Choose an automatic PIN for each stay or a permanent PIN you manage manually. For manual access, a reservation-specific code can override the shared property code.

Automatic or manual

1. Automatic TTLock PIN

A unique PIN for each stay. Superhostem creates and manages it directly on the lock.

  • Automatic PIN

    The system creates a separate code for each assigned lock and reservation.

    6 digits · check-in to check-out
  • Custom replacement PIN

    The owner chooses a different code for existing access.

    4–9 digits · same validity window

The reservation controls validity. TTLock must confirm changes.

2. Permanent PIN, managed manually

Save one shared code for the property. Override it for an individual reservation when needed.

  • Permanent property code

    Used when the persistent manual PIN method is selected. A reservation override takes precedence.

    Shared across multiple stays
  • Reservation code (optional override)

    Use a different, manually created code for one stay instead of the default.

    For one specific stay

Saving a code does not program the lock. Set validity separately in TTLock.

The PIN follows the stay

An automatic PIN is created before arrival, works only during the stay and updates when dates change. Requests and confirmations have distinct statuses in the app.

  1. 01

    Creation before arrival

    Creation starts automatically 48 hours before check-in. The owner can request it earlier.

  2. 02

    Confirmed PIN

    After TTLock confirms, the code is ready. It works only within its configured time window.

  3. 03

    End of stay

    The PIN expires when validity ends. Removing its record is a separate operation.

Dates change

Access validity is updated. A pending change remains visible until confirmed.

Reservation cancelled

PIN removal is requested. Until confirmed, its status remains removal pending.

Gateway offline

The operation waits or reports an error and is retried. An unconfirmed change is not shown as complete.

PIN management in the reservation

See access validity and status for each door alongside the stay. Open PIN management from the same place.

  • Status and validity together

    See which doors have a confirmed PIN and exactly when it is valid.

  • Your PIN, the same stay window

    Replace an active code with your own. The stay’s validity window remains unchanged.

  • History without exposing PINs

    Open the history of requests and confirmed operations. PIN values are not stored in it.

Actual app panel with demo data. Open the screenshot to zoom in.

Before connecting a lock

Compatibility and the actual feature scope.

What does automatic TTLock integration require?

A compatible TTLock lock with V4 passcodes, an available gateway and authorized-admin access. Check the specific model and firmware; a normal eKey is not enough.

Do you also support one-time or recurring PINs?

The app implements timed reservation PINs and custom replacement. This integration does not offer TTLock’s one-time or recurring PIN types.

How does the guest get the PIN?

Confirmed PINs are available in the verified private guide once the configured access requirements are met. Message templates and email automations can include the effective PIN through the access-code variable. Pending or unavailable access is not sent as a ready PIN.

Can I manage hotel rooms and shared entrances?

Yes. Room access and shared entrances are configured separately, and each can use its own manual or TTLock method. A reservation receives access for its assigned rooms and applicable entrances. Private, test, unconfirmed and cancelled stays do not receive automatic reservation PINs.

What happens during an outage or cancellation?

Cancellation requests code removal. Without an available gateway, the operation may wait for connectivity; the app shows a pending state or an error. Keep a backup entry method.

V4 passcode and gateway requirements: official TTLock documentation.

Prepare the whole stay

Connect compatible TTLock locks and manage automatic PINs and manual access codes alongside reservations and online check-in.

Try for free