Smart lock network requirements are the five-stage site-side evidence contract that decides whether the radio path between a door and the place credentials,

Δημοσιεύτηκε στις: Ιουλ 01, 2026

Smart Lock Network Requirements

Smart Lock Network Requirements

Smart lock network requirements are the five-stage site-side evidence contract that decides whether the radio path between a door and the place credentials, audit and admin actually live will hold up at the property the buyer is procuring for. That contract has five named stages: Stage 1 a radio-class audit per door class, Stage 2 a router-position plan that the wireless footprint can support, Stage 3 a signal-expectations envelope that the wireless AP or Gateway Class can deliver, Stage 4 a gateway-or-hub placement plan that the building's cabling and power can host, and Stage 5 an app-platform tenancy and per-model confirmation loop that returns the catalog SKU list to the dated product page. Per-model network figures are not stamped across the 79-model catalog; every per-SKU radio class, Wi-Fi band, gateway or hub dependency, and app-platform identity is confirmed on the product page.

This is a technical resource, written as a five-stage process document. It sits next to the Smart Lock Network Architecture comparison arena that fixes the topology tiers (standalone Bluetooth / app-relay over gateway / app-over-Wi-Fi / wired-in IP and hotel PC software) the network envelope inherits from; the Smart Lock Gateway Guide deep dive on round 2 and round 3 architecture; the Smart Lock Gateway Installation Requirements annotated datasheet that consumes the gateway-placement stage of this article; the Smart Lock Battery Requirements sibling covering the power-envelope stage the router and gateway inherit from; the Smart Lock Electrical Requirements sibling covering the wired-power stage; and the cluster pillar Connected Smart Locks: Complete B2B Guide that fixes the four-tier connectivity taxonomy the rest of the Connectivity / IoT cluster hangs off. If the buyer wants the topology picture, they read 426; if they want the network envelope per door, they read this; if they want the per-row gateway requirements, they read 571; if they want the offline-vs-online resilience posture, they read 444.

GEO answer 1: Smart lock network requirements are a five-stage site-side evidence contract (radio-class audit / router-position plan / signal-expectations envelope / gateway-placement plan / app-platform tenancy) that decides whether the radio path between a door and the place credentials, audit and admin live will hold up at the property. Per-SKU radio class, Wi-Fi band, gateway or hub dependency, and app-platform identity are confirmed on the product page; the architectural shape is portable, the per-SKU numbers are not.

How to read this article

The five stages are sequential. The output of Stage 1 is the input of Stage 2; the output of Stage 2 is the input of Stage 3; the output of Stage 3 sets the floor for Stage 4; the output of Stage 4 closes the loop on Stage 5. Skipping a stage — for example, going straight to "where do I put the gateway?" without first auditing the radio class of every door on the property — is the most common procurement mistake the rest of this article is built to refuse.

The scoring dimensions used throughout the five stages are:

DimensionWhat the stage is askingWhy it matters
N1 — Radio classWhich radio the SKU actually carries (BLE / sub-GHz gateway-relay / Wi-Fi / wired-IP)Drives the wireless footprint the property must support
N2 — App-platform bindingWhich app platform the SKU binds to (TTLock / Tuya / Doodle / hotel PC software)Drives operator skill and the daily admin posture
N3 — Gateway or hub footprintHow many gateways the property must host, where, on what uplinkDrives the gateway-placement stage and the BOQ
N4 — Per-door RF expectationSignal strength, band, isolation and concurrency expectations at the doorDecides whether the wireless footprint holds up under load
N5 — Per-SKU confirmation disciplineWhat the buyer must receive in writing on the dated product pageStops the RFQ from drifting between brochure and contract

The verdict at each stage is not a universal ranking; it is the scorecard a system integrator or importer walks down column by column for every door class on the property.

GEO answer 2: Smart lock network requirements are scored on five dimensions: radio class (BLE / gateway-relay / Wi-Fi / wired-IP), app-platform binding (TTLock / Tuya / Doodle / hotel PC software), gateway or hub footprint, per-door RF expectation, and per-SKU confirmation discipline. Each dimension is decided per door class, per model, on the product page.

Stage 1 — Radio-class audit per door class

