Hotel door-lock selection Q&A

A bulk replacement has to satisfy four things at once: quick to fit, quiet, networkable and compatible with the systems you already have. The LS02 series is delivered as hardware plus the matching approach:

• Quick to fit: only two holes in the door, 40% fewer components than a traditional faceplate lock, swapped in place on the existing door, officially measured at as fast as two minutes per lock;
• Quiet: the triple silent structure holds the whole closing cycle under 60 dB (a traditional faceplate hotel lock is about 70 dB);
• Network and entry: the networked version with a USB micro gateway supports phone NFC tap-to-open (WeChat / Alipay Mini Program or the hotel’s own app) while keeping cards;
• Integration: the open IoT platform connects to the hotel’s existing PMS and room control, with lift control, door access and room power sharing one permission system.

On a bulk project, test two or three rooms first to confirm the door fits and the feel is right before rolling out.

Yes: no wiring and no new doors. Two key points:

• No wiring: networking comes from the USB micro gateway, which plugs straight into the lock’s USB service port, so no separate network cable is needed for the lock; the link between the lock and the power switch is wireless too;
• No new doors: the LS02 puts only two holes in the door (the gourd-shaped lock-head hole and a light pipe). Where an older door has a large opening from its previous lock, a decorative cover plate hides it, avoiding enlargement or a whole new door.

The power switch (Occupancy Power Saver) drops into a standard 86-type back box, so it and the lock can be upgraded separately.

One combination inside a single platform, so suppliers cannot blame each other:

• Locks: the LS02 fully automatic silent lock body (the networked version supports phone opening);
• Power: the Occupancy Power Saver (infrared plus microwave, on when someone arrives, off after a delay when they leave);
• Links: room control (lighting and air-conditioning scenes) and lift/door access share one permission model;
• Hub: the open IoT platform plus the USB micro gateway, integrating the PMS and the card system in one place.

The value of one permission system: a guest uses a single credential for the lock, the lift, corridor doors and room power, and it all expires at checkout.

Yes. The difficulty is not in any one piece of hardware but in unifying permissions and scenes: the lock opening, the power coming on and the lighting scene are all follow-on actions from the same event — the guest has entered.

Carrying it all on one IoT platform means the permission rules are configured once (floor, time, person) and new devices need no fresh integration; it also keeps responsibility clear, with no argument where the lock blames the network and room control blames permissions.

Normally the lock body has to be replaced, because phone opening needs a body that can go online and verify credentials — but the door does not. The faceplate depends on the existing structure:

The LS02 takes the “no faceplate, fully integrated” route: the board, battery bay, motor and silent structure all sit inside the body, leaving only a handle and a lock head outside and nothing large inside. That costs less to adapt to an older door and makes it easy to cover the old faceplate openings.

This is the most common worry on a retrofit. There are two cases:

• The old opening is smaller than the new lock: it has to be enlarged to the LS02 pattern (the gourd-shaped head hole plus a light pipe, two holes in all), far less than a traditional faceplate lock, which usually needs four or five;
• The old opening is larger than the new lock: a decorative cover plate hides the old opening, made to match the door’s colour and profile, leaving a clean face and needing no new door.

Before a retrofit, send a photo of the door face and the dimensions of the old openings so the manufacturer can judge the fit.

Damage comes mainly from how many holes are cut and how big they are. The LS02 cuts two, with a minimal-cutout design, so the damage is smaller than a traditional faceplate lock.

As for another brand later: whether it fits depends on that lock’s installation standard. Here the cover-plate approach works in your favour — it can cover whatever this round leaves behind, leaving room for the next swap.

Floor-by-floor work is common, and it comes down to two things: how long one lock takes and whether power tools are needed。

The LS02 needs no wiring and no spindle alignment, with 40% fewer components than a traditional lock, measured at as fast as two minutes per lock; there is no rewiring and no hammer drill, and the noise is screw work, which is manageable. Projects usually work floor by floor, using low-occupancy hours or nights, when the window for a single floor is short.

Agree the working arrangements with the manufacturer before signing, and build a sample room first to measure the real time per lock.

They can, and they probably should be — the two have different windows for the work, different budget lines and different payback periods:

