A rental property should use a lock whose credential can be revoked without a truck roll, whose fallback works when the network does not, and whose

Đăng lúc: Th02 13, 2024

What Smart Lock Should a Rental Property Use?

What Smart Lock Should a Rental Property Use?

A rental property should use a lock whose credential can be revoked without a truck roll, whose fallback works when the network does not, and whose credential type matches the unit type — not one lock chosen once for the whole portfolio. The short answer for most mixed portfolios: a rotating-code path for short-term turnover, an individually revocable credential (card or personal code) for long-term tenants, a per-adult credential plan for shared occupancy, and a mechanical key as emergency backup on every door. Everything else in this article is the argument for that sentence.

Rather than a plain guide, this piece replays a real-shaped conversation we had on a sales-engineering call: a small portfolio owner with seventeen units — nine short-term, five long-term family tenancies, two shared-rental houses and one duplex with a live-in caretaker — and the lock supplier's sales engineer. The buyer's questions carry the structure; my annotation blocks between the turns add the parts neither party said out loud. Speakers are labeled Owner and Engineer; annotations are labeled Annotation. Scenario details are illustrative, not a customer record.

The opening exchange: one lock for the portfolio, or three paths?

Owner: I run seventeen units. Nine are short-term, five are longer tenancies, two are houses we rent bed-by-bed. Every lock supplier pitches me one hero product. I want to know which one to standardize on.

Engineer: The honest answer is that you should not standardize on one product. You should standardize on a revocation rule, and then pick hardware per unit type. What happens at your turnover — that is the question that selects the lock, not the other way around.

Annotation. This is the pivot of the whole article, and most buyers miss it. Portfolio owners buy uniformity because uniformity feels like operational simplicity: one SKU, one keyway, one manual. But a rental portfolio is three different access problems wearing one address. Short-term turnover is a frequency problem (a new credential every few days). Long-term tenancy is a privacy problem (one credential that must survive two years without leaking). Shared occupancy is an enrollment problem (how many people legitimately hold a credential, and what happens when one of four flatmates moves out mid-term). A lock that is excellent at one is usually mediocre at another. The correct procurement artifact is a unit-type decision matrix, and the sales engineer who hands you that matrix instead of a catalog is the one worth keeping on the phone.

Unit typeCore access problemCredential path that fitsTypical failure being prevented
Short-term (9 units here)High-frequency guest changeoverPer-booking code or card issued at check-in, expired at checkoutShared master codes leaking to review sites
Long-term family tenancy (5 units)Low-frequency but privacy-sensitiveOne personal code or one RFID card per tenancy, revoked only at lease endLandlord entering without notice; code reuse by former tenants
Shared house (2 units)Many co-existing holders, staggered departuresOne credential per named adult, individually deletableOne departure forcing re-enrollment of everyone
Caretaker / utility (duplex + store)Staff access independent of residentsScheduled staff credential with time windowOff-hours access after a caretaker leaves

Turnover and re-keying: what actually has to change

Owner: Today, every long-term move-out means a locksmith visit and new cylinders in the doors — sometimes at move-in too, depending on the state. If I go electronic, what replaces re-keying?

Engineer: Credential deletion replaces re-keying, but only if the lock lets you delete a single credential without touching the others. On a keypad model, the outgoing tenant's code is invalidated and a fresh code is enrolled for the incoming household — the door hardware is not touched at all. On a card-based lock, the old card is de-authorized or the lock is cleared and re-initialized, like the card-reset step guests never see in a hotel. On a fingerprint lock, you delete the stored prints. The re-keying labor does not vanish; it moves from the door to the credential list, and it takes minutes instead of a truck roll.

Owner: Minutes I have to spend on every single turnover, across seventeen doors.

Engineer: Yes — and that is exactly why your nine short-term doors should not use the same mechanism as your five long-term doors. For short-term units, you want turnover to cost no touch: a code whose validity window ends by itself. For long-term units, you want one clean delete-and-enroll event per tenancy, which is rare enough to do manually.

