Most buying guides answer this question at the door level: pick a lock, mount it, move on. A commercial building with several tenants does not work that way.

Опубликовано: авг 29, 2025

What Smart Lock Should a Commercial Building Use?

What Smart Lock Should a Commercial Building Use?

Most buying guides answer this question at the door level: pick a lock, mount it, move on. A commercial building with several tenants does not work that way. The building is a stack of different doors, owned by different parties, operated by one staff team, and inspected by insurers who want to know who had access and when. The right lock choice is therefore an access architecture choice first, and a model number second.

The short answer: for a multi-tenant commercial building, the approach that wins most often is the mixed model — a centralized RFID card system on entrances, common doors, and landlord-controlled risk points (plant rooms, risers, rear fire doors), with standalone keypad or fingerprint locks on individual suite doors, managed by each tenant. Full centralization pays for itself only when one operator controls every tenancy; pure per-suite standalone locks only where the landlord has no exposure on the perimeter. The rest of this article proves that with a round-by-round contest between the three approaches.

Note on scope: this article is about buildings with many tenants — landlord, property manager, and individual tenants each holding a piece of the access decision. If you are the sole tenant fitting out your own office floor, the geography is different and the office-buying comparison covers that case instead; the question there is which internal doors need which credential, not who governs thirty separate leases.

One Question, Three Stakeholders

The reason commercial building lock decisions go wrong is that three parties answer the same question with different objective functions. A purchase spec written by only one of them tends to fail at the handover.

StakeholderWhat they optimize forWhat they refuse to touchWhat breaks their model
Landlord / ownerAsset protection, insurable audit trail, low retrofit cost across many door typesTenant interior fit-outs; per-tenant administration laborA credential they cannot revoke building-wide
Property managerFast tenant onboarding/offboarding, one help channel, battery rounds that fit a weekdayDoors that need re-keying by a contractor at 6 p.m.Thirty suites each with a different lock brand and no records
Individual tenantAutonomy over their own suite, cheap temporary access for cleaners and couriers, no landlord waiting-listSharing code lists with neighbouring tenantsBuilding rules that force them through a card office for a one-hour delivery

Can one system satisfy all three? No, and pretending otherwise is where budget disappears. The mixed model works precisely because it assigns each stakeholder the layer they can govern: the landlord owns the entrance and core doors, the property manager runs the card system behind them, tenants run their own suite doors. What each party must agree on in advance is the boundary — which doors are "doors of record" for the building's liability, and which are tenant-managed.

A blunt manufacturer's observation from our own export work: buildings that standardize on one lock type everywhere end up either over-managed (tenants route every cleaner visit through the management desk) or under-governed (the landlord discovers during an insurance review that suite doors hold the only event records and nobody collects them).

The Three Contenders

Before scoring, define the entrants precisely.

Approach A — Centralized card system. One credential universe for the whole building. RFID card locks or readers on the main entrances, stairwell doors, plant rooms, and suite doors alike; cards issued, cached, and revoked from a single management position. In our catalog this maps to the RFID door lock category (9 models), and to locks whose specification language describes centralized management software with standalone or centralized database modes — the SLK-9936S block below shows what a documented, software-managed credential system looks like on paper.

Approach B — Per-suite standalone keypad. Each suite door carries its own battery-powered lock. Codes are created and deleted by that tenant; the landlord holds no master platform, only emergency mechanical keys. Maps to the keypad door lock category (18 models) and frequently to fingerprint-capable units from the 37-model fingerprint category where tenants prefer biometrics to shared codes.

Approach C — Mixed model. Centralized at the perimeter and at landlord-risk doors; standalone inside the tenancy line. The credential boundary follows the lease line.

Here is the door stack of a typical mid-rise these approaches must cover — 11 floors, 39 tenancies, 4 ground-floor storefronts:

 FLOOR 11 ┌ office suites ×3 wooden panel doors, 38–45 mm... ├ suite doors ×31 narrow-stile aluminum frames FLOOR 2 ├ suite doors ×5 mixed wood / metal-clad GROUND ╔ 4 glass storefronts (12 mm tempered, no drillable stile) ║ main lobby: 2 entrance doors + reception turnstile line ║ rear stairwell: metal fire-rated door → service yard BASEMENT ┴ plant room, riser cupboards, 6 storage cages (landlord-retained, highest audit value)

Read the stack before reading any brochure. Roughly a third of the doors above (glass storefronts, the fire-rated stairwell door, plant rooms) decide which approach is even possible.

Round One: Credential Governance — Who Can Revoke Access?

