
A rental lock earns its keep when every guest arrives alone, often late, with a phone that may have no signal. This guide covers dated codes, offline logic, gateways and host operations.
Self check-in is the baseline expectation of short-stay hospitality, and the lock is the piece that either makes a listing run unmanned or generates a midnight call. The workhorse credential is a time-limited PIN generated per booking: it works at the keypad without any phone pairing, starts and stops on schedule, and can be texted automatically with check-in instructions. Online locks push codes over Wi-Fi through a gateway or app; offline-capable locks also generate codes from a secret seed, so a basement flat with no signal can still receive a valid code. Hosts choose between managed ecosystems such as Tuya or TTLock, weighing channel-manager and PMS-style integrations, gateway hardware and platform lock-in; multi-property owners add centralized management, cleaner codes and battery monitoring. Outdoor or lobby doors demand IP-rated weather protection, and every deployment needs a documented fallback path. This guide explains those choices; model features, code capacity and integration scope are confirmed per SKU, and current MOQ policy, sample terms and lead time are confirmed in writing per quotation.
| Core workflow | Dated PIN codes are issued per booking, expire at check-out and require no guest app or phone signal at the door. |
| Offline codes | Seed-based code generation lets a code work on a lock that is currently offline, critical for basements and thick-walled buildings. |
| Online delivery | Wi-Fi locks or Bluetooth locks plus a gateway push codes and audits remotely; gateway placement and building coverage must be tested. |
| Ecosystem choice | Tuya and TTLock are common managed platforms; compare channel integrations, gateway models, app UX and lock-in before standardizing. |
| Multi-property work | Centralized dashboards handle many doors, dated cleaner codes, auto-expiry and low-battery alerts across an entire portfolio. |
| Door environment | Exposed exterior and gate doors need a verified IP rating and cold-temperature battery behavior for the complete fitted assembly. |
| Terms and evidence | Current MOQ policy, sample terms and lead time are confirmed per quotation; certificates and test reports for named SKUs are provided per RFQ. |
Match the network path to the real signal at the door, not to marketing claims. A connected lock that cannot be reached is worse than an offline lock with a disciplined code process.
| Property situation | Typical setup | Reason |
|---|---|---|
| City apartment with good Wi-Fi | Wi-Fi lock or Bluetooth plus gateway | Codes sync instantly and hosts see check-in events remotely. |
| Basement or thick-walled flat | Offline-capable lock with seeded codes | Guests type a valid code even when the door has no radio coverage at all. |
| Building with multiple units | Gateway-based system, one hub per zone | A single gateway often serves several nearby doors and cuts hardware cost. |
| Outdoor gate or exposed door | Weather-rated lock, verified IP and gaskets | Rain, dust and freezing temperatures punish indoor-rated electronics. |
| Host with dozens of listings | Multi-property platform with roles | Cleaners and co-hosts get scoped codes; battery alerts aggregate in one console. |
| Remote host in another country | Online lock plus auto-message flow | Dated codes arrive with instructions and access logs settle check-in disputes. |
Rentals contain several openings beyond the apartment front door. Guests rarely need all of them, but staff access and emergency paths do, so the access plan should cover the whole unit.
| Opening | Typical door | Lock approach |
|---|---|---|
| Apartment front door | Timber, metal or UPVC entrance leaf | Keypad smart lock with dated PINs and mechanical or emergency-power fallback. |
| Building common entrance | Shared lobby door not owned by host | Where permitted, an intercom-style or lobby code arrangement agreed with the building. |
| Interior room-let doors | Light interior doors | Room-specific dated codes for co-listing hosts renting individual rooms. |
| Outdoor gate or garden door | Exposed metal or timber gate | Weather-rated outdoor lock or gate-specific hardware with sheltered keypad. |
| Cleaning and utility closets | Interior service doors | Recurring-window codes for cleaners and maintenance, audited separately from guests. |
| Backup key storage | Lockbox or secure key custody | Last-resort entry for drained locks, kept in an audited location off the corridor. |
Hosts buying in volume should run one property as a pilot and document the failure paths below. Every item is answered for the named SKU; vague app screenshots do not survive a peak-season lockout.
| Component | Typical logic | Notes |
|---|---|---|
| Code engine | Dated codes, recurring cleaner codes, one-time codes and offline-code generation rules. | Ask for code capacity and what happens when the limit is reached. |
| Gateway and radio | Gateway model, doors per gateway, pairing mode and building coverage test. | Confirm whether Wi-Fi credentials use 2.4 GHz networks guests cannot change. |
| Ecosystem lock-in | Platform ownership, export of audit data and operation if the host changes software. | Multi-property groups should demand role and portfolio features in writing. |
| Fallback path | Mechanical key, emergency power contacts and verified procedure with timing. | Every listing instructions page should describe exactly what a locked-out guest does. |
| Weather and terms | Tested IP rating, temperature range and salt exposure for exterior use. | MOQ policy, sample terms, lead time and named-SKU certificates are confirmed per RFQ. |
An online lock receives a dated code through its cloud when it next syncs: the host creates a code valid from 3 p.m. Friday to 11 a.m. Sunday, the gateway delivers it, and it dies automatically at check-out. An offline-capable lock adds a second path — both lock and app share a secret seed, so a code computed for a specific time window is accepted at the keypad even if the lock has never connected, which is what saves basement flats and buildings with dead lobbies. Hosts should verify code length, whether one-time and recurring codes are supported, code capacity, and whether offline codes can be disabled per property. These limits differ strongly between firmware versions and are confirmed in writing for the quoted SKU.
Both provide app, gateway, sharing and audit families, but they are different business models. Tuya is a broad IoT platform used by many lock brands, giving wide hardware choice and familiar app flows while app experience and long-term support depend on the brand building on it. TTLock is a focused access ecosystem popular with rental and office operators, with strong temporary-code logic, gateway products and operator-facing management tools. Choice should be tested on three practical points: how booking codes are delivered and expire, how many doors one dashboard manages for a portfolio, and what the host retains if switching later. Multi-property operators should pilot both on identical doors and check channel integrations before standardizing.
Keypad-only entry is the safest default for transient guests: the host sends a dated PIN in the booking message, the guest types it at arrival, and nothing depends on app stores, Bluetooth pairing, phone model or cellular signal at the door. Apps remain valuable for hosts, owners and cleaners who operate repeatedly, and some locks offer optional mobile keys, but requiring every guest to register an account raises friction, creates privacy questions and increases support calls. Specify locks that work fully with PINs and keep the app optional. Accessibility also favors tactile keypads with clear operation over touch-only surfaces, especially for older travelers.
Offline-capable code logic covers the no-connection case because the code is validated at the lock itself. For drained batteries, well-designed locks warn early at the keypad and in the host app, keep opening for a grace period, accept external power through hidden contacts or a standard connector, and retain a mechanical override key. The operational fix is procedural: each listing instructions page should state what to do in order — wait and retry, use the code exactly as sent, use external power instructions, then call the host number — and hosts should service batteries on a schedule tied to turnovers rather than waiting for failure. Battery type, warning behavior and override options are confirmed per quoted model.
Weather resistance and security are separate questions. Exterior doors need a lock with a verified IP rating for the complete fitted assembly, tested temperature limits and ideally a canopy over the keypad; indoor-rated hardware on a coastal gate fails within months. Security comes from the bolt and strike as much as the electronics: specify a solid latch or deadbolt, anti-pry strike with long screws, tamper lockout after repeated wrong codes, and dated codes that expire rather than permanent codes shared forever. Verify the door and frame themselves; a smart lock cannot fix a weak frame. Certificates and test reports for the named SKU, including radio compliance and weather tests, are provided per RFQ and confirmed in writing.
Tell us door types, signal conditions and listing volume. We confirm code logic, gateway plans, weather ratings, fallback paths and current MOQ policy, sample terms and lead time in writing per quotation, with samples for a pilot listing.
Request Spec Sheet + QuoteOrder samplesLast updated: October 31, 2026 · Reviewed by the Smart Lock Factory editorial team