
Project-grade lock families, integration discussions on protocols and ecosystems, BOM-level support and engineering escalation — with compatibility confirmed per project rather than claimed universally.
Integrators do not buy locks one at a time — they deliver a working access system across doors, users and software. The failure points are predictable: a lock whose protocol cannot reach the management platform, lock bodies that do not fit the surveyed doors, or credentials that cannot be issued at the scale the operation requires. The integrator program supports the sale the way an integrator actually works: door-schedule and BOM discussions, model selection by integration need (offline RFID, Bluetooth/Wi-Fi ecosystems, or project-assessed protocol work), engineering escalation for connectivity questions, documentation for commissioning, and spares for the maintenance tail. Exact protocol support is a property of each SKU and is confirmed per project assessment rather than promised across the catalog.
| Selection by architecture | Offline RFID with encoder/software, Bluetooth or Wi-Fi ecosystem models (Tuya/TTLOCK-type), and gateway-based deployments selected for the site |
| Protocol discussion | Wiegand and other access-control interface questions handled by engineering on selected hardware; confirm support for the exact project configuration |
| BOM support | Locks, bodies, credentials, encoders/gateways, software and spares priced against a door schedule — see project configurations |
| Commissioning assets | Install sheets, credential/encoder setup documentation and remote configuration guidance for the deploying team |
| Engineering escalation | Technical questions that sales cannot answer route to engineering with the project context attached |
| Project verification | Samples tested against the real platform and door types before mass rollout — see samples |
| Maintenance tail | Spares packs and warranty flow protect multi-site contracts — support |
Architecture follows how credentials are issued and revoked, and whether real-time monitoring matters. Offline RFID suits large hotels issuing cards at a front desk; ecosystem Bluetooth/Wi-Fi suits rental and small-office operations managed by phone; connected gateway deployments suit sites needing centralized remote management. Choose the architecture first, then the lock bodies, or the BOM will be reworked during commissioning.
| Architecture | Credential flow | Typical site | Core components |
|---|---|---|---|
| Offline RFID + encoder | Cards issued at reception desk | Hotels, serviced apartments | RFID locks, encoder, cards, software |
| Bluetooth ecosystem | Phone credentials, optional keypad codes | STR rentals, small offices | BT locks, app platform, codes |
| Gateway / Wi-Fi | Remote codes and status from central software | Multi-unit residential, coworking | Connected locks, gateways, platform |
| Access interface (project) | Integration with existing control systems | Enterprise/government facilities | Interface hardware; project assessment required |
Integration rule: never quote a protocol or ecosystem feature from a marketing line. Confirm the exact SKU, firmware and interface against your platform with engineering, and verify on a sample before committing the rollout.
That depends on the platform and the exact SKU. Selected hardware supports access-interface discussions such as Wiegand, while connected ranges use Tuya/TTLOCK-type ecosystems. Share your architecture and protocol requirements with the RFQ; engineering confirms compatibility in writing and recommends a sample test before rollout.
Yes — the classic hospitality architecture is offline RFID locks plus an encoder, card stock and management software; cards are issued at the desk and checked against the lock's stored access rules. PMS-related integration is scoped as part of the project discussion, as covered on the hotel lock manufacturer page.
A door schedule (type, material, thickness, existing prep, count), credential and user flow, platform or integration requirements, site network availability, timeline and destination market. The project configurations hub provides the BOM planning structure.
Platform-specific integration documentation is shared for connected models after the project scope and chosen ecosystem are defined, typically under the project discussion rather than as an unrestricted public file. State the target platform and use case so the correct material reaches your technical team.
Delivery can be phased against site milestones, and spares packs are sized for the deployed door count rather than the first shipment alone. Warranty handling and technical escalation run through one project contact for the life of the installation — see the support page.
Send the door schedule and platform requirements — receive a model shortlist, integration assessment and project quote.
Discuss your integrationOrder verification samplesLast updated: October 31, 2026 · Reviewed by the Smart Lock Factory editorial team