Annotation. The industry euphemism "no re-keying needed" hides three genuinely different operations, and buyers should ask which one a lock performs. First: overwrite — the new code simply replaces the old one-slot credential. Common on cheap keypads, but it means only one active code exists at a time, so the household cannot keep a personal code and hand a separate one to a cleaner. Second: clear-and-reinitialize — every credential on the lock is wiped and rebuilt, which is the hotel-card pattern; safe on turnover, annoying mid-tenancy because the family loses their own cards too. Third: selective delete — remove one named credential while the rest survive; this is what shared houses need. Ask the supplier, per model, which of the three you are buying, and how many credential slots exist per type. The lock's own event log helps here: locks such as the SLK-9936S record door events locally (its published spec block cites audit/event records up to 1,000), so after a dispute you can see which credential opened the door and when, instead of arguing from memory. That log lives on the lock, not in the cloud — which matters later.

Temporary codes for cleaners versus the tenant's own PIN

Owner: My short-term units run on cleaner codes every turnaround. My long-term tenants hate the idea that I know their door code, and honestly they hate that I could know it. How do I keep cleaners working and tenants private on the same hardware?

Engineer: Two separate credential lanes. Cleaners get a code issued per visit with a validity window — Tuesday 9:00 to 14:00, one use or one-day use, different every time. The tenant gets a personal code the landlord never needs to know if the lock supports enrolling a code at the keypad without a prior code from the app side. When a dispute happens, the audit trail shows the cleaner's windowed code was used Tuesday at 11:40 — nobody had to reveal the tenant's PIN to prove it.

Owner: Can I see, after the fact, whether a cleaner used their code early?

Engineer: On models with event records, yes — a code used outside its window is rejected and the rejection is recorded. That is the operational difference between a windowed code and a standing spare key hidden in the garden.

Annotation. Tenants read "the landlord can generate a code for my door" as surveillance; cleaners read "you must let me in person" as wasted labor hours. A well-run rental lock policy resolves both by separating identity from access: nobody shares a code, so nobody needs to disclose one. Two rules are worth borrowing from hotel practice. First, no universal code, ever — one code per person per purpose, which is also how the SLK-9936S-class card systems avoid the master-credential disaster that a copied "all-access" code creates across a portfolio. Second, expiry is the default, not the exception — a credential without an end date is a debt you pay at move-out. If you want ready-made wording for lease addenda and cleaner handbooks on exactly this (window definitions, notice conventions, what happens when a window code fails at 8 a.m.), the sibling piece on lease and cleaner handbook wording for guest and service entry is built as a clause library; use it, do not reinvent it in an email.

ActorCredential shapeIssued byExpires whenWhat the tenant can infer
Short-term guestPer-booking codeAuto or front deskCheckout timeOnly their own code; no shared secret
Cleaner / maintenanceSingle-window codeOwner or appEnd of the visit windowStaff entered at a known time, for a known job
Long-term tenantPersonal code, enrolled locallyTenant at the keypadLease end (landlord deletes)Landlord does not need to know it
Flatmate (shared house)Own card or printEnrolled at move-inThat person's departureRoommate leaving does not lock them all out

Keypad or fingerprint for a shared house?

Owner: The two bed-rental houses are the hardest. Three or four unrelated adults, staggered move-outs, and I am the one holding the spare key in a drawer like a nineteenth-century custodian.

