
Reservation-window codes for unattended arrival, automatic expiry at checkout, simple host management across one or many units, and hardware built for weekly turnover.
Self check-in converts the riskiest moment in short-term hosting — key handover — into a background process: each reservation receives a code that works from check-in time and lapses at checkout, so a delayed flight, an early cleaner or a back-to-back booking never depends on the host being physically present. For hosts with one apartment this removes meet-and-greet logistics and lost-key callouts; for managers with scattered units it makes every door behave the same way regardless of city or lock brand. The access policy keeps guests, cleaners and maintenance in separate windows, and expired codes are cleared automatically rather than accumulating on the lock. The centralized property page covers multi-door portfolios, the bed and breakfast guide covers small hosted properties, and the vacation rental locks page covers hardware choice.
| Reservation codes | Guest codes valid only between the booking check-in and checkout times, issued ahead of arrival |
| Unattended arrival | Guests enter without a host present, including late-night and international arrivals |
| Turnover windows | Cleaner and linen codes work inside the gap between bookings, never during a stay |
| Auto expiry | Codes lapse at checkout and are removed so a past guest cannot return between stays |
| Multi-unit management | Scattered apartments follow one process and dashboard instead of a lockbox per city |
| Offline readiness | Battery and offline behaviour is specified so a network outage never blocks an arriving guest |
| BOM shape | One lock per entrance plus optional common-door and amenity controls per building |
Any host chasing reliability moves past lockboxes to dated per-booking codes; shared permanent codes are retained only by the smallest informal listings.
| Dimension | Lockbox / permanent code | Reservation-dated smart lock |
|---|---|---|
| Guest arrival | Host relays a fixed code or hides a key | Unique dated code issued per reservation |
| After checkout | Code still works until manually changed | Access lapses automatically at checkout time |
| Cleaning | Same code shared with the cleaner | Separate turnover-window credential per assignment |
| Audit | No record of who entered | Entry events show guest and cleaner windows |
| Scaled hosting | Inconsistent doors across units | One repeatable process across every apartment |
| Typical fit | Occasional single-room hosts | Professional and multi-unit short-term operators |
The unit entrance carries the guest code; building lobby, mailbox and amenity doors determine whether common-area controls are also needed.
| Opening | Typical door | Lock approach |
|---|---|---|
| Unit entrance | Apartment or house entry door | Reservation-dated lock with code and, where offered, mobile credential |
| Building lobby | Shared intercom or street door | Intercom code or common-door credential coordinated with the building |
| Turnover / linen | Cleaner cupboard or shared store | Assignment-window codes for housekeeping and linen partners |
| Amenity room | Gym, pool or co-work space in the block | Stay-dated credential where the building permits guest access |
| Back / side gate | Garden, parking or bin-store gate | Weather-rated lock with guest and service windows |
| Maintenance closet | Utility or boiler cupboard | Work-order code for technicians, never the guest code |
This example illustrates a typical configuration, not a specific customer project. Entrance count, building rules and turnover volume drive the list.
| Component | Typical logic | Notes |
|---|---|---|
| Entrance locks | One reservation-dated lock per rentable unit | Door thickness and fire rating confirmed per quotation |
| Common-door access | Lobby, gate and amenity credentials where the building allows | Coordination with strata or building management agreed in writing |
| Turnover controls | Cleaner and linen codes per assignment window | Separate from guest credentials and expired between bookings |
| Operating spares | Locks and batteries held for the portfolio | Battery replacement scheduled to turnover cycles under the current MOQ policy |
| Host setup | Listing-template arrival instructions and fallback contact | Documented before the first dated reservation goes live |
When a reservation is confirmed, a code is generated for that guest and the check-in to checkout window, then delivered through the host’s arrival instructions or messaging channel before arrival. The code opens the unit door and, where configured, the building lobby and permitted amenities, and it stops working at checkout without anyone visiting the property. For back-to-back bookings the next guest receives a new code while the cleaner holds a separate turnover-window code in between, so no two populations ever share a live credential. Hosts can still issue an assisted code manually when a booking platform or guest situation calls for it.
Windows are set against the listing’s check-in and checkout times, and hosts can extend a credential deliberately when a late checkout is approved or issue the cleaner a later window; early arrivals wait on the building or luggage policy rather than receiving a code that overlaps the previous guest or a servicing round. Keeping extensions deliberate matters, because an automatically widened window would undermine the separation between stays. The host dashboard makes a one-tap extension easy, and the pilot unit rehearses a same-day turnover to confirm the guest-expiry, cleaner-window and new-guest-activation sequence works under real timing pressure.
The lock is specified to enforce codes offline once they have been provisioned, so an arriving guest is not blocked by a home Wi-Fi outage, and battery operation continues through power loss. Management actions such as issuing a brand-new code need the management link, which is why hosts confirm provisioning timing before check-in day and keep a documented emergency path for rare lockouts. Battery level is monitored between stays so a low unit is serviced at turnover rather than mid-stay. Choosing hardware with clear offline behaviour and standard mechanical override documentation is part of the selection criteria rather than an after-purchase discovery.
When the unit sits behind a shared lobby, gate or intercom, guest access to those common doors must be coordinated with building management or the lease, because some buildings restrict transient codes or require the intercom directory to follow specific rules. The unit door itself is usually the host’s to equip, but fire-rated entrance doors and any master-keying used by management constrain which lock bodies fit. The door and building review confirms these points in writing before purchase, including whether cleaners may receive common-door credentials. Houses and private entrances avoid most of this coordination.
The BOM is one reservation-dated lock per rentable entrance, plus common-door, gate and amenity credentials only where the building permits them, with batteries and spares sized to turnover volume and MOQ confirmed in writing per quotation. Single hosts start with one unit, while professional managers run a pilot apartment then replicate the identical setup across the portfolio so listing instructions stay uniform. Send the door type, building common-door rules and monthly booking volume, and the quote maps hardware and spares to the actual turnover pattern.
Send the door type, building common-door rules and monthly booking volume — receive a per-entrance BOM with written MOQ and lead-time terms.
Discuss your project (RFQ)Project configurationsLast updated: October 31, 2026 · Reviewed by the Smart Lock Factory editorial team