Door Locks: The guest's key, made from the booking

Make the guest's key from the booking, on the lock system the hotel already has. Key card systems on the Oracle FIAS keycard interface take their card requests through a small bridge program on the hotel network. Lock systems connected to a Seam workspace get key cards, PIN codes and mobile key links. Lift floors, common doors and amenities ride on the same key, every request and answer is kept, and the keys stop when the stay ends.

See pricing Start free trial

Included: no integration fee. Free instant access, no credit card required.

Works with

Hotel Foundation

Door Locks in the Hotel Suite: The guest's key, made from the booking

Key Cards Made from the Booking

A checked-in stay shows a Key Card button. The desk picks the encoder, the number of cards and new or another card, sees the areas the card will open and until when, then presses Make. Each key is kept on the stay with its encoder, cards, areas, dates and state, and a new card cancels the room's other cards.

Lift Floors and Shared Doors on the Same Card

Each area of the lock system is a lift floor, a common door or an amenity. A lift floor goes to the guests whose room is on that floor, a common door can go to every guest, and an amenity goes by room type, by an extra on the stay, or when the desk adds it. On the demo every card opens its own lift floor and the pool gate.

See it running

More screens from the app

Real screens from the running product.

What's inside

Everything in Door Locks

28 items in 4 areas, every one shipping with the app today.

Key cards at the desk
- Key Card on the staya checked-in stay whose room has a card lock shows Key Card; the window opens on today's room.
- The encoder you stand atthe lock system's default encoder is chosen for you; any other encoder of the system can be picked.
- New cards or another cardnew cards cancel the room's other cards; another card adds one for a second guest. One to nine cards at a time.
- Until the check-out hourthe window shows the date and hour the card stops opening before you press Make.
- Areas chosen before Makethe areas the stay gives are filled in; the desk adds any area marked Desk Adds It.
- Refused when the link is downwhen the bridge or the lock server is not linked, the window says so and no card is asked for.
- Room movesthe old room's cards are cancelled and the stay gets a note to make the new room's cards.
- The booking number, not the namethe lock system is told the booking number; the guest's name only when you switch Send the Guest's Name on.
Lift floors and areas
- Lift floorsa lift area per floor goes to every guest whose room is on that floor.
- Common doorsan area marked Every Guest, such as the pool gate or the lobby, is on every guest key.
- By room typean area can go to the guests of chosen room types, such as a club lounge.
- By an extra bookedwith Hotel Management, an area can go to the guests whose bill carries a chosen extra, such as parking for the garage.
- Closed when not givenon a key card system, the known areas a key does not give are sent closed, or left to the lock system's default.
- On Seam tooan area is one more door or lock in the guest's access on Seam.
The lock systems
- Key card systems on Oracle FIASSalto Space, ASSA ABLOY VingCard Visionline, dormakaba Saflok and Ambiance, Onity / TESA, MIWA, Kaba Ilco, Orbita, Adel, Be-Tech, Hafele Dialock, Timelox or another system with a FIAS keycard interface: the records are the same for each.
- A bridge program includeda single file for Python 3.8 or later on a computer of the hotel network; it holds the FIAS link with the lock server and calls out over HTTPS, so nothing is opened in the firewall.
- A bridge key shown onceonly its fingerprint is kept; a wrong key gets nothing.
- Rooms linked in one pressLink the Rooms makes one lock per room, with the room number as the ID the lock system knows.
- Lock systems on Seamone API key of the hotel's Seam workspace; Fetch the Doors and Encoders lists them and a door named like a room gets that room.
- PIN codes and mobile key linkson Seam, a PIN code or a mobile key link at check-in, and a mobile key link emailed to the guest from the stay.
- Keypad rooms beside card roomsrooms on TTLock locks keep their door codes from the free Hotel Foundation, next to the rooms on key cards.
Records and control
- Every message kepteach card request and delete is kept with the record sent, the lock server's answer and its state.
- Answers in plain wordsencoder busy, guest not found, refused and the other answers read as words, with the lock system's own text.
- Nothing left hanginga card request the bridge has not taken in 3 minutes, or the lock server has not answered in 2, is given up and the card marked failed.
- Keys end with the stayat check-out the cards are deleted in the lock system, or the access removed on Seam.
- Door Keys filtersKey Cards and Mobile Keys filters, with the cards made and the areas each key opens.
- Multi-companyencoders, areas and messages stay within their own company.
- Demo systems open nothinga demo lock system makes its keys up, says so on every key and sends nothing.

Works with

What Door Locks works with

Door Locks shares one database with the rest of the Hotel Suite and BridgeERP: these are the apps it already talks to, with nothing to buy in between.