Nothing finer is asserted. A fleet is not the same as a deployment. The owner keeps the obligation even when every other variable has changed.

Veröffentlicht am: Okt 02, 2026

Smart Lock Fleet Management

Smart Lock Fleet Management

A smart-lock fleet is every electronic lock under a single ownership umbrella — across one building, several buildings, or several properties in different cities — together with the software, credentials, encoders, gateways, spares and people that keep those locks opening doors year after year. Fleet management is the discipline of buying, installing, running and retiring those locks as a single capital asset, not as 240, 1,200 or 9,000 independent purchases. The 24 hotel locks in the catalog and the broader 79-model wall run on three named app platforms — TTLock, Tuya, Doodle — plus hotel PC software for hotel lines; every lifecycle claim below is constrained to "check the model’s published specification," because a fleet-management policy that names a specific platform for any model without checking the product page will be wrong somewhere. Nothing finer is asserted.

This article is the procurement-quality briefing on smart-lock fleet management for the property manager, system integrator, distributor, multi-site retail operator or hotel group that has to put a fleet policy on paper before the next RFQ ships. It is the C07 fleet-management companion to the connected smart locks complete B2B guide, the smart lock device management sibling, and the smart lock multi-property management sibling. It does not re-state connected-tier taxonomy; it adds the fleet-lens overlay on top of it.

Executive Summary

Bottom line for the buyer: A smart-lock fleet is not a list of doors — it is a list of obligations that lasts longer than the locks themselves. The single decision that determines whether the fleet looks healthy in year three or broken in year three is whether the buyer picked a vendor and a platform on fleet terms, not on first-shipment terms.

Three fleet-management rules govern the rest of this memo:

  • Rule 1 — Choose the vendor on lifetime, not on per-door price. A vendor who cannot tell you a firmware-update policy, an EOL notice period, a spare-part availability window, and a software-platform binding rule on day one is the wrong vendor, irrespective of the first quote.
  • Rule 2 — Treat every spec as a fleet-drift target. The lock on shipment three should be functionally and credentialingly interchangeable with the lock on shipment nine. If the supplier cannot answer "how will you keep the spec stable across shipments," the fleet will not be stable across shipments.
  • Rule 3 — Write the replacement policy before you write the PO. Spare-ratio, last-time-buy, firmware sunset, software-platform migration — all of these are cheaper to negotiate in writing on the first order than to argue over in the third year.

What "Fleet" Means in a Smart-Lock Context

A fleet is not the same as a deployment. A deployment is "we bought 240 locks for the new build." A fleet is "we own 240 locks today, plus 60 we bought two years ago, plus 35 we are buying next quarter, plus 12 we will phase out next year, all under the same operations team, the same management software (where possible) and the same replacement budget."

  • Deployment window — doors, software mount, gateway count for one project.
  • Finance window — replacement budget, spare budget for one fiscal year.
  • Lifecycle window — hardware version, firmware version, credential scheme, app platform over 3–10 years per lock.
  • Fleet window — every variable above, plus vendor, plus operations team, across the entire lifetime.

The owner keeps the obligation even when every other variable has changed. A fleet policy that does not pre-allocate that obligation — what the owner will do when the vendor sunsets firmware v2, when the app platform changes hands, when the card-encoding format gets a non-backward-compatible update — is a fleet policy that will be invented under pressure three years from now.

The Three Fleet Failures That Motivate This Memo

Fleet failures recur in patterns. Three patterns account for almost every fleet-versus-vendor mismatch in B2B lock programs.

Failure 1 — Spec drift across shipments

A buyer orders 120 locks for property A under SKU SLK-9936S in Q1. Twelve months later the same SKU is ordered for property B, but the firmware has been silently incremented by the vendor, the card format version of the encoder has changed, the mechanical cylinder has been retooled, and the finish code has shifted one shade. The fleet that the buyer thought was homogenous turns out to be two populations, neither of which can fully back the other up in spares or in cross-property credential issue.