The governance test: a tenant gives notice, and one of their staff members who was never registered in any landlord system walks past the lobby on their last day carrying a box of company laptops. Who could have stopped them, and at what moment?

Under Approach A, revocation is one click — if that person ever touched a building door, their card lives in one database and dies in one action. The strength is also the weakness: the card system only sees people who pass through credentialed doors. If suite doors are also centralized, every courier, cleaner and intern must be enrolled by the card office, so tenants quietly start cloning courtesy access and the database stops matching reality. A credential universe that is too expensive to join honestly gets bypassed.

Under Approach B, the landlord cannot revoke anything inside a suite, by design. Tenant offboarding at suite level means the tenant changes codes and deletes fingerprints; the building's only lever is the entrance and mechanical emergency keys, whose control must be procedurally tight (sign-out log, restricted quantity, periodic reconciliation). The failure mode is silent: a departed tenant's staff keeps a valid code for a suite whose lock nobody re-provisioned because the code list lived in one office manager's notebook.

Under Approach C, governance splits cleanly along the lease line and each half is enforceable. Entrance and core revocation stays with the property manager; suite credential hygiene becomes a lease clause — "tenant shall re-provision all access credentials at surrender, and evidence it" — which the surveyor can check because standalone locks show enrollment counts at the keypad. Fingerprint deletion granularity is worth a line in the clause: per-finger removal beats a factory reset that also destroys the staff list mid-lease.

Round verdict: A takes the raw power score, C takes the realistic score. B governs well only inside one suite and cannot be trusted with the perimeter of a 39-tenancy building.

Round Two: Door-of-Record Variety — Glass, Metal, Wood

Commercial buildings are archaeology sites of door construction. The lock has to survive contact with all of it.

Door typeMounting realityCentralized card systemStandalone keypadCatalog family to shortlist
Glass storefront (12 mm tempered, frameless)Clamp/U-fixing or patch-fitting; drilling tempered glass destroys itPoor fit — most card systems assume a stiled door; entrances onlyPossible where a glass-specific body existsGlass door locks (3 models, incl. SLK-G200) — specs to verify in writing on product page
Metal fire-rated stairwell doorRating is the door assembly's property; hardware penetrations are regulated by that assembly's listingAcceptable at entrances if the assembly allows; not a lock choice you make aloneSame constraintConfirm fire door rating requirements and lock suitability with the door supplier and the lock factory — for each door model in scope. We do not present any model as rating-compatible by default.
Wooden office door, 38–45 mmThe easy case; standard mortise/cylinder prepNative fitNative fitMost of the 77-model smart door lock range; check door-thickness band per SKU
Narrow-stile aluminum frameStile width kills standard bodiesRequires narrow-edge hardware regardless of approachRequires narrow-edge hardwareSLK-1104-class narrow-edge units — door-fit fields to verify in writing per model
Basement plant/riser cupboardSteel cabinet or security door, dust, infrequent accessHighest-value doors to keep centralizedOverkill per-doorStainless keypad or RFID cabinet-class units

Two honest engineering notes. First, the glass line is where both pure strategies bleed: a fully centralized building still cannot badge its way onto a frameless storefront without a glass-class lock, and a fully standalone building still cannot leave four storefronts on one shared code with thirty-nine tenancies watching. Second, thickness bands are not marketing numbers. The SLK-9936S, our reference point for a documented spec block, publishes 36–100 mm door thickness — a wide envelope that makes retrofit onto assorted existing doors a fitment calculation rather than a replacement project. Ask every candidate lock the same question with its own datasheet, and where a datasheet is silent (G200 glass fit, SLK-1104 stile width), treat the field as to verify in writing and get it confirmed before the door schedule is signed off, not after.

Round verdict: C wins on coverage because it is the only approach designed to put a different lock family on each door line. A and B each force you to bend a door type to fit the platform.

Round Three: Audit and Liability — Reconstructing One Door, One Night

Insurance and litigation questions in commercial buildings are almost always retrospective: was the rear fire door secured at 02:10 on the 14th, and whose credential opened suite 503 forty minutes earlier?

Approach A answers this from one position, assuming suite doors were included and honestly enrolled. Centralized records are the reason landlords accept card-system capital cost in the first place. The specification shape to demand looks like the audit line of a well-documented platform: the SLK-9936S block records audit/event records up to 1,000 with standalone or centralized database modes and multilingual management software — read that as "the lock keeps a rolling local log and the platform can aggregate." For non-hotel models in this contest, per-model record capacity and retrieval paths are verified in writing; the 9936S line is a yardstick for what a real spec sheet publishes, not a claim that every catalog lock stores events.

