Smart lock user management software is the operator-side application surface that issues, revokes, schedules, and audits every credential — PIN, card, eKey,

Pubblicato il: ago 22, 2025

Smart Lock User Management Software

Smart Lock User Management Software

Smart lock user management software is the operator-side application surface that issues, revokes, schedules, and audits every credential — PIN, card, eKey, fingerprint template, face template, or remote unlock grant — on every door a buyer is responsible for. It sits between the buyer (importer, hotel chain, serviced-apartment operator, distributor's local IT team) and the catalog locks that have already been chosen. For B2B buyers, the user-management surface is the long tail of the procurement decision: hardware ships in cartons, but the people who actually use the property will live inside this software for the next decade, and the buyer who skips the feature-by-feature comparison matrix almost always pays for it later, in staff turnover at the front desk, in a guest lockout during a peak weekend, or in an audit log that cannot answer the only question a lawyer asks.

This article dissects the four features every B2B buyer must verify on the candidate platform before sending the RFQ — admin role, enrolment UI, role templates, and audit visibility — across the four platform classes named in the fact base (TTLock, Tuya, Doodle, hotel PC software). Every comparison cell is left as to verify in writing where the buyer must confirm with the supplier, because per-model platform identity is a property of the specific SKU, not a property of the platform brand.

to verify in writing marker convention used below. A cell marked to verify in writing is a cell the supplier must fill — either by pointing to a verifiable line on the product page, by demoing the running software, or by naming the version. A cell marked Buyer-fill is a cell the buyer fills themselves (e.g. by reading the lock's stated door thickness before evaluating a software claim that depends on it). A cell marked n/a by design is a cell where the answer is fixed by the platform class and does not depend on the supplier.

What "user management" actually controls on a B2B property

Before the nameplate, the buyer needs to know what the user-management surface is responsible for. The brief has six duties and the brief is the same whether the platform is TTLock, Tuya, Doodle, or hotel PC software:

  1. Identity issuance. Turning a person into a credential on a door: a fingerprint template, a PIN, an RFID card, an app eKey, or a face template.
  2. Identity withdrawal. Revoking the same credential when a guest checks out, a contractor's project ends, or a staff member leaves.
  3. Identity scheduling. Putting a time-window on a credential — check-in 14:00, check-out 11:00, recurring weekly window for housekeeping, one-hour contractor window for a third-party technician.
  4. Role mapping. Grouping identities into roles (owner, manager, receptionist, housekeeping, guest, contractor, maintenance) so that operations scale beyond a one-off "create this PIN" task.
  5. Audit. Recording every credential interaction — issued, revoked, opened, failed, lock-picked, door-forced, low-battery — with enough fidelity that the buyer can answer "who opened room 312 at 02:14 on Tuesday" a year after the fact.
  6. Handover. Transferring the property from one administrator account to another when the distributor changes, the operator rebrands, or the property is sold.

The app (TTLock, Tuya, Doodle) is a thin front-end on top of platform-side state for one or many locks. The hotel PC software class is a thicker on-premises application that historically serves hotel RFID-class locks (Mifare 1 @ 13.56 MHz in the SLK-9936S reference class) with a richer database layer. B2B buyers need to understand both classes because the procurement brief often spans both — a serviced-apartment operator runs the residential wing on an app platform and the staff areas on hotel-class RFID.

The cell-discipline rule. When a supplier says "we support user management", the buyer's correct next sentence is "on which platform class, on which of my shortlisted models, at which software version, with what audit retention." The remainder of this article is the comparison matrix that forces those answers out of the conversation.

The four platform classes you will be offered

The fact base names four platform classes that the supplier may offer against your shortlisted models. Each class is described below in the same annotated-datasheet format — what this line means / what to demand / what is a bluff — so the buyer can read the class as an artifact, not as a brand.

Class 1 — TTLock-class

What this line means. TTLock is the most common app-class platform you will be offered in residential and light commercial contexts. The app is the administrator's primary surface; the cloud is the source of truth for credentials and audit; the lock pairs over Bluetooth and re-syncs when within range.

What to demand. Version of the TTLock app (e.g. the build that the supplier's account is bound to). SDK or gateway compatibility if any networked control is in the scope (remote unlock, real-time audit). Confirmation on whether the admin account can be transferred to a brand account or a multi-property chain account without re-pairing every lock.

What is a bluff. "TTLock is TTLock" — same for every supplier. It is not. The supplier's specific implementation, lock-firmware pairing model, and gateway compatibility differ; assume nothing.

Class 2 — Tuya-class

What this line means. Tuya is a general-purpose IoT ecosystem with a smart-lock product line on top of it. Tuya's value proposition is ecosystem breadth — the lock lives inside the same app or skill tree as a wider range of smart devices — and the cost of that breadth is platform abstraction: features that are simple on a single-vendor app can require additional setup on Tuya.

What to demand. Whether the lock's Tuya support is exposed via the public Tuya platform, via the supplier's Tuya-private deployment, or via the buyer's own Tuya account. Whether scenes, automations, or third-party skills are available on this specific lock firmware. Whether the audit log is queryable via the Tuya API or only via the app UI.

What is a bluff. "Tuya is an open ecosystem, anything works." It is not. Openness is at the device-certification layer; specific feature availability for specific lock-device classes is a supplier-side decision.

Class 3 — Doodle-class

What this line means. Doodle is a platform class more often seen on residential and light-commercial locks in the catalog's keypad-and-fingerprint segment. It is a thinner platform than TTLock or Tuya in ecosystem terms; its strengths sit in enrollment UI and credential lifecycle for residential-staff scenarios.

What to demand. Confirmation that Doodle is the platform the supplier binds your property to (versus a Tuya rebadge or a private label). Whether Doodle's admin model supports a multi-property chain account. Whether Doodle's audit log is exportable in a buyer-vendor-readable format (CSV, API, or only the app).

What is a bluff. "Doodle is the same as TTLock." The supporting ecosystem, the partner-integrations model, and the audit retention model are different.

Class 4 — Hotel PC software

What this line means. Hotel PC software is a thicker, on-premises-style application that historically serves hotel RFID-class locks, typically Mifare 1 @ 13.56 MHz in the catalog's hotel class. The SLK-9936S reference model is positioned for 1–5 star hotels with multilingual management software and standalone or centralized database modes. The PC-software surface is distinct from the app-class surfaces in three ways: it runs on the property's IT, the database is the property's, and the credential model is RFID-card-centric rather than smartphone-centric.

What to demand. Whether the hotel PC software is shipped with the lock, sold as a separate SKU, or licensed per-property. Whether the audit log is stored locally on the PC, mirrored to a central database, or both. Whether the lock can run in standalone mode (one lock, one PC) versus centralized mode (many locks, one PC) without re-pairing.

What is a bluff. "Hotel PC software is old-fashioned, you should use the app." It is not old-fashioned; it is a different design choice with different audit-retention, different cybersecurity exposure, and different credential-medium assumptions. Buyers who only consider the app-class surfaces may end up retrofitting hotel-class properties that should never have been on app-class infrastructure. And if the underlying "whose server decides" question is still fuzzy for your team, the head-to-head in Smart Lock Cloud vs Local Management settles it before you spend an afternoon filling matrix cells.

The cross-class point. The four platform classes are not substitutes for each other. A buyer with a mixed property — 60-key hotel wing + 40-unit serviced-apartment wing + staff areas — is likely to need two classes operating side-by-side. The matrix below is built so the buyer can fill each cell of each row against each class on their specific lock model.

The four platform classes at a glance

The summary below maps each class to the buyer-side questions that recur in every supplier conversation. Every cell is left to verify in writing on this SKU for the same reason the matrix below is — the per-SKU answer differs, and the buyer must verify on the product page.

AttributeTTLock-classTuya-classDoodle-classHotel PC software
Primary deployment shapeApp + cloud + lock over BLEApp + cloud + lock over BLE (Tuya IoT)App + lock over BLEOn-premises PC + lock over RS-485 / wired
Database ownerCloud (TTLock)Cloud (Tuya)Cloud (Doodle)Property IT (the buyer's PC)
Credential-medium assumptionSmartphone-centricSmartphone-centricSmartphone-centricRFID card-centric
Typical catalog categoriesResidential / keypad / fingerprintResidential / keypad / fingerprint / select outdoorResidential / keypadHotel / RFID-class
Admin-side surfaceTTLock app + optional web consoleTuya app + Smart Life + optional cloudDoodle appOn-premises PC software
Audit retention defaultCloud-side, period = to verify in writing on this SKUCloud-side, period = to verify in writing on this SKUCloud-side, period = to verify in writing on this SKULocal PC database, period = to verify in writing on this SKU
Network-outage behaviourLock-local cache + cloud sync on reconnectLock-local cache + cloud sync on reconnectLock-local cache + cloud sync on reconnectLocal-first; the PC stays authoritative
Multi-property bindingSupported (to verify in writing on this SKU)Supported (to verify in writing on this SKU)Supported (to verify in writing on this SKU)Per-property install (n/a by design)
Typical pairing pathBLE pairing + admin bindBLE pairing + Tuya Smart LifeBLE pairing + Doodle appWired commissioning + PC-software enroll

Feature 1 — Admin role: who is the master, who is delegated, who is read-only

What this line means. Every user-management surface defines at least three privilege levels: master, delegated, and read-only. Master is the account that can bind the lock to the platform, transfer ownership, and create other master accounts. Delegated is the account that can issue and revoke credentials but cannot transfer the lock's ownership. Read-only is the account that can read the audit log and see which credentials exist but cannot issue or revoke.

What to demand. Confirmation that the lock on your shortlisted model supports all three privilege levels on the platform class you will be bound to. Confirmation on how many delegated accounts the platform allows. Confirmation on whether read-only access is possible at all (some platforms do not have a read-only role and treat it as equivalent to "no access"). Confirmation on whether the master account can be revoked by the supplier, the platform, or only by the buyer.

What is a bluff. "Admin role is standard." It is not. The number of admins allowed, the number of master accounts, the multi-step binding handshake, and the recovery procedure when a master account is lost all vary.

Fold-by-Fold annotation

  • Master-account recovery is the buyer-duty question most buyers skip. If the master account is lost and the platform has no documented recovery path, the buyer owns the consequence. The matrix below records this as a Buyer-fill cell — the buyer must ask, in writing, how recovery works for the specific SKU on the specific platform.
  • Multi-property binding. Some platform classes allow a single master account to bind many properties; others require one master per property. The supplier's per-model implementation decides; the platform's marketing copy does not.
  • Audit-only staff. Hotel-class properties often need a receptionist role that can check audit but cannot issue credentials. The matrix records whether the platform supports this role on this lock.

Privilege-tier depth by class (what the buyer typically gets)

Privilege tierTTLock-class expectationTuya-class expectationDoodle-class expectationHotel PC software expectation
Master accountOne per property or one for many — to verify in writing on this SKUOne per Tuya account — to verify in writing on this SKUOne per property — to verify in writing on this SKUOne PC per property — n/a by design
Delegated admin countMultiple — to verify in writing on this SKUMultiple (Tuya sub-accounts) — to verify in writing on this SKULimited — to verify in writing on this SKUMultiple PC-software roles — to verify in writing on this SKU
Read-only roleSupported on most models — to verify in writing on this SKUPossible via Tuya Smart Life family-sharing — to verify in writing on this SKUVariable — to verify in writing on this SKUSupported (audit-viewer login) — to verify in writing on this SKU
Master-account recoverySupplier-issued reset code — to verify in writing on this SKUTuya account-recovery flow — to verify in writing on this SKUSupplier-issued reset — to verify in writing on this SKUProperty-side (the buyer owns the PC) — to verify in writing on this SKU
Multi-property chain bindingYes (single admin) — to verify in writing on this SKUYes (Tuya account) — to verify in writing on this SKUYes (single admin) — to verify in writing on this SKUPer-property install — n/a by design
Role for housekeeping / maintenance / contractorAvailable via role templates — to verify in writing on this SKUAvailable via custom roles — to verify in writing on this SKULimited — to verify in writing on this SKUAvailable — to verify in writing on this SKU

Feature 2 — Enrolment UI: how a credential is created on a person and a door

What this line means. The enrolment UI is the surface that turns a guest, a staff member, a contractor, or a resident into a credential. The UI varies dramatically — some platforms offer a one-screen flow ("enter name, scan fingerprint, set PIN, tap card"), others require a separate app page per credential type.

What to demand. Confirmation on which credential types the per-supplicant platform supports on the per-supplicant model: PIN, RFID card, fingerprint template, face template, app eKey, time-limited eKey, recurring eKey, and one-time code. Confirmation on whether the enrolment is done by the admin (the buyer issues the credential) or self-service (the guest enrols themselves with a code from the admin). Confirmation on whether the enrolment UI is multi-language.

What is a bluff. "Enrolment is one tap." It is one tap in the marketing screenshot. In a 60-key property on a peak check-in day, it is whatever the slowest credential type takes — and that is the credential type the front-desk supervisor will judge the platform on.

Fold-by-Fold annotation

  • Self-service versus admin-issued. Self-service enrolment puts the burden on the guest (download the app, scan the QR, accept the invite). Admin-issued enrolment puts the burden on the front desk. The platform class decides which is the better fit; the buyer's own staffing model decides which is feasible.
  • One-time codes and time-limited eKeys. These are the two credential types that distinguish a platform that supports hospitality from a platform that supports only residential-staff. The matrix records both as to verify in writing per platform per model.
  • Bulk import. A 60-key hotel that has to reissue 60 RFID cards one at a time will fail on day one. The matrix records whether bulk import is supported on the platform for this model.

Credential-type × platform-class support matrix (typical buyer expectations)

Credential typeTTLock-class expectationTuya-class expectationDoodle-class expectationHotel PC software expectation
PIN (passcode)to verify in writing on this SKUto verify in writing on this SKUto verify in writing on this SKUto verify in writing on this SKU
RFID card / fobto verify in writing on this SKUto verify in writing on this SKUto verify in writing on this SKUStandard for the class — to verify in writing on this SKU
Fingerprint templateto verify in writing on this SKU (catalog category covers many fingerprint-capable SKUs)to verify in writing on this SKUto verify in writing on this SKUn/a by design on hotel PC class (fingerprint is residential/kitchen side)
Face templateto verify in writing on this SKU (face-recognition catalog class covers 6 SKUs)to verify in writing on this SKUto verify in writing on this SKUn/a by design on hotel PC class
App eKey (smartphone)Standard for the class — to verify in writing on this SKUStandard for the class — to verify in writing on this SKUStandard for the class — to verify in writing on this SKUn/a by design on hotel PC class
Time-limited eKeyto verify in writing on this SKUto verify in writing on this SKUto verify in writing on this SKUn/a by design on hotel PC class
One-time codeto verify in writing on this SKUto verify in writing on this SKUto verify in writing on this SKUStandard for the room class — to verify in writing on this SKU
Mechanical key (backup)to verify in writing on this SKUto verify in writing on this SKUto verify in writing on this SKUto verify in writing on this SKU
Self-service enrolment pathto verify in writing on this SKUto verify in writing on this SKUto verify in writing on this SKUn/a by design (front-desk issued)
Bulk import (CSV / API)to verify in writing on this SKUto verify in writing on this SKUto verify in writing on this SKUStandard for the class — to verify in writing on this SKU
Multi-language enrolment UIto verify in writing on this SKUto verify in writing on this SKUto verify in writing on this SKUto verify in writing on this SKU (the SLK-9936S class is documented as multilingual management software)

Feature 3 — Role templates: how roles are reused across people and properties

What this line means. Role templates are the predefined permission bundles a platform exposes — "receptionist", "housekeeping", "guest", "owner", "contractor", "maintenance". A platform with good role templates lets the admin assign a role in one step and inherit a known set of permissions. A platform without templates forces the admin to set permissions per-user, per-door, per-credential type — a task that scales linearly with property size.

What to demand. Whether the platform exposes predefined roles. Whether those roles can be edited (add permission, remove default). Whether a custom role can be saved as a template for re-use. Whether role templates can be assigned in bulk (e.g. "assign the housekeeping role to all 12 housekeeping staff on this floor in one action").

What is a bluff. "Templates are built in." They are built in on some platforms; on others, the platform's documentation lists "owner" and "guest" and nothing else, and the admin is left to invent everything in between.

Fold-by-Fold annotation

  • Predefined versus editable. Predefined roles that cannot be edited are fine for a residential owner. They are insufficient for a hotel chain that needs "regional housekeeping supervisor" as a role distinct from "housekeeping".
  • Role inheritance. A role that inherits from another role (receptionist inherits guest permissions plus a few more) saves the buyer from per-user configuration. The matrix records whether inheritance is supported.
  • Role-to-credential-type mapping. Some platforms bind a role to a single credential type (e.g. "housekeeping" always issues an RFID card, never a PIN). Others let a role have multiple. The matrix records both.

Role-template depth by class (typical buyer expectations)

Role-template attributeTTLock-class expectationTuya-class expectationDoodle-class expectationHotel PC software expectation
Predefined role count (typical)3–5 (owner / admin / guest / staff / limited-time)2–4 (owner / family / guest)4 — to verify in writing on this SKU6+ — to verify in writing on this SKU
Editable predefined rolesto verify in writing on this SKUto verify in writing on this SKUto verify in writing on this SKUto verify in writing on this SKU
Custom role save-as-templateto verify in writing on this SKUto verify in writing on this SKUto verify in writing on this SKUto verify in writing on this SKU
Role inheritanceto verify in writing on this SKUto verify in writing on this SKUto verify in writing on this SKUto verify in writing on this SKU
Bulk role assignmentto verify in writing on this SKUto verify in writing on this SKUto verify in writing on this SKUto verify in writing on this SKU
Multi-credential-type per roleto verify in writing on this SKUto verify in writing on this SKUto verify in writing on this SKUto verify in writing on this SKU
Typical housekeeping / maintenance / contractor roleAvailable — to verify in writing on this SKUAvailable via custom roles — to verify in writing on this SKULimited — to verify in writing on this SKUAvailable — to verify in writing on this SKU

The privilege tiers and the role bundles are not four unrelated checkboxes; they form a small hierarchy, and sketching the hierarchy once makes it easy to see which cells a supplier will be tempted to leave blank.

classDiagram
    class MasterAccount
    class DelegatedAdmin
    class ReadOnlyViewer
    class RoleTemplate
    MasterAccount --> DelegatedAdmin : creates
    MasterAccount --> ReadOnlyViewer : creates
    RoleTemplate --> DelegatedAdmin : bundles permissions
    RoleTemplate --> ReadOnlyViewer : bundles permissions
    note for MasterAccount "binds the lock · transfers ownership · recovery path is the buyer-duty question"
    note for DelegatedAdmin "issues and revokes credentials · cannot transfer ownership"
    note for ReadOnlyViewer "reads the audit log · absent on some platforms — to verify on this SKU"

Feature 4 — Audit visibility: who opened which door, when, with what, under what authority

What this line means. Audit visibility is the surface that records every credential interaction and exposes it for review. The audit log answers questions like "who opened room 312 at 02:14", "which PINs were active in March", "which contractor credentials were issued and to whom", "which lock lost connectivity and when".

What to demand. Whether the audit log is stored on the platform cloud, on a local PC (for hotel-class software), on the lock itself, or on a combination. What the retention period is. Whether the audit log is exportable and in what format (CSV, API, PDF). Whether the audit log survives a network outage (does the lock buffer events locally and push when reconnected). Whether the audit log includes failed attempts. Whether the audit log distinguishes credential types (PIN vs card vs fingerprint vs eKey).

What is a bluff. "Audit is in the cloud." It is in the cloud until the property's internet fails, the lock's local buffer fills, and the audit gap is silent. The product-page-documented SLK-9936S reference model is specified to hold up to 1,000 audit/event records locally; that figure is a hotel-class RFID-class property figure and does not transfer to a residential app-class lock or to a face-recognition-class lock. The buyer's correct move is to record the local audit buffer size for the specific shortlisted SKU as a Buyer-fill cell, and to ask whether the platform syncs the buffer to cloud on reconnect.

Fold-by-Fold annotation

  • Local buffer plus cloud retention is the audit-storage model that scales. A lock with no local buffer loses audit during a network outage. A lock with a large local buffer and a cloud-sync model captures steady-state audit. The matrix records both as to verify in writing.
  • Export format. CSV is the minimum. An API is the upgrade. A PDF is the courtesy. The matrix records which formats are exposed by the platform for this model.
  • Failed-attempt recording. A platform that records only successful opens is incomplete. A platform that records failed opens, denied opens, and forced opens is audit-grade. The matrix records the distinction.

Audit storage model by class (typical buyer expectations)

Audit attributeTTLock-class expectationTuya-class expectationDoodle-class expectationHotel PC software expectation
Local audit buffer on lockto verify in writing on this SKUto verify in writing on this SKUto verify in writing on this SKUto verify in writing on this SKU (the SLK-9936S reference class is documented as holding up to 1,000 audit/event records — hotel-class only; per-SKU figure differs)
Cloud retention periodto verify in writing on this SKUto verify in writing on this SKUto verify in writing on this SKUn/a by design (cloud not used)
PC-database retentionn/a by designn/a by designn/a by designto verify in writing on this SKU
Survives network outageto verify in writing on this SKUto verify in writing on this SKUto verify in writing on this SKUYes by design (local PC is authoritative)
Failed-attempt recordingto verify in writing on this SKUto verify in writing on this SKUto verify in writing on this SKUto verify in writing on this SKU
Credential-type distinction in logto verify in writing on this SKUto verify in writing on this SKUto verify in writing on this SKUto verify in writing on this SKU
CSV exportto verify in writing on this SKUto verify in writing on this SKUto verify in writing on this SKUto verify in writing on this SKU
API exportto verify in writing on this SKUto verify in writing on this SKUto verify in writing on this SKUto verify in writing on this SKU
PDF exportto verify in writing on this SKUto verify in writing on this SKUto verify in writing on this SKUto verify in writing on this SKU
Queryable via platform APIto verify in writing on this SKUto verify in writing on this SKUto verify in writing on this SKUn/a by design (on-premises)
Per-property audit scopingto verify in writing on this SKU (chain account behaviour)to verify in writing on this SKU (Tuya account scoping)to verify in writing on this SKUn/a by design (per-property install)

The four-feature comparison matrix (the article's load-bearing artifact)

The matrix below is the comparison matrix the buyer brings to the supplier. Every cell is marked to verify in writing where the supplier must answer, Buyer-fill where the buyer must answer, or n/a by design where the answer is fixed by the platform class. A cell that the supplier cannot fill is a cell that disqualifies the SKU — not the platform class.

FeatureTTLock-classTuya-classDoodle-classHotel PC software
Admin role — master account creationto verify in writing on this SKUto verify in writing on this SKUto verify in writing on this SKUto verify in writing on this SKU
Admin role — delegated account creationto verify in writing on this SKUto verify in writing on this SKUto verify in writing on this SKUto verify in writing on this SKU
Admin role — read-only account supportto verify in writing on this SKUto verify in writing on this SKUto verify in writing on this SKUto verify in writing on this SKU
Admin role — master-account recovery pathto verify in writing on this SKUto verify in writing on this SKUto verify in writing on this SKUto verify in writing on this SKU
Admin role — multi-property bindingto verify in writing on this SKUto verify in writing on this SKUto verify in writing on this SKUn/a by design (on-premises model)
Enrolment UI — PINto verify in writing on this SKUto verify in writing on this SKUto verify in writing on this SKUto verify in writing on this SKU
Enrolment UI — RFID cardto verify in writing on this SKUto verify in writing on this SKUto verify in writing on this SKUto verify in writing on this SKU
Enrolment UI — fingerprint templateto verify in writing on this SKUto verify in writing on this SKUto verify in writing on this SKUto verify in writing on this SKU
Enrolment UI — face templateto verify in writing on this SKUto verify in writing on this SKUto verify in writing on this SKUto verify in writing on this SKU
Enrolment UI — app eKeyto verify in writing on this SKUto verify in writing on this SKUto verify in writing on this SKUn/a by design (PC-software class)
Enrolment UI — time-limited eKeyto verify in writing on this SKUto verify in writing on this SKUto verify in writing on this SKUn/a by design (PC-software class)
Enrolment UI — one-time codeto verify in writing on this SKUto verify in writing on this SKUto verify in writing on this SKUto verify in writing on this SKU
Enrolment UI — self-service vs admin-issuedto verify in writing on this SKUto verify in writing on this SKUto verify in writing on this SKUto verify in writing on this SKU
Enrolment UI — multi-language supportto verify in writing on this SKUto verify in writing on this SKUto verify in writing on this SKUto verify in writing on this SKU
Enrolment UI — bulk importto verify in writing on this SKUto verify in writing on this SKUto verify in writing on this SKUto verify in writing on this SKU
Role templates — predefined rolesto verify in writing on this SKUto verify in writing on this SKUto verify in writing on this SKUto verify in writing on this SKU
Role templates — editable rolesto verify in writing on this SKUto verify in writing on this SKUto verify in writing on this SKUto verify in writing on this SKU
Role templates — custom role saved as templateto verify in writing on this SKUto verify in writing on this SKUto verify in writing on this SKUto verify in writing on this SKU
Role templates — bulk role assignmentto verify in writing on this SKUto verify in writing on this SKUto verify in writing on this SKUto verify in writing on this SKU
Role templates — role inheritanceto verify in writing on this SKUto verify in writing on this SKUto verify in writing on this SKUto verify in writing on this SKU
Role templates — multi-credential-type per roleto verify in writing on this SKUto verify in writing on this SKUto verify in writing on this SKUto verify in writing on this SKU
Audit visibility — local buffer sizeBuyer-fill from this SKU's PDPBuyer-fill from this SKU's PDPBuyer-fill from this SKU's PDPBuyer-fill from this SKU's PDP
Audit visibility — cloud retention periodto verify in writing on this SKUto verify in writing on this SKUto verify in writing on this SKUto verify in writing on this SKU
Audit visibility — local retention on lockto verify in writing on this SKUto verify in writing on this SKUto verify in writing on this SKUto verify in writing on this SKU
Audit visibility — survives network outageto verify in writing on this SKUto verify in writing on this SKUto verify in writing on this SKUto verify in writing on this SKU
Audit visibility — failed-attempt recordingto verify in writing on this SKUto verify in writing on this SKUto verify in writing on this SKUto verify in writing on this SKU
Audit visibility — credential-type distinction in logto verify in writing on this SKUto verify in writing on this SKUto verify in writing on this SKUto verify in writing on this SKU
Audit visibility — export format (CSV / API / PDF)to verify in writing on this SKUto verify in writing on this SKUto verify in writing on this SKUto verify in writing on this SKU
Audit visibility — queryable via platform APIto verify in writing on this SKUto verify in writing on this SKUto verify in writing on this SKUto verify in writing on this SKU
Audit visibility — admin-only vs role-scopedto verify in writing on this SKUto verify in writing on this SKUto verify in writing on this SKUto verify in writing on this SKU

How to use this matrix. Send it to the supplier with the column matching the platform class they offer. Ask for a row-by-row response: every to verify in writing cell gets either a "yes / no / version-specific" answer with evidence (a screenshot of the running software, a line on the product page, a documentation reference), or an honest "not supported on this SKU on this platform." A supplier who refuses to fill the cells is a supplier whose user-management surface is not procurement-ready.

Cross-platform buyer questions (independent of the matrix)

Eight questions sit outside the matrix but are equally load-bearing for a B2B buyer. They are recorded here as a buyer interview protocol — the questions the buyer puts in writing before the supplier call.

  1. What is the master-account recovery path? When the master account is lost, who can reset it, by what procedure, and on what documentation? A platform with no documented recovery is a platform the buyer owns.
  2. Can the lock be transferred to a new owner account? When the property is sold or the operator rebrands, does the lock re-bind to a new master without re-flashing firmware?
  3. Is the audit log exportable as CSV or API? PDF screenshots are not an export format.
  4. What is the local audit buffer, and does the lock sync to cloud on reconnect? The buffer is on the product page (where stated) or in the supplier's documentation (where stated). The figure is not transferable across SKU classes.
  5. Does the platform support multi-property chain accounts, and what is the per-property audit scoping? A chain with 12 properties needs audit scoping per property, not a single global audit.
  6. What languages does the enrolment UI support? Multilingual enrolment is mandatory for most cross-border B2B deployments; single-language enrolment disqualifies a SKU for most hospitality buyers.
  7. Does the role-template system support editable roles and inheritance? A platform that does not is unusable for any property beyond a handful of staff.
  8. What is the platform's documented version-control policy? When the platform updates, does the lock re-pair? Does the audit schema change? Does the credential format change?

The matrix above is what the supplier fills; this list is what the buyer verifies by writing the answers in the buyer's own column.

What to demand in writing (the procurement-grade version)

The buyer should not leave the call with screenshots. The right answers go into the buyer's own worksheet, with one row per question and one column per platform class. The minimum column set is: platform class, SKU model under evaluation, supplier's answer in writing, evidence reference (page number / screenshot / documentation link), buyer's own verification (live test or third-party confirmation).

A supplier's refusal to fill a row is a supplier's answer: the row is unsupported by the buyer. The matrix above is structured so that every row is a row the buyer can ask about in writing; the answer column under each platform class is what the buyer pastes into the worksheet.

The refusal to bring honest answers is the answer. A supplier that says "yes" to every cell without evidence is a supplier that does not know the answer; the buyer's move is to walk away. A supplier that says "no, this is not supported on this SKU on this platform" is a supplier that knows the SKU and the platform — that is the partner the buyer builds a long-term relationship with.

Illustrative scenario: a 60-key mixed-property rollout

Consider a 60-key property: 40 serviced-apartment units in the residential wing, a 20-key boutique-style hotel wing in the hotel wing, and three staff-only back-of-house doors. The buyer has shortlisted two candidate models from the catalog — one residential class lock with a TTLock or Tuya app, and one hotel-class lock (the SLK-9936S reference class, RFID Mifare 1 @ 13.56 MHz, multilingual management software, standalone or centralized database modes) for the hotel wing and back-of-house doors.

Step 1 — Read the matrix twice. Once against the residential SKU against the TTLock-or-Tuya-class column, once against the hotel-class SKU against the hotel PC software column. Every cell that is filled to verify in writing is a cell the buyer demands.

Step 2 — Audit-visibility cell is the gate. A serviced-apartment operator who cannot query "which contractor had an active credential in the past 90 days" is an operator who cannot answer the regulator's question. The residential SKU's local audit buffer and cloud-retention figure become the gate; if the supplier cannot fill it, the SKU is out.

Step 3 — Role-template cell is the operations test. A 60-key property with 8 housekeeping staff, 4 maintenance staff, 1 supervisor, 1 manager, and a rotating contractor population needs a platform that supports editable roles and inheritance. A platform that supports only "owner" and "guest" as predefined roles forces the manager to hand-configure every staff credential — a task that scales linearly and breaks at 40 units.

Step 4 — Enrolment UI cell is the staff-experience test. A boutique-hotel wing with 20 keys and a peak weekend needs an enrolment UI that the front-desk supervisor can complete in under 90 seconds per guest. A platform that requires the supervisor to navigate three app pages per credential type will be abandoned by week three.

Step 5 — Admin-role cell is the recovery test. A property whose master account is held by a single individual long-term admin is a property that will lose its master account on the day that individual leaves. The supplier's documented recovery path is the gate; the matrix records it.

The buyer who walks the matrix through this five-step scenario in advance arrives at the supplier call with a written worksheet, a refusal-to-fill list, and a decision criterion that is independent of the supplier's marketing deck.

Catalog-scale context for this matrix

The vendor's 79-model catalog spans 10 categories — Smart Door Locks 77, Fingerprint 37, Hotel 24, Keypad 18, Outdoor 10, RFID 9, Face Recognition 6, Cabinet 6, Video Camera 3, Glass 3 — and supports fingerprint, passcode, RFID/IC card, mechanical key, app/Bluetooth (TTLock / Tuya / Doodle), remote control, 3D face on a few models, hotel PC software, camera/cat-eye, and 4G models across those categories. Palm-vein, Matter, Zigbee, and Apple Home Key are not in the catalog and are not options in this matrix. UWB is not in the catalog. Wi-Fi is not presented as a catalog capability in this article — Wi-Fi-networked behavior depends on gateway pairing on the specific SKU and is a property of the per-model implementation, not of the platform class.

The matrix above is therefore the matrix the buyer runs against a specific shortlisted SKU on a specific platform class. The 79-model catalog does not pre-answer the matrix; it only tells the buyer that the platform classes named here are the platform classes the supplier is set up to support.

The catalog-level disclosure. The catalog is broad enough that the platform class on your shortlisted SKU is not predictable from the category. Two locks in the same category may be on different platform classes. The matrix above is the only honest way to find out which.

Where this article sits in the connectivity cluster

This article is one of a small shelf of C07 cluster pieces on the app-side capability and lifecycle of smart locks. The Connected Smart Locks: Complete B2B Guide maps the connectivity taxonomy across the catalog and explains the platform-class question at the architecture level. The Smart Lock Mobile App Guide documents the app-side onboarding workflow (invitation, pairing, role creation, handoff) for the same four platform classes. The Smart Lock App Features Buyers Should Check lays out the five-pillar capability check for the app side — time-bound access, role templates, audit-log access, credential reissue, account handover.

This article is the load-bearing annotated-datasheet view of the same domain: every feature cell of every platform class is left as to verify in writing for the supplier to fill. A sensible reading order starts with the connectivity tier, continues through onboarding the property onto the chosen platform, checks the feature pillars at the app level, and ends here, at the procurement-grade evidence level of the four-feature comparison matrix.

Closing CTA

The user-management-software surface is the one piece of the smart-lock stack a B2B procurement cannot fully outsource to the supplier's marketing deck. The four features in this matrix — admin role, enrolment UI, role templates, audit visibility — are the four features that determine whether the property runs smoothly on day one and survives the regulator's question on day 365. Send the matrix to your shortlisted supplier with the cells pre-marked to verify in writing, ask for a row-by-row written answer with evidence, and bring the answers to the call at /request-a-quote so the buyer and the supplier are negotiating on the same surface. For the broader procurement discipline around this matrix, the buyer-resources hub and the OEM/ODM program page (OEM/ODM program) document how this matrix fits inside a multi-property rollout.

Il tuo carrello
La tua esperienza su questo sito sarà migliorata consentendo i cookie Informativa sui cookie
Chat on WhatsApp