The same lock body, quoted across two application classes, lands on two different quotation lines because the cost stack is application-shaped, not lock-shaped.

Veröffentlicht am: Jan 19, 2024

Smart Lock Price by Application

Smart Lock Price by Application — A Five-Pillar Decision Framework for Application-Tier Price Decisions

Smart lock price by application is not a single tier ladder the buyer reads off a sheet. It is the price-component view that depends on which application class the buyer is actually buying into — hotel and serviced-apartment, multi-family apartment, office and commercial, retail and storefront, glass-door, industrial and staff-only, vacation rental, or institutional — and which application-class profile the buyer writes into the RFQ before any figure reaches the inbox. The price that lands on a quotation is the output of a five-pillar decision pipeline that takes the application class as the input: Pillar 1 names the application class and what it is actually buying; Pillar 2 reads the per-application cost-stack structure; Pillar 3 reads the application-specific RFQ scope drivers; Pillar 4 reads the per-application lifecycle cost posture; Pillar 5 consolidates the cross-application sign-off block and writes the RFQ into procurement. The same lock body, quoted across two application classes, lands on two different quotation lines because the cost stack is application-shaped, not lock-shaped. Every per-SKU figure is verified in writing or "check the model’s published specification"; the application-tier framing operates at category-fact level only and never invents a per-SKU numeric anywhere in the article.

This is a decision-pillar explainer. The subheads are pillar names, not questions. There is no FAQ section by design: every buyer question that belongs in a FAQ lives inside the pillar where the answer actually applies, so an application-tier definition question is answered in Pillar 1, a cost-stack question in Pillar 2, an RFQ-scope question in Pillar 3, a lifecycle-cost question in Pillar 4, and a sign-off question in Pillar 5. The voice is the supplier who has read more per-application RFQs than the brochure ever quoted, and who has seen what a hotel-tier cost stack inherited on a vacation-rental RFQ does to the buyer's headline figure the moment the third container ships. Tables are the working surface of each pillar. Scattered throughout, the product-page-documented SLK-9936S hotel-class first-party spec block (door thickness 36–100 mm · RFID Mifare 1 @ 13.56 MHz · read distance 0–5 cm · read time <0.25 s · 4 × AA · battery operating cycles >15,000 · audit/event records up to 1,000 · 5-pin cylinder · 3-point latch · stainless steel + alloy body · multiple finish options · mechanical emergency access · multilingual management software · standalone or centralized database modes · 1–5 star hotel positioning) appears ONCE only as the documentation-granularity yardstick at the Pillar 1 anchor under explicit no-porting-across-models firewall scoped strictly to that SKU — every per-SKU figure outside that yardstick firewall is routed to "check the model’s published specification".

For the surrounding price-by-axis context — the per-quantity, per-customization, per-material and per-access-method reading the application-tier framing sits inside — read alongside Smart Lock Price by Order Quantity, Smart Lock Price by Customization, Smart Lock Price by Material, Smart Lock Price by Access Method, and the door-type sibling at Smart Lock Price by Door Type. For the apartment-class buyer-guide posture the application-tier reading feeds under — multi-zone residential procurement — read alongside Smart Locks for Apartment Buildings: Buyer Guide. For the MOQ-and-price overlay that constrains the order-volume tier the application-tier RFQ consumes, read Smart Lock MOQ and Price.

What the application class actually buys — the framing before the figure

Before any pillar resolves, the buyer has to fix in writing what the application class actually buys. A smart lock is not a SKU. A smart lock is a component inside an application-class operating system, and the application class changes what that component has to do. A hotel-class lock body is one component in a four-component property operating system (door hardware + RFID card + front-desk encoder + hotel PC management software with optional centralized database above); a multi-family apartment-class lock body is one component inside a three-zone procurement stack (unit doors + common-area doors + staff or maintenance doors) running on a property-manager app with multi-role admin; an office-class lock body is one component inside a tenant-permission network that crosses reception, suite and staff doors under a system-integrator credential stack; a retail-class lock body is one component on a storefront or stockroom door that sees daily traffic, single-shift staff and a delivery cadence; a glass-door-class lock body is one component on a clamp-mounted body that cannot chisel into the glass leaf and that has to preserve a finish visible on a transparent substrate; an industrial or staff-only-class lock body is one component on a maintenance, server, plant or restricted door where audit depth and override posture dominate the credential question; a vacation-rental-class lock body is one component on a guest-turnover door where credential issuance is a per-stay workflow; an institutional-class lock body is one component on a school, clinic, dormitory or government door where the audit-trail posture is shaped by the institution's record-retention rule. Each application class carries a different credential volume, a different administrative posture, a different mechanical-load expectation, a different integration surface, and a different lifecycle story.

The honest supplier acknowledges that the application class is the buyer's input, the SKU is the supplier's answer, and the price the buyer reads off the line is the intersection of those two. The honest buyer writes the application class into the RFQ before the SKU is allocated, so that the per-application cost-stack lines, the per-application RFQ scope drivers, and the per-application lifecycle lines can be read against the application class without the buyer paying for application-class assumptions the supplier had to invent.


Pillar 1 — Application class: what the tier is actually buying

The first pillar answers one question only: which application class is this lock body actually being purchased into, and what is the tier buying? Application class is the buyer's input. The lock body is the supplier's input. The tier's administrative posture is the property's input. Confusing the three is the most common mistake in price-by-application conversations, and it starts at the buyer's first RFQ email.

1.1 The eight application classes the catalog and the brochure implicitly address