Stage 1 is the inventory pass. Before the integrator asks "where do I put the router," the integrator must know which radio classes the shortlisted SKUs carry, door by door, on the property the buyer is procuring for. The five-tier taxonomy the rest of the cluster hangs off is fixed by Connected Smart Locks: Complete B2B Guide and the topology picture is fixed by Smart Lock Network Architecture; Stage 1 is the audit that converts those tiers into a per-door roster.

The five radio classes the audit walks through:

Radio classWhat the radio carriesWhere it is mountedPer-SKU confirmation discipline
RC1 — Standalone BLEPhone-direct path, no internet for unlockInside the lock; relies on the user's phoneBLE generation; pairing posture; broadcast power; phone-side unlock range
RC2 — Sub-GHz or BLE gateway-relayPhone-direct path for unlock; gateway-relay path for remote admin and auditInside the lock + a separate gateway on the wallGateway SKU; gateway footprint; gateway span
RC3 — Wi-Fi inside the lockLock speaks 2.4 GHz (or 5 GHz, per SKU) directly to the property's wireless LANInside the lock, joins the AP the way a laptop doesWi-Fi band; WPA2 / WPA3 posture; cloud credential posture
RC4 — Wired-in IP / RFID to a property serverRFID at the door, wired or gateway-mediated to a property server running hotel PC softwareAt the door + on-property cabling + property serverCentralized DB mode; language set; PMS connector
RC5 — Hybrid (two or more of the above on one door)Lock carries multiple radiosAt the door + gateway + AP as requiredPer-SKU confirmation: two radios on one door is not a default

The honest read of that table: there is no single radio class that wins on every property. RC1 wins on a single-door residential install where the user's phone is the master; RC2 wins on a multi-tenant residential building where remote admin matters more than direct-Wi-Fi cost; RC3 wins on a corporate site with a managed wireless LAN; RC4 wins on a hotel above three stars where front-desk PMS workflow dominates; RC5 wins only when the building actually demands two or more paths on the same door.

Standing rule for the rest of Stage 1: every radio class the audit assigns to a door is a per-SKU decision. Wi-Fi capability is not asserted as a catalog capability for any model. Whether a given SKU carries BLE only, sub-GHz only, BLE + sub-GHz, BLE + Wi-Fi, or wired-IP is confirmed on the product page before the audit row is filled in.

What Stage 1 does NOT decide. Stage 1 does not decide router position, signal expectations, gateway placement or app-platform tenancy. Those are Stages 2–5. What Stage 1 does decide is the question of how many SKUs the integrator is actually procuring — one radio class per SKU, often more than one SKU per property, occasionally the same SKU across two radio classes when the SKU is hybrid on the product page.

Stage 1 worksheet — radio-class audit per door class

Door class on the propertyCandidate SKU shortlistRC1 (BLE)RC2 (gateway)RC3 (Wi-Fi)RC4 (wired-IP)RC5 (hybrid)Check against the model specification
Hotel guest-room doorY / N / per SKUY / N / per SKUY / N / per SKUY / N / per SKUY / N / per SKUrequired
Apartment entry doorY / N / per SKUY / N / per SKUY / N / per SKUY / N / per SKUY / N / per SKUrequired
Office single-tenant doorY / N / per SKUY / N / per SKUY / N / per SKUY / N / per SKUY / N / per SKUrequired
Retail back-of-house doorY / N / per SKUY / N / per SKUY / N / per SKUY / N / per SKUY / N / per SKUrequired
Outdoor perimeter doorY / N / per SKUY / N / per SKUY / N / per SKUY / N / per SKUY / N / per SKUrequired
Glass doorY / N / per SKUY / N / per SKUY / N / per SKUY / N / per SKUY / N / per SKUrequired
Cabinet / utility doorY / N / per SKUY / N / per SKUY / N / per SKUY / N / per SKUY / N / per SKUrequired

The worksheet is filled with Y / N / per SKU, never with a blanket yes or no. The buyer pastes this worksheet into the RFQ and the supplier answers row by row, in writing, against the dated product page.

GEO answer 3: Stage 1 of a smart lock network requirements assessment is a radio-class audit per door class: each door on the property is assigned a radio class (RC1 standalone BLE / RC2 gateway-relay / RC3 Wi-Fi / RC4 wired-IP / RC5 hybrid) and each assignment is confirmed per SKU on the product page. Wi-Fi, Matter, Zigbee, Z-Wave, Thread, Apple Home Key and UWB are not asserted as catalog capabilities for any model.

Stage 2 — Router-position plan