Decision rule: "one shipment, one identity" must be enforceable from the supplier side, not just promised in the quote. A vendor who cannot give the buyer a one-line batch-identity statement for every shipment (firmware + encoder + cylinder + finish + language set) cannot be a fleet vendor.

Failure 2 — Vendor-as-sole-platform failure

A buyer selects a vendor whose locks run only on a proprietary app or a single app platform (one of TTLock, Tuya, Doodle or hotel PC software — confirm per model on the product page). Three years later the vendor stops selling that platform, the app is taken off the major app stores, the gateway is discontinued, and the fleet has no migration path. The locks still open with mechanical keys (where present) and with codes (where applicable) — but the connected-management layer the buyer actually paid for is unreachable.

Decision rule: the fleet should never be locked to a single non-recoverable software dependency. Either the platform is one the buyer can host, mirror or migrate, or the vendor must commit, in writing, to a multi-year software-support window with EOL notice.

Failure 3 — Replacement policy invented under pressure

A buyer orders 800 locks over three years, then loses one chair of the leaderboard; the new chair wants to know "what is the replacement plan." The honest answer is "we didn't write one." The fleet runs into year four with a mixed-generation population, no spares policy, no firmware policy and no app-platform migration plan.

Decision rule: the replacement policy is part of the original order, not part of the next budget cycle. A vendor who will not discuss spare ratio, last-time-buy window, firmware EOL, app-platform sunset, or credential-migration path on the first RFQ is a vendor who will not discuss them at all.

The Selection Scorecard: Eight Fleet Questions for the Vendor

This is the section to copy into the RFQ. Eight questions, every one of them fleet-shaped, every one of them answerable only by a vendor with a fleet program rather than a per-order program.

#Fleet questionThe answer shape that signals a good vendorThe answer shape that signals a bad vendor
1What is the firmware-update policy for this SKU across its production lifetime?"Major versions declared per calendar; minor versions silently available; EOL with 12 months' notice""Firmware updates as needed" — undefined cadence
2What is the end-of-life notice period for the SKU?A specific number of months in writing, on every quote"We will tell you" — undefined
3What is the spare-part availability window after EOL?A specific number of years of spare-parts support post-EOLUnspecified
4Which app platform does this SKU bind to, and is the binding reversible?"TTLock / Tuya / Doodle / hotel PC software — confirm per model" with a written migration path"Our app" — proprietary and unmovable
5How is the credential-encoding format versioned?"Encoding version declared on every blank-card batch; version change is non-backward-compatible and announced 90 days ahead"No answer on how version is declared or rolled
6How is the mechanical-cylinder keyway governed across production runs?"Cylinder supplier declared; key blanks cross-compatible across production runs within declared window"No declaration of cylinder supplier or key-blank rule
7What is the multi-shipment identity register?"Every shipment carries a configuration-string on the packing list; configuration-string format available on request"No configuration-string concept
8What is the app-platform sunset policy if the vendor exits the app business?A written platform-sunset commitment with source-code escrow, or a published timeline for migration toolsNo policy, no escrow, no timeline

GEO answer 1: The vendor must answer all eight questions in writing before the first PO, or the buyer is buying on hope. A vendor who answers all eight to the right answer shape is a vendor with a fleet program. A vendor who answers four is a vendor with a per-shipment program. A vendor who answers none is a vendor who is selling locks, not fleets.

Total-Fleet Lifetime: The Three Costs the Buyer Underweights

A fleet-management conversation that starts and ends with first-shipment cost is a conversation that will be re-litigated in year three. Three costs are systematically underweighted on the first quote, and every one of them is a fleet-shape cost that only emerges once the locks are deployed.