The 79-model catalog and the eight published category pages — hotel-lock, fingerprint-door-lock, keypad-door-lock, rfid-door-lock, face-recognition-door-lock, glass-door-locks, bluetooth-lock, rfid-lock — collapse into eight application classes the buyer is asked to commit to before the SKU is allocated. Each class has its own administrative shape and its own per-tier cost posture.

  • Hotel and serviced-apartment class. One-component property operating system with a front-desk encoder, hotel PC management software, optional centralized database above, RFID credentialing at the door, mechanical emergency access, audit depth sized for front-desk daily incident pull, multilingual multilingual staff and a 1–5 star positioning. The product-page-documented SLK-9936S hotel-class first-party spec block (door thickness 36–100 mm · RFID Mifare 1 @ 13.56 MHz · read distance 0–5 cm · read time <0.25 s · 4 × AA · battery operating cycles >15,000 · audit/event records up to 1,000 · 5-pin cylinder · 3-point latch · stainless steel + alloy body · multiple finish options · mechanical emergency access · multilingual management software · standalone or centralized database modes · 1–5 star hotel positioning) is the documentation-granularity yardstick the article invokes here ONCE under explicit no-porting-across-models firewall scoped strictly to that SKU; every hotel-class sibling (SLK-9936G, SLK-9905A hidden-reader, SLK-9951TH, SLK-9962S, the legacy RFTC/RF card-and-code 118/118E/228/230/232/238/239/253/305/306/308/309/502/620/621/911/002/019/022/2020/760 line) is read at category-fact level only and every per-SKU figure routes to "check the model’s published specification".
  • Apartment and multi-family residential class. Three-zone procurement stack (unit doors + common-area doors + staff or maintenance doors) running on a property-manager app with multi-role admin, resident / staff / visitor population split, mechanical-key fallback per unit, multi-year credential lifespan. The apartment-class buyer-guide posture is the dedicated sibling Smart Locks for Apartment Buildings: Buyer Guide; the application-tier cost stack here is the application-layer view that 301 frames at the property-management layer.
  • Office and commercial class. Tenant-permission network crossing reception, suite, meeting-room, conference-room, server-room, staff-only and restricted doors, system-integrator credential stack with role hierarchy, daytime throughput prioritized, after-hours audit posture defined by the tenant agreement.
  • Retail and storefront class. Storefront or stockroom door with single-shift staff, delivery cadence, daily traffic, and a credential mix that has to survive the staff turnover the apartment class never sees and the audit depth the hotel class never asks for on a stockroom door.
  • Glass-door class. Clamp-mounted body on a single-leaf or double-leaf glass panel, no chisel into the glass, finish preserved on a transparent substrate, app-platform binding constrained by what can be wired or powered on a glass-door leaf; the catalog glass-door smart-lock line is the SLK-G200 class and the catalog double-opening face-recognition glass-door model is the B09 class — every per-model glass-thickness, glass-gap and finish figure is verified in writing and routes to the dated product page.
  • Industrial and staff-only class. Maintenance, server, plant, restricted or restricted door; audit-trail posture and override posture dominate the credential question, mechanical-override cylinder profile carries operational weight the hotel class offloads to a front desk.
  • Vacation rental and short-stay class. Guest-turnover door where credential issuance is a per-stay workflow, time-bounded passcode or issuance per staff per shift, integration with a property-management system optional but common, mechanical-key fallback typical.
  • Institutional class. School, clinic, dormitory, government or bank door where the audit-trail posture is shaped by the institution's record-retention rule and the credential authority is the institution rather than the household.

The pillar produces one artefact per shortlisted application class: a one-row class sheet that names the typical operating-system shape, the credential sub-population, the audit-trail expectation, the mechanical-override posture, and the integration surface. The supplier's per-class quotation is only useful when matched to the buyer-written class sheet; the same lock body on a hotel and on an institutional door will be quoted against two different cost stacks.

1.2 The product-page-documented hotel-class yardstick under firewall

The hotel-class tier is the only application tier the article anchors on a dated per-SKU spec block. The yardstick is the SLK-9936S hotel-class first-party spec block read from the dated product page: door thickness 36–100 mm, RFID Mifare 1 @ 13.56 MHz, read distance 0–5 cm, read time <0.25 s, 4 × AA battery format, battery operating cycles >15,000, audit/event records up to 1,000, 5-pin cylinder, 3-point latch, stainless steel + alloy body, multiple finish options, mechanical emergency access, multilingual management software, standalone or centralized database modes, 1–5 star hotel positioning. The firewall is explicit: the Mifare 13.56 MHz specification is sanctioned ONLY for SLK-9936S in this article; no hotel-class sibling (SLK-9936G / SLK-9905A / SLK-9951TH / SLK-9962S) inherits the figure, no residential or office or industrial or institutional SKU inherits the figure, and the buyer who needs a per-SKU figure for any sibling or for any non-hotel class reads the dated product page for that SKU. The yardstick's role is to demonstrate the documentation granularity the buyer should demand before any application-class figure moves.

1.3 Application-class fit scorecard

The scorecard below is the working surface for the application-class pillar. The buyer completes one row per application class under consideration. Every column is the buyer's reading of the tier — not the supplier's reading.

App-class IDOperating-system shapePopulation (sub-populations + turnover)Audit-trail expectationOverride postureIntegration surfacePer-SKU confirm-on-product-page flag
AC-01 Hotel and serviced-apartment4-component (door hardware + card + front-desk encoder + hotel PC software + optional centralized DB)Guest (per-stay) + staff (per-shift) + housekeeping + maintenanceDaily / per-incident / per-stay pullMechanical emergency access + front-desk master keyStandalone or centralized database per property or per groupcheck the model’s published specification (per-SKU)
AC-02 Apartment / multi-family3-zone (unit + common + staff) + property-manager app + multi-role adminResident (multi-year) + staff + visitor + vendorPer-incident / per-quarter complianceMechanical-key fallback in management custodyProperty-manager app, optional PMS, optional building intercomcheck the model’s published specification (per-SKU)
AC-03 Office / commercialTenant-permission network + system-integrator credential stackStaff (daytime) + visitor + after-hoursDaily / per-tenant pullPer-suite mechanical + master-key archiveTenant app + role hierarchy + audit-event buffercheck the model’s published specification (per-SKU)
AC-04 Retail / storefrontSingle-shift staff + delivery cadence + daily trafficStaff (per-shift) + deliveryPer-incidentPer-store mechanical + master-key archiveStandalone app or store-auditcheck the model’s published specification (per-SKU)
AC-05 Glass-door storefront / partitionClamp-mounted body + no-chisel constraint + finish preservationTenant / staff / visitor per storefront or partitionPer-incidentMechanical-key fallbackApp-platform (TTLock / Tuya / Doodle) — confirm per-SKUcheck the model’s published specification (per-SKU)
AC-06 Industrial / staff-onlyMaintenance / server / plant / restricted door + audit-dominant postureMaintenance + operations + restrictedContinuous audit + retention-rule-shapedMechanical override + restricted archiveStandalone or centralized auditcheck the model’s published specification (per-SKU)
AC-07 Vacation rental / short-stayPer-stay guest credential + per-shift staff + optional PMSGuest (per-stay) + housekeeping + maintenancePer-stay / per-incidentMechanical-key fallback + front-desk handoffOptional PMS + independent channelcheck the model’s published specification (per-SKU)
AC-08 Institutional (school / clinic / dorm / gov / bank)Institution-as-credential-authority + retention-rule-shapedStudent / patient / staff / restrictedPer-retention-cycle pullMechanical override + institution archiveInstitution app + record-retention packagecheck the model’s published specification (per-SKU)