Engineer: Then decide on two questions, not one. Question one: how many named adults must hold a credential at once? A keypad with multiple user slots handles four personal codes fine; a keypad with a single master-plus-visitor structure does not. Question two: what happens when one flatmate leaves mid-term? With codes, you delete one code — but codes travel (a departed flatmate may have photographed the keypad's worn buttons and inferred the PIN; clean the keypad surface and rotate codes after disputes anyway). With fingerprints, you delete one enrolled finger and the physical guessing problem disappears — but you now handle biometric enrollment, which some adults resist and some jurisdictions treat specially.

Owner: My gut says the flatmates would rather give a finger than share a code.

Engineer: Then a multi-user fingerprint-or-hybrid model is reasonable there. Keep in mind two shared-occupancy quirks: guest keys. A flatmate's partner staying a week needs a temporary credential, not a copy of someone's finger — so even on fingerprint doors, keep a code or card lane alive. And gloves, wet hands, manual labor: enrolled prints read worse for some tenants than others; every shared door needs a non-biometric fallback that a hungry 2 a.m. returning resident can use.

Annotation. The catalog's fingerprint and keypad categories both carry viable hardware for this, but do not let a feature list decide it: the deciding spec is per-user capacity and individual deletion, which is not always printed. Our hybrid multi-method models — the SLK-8831 class is published as a five-method lock (fingerprint, password, card, mechanical key and app) — show the right shape: several credential lanes co-existing precisely so that one lane's weakness (biometric refusal, wet finger, forgotten code) never strands the household. For the narrower edge doors some shared Victorian stock has, the narrow-edge four-in-1 class (SLK-1104) is in the same conversation with a waterproof exterior option. But every capacity number — how many prints, how many codes, how many cards per door — is verified in writing for your specific SKU: confirm it on the product page before you quote the layout to your letting agent. There is no universal industry number.

The Wi-Fi assumption that fails, and what standalone means

Owner: Last winter our broadband died for a day over half the street. My neighbour's "smart" rental lock stranded a guest outside because the code was cloud-generated. I need to understand what actually runs on the lock.

Engineer: For the locks we sell into your class of project, the lock itself is a standalone device. The credential list lives inside the lock; the code is verified locally against that list; the door opens with the network down. What dies without connectivity is the convenience layer: remote issuance, instant revocation at the front desk, and same-minute log export. If a booking's code was issued before the outage, the guest walks in during the outage and nobody knows. If it needed to be issued during the outage, that is when your phone number replaces your app.

Owner: So the honest architecture is: local brain, remote convenience.

Engineer: Exactly. And one more sentence I want you to repeat back: do not buy any lock on the assumption that it has Wi-Fi. Check the model’s published specification whether Wi-Fi is offered for that model. Many of our catalog models talk to a phone over Bluetooth via a supported app platform; Wi-Fi or bridge-style connectivity, where it exists, is per-model and per-generation. If your operating plan needs remote issuance during an outage, then remote issuance cannot depend on one lock's radio — it needs the hotel-style pattern instead: a laptop and card encoder on-site, which is how centralized hotel systems keep issuing when the internet is down, because the write happens at the desk, not in the cloud.

flowchart TD
    A[Guest or tenant enters credential at the door] --> B{Lock holds credential locally?}
    B -- Yes --> C[Motor unlocks, event written to local log]
    B -- No / credential expired --> D[Reject, reason written to local log]
    C --> E{Connectivity available?}
    D --> E
    E -- Yes --> F[App or management software syncs the event records]
    E -- No --> G[Lock keeps working standalone; records sync later or are read at the device]
    G --> H[Outage cost: delayed issuance and late logs, NOT a locked door]

Annotation. This diagram is the most under-sold asset in the category. Retail marketing collapses "smart lock" into "works with the internet", so rental operators buy on a connectivity story and discover the standalone reality during an outage. Read the spec block as the counterweight. Take the SLK-9936S's published line set as the worked example — door thickness 36–100 mm, RFID Mifare 1 at 13.56 MHz with 0–5 cm read distance and sub-quarter-second reads, 4 × AA cells rated above 15,000 battery operating cycles, audit/event records up to 1,000, a 5-pin cylinder with 3-point latch, mechanical emergency access, and management software that runs in standalone or centralized database modes. Notice what is not in that block: no Wi-Fi promise. The card is written at a desk encoder, the log lives in the lock, and the software syncs when it can. Those are architectural choices a rental portfolio should steal for its short-term units: turnover handled by credential lifecycle (issue at check-in, die at checkout), network treated as optional. The full first-party line-by-line dissection of that model is on its product page; the reason why short-term rental hardware demand keeps pulling suppliers toward exactly this card-and-code shape is covered in the market analysis of the short-term rental segment.

Batteries, winter and the second failure people forget

Owner: If the network is the first failure, what is the second?

Engineer: Power. A dead set of cells does to a keypad lock what an outage does to a cloud lock — but slower and sneakier, because low-voltage behavior degrades in cold before it fails outright, and lockouts cluster in exactly the weeks you have the most turnovers. Two rules: buy only models with visible low-battery warning thresholds and an emergency power path the installer can demonstrate — most field failures are untrained staff, not untrained locks — and treat the mechanical key that ships in the box as a portfolio asset with a custody rule, not as packaging filler.

Annotation. There is a whole standing discipline around what to do when lock batteries run out during turnover-season lockouts — cell chemistry, winter drain, warning thresholds and spare-cell custody — linked rather than re-hashed here, because this article's point is the purchase decision: battery behavior is a per-model spec to verify against the model’s published specification, and "4 × AA" in a quote email is not a battery strategy. The SLK-9936S block again shows what a serious line looks like — cells specified, operating cycles stated above 15,000 — which is the format to demand from any supplier, on any SKU, in writing.

What each door in this portfolio should get: the closing table

Owner: Can you compress this into my procurement sheet?

Engineer: Four rows, one per unit type. Ask each row's questions before you ask for a price.

Portfolio segment (illustrative: this 17-unit case)Mechanism to specifyFirst question for the supplierRed flag in the answer
9 short-term unitsWindow-expiring code or check-in card issued centrally"Does the credential expire without anyone touching the lock?""Works with our app" as the only expiry story — check what happens offline
5 long-term tenanciesPersonal code enrolled locally, landlord-deletable at lease end"Can the tenant set their own code without me ever seeing it?"Single-credential keypads with no user slots
2 shared housesPer-adult credential, selective delete, non-biometric fallback lane"How many users, and can I delete exactly one?""Clear all or nothing" credential management
Caretaker + utility doorsTime-windowed staff credential over the emergency key"Can access be limited by day and hour, not just deleted?"No schedule concept; keys as the only staff path

Annotation. Note the discipline in that table: the unit-type matrix at the start was diagnosis, this is specification, and both come before any SKU name appears. That ordering is why this article does not hand you a single hero lock. It is also why a mixed portfolio's RFQ usually goes out with two or three model families — a hotel-card-and-code class for the short-term turnover block, a multi-user keypad-or-hybrid class for tenanted doors (that class is walked through unit by unit in the SLK-8831 rental-property application guide), a narrow-edge or glass variant where the doors demand it (the SLK-G200 class exists for glass doors; its rental-duty detail fields are verified in writing ed on the page, before anyone proposes it for a tenanted rear entrance). If you are comparing per-door types for a whole building rather than a scattered portfolio, the sibling walkthrough on apartment-building procurement sequencing takes the same revocation-first logic through a 68-door single site; this conversation stays deliberately on the mixed-use, multi-unit-type case where one-standard-lock is the tempting and wrong answer.

Reading the spec block like a rental operator

The lines that matter for rentals are not the marketing lines. Here is how each part of a published spec block (using the SLK-9936S lines as the worked example, since it is the block we can quote exactly) answers a rental question:

Spec line (example: SLK-9936S, PDP-cited)What it decides for a rental portfolio
Door thickness 36–100 mmWhether one SKU spans your 1930s doors and your modern ones — measure first
RFID Mifare 1 @ 13.56 MHz, 0–5 cm, <0.25 sCard lane speed at check-in queue; card stock cost per turnover
4 × AA, >15,000 operating cyclesVisits between battery changes at your busiest short-term door
Audit/event records up to 1,000How far back you can answer a damage or entry dispute
Mechanical emergency accessThe 2 a.m. fallback that no app or cloud replaces
Standalone or centralized database modesWhether your office can keep issuing when the line is down
Multilingual management softwareStaff turnover in the cleaning crew; readable front-desk tools

Annotation. For every other model you shortlist — the 9936G, the 9905A hidden-reader, the 8831 five-method hybrid, the SLK-1104 narrow-edge, the G200 glass lock — the same table is your worksheet, and every cell you cannot source from that model's own product page is verified in writing, not "close enough" from the 9936S. A supplier who accepts "send me this table filled in per SKU" is being asked for evidence, not favors; that single RFQ clause separates catalog factories from dropshippers faster than any factory-tour video. And the connectivity row deserves one more restatement, because this title family keeps drifting there: several catalog models pair with a phone app over Bluetooth through a supported platform; Wi-Fi is not a blanket catalog claim — check the model’s published specification whether Wi-Fi is offered for the exact model and generation in your quote.

The questions this call should have ended with

Owner: So when I send this to you as an RFQ, what am I really asking for?

Engineer: Three sample doors, one per unit type, and one filled spec table per model. Test the turnover on the sample before the fleet: issue a credential, expire it, try the mechanical key, pull the event records, and cut the office internet mid-test. If your supplier hesitates on any cell of the table, that hesitation is the finding — not the price.

Annotation. That test protocol is the whole article in one paragraph, and it is worth writing into your sample request verbatim. Order samples the three segment types; run the outage drill; then request a quote scoped per segment rather than one SKU across seventeen doors. A rental property should use a lock chosen by what has to change at turnover — one code, one card, one finger, or one whole credential list — and a supplier who cannot say plainly which of those you are buying is selling you the wrong box.

Giỏ hàng của bạn
Trải nghiệm của bạn trên trang web này sẽ được cải thiện bằng cách cho phép cookie Chính sách cookie
Chat on WhatsApp