How to Choose Between Smart Lock Technologies — Flagship Pillar for B2B Buyers
Answer in the first 100 words. Choosing between smart lock technologies is not a single decision — it is a four-layer stack: (1) credential layer (PIN, RFID card, fingerprint, face, mechanical key, Bluetooth phone), (2) connectivity layer (standalone, Bluetooth, Wi-Fi, 4G, hotel PC-software over RS-485/Wi-Fi), (3) management layer (on-lock master code, TTLock / Tuya / Doodle app, or hotel PC-software in centralized-database mode), and (4) form-factor layer (mortise, cylindrical, glass-door, outdoor/aluminum, narrow-edge, cabinet). The correct stack is the one that fits the door population's credential turnover, audit posture, network reach, and door geometry — not the one with the longest feature list. Every per-model figure (read range, audit-event depth, app-platform binding, door-thickness envelope, mechanical-override posture) must be recorded in the model specification; this pillar lays out the decision rules, not the spec sheet.
This pillar is the technology-selection hub for the SmartLockFactory.com comparison cluster. Sibling articles /840 (keyless vs smart), /843 (smart vs RFID), /844 (smart vs Bluetooth), /845 (smart vs Wi-Fi), /810 (RFID vs PIN for commercial), /813 (Bluetooth vs Wi-Fi for commercial), /817 (mobile key vs RFID key card), /820 (PIN vs RFID for hotels), /821 (Bluetooth vs RFID for hotels) all sit beneath it as one-on-one comparisons; this article is the place a buyer lands first when they do not yet know which one-on-one they need. Site flow beyond the article is fixed: the buyer uses the rules here to shortlist a technology stack, then moves to model selection and product pages, then to /request-a-quote to verify in writing quantity, customization, and shipping terms.
No prices, MOQ floors, lead-time day counts, warranty years, or certification claims appear anywhere in this body. Every commercial term resolves to /request-a-quote; every per-model figure resolves to the dated product page; every catalog-coverage number (79 published models, 24 hotel locks, 37 fingerprint SKUs, 18 keypad SKUs, 9 RFID SKUs, 10 outdoor SKUs, 6 face-recognition SKUs, 6 cabinet SKUs, 3 video-camera SKUs, 3 glass SKUs) appears here only as catalog-coverage context, not as a category recommendation.
The Four-Layer Technology Stack
Every smart lock in this catalog is the combination of four engineering choices. The buyer is choosing a stack, not a brand.
| Layer | What it answers | Choices in this catalog | Where it is decided |
|---|---|---|---|
| Credential | What opens the door | PIN / RFID card / fingerprint / face / mechanical key / Bluetooth phone / 4G intercom | Per SKU on the product page |
| Connectivity | How the credential list travels | Stand-alone / Bluetooth / Wi-Fi / 4G / hotel PC-software | Per SKU + deployment mode |
| Management | Who runs the credential list | On-lock master code / TTLock / Tuya / Doodle / hotel PC-software | Per SKU + binding decision |
| Form factor | What door geometry it fits | Mortise / cylindrical / glass-door / outdoor/aluminum / narrow-edge / cabinet | Per SKU + door survey |
Reading rule. Lock the form-factor layer first (because the door geometry is fixed by the building), then the credential layer (because the people who pass through are fixed by the door population), then the connectivity and management layers (because those are operational choices the buyer can change after installation). Buying the wrong order — picking an app first, then discovering the door cannot accept a mortise — is the most common B2B procurement error.
Layer 1 — Credential Layer (What Opens the Door)
The credential layer is the surface the user touches. Each credential carries a different issuance path, a different loss profile, and a different audit signature. The seven credential surfaces that appear in the catalog are listed below with their primary use case and the catalog families that ship them. Per-SKU credential combinations must be confirmed on each product page; this table is the catalog-coverage map only.
| Credential | Primary use case | Catalog coverage | Loss profile |
|---|---|---|---|
| Mechanical key | Emergency override on every networked SKU | All lock families | Must be physically secured, no audit trail |
| PIN (keypad code) | Short-stay guests, staff doors, plant rooms | 18-model keypad family; co-present on most hotel and fingerprint units | Rotated, not issued as object |
| RFID/IC card | Hotel guests, multi-tenant common doors, staff entry | 9-model RFID family; hotel line; legacy 20-SKU RFTC-RF range (118/118E/228/230/232/238/239/253/305/306/308/309/502/620/621/911/002/019/022/2020/760) | Issued object, voided in software |
| Fingerprint | Owner-occupied units, owner-card-holding tenants, time-clock doors | 37-model fingerprint family; co-present on many keypad and hotel SKUs | Biometric, cannot be reissued |
| Bluetooth phone (app credential) | Tenant mobile access, B2B app-bound fleet | App-bound variants across fingerprint, keypad, and cylindrical families (TTLock / Tuya / Doodle bindings) | Phone-bound, voidable in software |
| 3D face | High-traffic lobbies, premium commercial entry | 6-model face-recognition family (9L5-R, Q7, Future 1, B09 double-opening, others) | Biometric, cannot be reissued |
| 4G intercom / cat-eye credential | Construction sites, unattended gates, projects where Wi-Fi is unreliable | Video-camera family (Q7 intercom, 516 cat-eye, 4G model) | Phone-bound over cellular |
Reading rule. The credential mix on a single SKU is rarely one. The SLK-8831 5-in-1 reference unit combines fingerprint, password, card, key, and app in a single body, and that combination is the most common shipping configuration across the catalog. The question the buyer is really asking is not "which credential" but "which mix, on which doors, with which override."
Layer 2 — Connectivity Layer (How the Credential List Travels)
Connectivity is the network posture of the lock. It decides whether the credential list is held on the door, on a phone, or on a server, and whether the operator can issue, void, and time-bind credentials remotely.
| Connectivity mode | What it does | Typical deployment | Audit posture |
|---|---|---|---|
| Stand-alone | Credential list on the lock, no radio | Back-of-house, plant rooms, low-traffic storage | On-device only, downloadable via master card |
| Bluetooth (BLE) | Credential list on a phone app, lock reaches phone when in range | Tenant units, residential retrofit, mid-size B2B | App-side event log, lock-side audit buffer |
| Wi-Fi | Credential list on a cloud platform, lock talks to AP | Multi-site offices, remote void requirement | Cloud-side event log; lock event buffer required for offline periods |
| 4G / cellular | Lock carries its own SIM | Construction sites, gates with no local network | Cloud-side, cellular as transport |
| Hotel PC-software (RS-485 / Wi-Fi / TCP/IP) | Credential list on a hotel server, locks polled by the front-desk software | Hotel guest rooms, back-of-house, common doors | PC-software-side event log, lock audit buffer required |
Reading rule. Bluetooth, Wi-Fi, and 4G are transport; the credential list still has to live somewhere. "App-bound" means the list lives in the app vendor's cloud or on a gateway. "PC-software-bound" means the list lives on the hotel server. Stand-alone means the list lives on the door. The three locations are not interchangeable: a stand-alone lock cannot be turned into a hotel-PC-software lock by adding an app, because the audit format and the encoding rules are different.
Layer 3 — Management Layer (Who Runs the Credential List)
The management layer is where credentials are issued, voided, time-bound, and audited. Three management platforms are present in this catalog. Anything outside them — Matter, Zigbee, Apple Home Key, palm-vein — is not in the catalog and must not be claimed to exist.
| Platform | Catalog binding | Where the credential list lives | Audit export path |
|---|---|---|---|
| TTLock | App-bound BLE units across fingerprint, keypad, and cylindrical families | Phone + TTLock cloud | App export, cloud export |
| Tuya | App-bound BLE units, including the cylindrical Tuya round-code SKU | Phone + Tuya cloud | App export, Tuya cloud export |
| Doodle | App-bound BLE units and selected hotel-line SKUs | Phone + Doodle cloud | App export, Doodle cloud export |
| Hotel PC-software | 24-model hotel line, operating in centralized-database mode | Hotel server | PC-software export; lock-side audit buffer used for offline event replay |
| Stand-alone master code | Any stand-alone-configured SKU | On the lock | Master-card downloader or keypad admin menu |
Reading rule. The platform choice is a contract — once a fleet is bound to TTLock, Tuya, or Doodle, the operator's credential issuance workflow is locked to that app's data model for the lifetime of the fleet. The hotel PC-software path is a separate contract with its own encoder hardware, its own PMS handshake, and its own card-encoding rule set. Mixing platforms within one property is operationally expensive; mixing within one door population is the most common procurement mistake in this layer.
Layer 4 — Form-Factor Layer (What Door Geometry It Fits)
The form-factor layer is the most binding. Once a door exists, the form-factor choices narrow immediately.
| Form factor | Door population it fits | Catalog coverage |
|---|---|---|
| Mortise (standard and ANSI) | Wooden/metal residential and commercial doors, hotel guest rooms | Hotel line (24), most fingerprint (37) and keypad (18) families |
| Cylindrical latch | Retrofit residential, light commercial, mid-size offices | Cylindrical Tuya round-code SKU; parts of the keypad and fingerprint families |
| Glass-door patch lock | Frameless glass doors, retail storefronts | SLK-G200, B09 (double-opening face-recognition), 3-model glass family |
| Outdoor / aluminum-door mortise | Gates, aluminum doors, exterior entries | D11, D12, D15, ODS, DQ outdoor family (10-model outdoor coverage) |
| Narrow-edge / rim | Security doors, armored doors, narrow-stile frames | SLK-1104-class narrow-edge 4-in-1 waterproof family |
| Cabinet / drawer | Lockers, file cabinets, package rooms | 6-model cabinet family |
| Hotel-line ANSI mortise | Hotel guest rooms, 1–5 star | 24-model hotel line, with the SLK-9936S profile block as anchor |
Reading rule. Door geometry is decided by the building, not by the buyer. The right procurement sequence is: door survey → form-factor family → credential and connectivity choice for that family → platform binding. Doing it in any other order produces a shortlist of SKUs that cannot physically ship to the property.
The SLK-9936S First-Party Spec Block (Documentation-Granularity Yardstick)
For buyers familiarizing themselves with the level of detail a hotel-line SKU document carries, the SLK-9936S profile block illustrates what "per-SKU spec" means in this catalog. This block is quoted ONCE, below, as a documentation-granularity example. None of these figures should be ported to any other SKU — every figure must be reconfirmed on each product's own dated page.
| Spec line | SLK-9936S value | Documentation purpose |
|---|---|---|
| Door thickness envelope | 36–100 mm | Door-population fit (single line) |
| Credential carrier | RFID Mifare 1 @ 13.56 MHz | Credential-layer identity (single line) |
| Read distance | 0–5 cm | UX expectation (single line) |
| Read time | < 0.25 s | Latency expectation (single line) |
| Power format | 4 × AA | Battery format (single line) |
| Battery operating cycles | > 15,000 | Maintenance expectation (single line) |
| Audit / event records | Up to 1,000 | Centralized-database audit posture (single line) |
| Cylinder format | 5-pin mechanical | Mechanical-override posture (single line) |
| Latch architecture | 3-point | Forced-entry posture (single line) |
| Body construction | Stainless steel + alloy | Material/body line (single line) |
| Finish options | Multiple | Cosmetic fit to property (single line) |
| Emergency access | Mechanical | Master-credential fallback (single line) |
| Management software | Multilingual PC software, standalone OR centralized mode | Management-layer identity (single line) |
| Target property tier | 1–5 star hotels | Deployment band (single line) |
The point of quoting this block is not to give the buyer a figure they can transpose onto another SKU. The point is to show that a complete hotel-line spec block is roughly 14 lines long, and that the buyer should expect — and demand — the same depth from every other SKU they shortlist. Anything shorter is a brochure, not a spec.
Decision Matrix — Technology Stack by Door Population
The matrix below maps ten common door populations to the technology stack that fits them. The matrix is generic; per-SKU figures (read range, audit depth, app-platform binding) always route to the dated product page.
| Door population | Form factor | Credential layer | Connectivity | Management | Why this stack |
|---|---|---|---|---|---|
| Hotel guest room | Hotel mortise (SLK-9936S profile) | RFID card + mechanical key | Hotel PC-software link | Centralized-DB mode via hotel server | High credential turnover, audit required, PMS handshake |
| Hotel back-of-house | Same hotel mortise family | RFID card, sometimes PIN | Hotel PC-software link | Centralized-DB mode | Staff turn-over, time-bound shift credentials |
| Hotel plant room | Mortise, light-duty | PIN only | Stand-alone | Master code on the lock | Low traffic, network may not extend; no audit demand |
| Apartment unit | Mortise or cylindrical, app-capable | Bluetooth phone + PIN + fingerprint fallback | BLE | TTLock / Tuya / Doodle binding | Tenant mobile credential; mechanical and PIN backup |
| Apartment common entrance | Mortise, heavier-duty | RFID + PIN + Bluetooth | BLE gateway if available | TTLock / Tuya / Doodle binding | High traffic, remote-void requirement |
| Office staff entrance | Mortise | PIN + RFID + Bluetooth | Wi-Fi | TTLock / Tuya / Doodle binding | Time-bound codes, audit on demand |
| Office meeting room | Mortise, light-duty | PIN, optional Bluetooth | Stand-alone or BLE | On-lock master, optional app binding | Re-programmable per meeting; offline-acceptable |
| Server / IT room | Mortise, heavier-duty | RFID or fingerprint + PIN | Wi-Fi | Audit-mandatory platform | Regulatory audit, incident review |
| Outdoor gate | Outdoor / aluminum mortise | PIN + fingerprint or RFID | Stand-alone preferred | On-lock master | Network unreliable, weather exposure |
| Glass storefront | Patch lock (SLK-G200 / B09 / 3-glass family) | RFID or face + PIN | BLE or stand-alone | App-bound or master code | No mortise cavity available |
Reading rule. The matrix is intentionally stack-shaped, not SKU-shaped. The buyer should pick the row first; the SKU is the second click on the same row.
Scorecard — Six-Factor Stack-Fit Scorecard
Use the scorecard below on each candidate SKU before shortlisting. Each factor is scored 1 (poor fit) to 5 (strong fit) against the door population the SKU is intended for. Any row scoring under 3 is a binding constraint.
| Factor | What to score | 1 (poor) | 3 (acceptable) | 5 (strong) | Source |
|---|---|---|---|---|---|
| Form-factor fit | Door geometry match | Bore/cover mismatch | Adaptor available | Direct fit | Product page + site survey |
| Credential coverage | All required credential types present | Missing one required | All required, extras irrelevant | All required + smart extras | Product page |
| Connectivity reach | Network available at the door | No network | BLE-only works | Wi-Fi or PC-software works | Site survey |
| Management platform fit | Platform binding aligns with operator stack | Wrong platform, lock-in risk | Compatible platform | Operator's existing platform | RFQ + audit-trail test |
| Audit posture | Audit log depth, export format, retention | No audit | Buffer only | PC-software export, retention documented | Product page + RFQ |
| Mechanical override | Emergency-access path documented and exercised | Undocumented | Documented, not tested | Documented + tested on sample | RFQ + sample-test plan |
A shortlist that does not clear 24 / 30 on this scorecard is not production-ready. Run it on every SKU on the candidate list; flag the failing rows; ask for substitutes or follow-up evidence before /request-a-quote.
Illustrative Project Scenario — A 120-Room Mixed-Use Property
Consider a 120-room mixed-use property in a coastal secondary city. The property has 80 hotel keys running under a regional PMS, 30 long-stay serviced-apartment units on three-month leases, and 10 short-stay retail tenants at street level. The four-layer stack resolves as follows.
- Hotel keys (80 doors). Form factor: hotel-line mortise family, with the SLK-9936S profile as the documentation yardstick. Credential: RFID Mifare 1 plus mechanical key. Connectivity: hotel PC-software link. Management: centralized-database mode via hotel server. Reason: high credential turnover, PMS handshake, audit-mandatory posture.
- Serviced apartments (30 doors). Form factor: cylindrical latch retrofit for the renovation-block doors; mortise for the new-build block. Credential: Bluetooth phone plus PIN plus fingerprint fallback. Connectivity: BLE. Management: TTLock or Tuya binding tied to the tenant app. Reason: tenant mobile credential, mechanical and PIN backup, no PMS handshake needed.
- Retail tenants (10 doors). Form factor: glass-door patch lock (SLK-G200 / glass family). Credential: RFID or face plus PIN. Connectivity: BLE or stand-alone. Management: app-bound or master-code. Reason: no mortise cavity, low credential turnover, app-bound because retail managers rotate frequently.
The property holds three technology stacks across three door populations, not one stack applied estate-wide. The single biggest procurement mistake in a project like this is buying the platform that fits the hotel line and forcing it onto the apartments and the retail doors; the right move is to keep the platform binding per door population and document the cross-platform transition points at the property boundary (front desk, lobby corridor, parking gate).
The site flow that follows this scenario is fixed: the buyer uses this article to pick the stack per door population, walks to each stack's PDP row to verify in writing the SKU, then walks to /request-a-quote to verify in writing quantity and customization; production begins after the sample is approved; shipping is routed via the same quote conversation.
Cross-Stack Failure Modes the Buyer Should Engineer Against
Failure 1 — picking an app-binding platform, then expecting hotel PMS integration. TTLock, Tuya, and Doodle are not PMSes. A property that needs PMS handshake needs the hotel PC-software path, on hotel-line hardware, in centralized-database mode. Defense: for any property with a PMS commitment, default the guest-room stack to the hotel-line family; reserve app-bound SKUs for non-PMS doors (plant rooms, retail fronts).
Failure 2 — picking stand-alone because "no network," then needing an audit trail six months later. A stand-alone lock keeps its events on the door, and the events are only retrievable by walking to the door with a master card. Defense: every door that will be audited (server rooms, common entrances, any door with regulated access) needs connectivity from day one; stand-alone is reserved for genuinely low-risk, low-traffic doors.
Failure 3 — picking a fingerprint SKU, then discovering the credential cannot be reissued. Fingerprints are not credentials that can be rotated; they are biometric ties. A fingerprint list of 200 employees means 200 employees cannot have their credential revoked without losing the slot. Defense: the 37-model fingerprint family is best reserved for owner-occupied units and small-employee pools; high-turnover workforces need RFID or BLE.
Failure 4 — buying three platforms, then expecting one operation team to run them. TTLock, Tuya, Doodle, and the hotel PC-software each carry their own admin workflow. Mixing them multiplies the operator's per-day workload; consolidating on one binding reduces it. Defense: pick one platform per door population, document the cross-platform hand-off, and do not introduce a fourth platform on retrofit.
Failure 5 — assuming the form-factor layer is interchangeable. Mortise, cylindrical, glass, outdoor, narrow-edge, and cabinet cannot be swapped on the same door without re-work. Defense: the door survey comes first; the platform discussion comes after the form factor is locked.
Six-Factor Stack-Fit Checklist (Quote-Ready Worksheet)
Use this checklist on each candidate SKU before sending /request-a-quote. Every cell is verified in writing — write the answer you need from the factory, or leave it blank and chase it down.
| # | Check | Required at quote | Check against the model specification | Notes |
|---|---|---|---|---|
| 1 | Form-factor family | Yes | Yes | Door thickness, backset, bore spacing |
| 2 | Credential stack on the SKU | Yes | Yes | PIN / RFID / fingerprint / face / key / app |
| 3 | Connectivity mode the SKU supports | Yes | Yes | Stand-alone / BLE / Wi-Fi / 4G / hotel PC-software |
| 4 | Platform binding (TTLock / Tuya / Doodle / hotel PC-software) | Yes | Yes | One platform per door population |
| 5 | Audit-event buffer depth and export format | Yes | Yes | Buffer, retention, export path |
| 6 | Mechanical-override posture and cylinder format | Yes | Yes | Key format, master-code path, battery-backup path |
A SKU with fewer than four of the six rows confirmed is not ready to order. The factory should not be asked to ship until the worksheet is filled.
Frequently Asked Questions
Q1. What is the single most important factor when choosing between smart lock technologies?Door geometry. If the form-factor does not fit the door, the credential and connectivity choices do not matter. The four-layer stack should always be evaluated in order — form factor first, credential layer second, connectivity and management layers last — because form factor is the only layer the building fixes; everything else can be reconfigured post-installation.
Q2. Are TTLock, Tuya, and Doodle interchangeable?No. They are three different platform contracts. Each one carries its own admin workflow, its own user-data schema, and its own credential-issuance model. Once a fleet is bound to one of them, the operator's daily workflow is locked to that platform for the lifetime of the fleet. The choice between them should be made by compatibility with the operator's existing app stack, not by feature checklist.
Q3. Can a fingerprint smart lock be reissued to a new employee?No. A fingerprint is a biometric tie to one person and cannot be rotated like a card or a code. The 37-model fingerprint family is best suited to owner-occupied residential units, small stable employee pools, and time-clock doors where the same person uses the lock every day. High-turnover workforces, shift-based operations, and outsourced service staff should be managed on RFID or Bluetooth credentials instead.
Q4. What is the difference between a smart lock and a hotel-PC-software lock?The hardware may be identical, but the management contract is not. A smart lock runs its credential list through an app platform (TTLock, Tuya, or Doodle) and the operator uses the app to issue, void, and audit credentials. A hotel-PC-software lock runs its credential list through a hotel server, with the locks configured in centralized-database mode, and the operator uses the hotel's PC software (not a phone app) to manage credentials. The two paths use different encoding rules, different audit formats, and different PMS handshakes; they cannot be mixed on the same door.
Q5. How many SKUs in this catalog are fingerprint locks?Thirty-seven. The fingerprint family is the largest single credential category in the catalog and ships across mortise, cylindrical, and outdoor form factors. The exact SKU list (which door thicknesses, which app bindings, which mechanical overrides) is sourced per SKU on the dated product page; this catalog-level count is for sizing only, not for SKU recommendation.
Q6. Can a stand-alone lock be upgraded to a connected smart lock later?In some product families, yes; in others, no. The matrix on each product page controls this. Even where the radio is present, the credential-list format on the door may be different from the format a connected platform expects, meaning a re-enrollment of every credential. Stand-alone is not a "deploy now, connect later" free option on every SKU; it is a deployment decision that should be made with the retrofit path already mapped.
Q7. Should the same platform run across an entire property?Usually, yes — but not always. The 24-model hotel line uses the hotel PC-software path in centralized-database mode, and a property with a PMS commitment must use that path on guest-room doors even if the rest of the property is bound to TTLock, Tuya, or Doodle. The cross-platform transition points (front desk, lobby corridor, parking gate) should be documented at the design stage. A property that mixes three platforms across three door populations is operationally expensive; mixing within one door population is the most common procurement mistake.
Closing — The Site Flow Beyond This Article
The site flow beyond this pillar is fixed. The buyer uses the four-layer stack and the door-population matrix above to shortlist a technology stack per door population; the SKU is recorded in the model specification (/fingerprint-door-lock, /hotel-lock, /rfid-door-lock, /bluetooth-lock, /keypad-door-lock as the category entries, and per-SKU pages below them); quantity, customization, finishes, and OEM/ODM terms are confirmed via /request-a-quote; sample approval precedes production; production precedes shipping; spare-parts and post-shipment support follow the same quote conversation. Certification-related questions are routed to /certifications for buyer self-check; the factory does not issue certification claims in this article.
The pillar complements the one-on-one comparison siblings in the 840s (keyless vs smart, RFID, Bluetooth, Wi-Fi, fingerprint, hotel RFID vs residential, commercial vs residential, office vs hotel, apartment vs hotel) and the technology-best-fit siblings in the 801–808 range (best smart lock technology for hotels, apartments, commercial buildings, and adjacent profiles); for procurement mechanics, the OEM/ODM siblings in the 700s and the private-label siblings in the 750s run the process side. When the buyer is ready to translate the stack into a shortlist, the catalogue at /request-catalog gives the SKU list, and the conversation at /request-a-quote converts the shortlist into a quote, a sample, and a production schedule.