The integration-surface column is the column the buyer uses in Pillar 3 to size the RFQ scope. The per-SKU documentation flag is the column the buyer uses in Pillar 5 to write the sign-off block. Every input cell in this scorecard defaults to the buyer's reading of the application class; the supplier has no input to this pillar.

1.4 What the application-class pillar does not say

The pillar does not assert that any particular catalog SKU belongs to any particular application class on any particular published price. It does not promote a particular lock body above another across application classes. It does not predict a per-class figure in any currency, in any tier, in any MOQ floor or in any lead-time window on any particular SKU. The application-class profile is the buyer's read of the tier; the cost-stack envelope of Pillar 2 is the supplier's read of the SKU; the per-class cadence of Pillar 5 is what the buyer writes into the procurement schedule.


Pillar 2 — Per-application cost-stack structure

The second pillar answers: what is the cost-stack structure the factory assembles when the application class is fixed, and which cost-stack lines move with which application class? Application-class cost-stack structure is unforgiving. The same lock body quoted across two application classes lands on two different quotation lines because the cost-stack lines are tier-shaped: the hotel-class quotation carries a front-desk encoder line, a hotel PC software line, a per-guest card consumable line and an optional centralized-database line; the apartment-class quotation does not; the office-class quotation carries a tenant-app license line and a role-hierarchy commissioning line; the glass-door-class quotation carries a glass-clamp hardware line and a finish-preservation line; the industrial-class quotation carries an audit-dominant retention-package line; the vacation-rental-class quotation carries a per-stay issuance line; the institutional-class quotation carries a record-retention package line. The buyer must read the cost-stack structure against the application class before any SKU is allocated.

2.1 The nine cost-stack lines every application class carries

Every application class assembles a quotation from nine factory-side cost-stack lines plus two buyer-side RFQ choices that determine which factory-side lines are present at all. The nine factory-side lines are:

  1. Mechanical / structural line. Lock body, mortise or clamp or cylindrical envelope, latch or bolt geometry, mechanical-override cylinder profile, finish, environmental envelope. Every per-SKU line is Check the model’s published specification.
  2. Electronic-module line. Fingerprint sensor, RFID reader, keypad, Bluetooth or Wi-Fi module, antenna. Each sub-module has its own PCB area, its own power consumption, and its own factory-side calibration step. The cost moves with every credential the buyer added at Pillar 1.
  3. Motor + gearbox + clutch line. The mechanical-release envelope has to be balanced against door-leaf weight and against the application-class mechanical-load expectation. Motor torque, gearbox ratio, clutch behavior, and free-rotation handle posture are part of this line. Per-SKU posture is Check the model’s published specification.
  4. Power-format line. Battery count, battery format (4 × AA on the SLK-1101 yardstick), battery operating-cycle figure, low-battery warning behavior, USB or emergency-power fallback. Per-SKU figure is Check the model’s published specification.
  5. Audit and event-record line. Audit-event-record depth (up to 1,000 on the SLK-1101 yardstick), event-pulling cadence, audit-event retention policy, log-rotation behavior. Per-SKU depth is Check the model’s published specification.
  6. Credential-issuance line. Per-tier credential issuance volume — per-guest for hotel and vacation-rental, per-resident for apartment, per-staff for office, per-shift for retail, per-tenant for institutional. The factory-side cost of the issuance workflow (encoder hardware, encoder commissioning, software seat, PMS integration, per-credential consumable) lives here.
  7. Integration line. Front-desk encoder + hotel PC software + optional centralized database (hotel); property-manager app + multi-role admin + optional PMS (apartment); tenant app + role hierarchy + audit-event buffer (office); standalone or store-audit (retail); standalone app or PMS (vacation rental); institution app + record-retention package (institutional); audit-dominant retention package (industrial). Per-SKU integration posture is Check the model’s published specification.
  8. Configuration-string line. Per-program configuration string the buyer writes into the RFQ: per-tier credential methods, per-tier audit depth, per-tier mechanical-override cylinder profile, per-finish option, per-platform binding (TTLock / Tuya / Doodle / hotel PC software — confirm per-SKU), per-tier branding (logo / packaging artwork / user manual artwork / product photography / catalog artwork), per-tier firmware revision. Per-tier configuration-string line is Check the model’s published specification.
  9. Lifecycle and day-2 line. Per-tier lifecycle story: spare parts ordering, replacement cycle, firmware upgrade, audit-event buffer reset, credential re-issuance, encoder commissioning day-2, software seat day-2, day-2 installer labor. Per-tier day-2 figure is Check the model’s published specification.

The two buyer-side RFQ choices that determine which factory-side lines are present at all are: which application class the buyer is committing to (the Pillar 1 answer) and which per-class integration surface the buyer is opting into (standalone / property-manager app / hotel PC software / PMS / institution app). If the buyer commits to hotel-class but skips the hotel PC software line, the quotation drops the software seat line but the front-desk encoder line stays; if the buyer commits to apartment-class but skips the multi-role admin line, the quotation drops the role-hierarchy commissioning line but the property-manager app seat stays.

2.2 Cost-stack composition by application class

The table below is the working surface for the cost-stack pillar. The buyer reads one column per application class. Every cell is the cost-stack line that the application class triggers. Every per-SKU numeric is Check the model’s published specification.

