
Hotel projects ask about card technology, PMS interfaces, emergency access and energy control; this FAQ explains how those pieces connect and what to specify.
Hotel lock questions rarely stop at the lock itself: a property needs guest cards that also open a lift floor and switch on room power, a front desk that can issue and cancel access in seconds, an audit trail for disputes, and a way in when the network, the server or a guest card fails. This FAQ covers card technologies and their read ranges, PMS interfaces and what data crosses them, offline and online operation, master cards and emergency override, energy-saving link-ups, door fit and fire-rated guest doors, battery service, phased installation across occupied floors, staff training and handover. The answers describe how hotel access systems are normally engineered and specified. Model compatibility, interface protocols, battery service intervals and project schedules are confirmed in writing per quotation.
RFID is the default for new hotels because there is no contact wear, read speed is high and cards can be cloned only with effort; MIFARE Classic suits basic room access, while DESFire or similar secure cards fit properties that also use the card for payment, lockers or staff canteens. Magnetic stripe is legacy: it needs physical swipe contact, wears out faster and is easier to copy, but many existing PMS installations still depend on it, so a mixed estate often keeps both. Mobile keys via phone NFC or app are an add-on for loyalty guests and contactless check-in, not a replacement for cards at every property. Card standard, reader compatibility and encoding format for the named SKU are confirmed in writing per RFQ.
The lock itself does not talk to the PMS directly; a lock management system sits between them, usually running on a front-desk PC or a local server, and exchanges room, guest, reservation and keycard data through a defined interface. Typical interfaces are an encoder connected to the property-management software, a file or API exchange, or a certified middleware package from the PMS vendor. What crosses the boundary is reservation dates, room numbers, card numbers and check-in or check-out events, not payment data. Integration scope, supported PMS versions, interface type and testing responsibility are confirmed in writing per quotation, because a PMS upgrade can break an untested link.
Guest access must not depend on a live network, so hotel locks store their own authorization data and validate cards locally. Cards issued before the outage keep working because each card carries its own validity window and room rights; what stops is issuing new cards, remote cancellation and live event collection. Front-desk systems normally run on a local PC with a database backup, and a printed emergency procedure allows manual issuance from a master card. Properties that rely on cloud dashboards need a documented offline fallback rather than hope. Offline capacity, local storage limits, synchronization behaviour and fallback procedures are confirmed in writing per quotation for the specific model and software version.
Issuance writes the room number, validity dates and access rights onto the card through an encoder or a handheld programmer, so a guest checking in for two nights receives a card that expires automatically. Extending a stay means rewriting the validity dates; changing rooms means rewriting the room rights; cancelling means either rewriting the card with no rights or relying on the lock to reject an expired card at the door. Lost cards are replaced by reissuing a new card number rather than by finding the old one. Front-desk steps, encoder compatibility and the exact card data layout are confirmed in writing per quotation and covered in handover training.
Yes, when the lock system, the elevator controller and the energy switch share the same card technology and rights model. The card carries room access plus a floor list, and a floor-control board in the lift reads the card and releases only permitted floors; a keycard energy switch inside the room powers lighting and air conditioning only while a valid card is inserted or held. All three must agree on card standards and numbering, and the rights are managed in one system rather than three. Elevator integration may need local lift-controller interfaces and approval from the lift vendor. Card data sharing, floor-control hardware and energy-switch wiring are confirmed in writing per quotation.
Hotels normally run several levels: guest cards limited to one room and a date window, floor or area master cards for housekeeping and maintenance, a general master for management, and an emergency card that opens rooms and deadbolt states under controlled conditions. The emergency card is stored in a sealed or signed-out container with an audit record, because it is the highest-risk credential in the building. A mechanical override cylinder or concealed key remains the last resort for dead batteries and failed electronics, and it must be keyed into the property master-key system. Master-card hierarchy, emergency-card handling and override cylinder keying are confirmed in writing per quotation.
Three mechanisms normally combine. The card itself carries an expiry, so a card issued for a two-night stay stops working at checkout time even if it is never returned. The lock maintains a cancellation list, so reported-lost cards are refused at the door once that list reaches the lock through the local system. And rights are rewritten when a new guest checks in. Relying on expiry alone leaves a window, which is why properties cancel reported losses at the front desk immediately. How cancellation lists propagate to offline locks, how often locks synchronize and what happens if a lock has not been visited are confirmed in writing per quotation.
Guest doors are usually 40 to 55 mm thick timber, often with a Euro profile mortise body, a narrow-stile aluminium frame in resort buildings or a fire-rated assembly in corridors. Fit depends on the mortise case size, backset, faceplate and the handing of the door, and on whether the existing prep can be reused. Fire-rated doors require hardware listed in the door assembly, so the lock model must be cross-referenced to that listing before order. Finish selection matters for corridor aesthetics, but it should not drive the mechanical choice. Door measurements, existing prep photos, fire listing and finish requirements should be in the RFQ; matching models are confirmed in writing per quotation.
Each hotel lock keeps an internal event log of card number, time, opening method and door state, and the front-desk system collects it through a portable programmer, a network gateway or a data card carried by housekeeping. The log is read into the management software, where it can be filtered per room and per time range and exported for a dispute or an investigation. Log capacity is finite and rolls over, so collection frequency matters; a property that reads logs once a month may lose detail on a busy corridor. Log capacity, collection method, timestamp source and export format are confirmed in writing per quotation for the specific model.
The energy switch is a separate device in the room, usually a wall-mounted keycard holder wired to a relay that controls lighting and HVAC circuits, and it reads the same card as the door lock. A valid card for that room closes the relay; removing the card or expiry opens it again, so empty rooms do not run air conditioning. Some installations combine the function in a single controller, others keep the door lock and the energy switch as two devices with one card. Wiring, relay rating, load limits and hotel-specific fire or electrical rules belong to the electrical contractor. Switch compatibility, wiring diagrams and card-sharing requirements are confirmed in writing per quotation.
Battery life depends on openings per day, radio polling, temperature and cell type, and it is specified under a stated test condition rather than as a marketing number. A card-only lock with no network typically lasts far longer than a gateway-connected model on the same cells. Hotels plan service as a scheduled housekeeping task with a low-battery report from the management software, so cells are changed before a room fails; locks also give a local warning and retain the mechanical override as the final path. Battery type, expected life under the stated condition, warning behaviour and replacement procedure are confirmed in writing per quotation.
Yes, and phased installation is the normal approach for operating properties. The sequence is usually a survey of every door and finishing, a pilot floor or a few rooms, then roll-out by floor or by wing with the management system pre-loaded before each cut-over. Each phase needs a temporary dual-credential period, where the old key or card and the new card both work, plus a written rollback plan if a batch behaves badly. Noise and access to guest corridors set the working window. Phasing plan, per-floor schedule, temporary credential handling and rollback provisions are confirmed in writing per quotation and project schedule.
The property needs a documented escalation path rather than an improvised one. Typically the night manager uses a floor master card or an emergency card held under sign-out control, checks the guest against the reservation, and records the event in the log; if the lock itself has failed, the mechanical override key opens the door. Where the lock supports remote unlocking, a front-desk or cloud command can open a specific door with an audit entry. The path must be rehearsed during training, because a procedure nobody has practised fails at 2 a.m. Escalation roles, emergency-card custody and remote-unlock authority are confirmed in writing per quotation.
Fire doors are certified as complete assemblies, so the lock must appear in the listing of that specific door assembly; a general product certificate does not satisfy a fire inspector. For European projects the door is tested to EN 1634-1 and the hardware to its own product standard, and for North American projects the assembly is listed to UL 10C with matching hardware listings. What a project needs is the hardware listing cross-reference for the exact SKU, the installation instructions that preserve the rating, and confirmation of which intumescent or sealing details are affected. Certificates and test reports for named SKUs are provided per RFQ, and the door manufacturer or fire consultant should confirm acceptance.
Partly. Locks can run offline indefinitely with locally stored rights, cards issued by a programmer and logs collected manually, which suits small guesthouses and properties with unreliable infrastructure. What offline operation removes is central reporting, remote cancellation of lost cards, live low-battery alerts and instant rights changes across the building; those return only with a local PC, gateway or cloud connection. Most hotels therefore run a hybrid: offline locks plus a local front-desk system that synchronizes when it can. Offline-only capability, minimum software for a central desk and the synchronization model for a given model are confirmed in writing per quotation.
Guest-room locks normally support an inside deadbolt or privacy state that blocks card access from outside except for an emergency or general master, so housekeeping cannot walk in on an occupied room. The state should be visible to the management system, otherwise staff knock on doors unnecessarily, and it must be released automatically when the guest checks out or when an emergency card is used. Staff master cards open occupied rooms under a defined policy and leave an audit entry. Deadbolt behaviour, privacy indicators, master override rules and the audit consequences are confirmed in writing per quotation.
Handover should cover front-desk issuance and cancellation, encoder operation, lost-card procedure, emergency-card custody, night lockout escalation, battery reporting, log collection and what to do when a lock is unresponsive. Documentation typically includes a management-software manual, a quick-reference card for reception, wiring and installation drawings, a maintenance schedule and an escalation contact list. Training is most effective when it is split by role and rehearsed on a real door rather than delivered as one long session. Training scope, language, documentation set and refresher arrangements are confirmed in writing per quotation and project plan.
Before opening, every door is checked individually: card read on the correct room only, expiry behaviour, master and emergency access, deadbolt and privacy states, energy switch response, log collection and battery status in the management software. The handover pack records door numbers against lock serial numbers, firmware versions, card formats and the master-card hierarchy, so later service does not depend on one person's memory. Punch-list defects are fixed and re-tested rather than carried into operation. Test checklist, handover documentation, serial-number register and acceptance sign-off are confirmed in writing per quotation and contract.
Send room count, door specification, card standard, PMS version and lift and energy requirements. Model compatibility, interface support and the phased schedule are confirmed in writing per quotation.
Ask Our EngineersRequest a QuoteLast updated: November 1, 2026 · Answers reviewed by the Smart Lock Factory engineering team