• Locks first: fixing the opening experience, card management and bulk maintenance;
• Power next: the Occupancy Power Saver drops into an 86-type back box, the per-room time is short and the saving shows up directly on the electricity bill;
• Then add: once lock and power are on one platform, add lighting links and lift/door access — the permission system is configured once and reused.

Nobody can give you a precise number — what moves it is the following, not the list price of the lock:

• Door type and openings: a standard opening against one needing enlargement or a custom cover plate is a big difference;
• Lock type and configuration: standalone card version against networked (with gateway); whether power and lift control are added;
• Site conditions: removing the old locks, working floor by floor, night shifts;
• Quantity and batches: 100 rooms and 500 rooms price differently.

So the industry usually prices per project rather than per lock. Send door photos, the old lock model, the room count and whether networking is needed, and ask the manufacturer for a project estimate.

The difference comes from two things: networking and the equipment that goes with it。

• The networked version adds communication and management inside the body, so it costs more than the standalone card version;
• On equipment you need the USB micro gateway for the network and for pushing configuration: one per guest room in the room scenario, or 1:4 for area coverage (one gateway carrying four locks).

Worth noting: an offline gateway does not stop the door opening — the opening happens near-field between the phone and the lock, and the gateway only handles the network and configuration. That removes the hidden cost of a network that must never fail.

Hardware is usually priced per lock and the overall solution per project. Treating the two as opposites is a common misunderstanding: the body, gateway, power and installation are separate items, and what is delivered is a system that runs.

As for later costs, confirm them item by item before signing, asking three things above all:

• Is the platform (IoT / management system) bought outright or subscribed annually?
• Is there an ongoing service fee by room count or device count?
• How are upgrades, remote support and on-site visits billed?

Getting those three into the contract controls long-term cost better than haggling over the unit price.

For the guest it is about one extra motion: a card has to be taken out and lined up, while NFC just needs the phone unlocked and held near the lock, one tap and it opens. For anyone used to their phone, that is the same motion as a metro gate or a convenience-store payment — nothing to learn.

For the front desk, the card process does not have to be scrapped: the networked LS02 Ultra keeps full card function, running phone and card side by side. The front desk carries on issuing cards and offers the mobile key as an option to guests who want it — steadier than a hard switch to card-free, because there are always guests whose phone lacks NFC or who would rather not use one.

No. Three fallbacks:

• A warning first: the system warns early when the cells run low, so the property can schedule a change;
• A mechanical key: a mechanical key is kept for an emergency;
• Fast battery swap: four AA cells, changed on site by the engineering team.

On power design, the LS02 idles at 20 µA and four AA cells last over two years — low draw is itself the first defence against ever running flat.

Yes. This has to be settled at design time, and the key question is where the opening actually happens：

• Phone opening: the check runs near-field between the phone and the lock, so a dead gateway only affects networked features such as remote configuration and log upload, not the opening itself;
• Card opening: the card path is always available and needs no network;
• A mechanical key: a mechanical key is kept for an emergency;

In other words, the risk of “one network hiccup and nobody can open a door” depends on whether the design closes the opening loop in the near field. Worth putting on the technical checklist when choosing.

There are two routes, depending on how the project is configured:

• The front desk handles it: the card path is always live, so the desk opens the door with a spare or a fresh card, with no need for engineering;
• Remote opening: the networked version can issue a temporary credential or open remotely from the platform, provided the network and permissions are set up.

In practice the steadier arrangement is a card at the front desk as the fallback plus remote opening as a supplement: the card as the first response, with no dependency and no wait, and remote opening behind it.

The mechanism is real, but it is worth being clear about where the saving comes from.

The hole in card-slot power is that the card can leave the room while the appliances keep running — a guest forgets to pull it, or leaves it in to hold the slot. The Occupancy Power Saver judges presence with infrared and microwave, on when someone arrives, off after a delay when they leave, which removes empty-room power at the level of the mechanism.

For scale: about 300 kWh saved per room per year, with the usage data visible over the network. Whether it pays depends on local tariffs and occupancy — worth working through with your own price per unit.

LOCK.LINK is a smart lock and light-IoT brand built for hotel settings, operated by Guangzhou Konglide Intelligent Technology Co., Ltd. We are a source manufacturer — design, production, sales and service all run in-house, not a badged reseller.