Cost-stack lineAC-01 HotelAC-02 ApartmentAC-03 OfficeAC-04 RetailAC-05 Glass-doorAC-06 IndustrialAC-07 Vacation-rentalAC-08 Institutional
Mechanical / structuralLock body + mortise + 5-pin cylinder + 3-point latch + finish (per-SKU)Lock body + mortise + finish (per-SKU)Lock body + mortise + finish (per-SKU)Lock body + mortise + finish (per-SKU)Clamp body + glass-clamp hardware + finish preservation (per-SKU)Lock body + mortise + heavy-duty finish (per-SKU)Lock body + mortise + finish (per-SKU)Lock body + mortise + heavy-duty finish (per-SKU)
Electronic moduleRFID + keypad + (optional fingerprint) per-SKUFingerprint / RFID / keypad / app per-SKURFID / keypad / app per-SKUKeypad / RFID / app per-SKUApp-platform binding constrained per-SKURFID / fingerprint / app per-SKUApp / keypad / RFID per-SKURFID / fingerprint / keypad per-SKU
Motor + gearbox + clutchPer-SKU motor + gearbox + clutchPer-SKU motor + gearbox + clutchPer-SKU motor + gearbox + clutchPer-SKU motor + gearbox + clutchPer-SKU motor + gearbox + clutch (clamp envelope)Per-SKU heavy-duty motor + gearboxPer-SKU motor + gearbox + clutchPer-SKU motor + gearbox + clutch
Power format4 × AA per-SKU (yardstick) + USB fallbackPer-SKU + USB fallbackPer-SKU + USB fallbackPer-SKU + USB fallbackPer-SKU (clamp envelope) + USB fallbackPer-SKU + USB fallbackPer-SKU + USB fallbackPer-SKU + USB fallback
Audit / event-recordUp to 1,000 per-SKU (yardstick) + retention policyPer-SKU depth + retention policyPer-SKU depth + tenant retentionPer-SKU depth + retentionPer-SKU depth + retentionPer-SKU continuous + retention-rule-shapedPer-SKU depth + per-stay retentionPer-SKU depth + institution retention-rule-shaped
Credential issuanceFront-desk encoder + per-guest card consumableProperty-manager app + per-resident issuanceTenant app + per-staff issuanceStore app + per-staff issuanceApp-platform issuance (per-SKU)Audit-dominant + per-staff issuancePMS / app + per-stay issuanceInstitution app + per-staff + retention
Self-install softwareHotel PC software + optional centralized databaseProperty-manager app + multi-role adminTenant app + role hierarchyStandalone app or store-auditApp-platform per-SKUStandalone or centralized auditPMS or standaloneInstitution app + retention package
Configuration stringPer-tier credential + per-tier finish + per-tier brandingPer-tier credential + per-tier finish + per-tier brandingPer-tier credential + per-tier finish + per-tier brandingPer-tier credential + per-tier finish + per-tier brandingPer-tier clamp + per-tier finish preservation + per-tier brandingPer-tier credential + per-tier finish + per-tier brandingPer-tier credential + per-tier finish + per-tier brandingPer-tier credential + per-tier finish + per-tier branding
Lifecycle / day-2Spare parts + firmware + encoder day-2 + software day-2 + per-guest consumableSpare parts + firmware + app day-2 + per-resident day-2Spare parts + firmware + tenant app day-2Spare parts + firmware + store app day-2Spare parts + firmware + app day-2Spare parts + firmware + audit day-2Spare parts + firmware + PMS day-2 + per-stay day-2Spare parts + firmware + institution app day-2 + retention day-2

The application-tier column is the column the buyer uses in Pillar 3 to size the RFQ scope; the application-tier per-line numeric is the column the buyer uses in Pillar 5 to write the per-line sign-off.

2.3 What the cost-stack pillar does not say

The pillar does not assert that any application class carries a higher or lower headline figure than any other on any per-SKU basis. It does not assign a price tier to any application class. It does not predict an MOQ floor or a lead-time window on any application class. The application-class composition is the buyer's read of the cost-stack lines; the per-line figure is the supplier's read of the SKU and routes to the dated product page.


Pillar 3 — Application-specific RFQ scope drivers

The third pillar answers: which application-specific RFQ scope drivers the buyer has to surface before the supplier can quote honestly? RFQ scope drivers are the variables that move the per-line figure from a default assumption to a buyer-written specification. The buyer who omits them receives a quotation the factory had to guess at, and that guess is the single most expensive guess in the lifecycle — because every pillar downstream reads from it.

3.1 The eleven RFQ scope drivers every application class carries

Every application class carries eleven RFQ scope drivers the buyer has to write into the RFQ before the supplier can quote honestly. The drivers are:

  1. Door class. Single-leaf or double-leaf; mortise or cylindrical or clamp; aluminum or wood or steel or glass; intended swing direction; existing or absent strike pocket; fire-rating posture inherited from the local AHJ.
  2. Door survey numbers. Door thickness envelope, glass thickness envelope (glass-door class), frame material, frame profile, gap dimensions, intended swing direction.
  3. Credential sub-population. Resident / guest / staff / visitor / vendor / maintenance; per-tier turnover cadence; per-tier credential sub-population mix.
  4. Credential stack. Fingerprint / RFID / PIN / Bluetooth / Wi-Fi / mechanical key / combination; per-tier credential mix the application class triggers.
  5. Mechanical-override posture. Mechanical emergency access (hotel-yardstick), per-suite mechanical (office), per-store mechanical (retail), per-tenant mechanical (institutional), per-stay mechanical (vacation-rental), per-property mechanical fallback (apartment).
  6. Audit-trail expectation. Per-incident pull (apartment, retail), per-stay pull (hotel, vacation-rental), per-day pull (office), continuous audit (industrial), per-retention-cycle pull (institutional).
  7. Network and admin posture. Standalone / property-manager app / hotel PC software + optional centralized database / tenant app / store app / PMS / institution app.
  8. Integration surface. PMS (hotel, vacation-rental), building intercom (apartment), tenant-app role hierarchy (office), store-audit (retail), record-retention package (institutional), audit-dominant retention package (industrial).
  9. Configuration string. Per-tier credential methods + per-tier audit depth + per-tier mechanical-override cylinder profile + per-finish option + per-platform binding (TTLock / Tuya / Doodle / hotel PC software — confirm per-SKU) + per-tier branding + per-tier firmware revision.
  10. Lifecycle posture. Spare parts ordering + replacement cycle + firmware upgrade cadence + audit-event buffer reset + credential re-issuance cadence + encoder commissioning day-2 + software seat day-2 + day-2 installer labor.
  11. Branding and packaging. Logo placement + packaging artwork + user manual artwork + product photography + catalog artwork + per-tier artwork surface + per-tier packaging development.