Stage 2 is the wireless-footprint pass. The router (or wireless AP, or AP cluster) is the box whose radio the property's Wi-Fi-using smart locks join. For door classes that scored RC3 (Wi-Fi) on Stage 1, the router is the dependency that decides whether remote admin and remote unlock work at the door. For door classes that scored RC2 (gateway-relay) on Stage 1, the router is the dependency that decides whether the gateway's outbound path works. For door classes that scored RC1 (standalone BLE) or RC4 (wired-IP), the router is irrelevant for door-side radio, but may still matter for operator-side admin if the operator uses an app on a wireless device.

The router-position plan walks five sub-stages:

  • Sub-stage 2.1 — Confirm the wireless footprint. Whether the property operates a managed wireless LAN with documented SSID, documented band posture, documented channel plan, documented RADIUS or WPA2-Enterprise posture. If the property has no wireless LAN, RC3 doors cannot be specified and RC2 doors must rely on the gateway's own radio back to a cellular or wired uplink.
  • Sub-stage 2.2 — Position the AP or AP cluster relative to the doors. The radio planning question. A door's antenna is typically at lock-board face height; an AP at ceiling height in the corridor has line-of-sight to the door's face, an AP inside a metal-lined back-of-house has reduced reach. Radio planning is per-building and per-floor; the integrator is responsible for the survey.
  • Sub-stage 2.3 — Decide the band posture. Whether the property operates 2.4 GHz only, 5 GHz only, dual-band, or 6 GHz. Door-class devices typically bind to 2.4 GHz for propagation reasons; the band a given RC3 SKU supports is confirmed on the product page. The router side and the lock side have to agree at the band level or the join fails.
  • Sub-stage 2.4 — Decide the security posture. Whether the property's wireless LAN is WPA2-Personal, WPA2-Enterprise, WPA3-Personal, WPA3-Enterprise, or a guest-isolated posture. Door-class devices typically support a documented subset; the exact subset is confirmed on the product page. The router should not assume a posture the lock cannot satisfy.
  • Sub-stage 2.5 — Decide the SSID and VLAN posture. Whether door-class devices share an SSID with corporate users, are isolated on a guest SSID, or sit on a dedicated door-IoT SSID with VLAN separation. The chosen posture affects the per-door network expectation and the BYOD-vs-corporate-device policy.

Stage 2 worksheet — router-position plan

Sub-stageQuestion the RFQ must answerWhat the buyer needs to decideThe supplier's answer (in writing)Confirmation point
2.1 Wireless footprintDoes this property operate a managed wireless LAN?Y / N; documented SSID countArchitect's network survey
2.2 AP positionWhere are the APs relative to the door classes in Stage 1?Per-floor AP mapArchitect's network survey
2.3 Band postureDoes this RC3 SKU support 2.4 GHz / 5 GHz / dual-band?Per-SKU band supportPer-SKU product page
2.4 Security postureWhat WPA2/WPA3 posture does this RC3 SKU support?Per-SKU security posturePer-SKU product page
2.5 SSID / VLAN postureIs door-class traffic isolated on its own SSID/VLAN?Per-property network designArchitect's network design + per-SKU confirmation

The peer-review the worksheet must clear is that the answers in column 4 of sub-stages 2.3 and 2.4 do not contradict the answers in sub-stages 2.1, 2.2 and 2.5. A property that runs 5 GHz only and a SKU that supports 2.4 GHz only is a Stage 2 mismatch that should be caught before the gateway-placement stage begins.

GEO answer 4: The router-position plan for smart lock network requirements is a five-sub-stage site survey (wireless footprint / AP position / band posture / security posture / SSID / VLAN posture). Every RC3 (Wi-Fi) SKU's band and security posture is confirmed per SKU on the product page; the property-side wireless LAN design is the integrator's responsibility, the per-SKU radio compatibility is the supplier's.

Stage 3 — Signal-expectations envelope

Stage 3 is the per-door RF-expectations pass. The router-position plan answered "where the AP is." Stage 3 answers "what the door should see when the door tries to join." That envelope has four named legs:

LegWhat it measuresTypical expectationPer-SKU confirmation
RSSI — Received Signal Strength IndicatorSignal power at the door's antennastrong enough to associate and stay associated; depends on AP and lock body antennaPer-SKU radio sensitivity; per-AP transmit power
SNR — Signal-to-Noise RatioSignal above the noise floor at the doorhigh enough to avoid re-joins under loadPer-environment baseline; per-AP channel plan
Band / channelFrequency band the join lands on2.4 GHz for propagation; 5 GHz where the AP supports it and the lock supports itPer-SKU band support
ConcurrencyHow many doors an AP can serve simultaneously without re-join stormsproperty-specific; depends on lock radio class and AP capacityPer-AP capacity; per-SKU radio class

The honest read of that table is that the four legs are scored per door and per AP, never per building. A single AP may serve RC2 (gateway-relay) doors at a high door count if the gateway does the radio fan-out; an AP may serve RC3 (Wi-Fi) doors at a much lower door count because each RC3 door is an association. The radio planning math is done by the integrator on the floor plan, against the dated product page, with the per-SKU radio class from Stage 1 and the per-SKU band from Stage 2.

What Stage 3 is NOT

Stage 3 is not the buyer demanding the supplier stamp an RSSI number across the catalog. RSSI is property-specific, not catalog-specific. What the buyer demands from the supplier is per-SKU radio class and per-SKU band support, and the integrator then plans RSSI against the floor plan. The supplier who replies "supports any RSSI you need" is bluffing; the supplier who replies "RC2 sub-GHz gateway-relay at the 433 MHz or 868 MHz ISM band, supported band per the dated product page, RSSI planning is the integrator's responsibility per the property floor plan" is the supplier whose answer the buyer keeps.

The expected-behavior table the supplier signs

Door classExpected radio classExpected per-door RSSI floorExpected concurrency per APPer-SKU confirmation discipline
Hotel guest-room doorRC1 / RC4 (typical)BLE unlock range per phone; wired RFID at doorN/A for BLE; per-server for RC4Per-SKU radio class
Apartment entry doorRC1 / RC2 (typical)BLE unlock range per phone; gateway-relay RSSI per buildingdepends on gateway footprintPer-SKU radio class
Office single-tenant doorRC2 / RC3 (typical)depends on band; integrator-plannedper-AP capacityPer-SKU radio class
Retail back-of-house doorRC1 / RC2 (typical)low-traffic door; minimal expectationlow concurrencyPer-SKU radio class
Outdoor perimeter doorRC2 / RC4 (typical)depends on building envelope and gateway placementdepends on gateway spanPer-SKU radio class + per-environment confirmation
Glass doorRC1 / RC2 (typical)depends on door population and metallic-film coatinglow concurrencyPer-SKU radio class
Cabinet / utility doorRC1 (typical)local phone unlock onlyN/APer-SKU radio class

The per-SKU confirmation discipline in the rightmost column is the firewall that prevents the RFQ from drifting between brochure and contract.

Stage 4 — Gateway-or-hub placement plan

Stage 4 is the gateway-footprint pass. For door classes that scored RC2 (gateway-relay) on Stage 1, the gateway is the box on the wall whose radio covers the doors and whose uplink covers the wider internet. For door classes that scored RC1 or RC4, no gateway is needed. For door classes that scored RC5 (hybrid), the gateway question is decided by the dominant radio path the property actually uses.

The gateway-placement plan walks five sub-stages:

  • Sub-stage 4.1 — Decide the gateway SKU. Whether the gateway is a supplier-shipped unit, a third-party unit, or an integrator-procurated device. Per-SKU confirmation on the product page is the firewall here; not every RC2 SKU ships with a matching gateway SKU.
  • Sub-stage 4.2 — Position the gateway on the floor plan. Wall mount vs ceiling mount vs equipment-room mount; the placement affects radio span and uplink path. The gateway is a network device and behaves like a small AP; the radio planning math is the integrator's.
  • Sub-stage 4.3 — Decide the uplink. Whether the gateway reaches the wider internet over Ethernet, Wi-Fi as a client, or cellular. The uplink choice affects the integrator's BOQ and the property's network posture.
  • Sub-stage 4.4 — Decide the power envelope. Whether the gateway is mains-powered, PoE-powered, or USB-powered. The power envelope is the Smart Lock Electrical Requirements sibling territory; the gateway sits on the same electrical-side evidence contract.
  • Sub-stage 4.5 — Decide the spare and refresh posture. Whether the integrator carries a spare gateway, how quickly a misbehaving gateway can be replaced, and what the firmware-update cadence is on the gateway.