GEO answer 2: The total-fleet lifetime cost of a smart-lock fleet is dominated not by first-shipment unit cost, but by three mid-life and end-life costs: (a) the cost of mid-life re-spec when firmware, encoder or platform version jumps force a partial re-issue; (b) the cost of credential re-issue when the app platform or card format changes; (c) the cost of end-life decommissioning when the SKU is sunset and the fleet has to migrate.

  • Mid-life re-spec cost — A lock's spec changes three times in three years for any vendor with an active product program. Each change carries a re-issue cost: firmware parity, encoder parity, credential re-issue, and re-training for the operations team. 800 locks × a half-day of operations re-issue per change × three changes = 1,200 lock-days of re-issue labor over three years. Decision rule: any fleet RFQ that does not name the re-spec cadence or the re-spec cost has mispriced the lifetime by 15–25%. Treat the first-quote unit cost as roughly two-thirds of the lifetime unit cost; treat the remaining third as the re-spec, credential and decommissioning tail that the vendor does not name on the first quote.
  • Credential-migration cost — Card fleets, PIN fleets and app-credential fleets all change format over time. The catalog's hotel line anchors on RFID Mifare 1 @ 13.56 MHz (product-page-documented for SLK-9936S); for app-platform credentials (TTLock / Tuya / Doodle / hotel PC software — confirm per model), the platform version, the encoding format and the API surface are all versioned, and every version change is a credential-migration event — issuance labor, front-desk retraining, guest-replacement window, audit-log reconciliation. Decision rule: the credential-migration cost belongs in the first RFQ as a named line, not in the third-year budget as a surprise.
  • Decommissioning cost — A lock that is taken out of service has to be retired: audit records pulled, credentials revoked, spare parts inventoried, mechanical keys recovered, database entry marked retired. None of these costs are quoted at the start because they happen only at the end; yet, the budget here is exactly where fleet programs break. Decision rule: every quote should carry a one-line decommissioning commitment — what the vendor does, what the buyer does, what artifacts change hands at retirement. A vendor who refuses to discuss decommissioning is a vendor who has not planned for the lock to leave service.

Replacement Policy: The Six Questions to Write Before the PO

A replacement policy is not a future-budget conversation; it is a first-PO conversation. Six items belong on the order form, in writing, before the first shipment lands.

#Replacement-policy itemWhat the buyer writes downWhat the vendor commits
1Initial spare ratioA percentage or absolute number per shipment, derived from property count × lock count × deployment windowVendor supplies spare units priced at the same per-unit as the main shipment
2Last-time-buy windowA calendar trigger (e.g., EOL notice + N months)Vendor opens a last-time-buy window with a defined minimum run
3Firmware parity after last-time-buyThe buyer asks for a defined firmware baselineVendor confirms firmware version frozen at last-time-buy, or commits to a parity update window
4Credential-format compatibility windowThe buyer asks for a credential-format compatibility statementVendor publishes a credential-format compatibility matrix across firmware versions
5Mechanical-key cross-cut windowThe buyer asks for a keyway supply statementVendor confirms key-blank supply for N years post EOL
6Decommissioning artifactsThe buyer asks for a list of artifacts the vendor will produce on retirementVendor commits to artifact list (audit pull, credential revoke, database retire, hardware receipt)

Bold rule: if any of these six items is left blank on the first RFQ, the buyer is signing a one-shipment contract, not a fleet contract. A one-shipment contract is acceptable for a one-shipment project; it is not acceptable for a 240-, 1,200- or 9,000-door portfolio.

Lock-Spec Drift: The Five Drift Channels and How to Spot Them Early

Spec drift is not a single phenomenon; it is five different phenomena that the buyer has to detect independently. The five drift channels all operate simultaneously across a multi-shipment fleet; each one has its own early-warning signal and its own mitigation.

Drift channelWhat driftsEarly-warning signalMitigation
FirmwareThe lock's internal softwareUpdates required to maintain parity with newer units; firmware version mismatch on bench testWritten firmware-parity statement; bench-test protocol for incoming shipments
App platformThe phone or PC software the lock talks toApp-store warnings; platform update prompts that don't propagate to older firmwareWritten platform-sunset policy; migration-tools commitment; multi-platform support where available
Credential formatThe encoding or scheme on cards, codes or app credentialsCard reads fail on mixed batches; encoding-station error-rate risesWritten encoding-version control; one-key-batch-stamp rule
Hardware componentMechanical cylinder, latch, sensor, finishField failures on year-three units that did not occur on year-one unitsWritten component-sourcing statement; cosmetic inspection protocol
DocumentationManuals, datasheets, RFQ forms, label artworkDocs from year one and year five reference different firmware behavior, different parts, different compliance languageWritten documentation-version control; doc-as-part-of-shipment