The buyer who writes all eleven drivers crisply into the RFQ gets a one-round quotation. The buyer who leaves them blank gets a quotation the factory had to assume at, and that default is the single most expensive assumption in the lifecycle.

3.2 RFQ scope driver read by application class

The matrix below is the working surface for the RFQ scope pillar. The buyer reads one row per driver and one column per application class. Every cell is the application-class-specific reading the buyer has to write into the RFQ. Every per-SKU numeric is Check the model’s published specification.

| RFQ scope driver | AC-01 Hotel | AC-02 Apartment | AC-03 Office | AC-04 Retail | AC-05 Glass-door | AC-06 Industrial | AC-07 Vacation-rental | AC-08 Institutional || --- | --- | --- | --- | --- | --- | --- | --- || Door class | Mortise hotel door + AHJ fire-rating posture | Mortise unit / cylindrical common / cylindrical staff | Mortise suite / cylindrical common | Mortise storefront / cylindrical stockroom | Clamp glass single / clamp double | Mortise heavy-duty + cylindrical restricted | Mortise guest / cylindrical staff | Mortise institutional + cylindrical restricted || Door survey | Per-SKU door thickness envelope (yardstick 36–100 mm) | Per-SKU door thickness envelope | Per-SKU door thickness envelope | Per-SKU door thickness envelope | Per-SKU glass thickness + gap envelope | Per-SKU door thickness envelope | Per-SKU door thickness envelope | Per-SKU door thickness envelope || Credential sub-population | Guest (per-stay) + staff + housekeeping + maintenance | Resident + staff + visitor + vendor | Staff + visitor + after-hours | Staff + delivery + cleaning | Tenant / staff / visitor per storefront or partition | Maintenance + operations + restricted | Guest (per-stay) + housekeeping + maintenance | Student / patient / staff + restricted || Credential stack | RFID + PIN + mechanical (yardstick); fingerprint optional per-SKU | Per-SKU credential mix + per-tier fallback | Per-SKU credential mix + per-tenant fallback | Per-SKU credential mix + per-store fallback | Per-SKU credential mix + glass-clamp constraint | Per-SKU credential mix + audit-dominant posture | Per-SKU credential mix + per-stay fallback | Per-SKU credential mix + institution retention posture || Mechanical override | Mechanical emergency access + front-desk master key (yardstick) | Per-unit mechanical + management custody | Per-suite mechanical + master-key archive | Per-store mechanical + master-key archive | Per-glass mechanical + master-key archive | Per-restricted mechanical + restricted archive | Per-stay mechanical + front-desk handoff | Per-institution mechanical + institution archive || Audit-trail expectation | Up to 1,000 events (yardstick) + per-stay pull | Per-SKU depth + per-incident pull | Per-SKU depth + per-tenant pull | Per-SKU depth + per-incident pull | Per-SKU depth + per-incident pull | Per-SKU depth + continuous audit | Per-SKU depth + per-stay pull | Per-SKU depth + retention-rule-shaped pull || Network + admin | Hotel PC software + optional centralized database | Property-manager app + multi-role admin | Tenant app + role hierarchy | Standalone app or store-audit | App-platform per-SKU | Standalone or centralized audit | PMS or standalone | Institution app + retention package || Integration | PMS + hotel software + encoder commissioning | Building intercom + optional PMS | Tenant-app role hierarchy + audit buffer | Store-audit + per-shift log | App-platform per-SKU + storefront integration | Audit-dominant + retention package | PMS + per-stay workflow + maintenance | Institution app + record-retention + role hierarchy || Configuration string | Per-tier credential + per-tier finish + per-tier branding | Per-tier credential + per-tier finish + per-tier branding | Per-tier credential + per-tier finish + per-tier branding | Per-tier credential + per-tier finish + per-tier branding | Per-tier clamp + per-tier finish preservation + per-tier branding | Per-tier credential + per-tier finish + per-tier branding | Per-tier credential + per-tier finish + per-tier branding | Per-tier credential + per-tier finish + per-tier branding || Lifecycle posture | Spare parts + firmware + encoder day-2 + software day-2 + per-guest consumable | Spare parts + firmware + app day-2 + per-resident day-2 | Spare parts + firmware + tenant app day-2 | Spare parts + firmware + store app day-2 | Spare parts + firmware + app day-2 | Spare parts + firmware + audit day-2 | Spare parts + firmware + PMS day-2 + per-stay day-2 | Spare parts + firmware + institution app day-2 + retention day-2 || Branding + packaging | Per-tier logo + per-tier packaging + per-tier manual + per-tier catalog | Per-tier logo + per-tier packaging + per-tier manual + per-tier catalog | Per-tier logo + per-tier packaging + per-tier manual + per-tier catalog | Per-tier logo + per-tier packaging + per-tier manual + per-tier catalog | Per-tier logo + per-tier packaging + per-tier manual + per-tier catalog | Per-tier logo + per-tier packaging + per-tier manual + per-tier catalog | Per-tier logo + per-tier packaging + per-tier manual + per-tier catalog | Per-tier logo + per-tier packaging + per-tier manual + per-tier catalog |

The application-class column is the column the buyer uses in Pillar 4 to size the per-tier lifecycle posture; the application-class driver-by-driver reading is the column the buyer uses in Pillar 5 to write the cross-application sign-off.

3.3 What the RFQ scope pillar does not say

The pillar does not assert that any application class is easier or harder to specify on any per-SKU basis. It does not promote a particular driver above another across application classes. It does not predict a per-driver figure in any currency, in any tier, in any MOQ floor or in any lead-time window on any particular SKU. The application-class driver profile is the buyer's read of the RFQ scope; the per-driver numeric is the supplier's read of the SKU and routes to the dated product page.


Pillar 4 — Per-application lifecycle cost posture

