
Hosts and property managers ask about self check-in codes, offline access, cleaner permissions and managing many listings from one account.
Short-term rental access has a different rhythm from a hotel or an office: guests arrive at any hour without a front desk, cleaning staff need time-limited access between stays, co-hosts and property managers need oversight across many doors, and a locked-out guest at midnight becomes an urgent support case. This FAQ covers PIN and time-limited codes, offline access when the internet fails, Wi-Fi gateways and their limits, remote unlocking and app accounts, cleaner and contractor permissions, grouping listings by building, battery failure behaviour, event logs for disputes, and door compatibility for timber, aluminium and glass entry doors. Answers describe how rental locks normally behave. Gateway requirements, app features, cloud terms and lead time are confirmed in writing per quotation.
No for basic keypad entry, yes for remote management. A keypad lock can validate its own codes from local memory, so a guest can check in when the internet or the router is down; what you lose without a connection is remote code changes, live entry notifications and remote unlocking. If you want to issue a code from another city an hour before arrival and see the entry event afterwards, the lock needs a gateway or a Wi-Fi-enabled model at the property, plus a working internet connection and power at the router. Offline code capacity, whether a gateway is required for the chosen app and what still works during an outage are confirmed in writing per quotation.
Codes are normally created in the management app or dashboard, linked to a specific listing and a specific date range, and delivered through the booking channel message, a scheduled email or SMS, or the app itself. Automatic delivery depends on channel integration: platforms that pass arrival data into the property software can trigger the message without host action, while manual channels need the host to issue and send the code. Delivery should include the door location and a fallback contact, because a guest standing at the wrong building cannot use the best code. Delivery method, message templates, channel integration and scheduling behaviour are confirmed in writing per quotation and app plan.
Yes — time-limited or scheduled codes are the core feature of rental locks. A code carries a start and end time, sometimes weekday rules and a use count, and the lock rejects it outside that window even if the guest kept the digits. That removes the manual step of deleting codes after checkout and protects against a guest sharing the code with someone who arrives a week later. Limits exist: offline locks rely on their internal clock, so time drift and timezone settings matter, and very large numbers of stored codes consume memory. Code capacity, scheduling rules, clock behaviour and timezone handling are confirmed in writing per quotation.
A keypad code needs nothing from the guest but the digits, which is the main reason keypad access is preferred for self check-in. If the property relies on app-based or Bluetooth keys, a flat phone or a failed app update can leave the guest stranded, so a code or a physical key should always exist as a fallback. The lock itself is independent of the guest's network once the code is stored locally; the risk sits on the host side, where an unreachable gateway prevents last-minute changes. Fallback credentials, offline mode behaviour and the recommended guest instruction sheet are confirmed in writing per quotation.
Use a recurring window rather than a permanent code: housekeeping receives a code valid on cleaning days between set hours, which stops working outside that slot and can be disabled when the relationship ends. Some systems support separate staff roles with their own logins, so the cleaner sees only the listings assigned to them and cannot read guest data. A one-off code for a plumber or an electrician can be issued for a single day and deleted afterwards. The important discipline is deleting or expiring access when a person leaves. Role permissions, recurring window rules and staff account limits are confirmed in writing per quotation and app plan.
Yes, if the locks are on the same platform and the account structure supports groups. Listings are usually organised by property, building or portfolio, with user roles that scope each manager or cleaner to a subset; codes are created per listing rather than per lock, and reports can be filtered by portfolio. Mixed platforms are the real problem, because each ecosystem has its own app, account and guest data, so standardising on one platform before scaling saves years of administration. Offline locks in remote buildings still need local code delivery, which the app handles but the host must plan. Multi-listing structure, role scoping, account limits and platform coverage are confirmed in writing per quotation.
Both are support-process questions, not lock questions. Arrival instructions should include a photo of the entrance, the exact door, the location of the keypad, and a phone number that a person actually answers; codes should be sent early enough that a guest can ask for help before standing in the rain. If the lock does not respond, the first checks are power, battery state and whether the code window is correct, then the mechanical key or a remote unlock where available. A written escalation path with a backup key holder prevents an improvised midnight solution. Support procedures, backup key custody and remote unlock availability are confirmed in writing per quotation.
Yes, and separately. A co-host who handles messages needs dashboard access, not necessarily a door code; a neighbour who holds a spare key needs a physical key, not a permanent PIN that can be shared onward; a property manager needs a master-level credential with an audit trail. Giving everyone the same code destroys accountability, because the entry log can no longer show who opened the door. Separate credentials also make revocation clean when a person leaves the team. Role design, master credential scope and audit-log visibility are confirmed in writing per quotation and app plan.
A keypad covers the normal case: a guest arrives, enters the code and goes in. Remote unlocking matters for exceptions — a guest who forgot the code, a delivery that must be placed inside, a cleaner who needs immediate entry — and it requires a connected lock with a gateway or Wi-Fi, plus a defined authority to use it. Remote unlock without an audit trail is a security hole, so the platform should record who unlocked which door and when. Many hosts run keypad-only locks and keep a local key holder for exceptions. Remote-unlock features, authority levels and gateway requirements are confirmed in writing per quotation.
The reliable method is an expiry built into the code, not a manual deletion that depends on someone remembering. When a code is created with an end date and time, the lock refuses it after that moment whether or not the host deletes it, so a late checkout or a returning former guest cannot re-enter. Manual deletion is a second layer for codes with no end date, such as a permanent family code, and those should be reviewed periodically. If the lock is offline and never synchronized, deletion may only take effect when the code list reaches the lock, which is another reason to prefer time windows. Expiry rules, deletion propagation and offline synchronization are confirmed in writing per quotation.
Timber entry doors usually take a mortise or cylindrical body depending on the existing prep, and a deadbolt replacement is the fastest retrofit when a standard bore already exists. Aluminium and narrow-stile doors need a slim reader plate and a matching narrow mortise case, or a glass-door lock with a different mounting method entirely. Holiday lets often have an unusual door — a barn door, a sliding door or a security gate — where the standard product does not apply. Send door photos with a tape measure, the existing hardware and the opening type before ordering. Fitting options for a specific door are confirmed in writing per quotation.
Yes in many cases: local codes, an app connected directly over Bluetooth and manual log reading work without a paid cloud service. What a cloud subscription typically buys is remote code management from another location, gateway connectivity, automatic guest messaging, multi-user dashboards and long-term event history. Whether a particular model needs a subscription for its core features, what is included at no cost and how data is retained if the subscription lapses should be settled before you build a portfolio around it. Subscription scope, free-tier limits and data-retention behaviour are confirmed in writing per quotation and platform terms.
Quality rental locks warn before failure: a low-battery alert on the keypad and in the app, a grace period of openings after the first warning, and an external emergency power point where a battery pack or power bank can be touched to the escutcheon. The mechanical key remains the final route, which is why key custody matters for a self-managed property. Hosts should treat the low-battery alert as a work order, not a suggestion, and keep a spare set of the correct cells. Warning thresholds, emergency power method, cell type and the mechanical override are confirmed in writing per quotation.
Not to the lock itself. Channel managers and property-management systems connect to the booking platforms, and the lock platform connects to those systems through an integration; the code is created when a reservation arrives and the guest message goes out through whichever channel is configured. Direct lock-to-platform integration does not exist in the usual sense, and the practical question is which channel manager or PMS your lock platform supports. Gaps in the chain — a listing that is not mapped, a manual booking that never reaches the system — are where automation fails. Integration route, supported channel managers and mapping requirements are confirmed in writing per quotation.
A gateway is normally one per property or per building, connecting nearby locks to the internet over Wi-Fi, ethernet or another local link, and its practical range depends on walls, floors and interference rather than on the marketing figure. A gateway in a hallway may not reach a lock in a basement unit or an annex, so large or spread-out properties need more than one, or a different connectivity model. Each gateway also needs power and a network connection that survives a guest turning off the router. Gateway count, coverage, power and network requirements for your property layout are confirmed in writing per quotation.
The lock keeps an event log of code used, time and opening result, and a connected platform collects it automatically while an offline lock needs a local read through the app or a data card. For a dispute, the log shows whether a valid code was tried, whether it was outside its window, and whether the door was opened from inside. Logs are evidence only if the device clock is right and collection has been regular, so set the time source and check retention. Log fields, collection method, retention period and export format are confirmed in writing per quotation and platform plan.
Grouping is an account-structure question: listings map to physical doors, buildings or portfolios group listings, and user roles scope people to the listings they serve. A cleaner assigned to three buildings should see those three, not the whole account; a regional manager may need read access across a portfolio without the ability to change codes. Grouping also drives reporting, so a lost-key investigation can be limited to one building. The structure should be designed before the first lock is installed, because reorganising later is tedious. Account hierarchy, listing mapping and role scoping are confirmed in writing per quotation and platform plan.
Access hardware cannot solve a regulatory problem, but it should not create one. Some jurisdictions require a physical key or a documented emergency egress path, and some require host registration and guest identification; a lock that only opens by app can conflict with fire-safety expectations if a guest cannot exit quickly. Noise complaints are usually about behaviour, yet entry logs and time-limited codes help a host show who was present. Check local rules before choosing a keypad-only design. Compliance obligations, egress requirements and any documentation the authority expects should be confirmed with a local advisor, not assumed from a product page.
Send door photos, unit count, cities, cleaner workflow and whether gateways are possible. Code rules, gateway coverage and multi-listing management are confirmed in writing per quotation.
Ask Our EngineersRequest a QuoteLast updated: November 1, 2026 · Answers reviewed by the Smart Lock Factory engineering team