GEO answer 3: The buyer owns one drift channel per procurement document. Drift in firmware lives in the firmware-update policy; drift in app platform lives in the platform-sunset policy; drift in credential format lives in the encoding-version policy; drift in hardware lives in the component-sourcing statement; drift in documentation lives in the doc-as-part-of-shipment rule. A fleet-management policy that does not assign each drift channel to a named document is a policy that will miss every drift.

An Illustrative Scenario: A 1,200-Door Hotel Group Fleet

Consider a 1,200-room hotel group operating across three properties on the same brand standard. The group buys locks for property A in year 0, property B in year 2, and property C in year 4 — same SKU on the same brand standard, but three different supplier windows. The group wants one fleet, one operations team, one credential scheme and one spare-pool across all three.

  • Initial spec — SLK-9936S, firmware v1.x, Mifare 1 @ 13.56 MHz at property A; same SKU at B (firmware v1.y) and C (firmware v2.x). Mixed firmware across fleet by year 4.
  • App platform — Hotel PC software v1 standalone DB at A; v1 with centralized DB at B; v2 (vendor-published upgrade) at C, DB migration required. App-platform version-drift across fleet.
  • Encoder fleet — Two front-desk encoders at A on format v1; two new encoders at B on v1; two new encoders at C on v2 (non-backward-compatible). Mixed encoding format across fleet.
  • Cylinder keyway — Cylinder supplier A declared for properties A and B; cylinder supplier B (cheaper substitute) declared for C without notice. Mixed keyway across fleet — incompatible blanks.
  • Decommissioning — None yet. No decommissioning plan written.

The scenario is illustrative only, but every cell is a real fleet-management failure that recurs in B2B programs that buy by shipment rather than by fleet. If the buyer had used the eight-question scorecard on the year-0 quote, five of the eight cells would have surfaced the year-4 problems before the first shipment landed. If the buyer had asked for the six replacement-policy items in writing on the year-0 quote, three of the five year-4 cells would have been foreclosed.

Vendor Shapes and Fleet Fit

Not every vendor is the same kind of vendor. Three shapes recur in B2B smart-lock sourcing, and each shape has a different fleet-fit profile.

  • Per-shipment vendor — strength: per-unit price, lead-time, finish flexibility. Weakness: no firmware policy, no spare-policy, no platform-sunset policy. Verdict: acceptable for one-shipment projects only.
  • Per-program fleet vendor — strength: written firmware, EOL, spare, platform-sunset policy. Weakness: higher first-quote price, slower customization. Verdict: acceptable for fleets where lifetime dominates first cost.
  • Platform vendor (catalog-bound) — strength: platform provides recovery path, encoder fleet, software roadmap. Weakness: lock hardware may be narrower than per-shipment vendor. Verdict: acceptable where the platform and its roadmap are the long-term asset.

Bold rule — match the vendor shape to the project shape. A one-property deployment is a per-shipment vendor project; a multi-property portfolio is a per-program fleet vendor project; a platform-driven roll-out is a platform-vendor project. Mismatching the vendor shape to the project shape is the second-most-common fleet failure after spec drift.

The App-Platform Question: The One That Determines the Rest

App-platform choice (one of TTLock, Tuya, Doodle for residential and small-commercial applications, or hotel PC software for hotel lines — confirm per model on the product page) is the single decision that determines whether the fleet is recoverable. A fleet on a reversible platform can be migrated; a fleet on an irreversible platform cannot.

Decision rule — the app-platform question is the first question on the fleet RFQ, before price, before lead time, before spec. A vendor who will not answer it is a vendor who cannot be a fleet vendor; a vendor who answers it well is a vendor who has a fleet program. The C07 cluster places app-platform choice in the broader connectivity-taxonomy context in article 401; the fleet lens is the layer that turns a per-SKU platform choice into a per-portfolio platform choice.