The fourth pillar answers: what is the per-application lifecycle cost posture the factory assembles once the application class is fixed, and which day-2 lines move with which application class? Application-class lifecycle posture is unforgiving in its own way. The hotel-class day-2 line carries encoder commissioning, hotel PC software seat day-2, per-guest card consumable and firmware upgrade across a multi-property group; the apartment-class day-2 line carries property-manager app day-2 and per-resident credential re-issuance across a multi-year stay; the office-class day-2 line carries tenant-app day-2 and role-hierarchy commissioning day-2; the retail-class day-2 line carries store-app day-2 and per-shift log rotation; the glass-door-class day-2 line carries app-platform day-2 and storefront integration day-2; the industrial-class day-2 line carries audit-dominant retention day-2; the vacation-rental-class day-2 line carries PMS day-2 and per-stay workflow day-2; the institutional-class day-2 line carries institution-app day-2 and retention-package day-2. The buyer must read the per-tier lifecycle posture against the application class before any SKU is allocated.

4.1 The eight lifecycle posture dimensions every application class carries

Every application class carries eight lifecycle posture dimensions the buyer has to write into the RFQ before the supplier can quote honestly. The dimensions are:

  1. Spare parts ordering. Per-tier spare parts ordering cadence, per-tier spare parts inventory posture, per-tier replacement cycle.
  2. Replacement cycle. Per-tier lock-body replacement cycle, per-tier mechanical-override cylinder replacement cycle, per-tier finish replacement cycle.
  3. Firmware upgrade. Per-tier firmware revision cadence, per-tier firmware upgrade posture, per-tier firmware compatibility posture.
  4. Audit-event buffer reset. Per-tier audit-event buffer reset cadence, per-tier audit-event retention policy, per-tier audit-event log-rotation behavior.
  5. Credential re-issuance. Per-tier credential re-issuance cadence, per-tier credential lifespan, per-tier credential revocation cadence.
  6. Encoder commissioning day-2. Per-tier encoder commissioning day-2 cadence (hotel class triggers this), per-tier software seat day-2 cadence (hotel, office, apartment, institutional), per-tier PMS day-2 cadence (hotel, vacation-rental), per-tier tenant-app day-2 cadence (office), per-tier store-app day-2 cadence (retail), per-tier institution-app day-2 cadence (institutional).
  7. Day-2 installer labor. Per-tier day-2 installer labor envelope, per-tier audit-event buffer reset labor, per-tier credential re-issuance labor, per-tier firmware upgrade labor.

4.2 Lifecycle posture read by application class

The table below is the working surface for the lifecycle pillar. The buyer reads one column per application class. Every cell is the application-class-specific lifecycle dimension. Every per-SKU numeric is Check the model’s published specification.

Lifecycle dimensionAC-01 HotelAC-02 ApartmentAC-03 OfficeAC-04 RetailAC-05 Glass-doorAC-06 IndustrialAC-07 Vacation-rentalAC-08 Institutional
Spare parts orderingPer-tier cadence + per-property inventoryPer-tier cadence + building inventoryPer-tier cadence + tenant inventoryPer-tier cadence + store inventoryPer-tier cadence + storefront inventoryPer-tier cadence + restricted inventoryPer-tier cadence + property inventoryPer-tier cadence + institution inventory
Replacement cyclePer-tier lock body + per-tier cylinder + per-tier finishPer-tier lock body + per-tier cylinder + per-tier finishPer-tier lock body + per-tier cylinder + per-tier finishPer-tier lock body + per-tier cylinder + per-tier finishPer-tier lock body + per-tier clamp + per-tier finishPer-tier lock body + per-tier cylinder + per-tier finishPer-tier lock body + per-tier cylinder + per-tier finishPer-tier lock body + per-tier cylinder + per-tier finish
Firmware upgradePer-tier revision + per-tier posturePer-tier revision + per-tier posturePer-tier revision + per-tier posturePer-tier revision + per-tier posturePer-tier revision + per-tier posturePer-tier revision + per-tier posturePer-tier revision + per-tier posturePer-tier revision + per-tier posture
Audit buffer resetPer-stay reset + retention policy (yardstick up to 1,000)Per-incident reset + retention policyPer-tenant reset + retention policyPer-incident reset + retention policyPer-incident reset + retention policyContinuous audit + retention-rule-shapedPer-stay reset + retention policyPer-retention-cycle reset + institution rule
Credential re-issuancePer-stay issuance + housekeeping + maintenancePer-stay / per-multi-year + staff + vendorPer-staff + per-tenant + per-after-hoursPer-shift + per-deliveryPer-tenant / per-staff + visitorPer-staff + per-restricted + per-maintenancePer-stay + housekeeping + maintenancePer-staff + per-student / per-patient + restricted
Encoder + software day-2Encoder commissioning day-2 + hotel PC software seat day-2 + per-guest consumableProperty-manager app day-2 + per-resident day-2Tenant app day-2 + role hierarchy commissioningStore app day-2 + per-shift log rotationApp-platform day-2 + storefront integration day-2Audit-dominant retention day-2PMS day-2 + per-stay workflow day-2Institution app day-2 + retention package day-2
Day-2 installer laborPer-tier labor envelopePer-tier labor envelopePer-tier labor envelopePer-tier labor envelopePer-tier labor envelopePer-tier labor envelopePer-tier labor envelopePer-tier labor envelope
Per-SKU documentation flag————————

Cells marked — have no documented value in this article’s sources; obtain the figure from the supplier’s written specification.

The application-class column is the column the buyer uses in Pillar 5 to size the cross-application sign-off; the application-class lifecycle dimension is the column the buyer uses in Pillar 5 to write the per-class procurement schedule.

4.3 What the lifecycle posture pillar does not say

The pillar does not assert that any application class carries a higher or lower day-2 line than any other on any per-SKU basis. It does not assign a lifecycle tier to any application class. It does not predict a per-class spare parts ordering cadence or a per-class firmware upgrade cadence on any particular SKU. The application-class lifecycle posture is the buyer's read of the day-2 lines; the per-line figure is the supplier's read of the SKU and routes to the dated product page.


Pillar 5 — Cross-application consolidation and procurement sign-off