Approach B distributes the truth across 39 boxes. Each standalone lock can hold its own records — if it holds any; some keypad units publish no event capability, which is why "confirm whether event records are offered on the product page" belongs in your RFQ for every SKU in the shortlist. Reconstruction after an incident means a technician visiting doors with handheld collection, and by then a departed tenant's lock may already be factory-reset. The liability posture is: landlord can prove the perimeter was (or was not) crossed, and nothing beyond the lease line — which, in many standard commercial leases, is exactly where the landlord's duty ends anyway.

Approach C makes the exposure explicit and matches hardware to it. Doors of record — rear fire door, plant rooms, risers, entrances, loading — stay centralized, so the building's insurable narrative is one export. Suite doors keep tenant-level records where the tenant's own insurer may require them. The survey point is simple: list every door where the building (not the tenant) carries the liability, and that list is your centralized zone.

Round verdict: A takes this for buildings whose leases make the landlord responsible inside suites (serviced offices, managed space); C takes it for conventional multi-tenancy where the lease line is the liability line. B is weakest when anyone asks "prove it" across tenancies.

Round Four: Tenant Turnover — Onboarding and Offboarding Friction

Multi-tenant buildings churn. In a healthy market a mid-rise re-shuffles a quarter of its tenancies in a year, and every shuffle touches access at both ends: keys-to-codes-to-badges in, everyone-out.

Friction pointA: centralizedB: per-suite standaloneC: mixed
New tenant day 1Card office enrollment + suite-door provisioning visit; clean but scheduledTenant self-serves codes same-day; zero landlord touchEntrance badges scheduled; suite codes same-day
Staff join/leave inside a tenantEvery add = card issued at desk; queues on busy MondaysTenant adds/deletes at own keypad instantlyTenant's staff badge for entrances (desk), own codes/biometrics for suite (self)
Tenant leavesRevoke building-wide; still a physical re-provision of suite locks at surrenderCode change at handover — only works if the lease forces evidence of itRevoke badges at boundary; lease clause + enrollment-count check at suite line
Contractor/courier one-hour accessVisitor card process with a host signatureTenant hands a one-time code (some models support temporary/single-use codes; confirm per model)Visitor card to the floor, one-time code to the suite
Property-manager laborHighest — a credential desk is a real postLowest — none, which is the risk, not the benefitModerate — desk covers the perimeter only

The trap in Approach B is the same in both directions: onboarding friction is zero, so nobody documents it, and offboarding is a trust exercise. The trap in Approach A is that a card office is a cost centre tenants resent until they need it; if it is understaffed, tenants route around it and your credential database starts lying. Approach C's friction is deliberately asymmetric — cheap for tenants at suite level, disciplined at the building level — which is what the stakeholder table in section one actually asked for.

Round verdict: B wins tenant satisfaction outright; C wins net-of-governance; A loses this round more often than it concedes, because centralized onboarding only feels smooth when staffed generously.

Round Five: Failure Modes on a Friday Evening

Every access architecture gets tested when something fails outside office hours. Three questions separate the contenders:

What happens when the network or platform is unavailable? Centralized card systems that lean on a live platform degrade to local-caching behaviour only if designed that way — a card revoked minutes ago may still open a door whose lock cached it, and a card enrolled offline may not work until sync. With standalone locks there is no platform to lose: the Friday-evening failure is a dead battery or a forgotten tenant admin code. Mixed systems inherit both failure classes, which is survivable because each failure is confined to its zone. One catalog discipline point: our smart locks run on batteries or mains per model and connect by Bluetooth app control on models that offer it; whether any individual model offers Wi-Fi or wider network options must be confirmed on the product page — nobody in this building decision should plan around a radio they have not read about on the spec sheet.

What happens when a battery dies? All three approaches need battery-cycle figures and low-voltage warning behaviour read per model. The 9936S publishes >15,000 battery operating cycles on 4×AA — one reference envelope for a high-read environment; for suite-door candidates, ask each SKU's own published figure or treat the field as to verify in writing. A property manager's real planning variable is battery-round labor: 39 tenant-managed locks mean the tenant takes the visit, with a posted instruction; a centralized floor means the staff does all visits, every visit, forever.

What happens when someone is locked out with no card and no code? Mechanical emergency access is the floor of safety here. The 9936S spec line includes mechanical emergency access; confirm its presence per model on any shortlist, and never accept a building plan where the only override is "call whoever has the app admin." For fire-pushed doors, egress behaviour is a door-assembly question again: confirm with the door supplier and factory that the chosen hardware keeps the assembly's required egress operation.