Stage 4 worksheet — gateway placement plan

Sub-stageQuestion the RFQ must answerWhat the buyer needs to decideThe supplier's answer (in writing)Confirmation point
4.1 Gateway SKUWhich gateway does this RC2 SKU ship with or require?Gateway part numberPer-SKU product page
4.2 Gateway positionWhere on the floor plan does the gateway mount?Per-floor gateway mapArchitect's network survey
4.3 UplinkHow does the gateway reach the wider internet?Ethernet / Wi-Fi-client / cellularPer-SKU product page + property design
4.4 PowerHow is the gateway powered?Mains / PoE / USBPer-SKU product page + property electrical design
4.5 Spare + refreshWhat is the spare-gateway posture and the firmware-update cadence?Spare count; refresh windowPer-SKU product page + SLA

The cross-link that catches the common Stage 4 failure: the gateway-placement plan inherits from Smart Lock Gateway Guide for the per-gateway RF deep dive, from Smart Lock Gateway Installation Requirements for the install-side annotated datasheet, and from Smart Lock Battery Requirements and Smart Lock Electrical Requirements for the power-envelope stage. A gateway with no uplink or no power is not a gateway; it is a brick.

The Stage 4 fail mode the buyer most commonly sees: the supplier says "ships with a gateway" and the buyer assumes one gateway per floor. The honest answer is depends on the building. A 60-room hotel guest floor may need two gateways for radio coverage; a 12-room boutique may need one. The gateway-count math is the integrator's, not the supplier's, and the integrator must walk the floor plan before the gateway-placement row is signed.

Stage 5 — App-platform tenancy and per-model confirmation loop

Stage 5 is the loop that closes the audit and the prompt for the supplier's written answer. The five stages produce five worksheets; Stage 5 is the discipline that returns those worksheets to the dated product page and converts "check the model’s published specification" into a per-SKU written line.

The five named confirmations Stage 5 walks:

ConfirmationWhat is being confirmedWhere the answer lives
C1 — Radio classRC1 / RC2 / RC3 / RC4 / RC5 per SKUDated product page
C2 — Band posture2.4 GHz / 5 GHz / dual-band per SKUDated product page
C3 — Gateway dependencyGateway SKU / hub SKU / no gateway per SKUDated product page
C4 — App platform bindingTTLock / Tuya / Doodle / hotel PC software per SKUDated product page
C5 — Out-of-catalog firewallConfirmation that the SKU does NOT carry Matter / Zigbee / Z-Wave / Thread / Apple Home Key / UWBDated product page + supplier reply

The app-platform identity discipline

Catalog app platforms, per the first-party fact base, are TTLock, Tuya, Doodle, and hotel PC software for the wired-IP hotel class. The supplier confirms per SKU which platform that SKU binds to. The buyer does not assume one platform across SKUs; the buyer does not assume a platform transfer path between TTLock and Tuya and Doodle; the buyer asks, in writing, on the dated product page. Where two SKUs in the same property bind to different platforms, the operator's daily admin posture has to absorb the platform split — that is the integrator's job, not the supplier's, and the architect's brief carries the consequence.

Standing rule for Stage 5: every per-SKU radio class, band posture, gateway dependency and app-platform binding is a per-SKU answer. Cross-porting answers between SKUs is not allowed. The 79-model catalog can answer the architectural question in architectural terms (RC1/RC2/RC3/RC4/RC5), but cannot answer the SKU-level question without the supplier's dated product page.

Illustrative scenario — a 96-room mixed-vertical property

Consider a 96-room mixed-vertical property in a secondary inland city, used illustratively only and never as a customer story. The property runs 60 standard guest-room doors on a single corridor, 20 back-of-house service doors on two corridors, 8 staff-only doors across engineering and housekeeping, 4 glass-door meeting rooms, and 4 outdoor perimeter doors. The integrator has to walk the five stages with the supplier's reply on the dated product page and live with the choice for the next decade.