The fifth pillar answers: how does the buyer consolidate the four prior pillars into a cross-application RFQ and a procurement sign-off block, and what does the factory's quotation look like when the application-class profile is complete? Cross-application consolidation is unforgiving. The buyer who has not consolidated the four prior pillars into a single RFQ receives a quotation the factory had to assemble across multiple defaults, and that default-composition is the single most expensive composition in the lifecycle — because every per-line gate the supplier had to assume is a per-line gate the buyer will pay for at revision.

5.1 The cross-application consolidation rules

The buyer consolidates the four prior pillars into a single RFQ by writing the application-class profile, the cost-stack profile, the RFQ scope profile and the lifecycle posture profile into a single document the supplier can read against. The consolidation rules are:

  • Rule A — Application class first. The RFQ names the application class on every line that depends on it. The supplier reads the application class before reading any cost-stack line, any RFQ scope driver, or any lifecycle dimension.
  • Rule B — Cost-stack profile per class. The RFQ carries one cost-stack profile per application class. The supplier reads the cost-stack profile before reading any RFQ scope driver or any lifecycle dimension.
  • Rule C — RFQ scope per class. The RFQ carries eleven RFQ scope drivers per application class. The supplier reads the RFQ scope before reading any lifecycle dimension.
  • Rule D — Lifecycle posture per class. The RFQ carries eight lifecycle posture dimensions per application class. The supplier reads the lifecycle posture before assembling the day-2 line.
  • Rule E — Per-line documentation flag. The RFQ carries a per-line documentation flag for every per-SKU numeric. The supplier reads the flag before quoting; the buyer reads the flag before signing the procurement schedule.
  • Rule F — Cross-application overlap. The RFQ names any cross-application overlap the buyer has consolidated (one supplier ordering two across an apartment-class and an institutional class within one block, one supplier ordering three across a hotel-class, an office-class and a glass-door class within one property). The supplier reads the overlap before assembling the cross-class line.

5.2 Cross-application sign-off block

The buyer writes a sign-off block that captures the application-class profile, the cost-stack profile, the RFQ scope profile and the lifecycle posture profile into a single block the supplier can read against. The block has five sections:

  1. Application-class section. One row per application class under consideration. Carries the operating-system shape, the credential sub-population, the audit-trail expectation, the override posture, the integration surface, and the per-SKU documentation flag.
  2. Cost-stack section. Nine cost-stack lines per application class. Carries the mechanical / structural line, the electronic-module line, the motor + gearbox + clutch line, the power-format line, the audit / event-record line, the credential-issuance line, the integration line, the configuration-string line, and the lifecycle / day-2 line.
  3. RFQ scope section. Eleven RFQ scope drivers per application class. Carries the door class, the door survey, the credential sub-population, the credential stack, the mechanical-override posture, the audit-trail expectation, the network and admin posture, the integration surface, the configuration string, the lifecycle posture, and the branding and packaging.
  4. Lifecycle section. Eight lifecycle posture dimensions per application class. Carries the spare parts ordering, the replacement cycle, the firmware upgrade, the audit-event buffer reset, the credential re-issuance, the encoder + software day-2, the day-2 installer labor, and the per-SKU documentation flag.
  5. Cross-application section. Cross-application overlap the buyer has consolidated. Names the supplier, the supplier role, the cross-application line, and the cross-class line.

5.3 Per-line sign-off table

The table below is the working surface for the cross-application sign-off pillar. The buyer reads one row per application class and one column per section. Every cell is the application-class-specific reading the buyer has to write into the sign-off block. Every per-SKU numeric is Check the model’s published specification.

App-class IDApplication-class sectionCost-stack sectionRFQ scope sectionLifecycle sectionCross-application sectionPer-SKU confirm-on-product-page flag
AC-01 Hotel and serviced-apartment4-component OS + guest/staff/HK/maintenance + per-stay pull + mechanical emergency + hotel PC software (per-SKU)9 lines per-SKU11 drivers per-SKU8 dimensions per-SKUCross-class with AC-02 / AC-03 / AC-05 if applicablecheck the model’s published specification (per-SKU)
AC-02 Apartment / multi-family3-zone stack + resident/staff/visitor/vendor + per-incident pull + management custody + property-manager app (per-SKU)9 lines per-SKU11 drivers per-SKU8 dimensions per-SKUCross-class with AC-01 / AC-08 if applicablecheck the model’s published specification (per-SKU)
AC-03 Office / commercialTenant network + staff/visitor/after-hours + per-tenant pull + per-suite mechanical + tenant app (per-SKU)9 lines per-SKU11 drivers per-SKU8 dimensions per-SKUCross-class with AC-01 / AC-05 / AC-06 if applicablecheck the model’s published specification (per-SKU)
AC-04 Retail / storefrontSingle-shift + delivery + per-incident pull + per-store mechanical + standalone or store-audit (per-SKU)9 lines per-SKU11 drivers per-SKU8 dimensions per-SKUCross-class with AC-05 if applicablecheck the model’s published specification (per-SKU)
AC-05 Glass-door storefront / partitionClamp body + tenant/staff/visitor + per-incident pull + per-glass mechanical + app-platform (per-SKU)9 lines per-SKU11 drivers per-SKU8 dimensions per-SKUCross-class with AC-03 / AC-04 / AC-07 if applicablecheck the model’s published specification (per-SKU)
AC-06 Industrial / staff-onlyMaintenance / restricted + operations + continuous audit + per-restricted mechanical + audit-dominant (per-SKU)9 lines per-SKU11 drivers per-SKU8 dimensions per-SKUCross-class with AC-03 if applicablecheck the model’s published specification (per-SKU)
AC-07 Vacation rental / short-stayPer-stay guest + per-stay pull + per-stay mechanical + PMS or standalone (per-SKU)9 lines per-SKU11 drivers per-SKU8 dimensions per-SKUCross-class with AC-05 if applicablecheck the model’s published specification (per-SKU)
AC-08 Institutional (school / clinic / dorm / gov / bank)Institution + retention-rule-shaped + per-retention-cycle pull + per-institution mechanical + institution app (per-SKU)9 lines per-SKU11 drivers per-SKU8 dimensions per-SKUCross-class with AC-02 if applicablecheck the model’s published specification (per-SKU)

