This article is written by the WAFU B2B Engineering Team for procurement managers and system integrators at hotels, apartments, and property management companies. WAFU Smart (Shenzhen) specializes in invisible remote control lock OEM/ODM, with a factory established in 2013 and exports to 60+ countries.
Opening: When All Three Parties Point Fingers
Last year, a 180-room boutique hotel in Southern Europe approved a "keyless upgrade." The owner liked invisible locks—no keyhole on the exterior, no need to replace card readers on every door. The integrator quoted a mobile key solution linked to the PMS, and the lock manufacturer supplied WF-019-class products with RF remote control. At the kickoff meeting, all three parties were nodding.
Three months later, the project stalled.
The integrator said: "The locks don't support Opera." The lock manufacturer said: "Your gateway protocol stack is wrong." The PMS vendor's API sandbox had never been tested for encrypted credential delivery. Guests were still checking in with plastic key cards, and 60 doors sat half-configured with no one taking ownership. Legal fees, change orders, and reputational damage all landed in the gray zone where the contract never spelled out "integration responsibility."
These stories are not rare. When hardware, networking, and software are procured separately, this is the default outcome. Invisible locks add another variable: the lock body is installed inside the door—choose wrong, and rework costs are extremely high.
The fix is not sending more brochures. It is using a short engineering question checklist before signing, requiring suppliers to answer in writing.
Below are the 8 questions WAFU recommends every hotel, multi-unit apartment, and integrator partner must ask. We use the same list internally on OEM/ODM projects. You can send it to any supplier; if you send it to us, we will evaluate each item for you free of charge.
Further Reading
PMS Integration & Deployment Resources
When evaluating invisible lock integration with property management systems before signing, we recommend reviewing the following on-site resources in parallel.
Before You Sign
1. Which communication protocols do you support? Is there API documentation?
Why ask: "Smart lock" is not a protocol name. 433 MHz RF remote control (entry-level WF-019 invisible remote control lock) and Wi-Fi knob locks (WF-Q7, Tuya App) or BLE handle locks (WF-016) are completely different logic stacks. The PMS does not connect directly to the lock—it connects to a cloud platform, middleware, or property gateway. If no one maps the RF → gateway → REST/Webhook → PMS chain upfront, problems will surface during commissioning, not in the brochure.
A qualified answer should include: A responsible manufacturer lists protocols by SKU and deployment tier, not "we support everything." The WAFU product line covers 433 MHz RF, 2.4 GHz Wi-Fi, and Bluetooth / BLE; hotel-grade WAFU SMART-LOCK+ solutions use SecureMesh™ mesh networking with gateway redundancy. ODM projects can swap modular communication boards (Wi-Fi 6E, Zigbee 3.0, NB-IoT, Tuya, Matter-ready design) without redesigning the entire lock body.
When integrating with a PMS, explicitly require:
- WAFU Connect SDK documentation and sandbox environment
- Webhook / event schema (check-in, check-out, credential revocation, low battery)
- Middleware proven on Oracle Opera, Protel, Fidelio, RMS, and similar systems—not just an "open API" slide deck
If a supplier cannot produce versioned API documentation and a test tenant, "easy PMS integration" should be treated as unverified marketing language.
2. Who operates OTA firmware upgrades? How are failures rolled back?
Why ask: OTA is a routine means to patch vulnerabilities and add PMS field mappings—but it is also the source of risk when a careless batch upgrade "bricks" hundreds of locks in one night, especially when multiple batches and firmware versions coexist on the same property.
A qualified answer should include: Require a written OTA policy, not just verbal "we can upgrade remotely." WAFU cloud-enabled models support remote firmware push via the management platform; hotel projects typically use staged rollout (pilot floor → full property), with signed packages and compatibility checks against the current PMS middleware version. The manufacturer should clarify:
- Who clicks "Deploy" (your IT, the integrator, or WAFU managed service)
- Whether updates are mandatory or optional per property
- How to roll back or flash a recovery image when a single unit fails
- Whether OTA automatically pauses when gateway connectivity falls below a threshold
We do not ask you to trust magic "failure rate" numbers in brochures—request on-site rollout records from properties of comparable scale. If a supplier cannot explain rollback, do not grant it OTA authority over production door locks.
3. Do you have proven integration cases with similar PMS / property systems?
Why ask: Paper protocol compatibility ≠ end-to-end latency for "check-out → credential invalidation" at 3 PM on a Saturday. You need someone who has already run the full chain—"reservation event → door access → audit log"—in a real hotel or multi-unit environment.
A qualified answer should include: Case studies must be specific: PMS name, room count, credential type (mobile key / PIN / NFC), middleware ownership. WAFU reference examples:
- German premium hotel chain bulk deployment of WF-019 invisible locks (1000+ units), PMS-synced temporary passwords, stable IP65 operation in humid corridors
- WAFU SMART-LOCK+ deep integration with Protel (e.g., ~120 rooms at a Cologne business hotel), Opera-class systems linked via API/Webhook for Mobile Key
- Multi-unit apartments using BLE or Zigbee gateways, with the property operator—not the lock manufacturer—holding the tenant app
Request a sandbox replay: create a test reservation → credential appears on lock or phone → check out → confirm revocation. If a supplier only provides hardware spec sheets, they are selling locks, not an access control system.
During Installation
4. Can you install on door thicknesses from 35 mm to 80 mm? What if out of range?
Why ask: Procurement often negotiates "35–80 mm door thickness" as a blanket term, but each SKU has its own mechanical envelope. Installing the wrong series on thin retrofit doors or heavy fire-rated doors causes jamming, false "motor stall" alerts, or door damage.
A qualified answer should include: Measure with calipers at top, middle, and bottom of the door, take the minimum value, and match against the specific model:
| Product Line | Door Thickness Range (WAFU Spec) | Notes |
|---|---|---|
| WF-019 Invisible Remote Control Lock | 30–70 mm | Lock body depth 22 mm; frame depth ≥ 22 mm |
| WF-026 Hidden Anti-Theft Lock | Confirm per order configuration | Dual-system dual-motor; optional Wi-Fi remote version for centralized management |
| WF-F8, WF-Q7, WF-F4 Handle/Knob Locks | 35–55 mm | Drill-free replacement; standard interior door install in ~3 minutes |
| WF-V2 Thermal Break Aluminum Smart Lock | 30–60 mm | 34 mm ultra-narrow body, suited for framed/sliding aluminum doors |
| H2 Premium Biometric Lock | Narrow-frame aluminum / commercial door types | On-site frame geometry confirmation required |
If you have 80 mm solid-core or fire-rated doors, do not assume catalog handle locks will fit. WAFU can provide custom latch extensions and ODM lock body variants—provided pre-installation survey has recorded door thickness, not discovered on installation day.
5. If the gateway goes offline, can locks still work? What is the offline contingency plan?
Why ask: Networks fail. Construction crews cut cables; ISPs go down during peak check-in. Treating "must be cloud-connected" as the only strategy will eventually trap guests or staff.
A qualified answer should cover three layers:
- Local unlock without gateway dependency
- WF-019: 433 MHz RF remote operates independently of the hotel LAN (typical ≤ 10 m line-of-sight); manual/mechanical emergency retained per configuration.
- Fingerprint / PIN / NFC stored on the lock works offline.
- Supercapacitor emergency (WAFU invisible dual-system design 5F / 5.4V) completes three full unlock cycles when the main battery is depleted.
- PMS-dependent credentials
Mobile keys and one-time check-out codes typically require recent sync. WAFU middleware can switch to local cache mode when the PMS link breaks and alert engineering—front desk can still issue PINs while IT restores the gateway. - Gateway architecture
Hotel-grade SecureMesh™ uses multi-path routing; a single AP failure does not isolate an entire floor. Zigbee 3.0 or BLE gateways for retrofit projects should have redundancy; relay placement verified by on-site RF survey, not floor-plan estimates alone.
The integrator should document in writing: which unlock methods work on a zero-cloud day, and which require sync within 24 hours.
6. Does door frame material (wood / metal / fire-rated) matter? Are there installation restrictions?
Why ask: Invisible locks sit inside the door leaf. Metal cladding, fire-rated cores, and glass assemblies change cavity depth, RF attenuation, and screw grip. A lock certified for residential hollow-core wood doors cannot go on a 60-minute fire door without project-level evaluation.
A qualified answer should include:
- Wood doors: Self-tapping screws + expansion anchors to handle wood shrinkage (standard WF-019 deployment practice).
- Steel-wood composite / metal doors: Antenna layout is critical; metal shielding may weaken Wi-Fi, BLE, or 433 MHz signals—on-site survey recommended.
- Glass doors: Require dedicated clamps; not all invisible lock bodies are suitable.
- Fire doors: Subject to local codes. WAFU invisible locks can preserve exterior hardware appearance, but fire compliance is a project certification issue—requires written confirmation from fire consultant and lock manufacturer engineering.
WF-019 factory specs list suitability for wood, metal, and glass doors; WF-Q7 additionally supports stainless steel, aluminum, and copper. "Compatible" still means "measure first."
After Go-Live
7. Who troubleshoots firmware issues? Is there a technical support SLA?
Why ask: After handover, the front desk calls the general manager, not the Shenzhen factory. Someone must own the Tier 1 → Tier 2 → OEM engineering escalation path, with response times enforceable in the contract.
A qualified answer should include:
- Named support channels (Chinese/English engineering desk) and severity level definitions
- Remote diagnostics: lock heartbeat, RSSI, battery trends, last PMS sync timestamp
- Spare parts policy: motors, RF modules, lock bodies—essential for 5–10 year hotel project lifecycles
- Defect ownership: if a bug only appears after PMS middleware v2.3, the fix may require a joint release from integrator and OEM
WAFU B2B hotel projects typically quote annual software/service OPEX (cloud platform, security updates, technical support) separately from hardware CAPEX. If an integrator resells locks, clarify under whose name the SLA sits—whether firmware tickets are handled by the same team that wrote the SDK.
8. Where is user data stored? Who has access? (GDPR / Privacy Compliance)
Why ask: Access logs, mobile key numbers, and biometric templates are all personal data under regulations like GDPR. As data controller, a hotel group cannot outsource compliance to a lock manufacturer with opaque cloud tenancy.
A qualified answer should include:
- Biometric templates (H2 / peephole series fingerprint, 3D face): WAFU hotel solutions follow privacy by design—templates encrypted with AES-256 and stored only on the lock-side secure chip; raw images are not uploaded.
- Access logs and guest identifiers: TLS 1.3 in transit; cloud storage region and retention period must be documented. WAFU SMART-LOCK+ hotel stack uses FIPS 140-3-grade hardware security modules.
- Sub-processors: Who hosts the cloud (AWS, Azure, Tuya, private tenant)?
- Data Processing Agreement (DPA) ready for EU/UK properties
- Audit trail: who views logs, exports reports, issues override keys
If the answer is just "it's all in the app," it is not qualified. You need a data flow diagram: lock → gateway → cloud → PMS → staff admin interface.
Closing: Send Us These 8 Questions
Integration failures are rarely a "technical mystery"—more often, questions all three parties assumed someone else would answer, and no one did.
Copy this checklist into your RFP and send it to WAFU—we will provide written responses item by item based on your door schedule, PMS stack, and target SKU (WF-019, WF-026, WF-F8, H2, WF-V2, WF-Q7, or custom ODM), with no sales pitch.
Free Integration Assessment — Contact WAFU
- Website inquiry: Contact Us
- Products: Products
- Technical article library: Technical Articles
- WhatsApp / Phone: +86 15914193183
- Email: wafutechnology@gmail.com | wafutechnology@outlook.com
Please specify property type (hotel / apartment / mixed-use), approximate door count, PMS brand and version, and whether you need invisible locks (WF-019 / WF-026) or surface-mounted smart lock series. Our Shenzhen factory (13 years, 60+ export markets, 8000+ B2B customers served) supports sample testing, OEM/ODM RF module customization, and on-site survey templates for integrators.
For locks to be truly "invisible," integration must be solid first. These 8 questions help you put responsibility on paper before signing.
© 2026 WAFU Smart Lock. Technical brief for B2B procurement and integrators. Specifications vary by SKU and firmware version; subject to purchase order confirmation.