The integrator's reasoning path:

  • Stage 1. Guest-room doors score RC4 (wired-in IP / hotel PC software) because the property is a hotel above three stars with a front-desk PMS workflow. Check the model’s published specification whether the specific hotel-class SKU under quotation supports centralized DB mode and whether the multilingual hotel PC software language set covers the destination market.

  • Back-of-house doors score RC2 (gateway-relay) because they want remote admin but not full PMS integration. Check the model’s published specification which gateway SKU the back-of-house RC2 locks ship with or require.

  • Staff-only doors score RC1 / RC2 (mixed) because some are shift-audit-only and some are shift-audit-plus-eKey. Check the model’s published specification per SKU.

  • Glass-door meeting rooms score RC1 (standalone BLE) because the doors are rarely audited centrally. Check the model’s published specification whether the specific glass-door SKU supports BLE at the expected range on a metallic-film-coated glass door.

  • Outdoor perimeter doors score RC2 with a documented gateway-placement plan, because the property does not run a managed outdoor wireless LAN for door-class devices. Check the model’s published specification whether the specific outdoor-rated SKU supports RC2 and what its sealing envelope is — see Smart Lock Sealed Electronics sibling for the sealing discipline.

  • Stage 2. The property runs a managed wireless LAN on the guest floors for corporate and guest users; the integrator decides that RC3 doors are not part of this property's architecture, because the Wi-Fi posture is guest-isolated and cannot host door-class devices. The wireless footprint document is the architect's; the integrator confirms against the per-SKU band posture from the supplier's product page.

  • Stage 3. The integrator plans RSSI against the floor plan for the RC2 doors. The four legs (RSSI / SNR / band / concurrency) are walked per door; the supplier's answer is the per-SKU radio class from Stage 1; the integrator's answer is the per-door RF expectation on the floor plan.

  • Stage 4. The integrator positions two gateways on the back-of-house corridors (one per corridor) and one gateway on the staff corridor. The gateway uplinks are Ethernet to the property server room. The gateway power is PoE from the property's PoE switch. Check the model’s published specification whether the specific gateway SKU supports PoE input.

  • Stage 5. The integrator closes the loop with the supplier: per-SKU radio class (RC4 for guest rooms / RC2 for back-of-house / RC1/RC2 for staff / RC1 for glass / RC2 for outdoor), per-SKU band posture (no Wi-Fi at the lock), per-SKU gateway dependency (gateway SKU for back-of-house and outdoor; no gateway for guest-room wired-IP or glass BLE), per-SKU app-platform binding (hotel PC software for guest rooms; one app platform per back-of-house / staff / outdoor SKU; BLE-only for glass), per-SKU out-of-catalog firewall (none of the RC1 / RC2 / RC4 SKUs claim Matter / Zigbee / Z-Wave / Thread / Apple Home Key / UWB — confirmed in writing).

The architectural verdict on this 96-room illustrative arc is a hybrid: RC4 for 60 guest-room doors, RC2 for 20 back-of-house + 4 outdoor perimeter doors, RC1 for 4 glass-door meeting rooms, RC1/RC2 mixed for 8 staff doors. No RC3. RC5 is not needed because no individual door runs more than one architecture. The per-SKU confirmation discipline is what carries the verdict; the architectural shape is portable, the per-SKU numbers are not.

The scenario is illustrative-only. No property name, no city, no operator, no SKU number, no platform version, no gateway part number appears in this paragraph, and none is meant to. The architectural shape is portable; the per-SKU numbers are not, and would be confirmed on the product page if the operator were to convert the scenario into a quotation.

The per-tier sanity check — what the integrator walks away knowing

Before the integrator signs the quotation, they should be able to finish five sentences out loud, one per stage, without opening the supplier's reply.

  • For Stage 1 — My radio-class audit has assigned RC1 / RC2 / RC3 / RC4 / RC5 to every door class on the property, and every assignment is confirmed per SKU on the product page.
  • For Stage 2 — My router-position plan has five named sub-stages (wireless footprint / AP position / band posture / security posture / SSID / VLAN posture), and every RC3 door's band and security posture is confirmed per SKU.
  • For Stage 3 — My signal-expectations envelope has four named legs (RSSI / SNR / band / concurrency), and the per-door RF expectation is the integrator's plan, not the supplier's promise.
  • For Stage 4 — My gateway-or-hub placement plan has five named sub-stages (gateway SKU / position / uplink / power / spare-and-refresh), and every RC2 door's gateway dependency is confirmed per SKU.
  • For Stage 5 — My app-platform tenancy and per-model confirmation loop has five named confirmations (radio class / band posture / gateway dependency / app platform binding / out-of-catalog firewall), and every per-SKU cell is filled in writing on the dated product page.