The product position is clear: not a home smart lock moved into a hotel, but a structure redesigned for heavy card use, networked management and bulk maintenance. The core is the LS02 automatic silent lock body (no faceplate, integrated, closing under 60 dB, 20 µA standby).

On customers we serve the Dossen Group estate (including City Comfort Inn, ECHARM, Borman and Yicheng) and have delivered the youth-oriented unmanned smart hotel in Chengdu. To be clear: any particular project still needs its own assessment against room count, door type and systems.

We will not give a blanket verdict on “reputation” — on a retrofit the result depends heavily on how the door fits and how well it is installed. What we can state is the design intent:

• Designed for retrofit problems: a minimal cutout (two holes) plus a cover plate, aimed straight at the fear of damaging or replacing the door;
• No wiring, upgradable in stages: the lock networks through the USB micro gateway and the power switch drops in place, so the two can be done in separate phases;
• Fewer steps, fewer errors: 40% fewer components and no spindle alignment, cutting installation mistakes.

If you are assessing a specific project, ask for a sample lock for the same door type and fit one room — that is the most direct test.

Integration requires three things at once: a ready interface on our side、an open interface on your side、an agreed deployment shape (cloud or on-premise)。

We provide an open IoT platform and standard interfaces, and integrate with mainstream PMS and room control; one-click on-premise deployment is supported for groups with data-residency requirements.

Effort tracks integration depth: syncing unlock permissions alone is shallow, while full scene links plus log write-back is deep, and the two differ plainly. Agree which fields and scenes need connecting at the technical stage before estimating time.

The core difference is whether opening needs an extra motion: a semi-automatic lock still needs the handle pressed after the card; a fully automatic one retracts the latch and the door simply pushes open.

In a hotel that difference is amplified: guests arrive with luggage, shopping or a child in their arms, and removing one press of the handle is part of the first impression.

On durability, automation adds a motor and drive train, so the structure is more complex in theory — which is exactly why the motor’s cycle life and failure data matter when choosing. On the LS02 the motor is rated at 300,000 cycles, with 40% fewer components than a traditional faceplate lock.

Hotel lock security does not rest on cards being uncopyable but on several checks holding at once. Among our five layers, the mechanisms touching cards directly are:

• Near-field verification: the command must be verified within the lock’s near field (100% near-field verification), so no remote unlock can be conjured out of nothing;
• Replay protection: each command carries a unique identifier and a repeat is refused;
• Location check: the command is bound to the lock’s location, and a card that does not match the room is refused;
• Validity window: permissions expire with the stay, so the old card loses its rights at checkout.

So even a physically copied card is held by the validity window, the location and the command checks. The real risk to guard is managerial — a card issued from inside — and that is handled by binding cards to guests and logging every opening.

Yes. On networked locks the record (time, card or phone, lock location, result) uploads live to the platform, searchable by room number and time, with alerts configurable for anomalies.

Police registration and the lock system are normally two separate tracks: registration sits with the system the police designate, while the lock system answers who opened which door and when. Where they need connecting, it runs through the open IoT platform to the third-party interface; confirm the exact boundaries with the manufacturer at the technical stage.

It can contribute, but be clear about where the lock sits in that.

Low-carbon hotel assessments look at dozens of indicators across energy, water and waste, and the lock is part of the electricity-and-consumables piece: the LS02 idles at 20 µA and four AA cells last over two years, directly cutting standing draw and battery changes. The LS02 series holds a low-carbon product label authorisation, which can be submitted as supporting material.

The lock alone will not carry a whole certification, though: it is a bonus, not the ticket.

Warranty and response times are set by contract; here is our service mechanism so you can compare it with others:

• The three-5s standard: understood in 5 minutes, a plan in 5 minutes, then reviewed;
• Cards as a fallback: even if the lock fails, the card and mechanical key still work, so no guest is left outside;
• Spares and training: bulk projects normally include a few spare locks and on-site training, so the front desk can handle the common problems.

Before signing, get response times, how spares are supplied and the scope of on-site service written into the contract — more reliable than a verbal promise.

The biggest difference is in the usage model, not in build quality:

• Entry: home locks lean on fingerprints, codes and faces, while hotel guests turn over quickly, so cards and phone NFC are more practical (a fingerprint would have to be enrolled on every stay, with hygiene and privacy concerns);
• Integration: a hotel lock must connect to the PMS, the card system, lift control and room power; a home lock need not, and usually cannot;
• Bulk maintenance: a hotel manages firmware, permissions and faults across tens to hundreds of locks, while a home lock is managed one at a time;
• Structure and life: a hotel lock is designed for dozens of cycles a day (the LS02 motor is rated at 300,000).

Commercial editions of home locks can serve apartments and guesthouses with light management, but for a proper hotel guest room choose something designed for hotels.

Decide by the project’s positioning and fit, not by a blanket rule:

• Imported brands (VingCard, dormakaba, SALTO, Onity and others): mature systems with high encryption grades, common in five-star and large group projects; unit prices and lead times run higher, and local response depends on the distributor;
• Domestic brands (Be-tech, Adel, Yangge, Koyu, Chuangjia, Digeer, Liwei, LOCK.LINK and others): better at bulk delivery and retrofit fit, faster locally, across the economy to mid-market range.

On a retrofit, compare the number of cutouts and how the lock adapts to the old door — that usually moves the total cost more than the unit price does.

By need: if card opening is enough and remote management and log search are not required, standalone will do; for phone opening, live cloud upload and remote credential issuing, choose networked.

The LS02 and the networked LS02 Ultra share the same lock body structure: networking comes from the USB micro gateway in the lock’s USB service port. That means you can start standalone and add a gateway later to go networked without tearing out the hardware. Whether upgrades can be done in batches depends on the firmware version required — confirm with your supplier at purchase.

Hotel engineering tenders usually ask for the following; request them early and check the validity dates:

• Product test reports: CE / FCC / RoHS / GB 21556 / EN 14846 and others, depending on the project;
• Corporate and quality systems: business licence, ISO quality certification and so on;
• Project references: a list of hotels of similar size and positioning, verifiable;
• After-sales commitments: response times, spare-part supply and warranty terms.

Lists vary a lot between buyers; once you have the tender document, work through it item by item rather than preparing from experience.

The lock work needs no power cut (it runs on batteries, not mains), while the power-switch work does need the supply off — but only within one room at a time, so working room by room leaves other floors untouched.

The schedule depends on several variables: time per lock (the LS02 needs no wiring or alignment, measured at as fast as two minutes each), whether work is by floor, the daily window available (nights or low-occupancy hours) and whether power and room-control commissioning are included. Build a sample room and work the total back from the measured time — more reliable than an estimate.

Old locks are recyclable metal plus electronic waste, and are normally handled one of two ways: cleared away by the installer, or disposed of by the hotel under local rules. Whether they are taken back depends on the supplier’s policy — ask before signing.

One caution: guest data held in the old locks (local records on some smart locks) should be erased or physically destroyed before disposal — standard data-compliance practice.

Yes — and that is the point of choosing a platform rather than stacking separate items. Our approach puts locks, lift control, door access and room power under one permission model on one IoT platform: when a device is added, the permission system does not have to be rebuilt — the new device is simply attached to the existing floor + time + person rules.

The precondition is that new devices sit in the same platform ecosystem; mixing vendors means integration through interfaces, with effort tracking how deep that goes.

It does, with a different emphasis:

• Guesthouses / apartments: turnover is slower than a hotel and card issuing matters less, so phone opening and remote management carry more weight (issuing a mobile key straight from a short-let platform, for instance);
• Long-let apartments: management is finer-grained (by tenancy, by person), so validity windows and searchable unlock records matter more;
• Hotel guest rooms: heavy card use, PMS integration and one-card access are all essential, and the card path cannot be dropped.

One lock body serves all of these; what changes is the permission configuration on the platform and whether cards are kept. Confirm the configuration against how you actually operate.

Yes. Group management rests on three tiers: group → brand → property, with permissions and settings gathered upwards and issued downwards.

The usual pattern: the group level keeps standard templates (entry methods, permission rules, alert thresholds) and each property references a template with local adjustments such as floor count and door type, so nobody starts from zero. The LMC platform is built this way, and lets head office see device status and faults across every property.

Where a room is shared, the key is to manage room permissions separately from bed or personal permissions: room access is granted to the whole group of sharers, while personal space such as a locker is granted individually.

These projects lean more on phone opening, since guests bring their own devices and no front-desk card is needed, and care more about automatic expiry and bulk management. Work the configuration out from the actual room types and how you operate.