Round verdict: draw — each approach fails differently, none catastrophically, provided override mechanics are specified per model. C needs two playbooks instead of one; that is its honest cost.

The Scoreboard

Scoring dimension (weight in a typical multi-tenant buy)A — Centralized cardB — Per-suite keypadC — Mixed
Credential governance (high)524
Door-of-record variety (high)235
Audit and liability (high)524
Onboarding/offboarding friction (medium)354
After-hours failure handling (medium)343
Pattern this scores forSingle-operator buildingsSmall, owner-occupied or low-exposure buildingsConventional multi-tenant commercial buildings

The totals matter less than the shape. A and B peak at opposite ends of the governance/autonomy axis; C never wins a round outright but never loses one badly, which is exactly what a 39-tenancy building with four glass fronts and one fire door rewards.

How the Catalog Categories Map to the Three Approaches

Within the 79-model catalog, the three approaches draw on different category pools:

  • RFID / card (9 models, Keypad RFID Hotel Door Lock) — the backbone of A and of C's centralized zone. Card credentials are the only type here that a landlord can issue, cache, and revoke from one desk at scale. The RFTC/RF card-lock line (118/118E, 228, 230, 232, 238, 239, 253, 305–309, 502, 620/621, 911, 002, 019, 022, 2020, 760) is the breadth this zone draws from; stainless variants (019/022/309) suit exposed entrances.
  • Keypad (18 models, Electronic Keypad Entry Door Lock) — the default of B and of C's suite-side line. Codes need no credential medium and no enrollment ceremony, which is why tenants like them and audit lawyers do not.
  • Fingerprint (37 models, Digital Fingerprint Smart Door Lock) — the strongest answer to round four's staff-churn row: fingers cannot be misplaced and deletion is per-person. Enrollment governance is the open question: who at the tenant is an admin, and what happens to the finger list at surrender. Where card-versus-biometric choice is genuinely contested inside a suite programme, the RFID-versus-fingerprint comparison for commercial doors covers the population and environment arithmetic.
  • Glass (3 models, Glass Door Locks) — SLK-G200 and the double-opening face-recognition B09 class cover frameless storefronts. G200's fitment fields are verified in writing on our side of the table; send the glass thickness and a door photo before any commitment.
  • Multi-credential units — SLK-8831 (fingerprint, password, card, key, and Bluetooth app in one body) and the SLK-1104 narrow-edge class blur the lines usefully in C, letting the same credential culture exist at suite level without a card. Door-fit detail per project is verified in writing.

What We Can Publish, and What You Must Confirm

Spec-sheet literacy is part of this decision. Here is one fully documented block next to the fields this building question keeps hitting on models where we have not published every line:

Spec fieldSLK-9936S (PDP-cited, applies only to this model)Typical open question on suite/glass candidates
Door thickness range36–100 mmNarrow-stile and 38 mm doors: confirm band per SKU — to verify in writing
Credential & readRFID Mifare 1 @ 13.56 MHz, 0–5 cm, <0.25 sFingerprint capacity & deletion granularity per model: confirm
RecordsAudit/event records up to 1,000Whether a keypad candidate keeps records at all: check against the model specification
Power4×AA, battery operating cycles >15,000Battery round ownership: tenant or staff — a policy line, not a spec line
ManagementMultilingual software; standalone or centralized database modesWhat "centralized" concretely exports, and to whom, after a lease ends
Body & override5-pin cylinder, 3-point latch, stainless steel + alloy, mechanical emergency accessEgress behaviour on fire-rated assemblies: confirm with door supplier + factory
Network optionsNot published beyond the aboveWi-Fi availability for any model: check the model’s published specification only

Read this firewall carefully. The 9936S block is a hotel-class lock's published specification — used here as the completeness yardstick, never portable to G200, 8831, SLK-1104, or any other model. Its "standalone or centralized database modes" line is exactly the format of governance claim a commercial building should demand in writing from any candidate for Approach A or C's centralized zone. Where a candidate's sheet is silent, the silence is the answer you must extract before ordering, via the product page or the factory.

Illustrative Scenario: A 39-Tenancy Mid-Rise Lease-Up

Consider an 11-floor frame building, 39 tenancies, four ground-floor glass storefronts, one metal rear fire door, wooden suite doors above floor 3, narrow-stile aluminum frames below it, and a basement the landlord keeps locked. The management agent handles an average of five tenant moves and roughly forty staff-card events per month.