If those five sentences come out cleanly, the integrator has understood the envelope. If any of them reads awkward, that stage is the one that needs another pass on the product page before the quotation is signed.

The boundary the network envelope does not cross

A network-requirements decision does not decide the credential format, the audit-log field shape, the per-credential TTL primitive, the role hierarchy, the operator-handover procedure, the lock-firmware security-patch cadence, or the compliance posture against telecom, electrical, fire-egress, accessibility and data-protection codes. Each of those is a separate architectural conversation — handled, in this cluster, by Connected Smart Locks: Complete B2B Guide, Smart Lock Cloud Management, Smart Lock Cloud vs Local Management, Smart Lock Offline vs Online Mode, and Smart Lock Security Architecture respectively. The reader who has the network envelope right and any of those conversations wrong still ends up with a building that does not behave the way the contract says it should.

This article also does not decide prices, MOQs, lead times, warranty terms or certifications; every one of those is a quote-thread conversation routed to /request-a-quote. Compliance with telecom, electrical, fire-egress and accessibility codes is the reader's own counsel and authority having jurisdiction.

Closing the network envelope

The five stages are tools, not winners. The integrator lands on a network envelope by walking Stage 1's per-door radio-class audit, dropping each candidate SKU onto Stage 2's router-position worksheet, asking Stage 3's signal-expectations questions on the floor plan, scoring Stage 4's gateway-placement worksheet against the building, and closing the loop with Stage 5's per-model confirmation discipline before the quotation is signed. The supplier's job on this article is verified in writing — in writing, on the dated product page, and ideally in the RFQ reply — what each shortlisted SKU actually supports at each stage. The integrator's job is to refuse any answer that ends in "or equivalent" without a per-stage yes-or-no paired with a per-SKU citation.

The catalog this site sells from carries 79 published models and supports a real subset of the radio classes the stages name. Where it supports the radio class, the SKU is on this site; where it does not, the SKU is a different product on a different shelf. The honest sentence in either direction has been written into the per-stage worksheets above and the per-SKU confirmation discipline that closes them. The next step is to bring the shortlist, the five worksheets, and one specific Stage 1 / Stage 4 / Stage 5 decision to the conversation at /request-a-quote; the secondary step, if the operator wants hands-on evaluation, is the sample-order path on /order-samples.

Cross-link table — where the network-requirements decision hands off

Concern this article reachesNext article to readSlug
Cluster-wide connectivity taxonomy (four tiers across 79 models)Connected Smart Locks: Complete B2B GuideConnected Smart Locks: Complete B2B Guide
Topology picture (RC1–RC5 across standalone / gateway / Wi-Fi / wired-IP / hybrid)Smart Lock Network ArchitectureSmart Lock Network Architecture
Round-2 and round-3 gateway/hub deep diveSmart Lock Gateway GuideSmart Lock Gateway Guide
Per-row gateway install-side datasheetSmart Lock Gateway Installation RequirementsSmart Lock Gateway Installation Requirements
What happens to each stage when the network is offlineSmart Lock Offline vs Online ModeSmart Lock Offline vs Online Architecture
Cloud-tier posture for RC2 / RC3Smart Lock Cloud ManagementSmart Lock Cloud Management
Power envelope the router and gateway inherit fromSmart Lock Battery Requirements + Smart Lock Electrical RequirementsSmart Lock Battery Requirements, Smart Lock Electrical Requirements
Catalog category anchors (Bluetooth, hotel)Bluetooth lock and Hotel lock categoriesRound Fingerprint Keypad Smart Lock with TUYA Bluetooth, RFID Hotel Card Lock
Program-level quotation for the chosen envelopeRequest-a-quote (primary) and order-samples (secondary)Request a quote, Order samples

The network envelope is portable; the per-SKU numbers are not. The cluster pillar sets the taxonomy; the topology arena carries the round-by-round picture; the gateway guide works the deep dive on RC2; the offline-vs-online sibling handles the resilience half of the conversation; the install-side datasheet consumes the gateway-placement stage. The buyer takes the five worksheets, takes the per-SKU confirmation discipline, and walks it into the supplier meeting before the quotation is signed. That is the entire B2B job this technical resource is meant to do.

Το καλάθι σας
Η εμπειρία σας σε αυτόν τον ιστότοπο θα βελτιωθεί με την ενεργοποίηση των cookies Πολιτική cookies
Chat on WhatsApp