The cross-application column is the column the buyer uses to consolidate the cross-class line; the per-SKU documentation flag is the column the supplier reads before assembling the cross-class line.

5.4 A realistic project scenario — illustrative, not a customer story

Consider a 240-unit mixed-use property under one ownership, with three application classes the buyer has to consolidate into a single RFQ: 48 boutique-hotel keys on floors 3–5 (AC-01 hotel-class with a staffed front desk and hotel PC software + optional centralized database), 120 multi-family apartment units on floors 6–12 (AC-02 apartment-class with a three-zone procurement stack and property-manager app + multi-role admin), and 24 serviced-apartments on floors 13–14 run hotel-class (AC-07 vacation-rental-class with PMS and per-stay workflow). The property also has 8 retail storefront glass entries on the ground floor (AC-05 glass-door class with clamp-mounted body and storefront integration) and 12 office suite common doors on floor 2 (AC-03 office-class with tenant app and role hierarchy). The application-class profile the buyer has to write into the RFQ names every one of those five classes, the cost-stack profile carries nine cost-stack lines per class, the RFQ scope profile carries eleven RFQ scope drivers per class, and the lifecycle profile carries eight lifecycle posture dimensions per class — five classes × nine cost-stack lines × eleven RFQ scope drivers × eight lifecycle posture dimensions × one per-SKU documentation flag per line, all consolidated into a single RFQ the supplier reads before any line is quoted. The cross-application overlap section names the supplier (one factory supplying across all five classes), the supplier role (OEM/ODM factory, 79-model catalog, 10+ years, sold into 80+ countries, quote-based commerce — confirm per the catalog spec), and the cross-class line the buyer has consolidated (one supplier across the boutique-hotel keys, the multi-family apartments, the serviced-apartments, the ground-floor retail storefronts and the second-floor office suites). Every per-SKU numeric the buyer needs routes to the dated product page; no headline figure is asserted in this scenario. The scenario is illustrative — every name fictitious, every count illustrative, every per-SKU figure routed to the dated product pages.

5.5 What the cross-application sign-off pillar does not say

The pillar does not assert that any cross-application consolidation produces a higher or lower headline figure than any other on any per-SKU basis. It does not assign a cross-application tier to any application class. It does not predict a per-class consolidation figure in any currency, in any tier, in any MOQ floor or in any lead-time window on any particular SKU. The cross-application sign-off block is the buyer's read of the cross-class profile; the per-line figure is the supplier's read of the SKU and routes to the dated product page.


What the five-pillar framework deliberately does not cover

The framework does not cover the per-SKU price tier, the per-SKU MOQ floor, the per-SKU lead-time window, the per-SKU warranty year, the per-SKU certification claim, the per-SKU finish list, the per-SKU environmental envelope, the per-SKU firmware revision, the per-SKU mobile-app platform binding (TTLock / Tuya / Doodle / hotel PC software — confirm per-SKU), the per-SKU sample cost, the per-SKU artwork cost, the per-SKU freight slot, the per-SKU duty rate, the per-SKU encoder commissioning day-2 cost, the per-SKU software seat day-2 cost, the per-SKU PMS integration cost, the per-SKU per-guest card consumable, the per-SKU per-resident credential re-issuance cost, the per-SKU per-staff credential re-issuance cost, the per-SKU spare parts ordering cost, the per-SKU firmware upgrade cost, the per-SKU audit-event buffer reset cost, the per-SKU day-2 installer labor cost, the per-SKU brand-wrap cost, the per-SKU packaging artwork cost, the per-SKU user-manual artwork cost, the per-SKU product-photography cost, the per-SKU catalog artwork cost, the per-SKU hotel-class client logo, the per-SKU apartment-class client logo, the per-SKU office-class client logo, the per-SKU retail-class client logo, the per-SKU glass-door-class client logo, the per-SKU industrial-class client logo, the per-SKU vacation-rental-class client logo, the per-SKU institutional-class client logo, the per-SKU factory-floor stats, the per-SKU certification claim of any kind (CE / FCC / UL / EN / IEC / BHMA / ANSI / SKG / VdS / ISO / IP-rating / fire-rating / ADA — NONE asserted anywhere), the per-SKU out-of-catalog capability (no palm-vein / Matter / Zigbee / Z-Wave / Thread / Apple Home Key / UWB / vein-recognition / Wi-Fi-as-catalog-radio / proprietary-radio asserted as catalog capability anywhere). Every per-SKU numeric the buyer needs is verified in writing or routes to "check the model’s published specification". The framework operates at application-tier level only.

Closing — the application-tier procurement sign-off block

The application-tier price is not a single number on a quotation line. It is the output of a five-pillar decision pipeline that takes the application class as the input, reads the per-application cost-stack structure, surfaces the application-specific RFQ scope drivers, sizes the per-application lifecycle posture, and consolidates the cross-application sign-off block the supplier reads before any figure reaches the inbox. The same lock body, quoted across two application classes, lands on two different quotation lines because the cost stack is application-shaped, not lock-shaped. The buyer who treats the application class as the input and the per-application cost-stack lines, the per-application RFQ scope drivers and the per-application lifecycle posture as the working surface leaves every RFQ review knowing which application class the quotation is reading against, which cost-stack line produced each per-line figure, which RFQ scope driver the supplier had to assume at, which lifecycle dimension the supplier had to default at, and how the buyer's own application-class profile moves the headline figure up or down before it ever reaches the inbox.

For the application-class sign-off the buyer pastes into the supplier conversation, the cross-application consolidation that brings five application classes into one RFQ, and the per-line documentation flag that anchors the sign-off block, the primary CTA is Request a quote. The secondary CTA is Order samples for the buyer who wants the per-application cost-stack envelope read against a per-tier sample before any application-class figure is committed. For the catalog PDF the buyer references at the application-class read, the supporting CTA is Request the catalog. The framework closes here. Every per-SKU figure routes to the dated product page; every commercial term routes to Request a quote; every per-application sign-off block the buyer pastes into the supplier conversation carries the application-class profile, the cost-stack profile, the RFQ scope profile, the lifecycle posture profile and the cross-application consolidation the five pillars produce.

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