They tested A first — a full card system down to suite doors. It died on the stile widths of the third-floor frames and on the storefronts, and because the card desk could not absorb tenant staff turnover at suite level without a queue. They tested B for one floor as a pilot. Tenant satisfaction rose, and the insurance review went badly: nobody could demonstrate who held access to the rear stairwell corridor after hours, because corridor hardware had been swapped to standalone too.

The landed pattern is C with a hard boundary: centralized RFID at lobby entrances, rear fire door (suitability confirmed with the fire-door contractor before any hardware was discussed), risers, plant, and loading; multi-credential standalone units at suite doors on the wide-stile floors; narrow-edge candidates on the aluminum frames, fitment confirmed per door survey; glass-class units on the four storefronts once the tenant's glass spec is on file. Tenant leases amended with a re-provision-and-evidence clause at surrender. Two lock classes, two admin cultures — and a door-of-record map that answers the 02:10 question from one export.

flowchart TD
    S["Start: who signs the lease on each door?"] --> B1{"Landlord carries liability INSIDE suites?"}
    B1 -- "Yes (serviced / operator-managed space)" --> A1["Approach A: extend card system to suite doors"]
    A1 --> A2["Verify every door fit first: stiles, glass, fire assemblies"]
    B1 -- "No (conventional multi-tenancy)" --> B2{"Common perimeter + risk doors exist?"}
    B2 -- "Yes" --> C1["Approach C: centralized at entrances and risk doors"]
    C1 --> C2["Standalone keypad/fingerprint at suite line with lease clause"]
    B2 -- "No (small owner-run building)" --> B3["Approach B: per-suite standalone + tight mechanical key control"]
    A2 --> DONE["Spec block + door schedule to RFQ"]
    C2 --> DONE
    B3 --> DONE

Verdicts by Building Profile — No Single Winner

Profile 1 — The conventional multi-tenant mid-rise (11 floors, 39 tenancies, retail ground floor). Mixed model. Centralized at the entrance and landlord-risk doors, tenant-managed at suite doors, glass-class hardware wherever there is no stile. This is the contest's structural winner because the lease line, the liability line, and the credential-administration line all coincide at the tenancy boundary, and C is the only approach that admits that.

Profile 2 — The walk-up professional building (5 floors, 13 suites, one shared street entrance, absent landlord). A lean mixed model — really Approach C at minimum viable: a single credentialed entrance lock (card or multi-credential) on the street door plus per-suite standalone units, with the mechanical override in one accountable hand. Full centralization is unaffordable to administer; pure standalone leaves the street door — everyone's, therefore nobody's.

Profile 3 — The high-churn small-office building (3 floors, 27 micro-suites, mostly glass fronts, month-to-month tenants). Startle answer: centralize less than expected at suite level but more than expected at the storefront line. Micro-tenancies turn over so fast that per-suite credential hygiene is fiction; the honest control point is the building entrance and the corridors, kept centralized, with glass-compatible units on storefronts treated as tenant-fit-out items under landlord-approved hardware rules (confirm G200-class fitment per door — to verify in writing). Audit lives where the landlord can actually see it.

Profile 4 — The operator-managed floorplates (serviced-office operator running all 24 suites as one business). This is where full Approach A wins outright. One operator is both landlord and tenant; every door is a door of record; the credential desk is a service they sell, not friction they resent. Governance, audit, and friction all peak when one party owns every end of the leash.

Taking the Question to the Factory

A commercial building's lock specification is not a product choice; it is a door schedule, a credential boundary map, and a lease clause that happen to end in hardware. Before asking any supplier — us included — "which lock," prepare three artefacts: the door-of-record list (liability view), the door survey (thickness, stile width, glass type, egress requirements per door — with rated assemblies confirmed alongside the door supplier), and the churn profile (tenancy turnover, staff enrollment volumes, who administers credentials at suite level).

Those three artefacts turn an RFQ into a fitment review: the factory can then answer model-by-model against your fields instead of pitching a catalogue, and every to verify in writing gap gets closed in writing with numbers that belong to your building. Doors, tenancies, and governance models vary too much for a generic answer to be an honest one — bring the survey and the boundary map, and get the exact figures, fitment envelopes, and options through the quote process.

Start at request-a-quote with your door schedule; if you manage the building's day-to-day access yourself, the property-manager buying protocol pairs with this article's boundary logic, and the apartment-building decision covers the residential version of the same mixed-model question.

Ваша корзина
Ваш опыт использования этого сайта будет улучшен, если вы разрешите использование файлов cookie Политика использования файлов cookie
Chat on WhatsApp