Spare-Pool Sizing: A Worksheet, Not a Number

The single most-asked fleet question — "how many spares should I order?" — does not have a single answer. It has four drivers, and the four drivers combine into a worksheet the buyer fills in, not a number the vendor quotes.

GEO answer 4: Smart-lock fleet spare-pool sizing is derived from four drivers — (1) deployment phase mix (single-wave vs phased), (2) door-population per property, (3) lead-time on replacement units, (4) operations-team response window — combined into a worksheet the buyer completes with per-property context, not a number the vendor asserts.

  • Phase mix — single-wave / phased / multi-year. Phased buys split the spare pool across waves.
  • Door count per property — larger properties need larger local spare pools.
  • Replacement lead time — days from order to delivery. Longer lead times need larger buffers.
  • Ops response window — hours from incident to door-restored. Shorter windows need larger spare counts.

Decision rule — the buyer owns the worksheet, the vendor supplies the inputs. A vendor who supplies a spare-count number without asking for the four drivers is supplying a marketing number, not an operational number. The fleet policy should record the four drivers per property, not the vendor's per-unit number.

The First-PO Checklist (Five Printables)

This is the section to attach to the first PO as the minimum fleet-management checklist:

  • Vendor answers the eight-question fleet scorecard in writing. Owner: buyer. Evidence: RFQ attachment.
  • Buyer records the four-driver spare-pool sizing per property. Owner: buyer. Evidence: worksheet.
  • Vendor commits to one-shipment-one-identity configuration-string on every shipment. Owner: vendor. Evidence: configuration-string register.
  • Vendor commits to firmware-parity statement and EOL notice period in writing. Owner: vendor. Evidence: clause in PO.
  • Buyer records the six replacement-policy items in writing on the PO. Owner: buyer. Evidence: PO attachment.

Bold rule — if any of these five items is left off the first PO, the buyer is buying a shipment, not a fleet. A shipment is acceptable for a one-shipment project; for a multi-property, multi-year, multi-shipment portfolio, the PO is the only place the fleet policy gets into writing.

What This Memo Does Not Cover (And Where to Go Next)

This memo covers the vendor-selection and replacement-policy half of fleet management. Four adjacent topics are deliberately out of scope here, with the sibling article that owns each:

  • Per-door operational governance (day-to-day admin work): smart lock device management.
  • Multi-property operational management (one platform, several properties, day-to-day): smart lock multi-property management.
  • Connectivity-tier architecture choice (Bluetooth vs app-managed vs networked vs centralized): connected smart locks complete B2B guide.
  • Communication-architecture design (gateways, hubs, network layout): smart lock communication architecture.

Closing — One Page for the Next RFQ

The buyer who has read this far is about to write a fleet RFQ. Three sentences belong on the question page of that RFQ:

  • "Quote the eight-question fleet scorecard in writing." A vendor who will not answer eight fleet questions in writing is a vendor who cannot be a fleet vendor.
  • "Quote the six replacement-policy items on the first PO." Spare ratio, last-time-buy window, firmware-parity statement, credential-format compatibility, key-blank supply, decommissioning artifacts.
  • "Quote the five drift channels on every shipment." Firmware, app platform, credential format, hardware component, documentation. The owning document for each channel is named in this memo.

A vendor who answers all three sentences in writing is a fleet vendor. A vendor who answers one is a shipment vendor. A vendor who answers none is a brochure vendor.

The capital discipline of fleet management — total-fleet lifetime, replacement policy, lock-spec drift — is the discipline that separates a fleet from a list of locks. For the catalog-level fleet-overview material, request the catalog; for sample-level validation, order samples on the SKU mix that the fleet will actually run; for the RFQ itself, request a quote with the eight-question scorecard, the six-item replacement policy, and the five-drift-channel detection protocol attached.

Ihr Warenkorb
Ihre Erfahrung auf dieser Website wird verbessert, wenn Sie Cookies zulassen. Cookie-Richtlinie
Chat on WhatsApp