Home / Answers

Can I keep the smart lock I already installed when I switch booking software?

Which door systems OpenTeeSheet drives directly, how a keypad reader is driven with its own API credential instead of a staff login, and what happens when your lock is none of the six.

Updated 2026-11-06. Every quote links to where it was published.

In owners' own words

“The keypad is on the right.”

An unstaffed one-bay simulator studio, on its own site · source

“you will likely be prompted to change the password when you log in, which will break the integration”

A launch-monitor vendor's own support article on its door integration (vendor-authored) · source

What it is

The door hardware is the part of an unstaffed studio that is already paid for and already drilled into the wall. A keypad reader, its controller and the wiring are the most expensive thing in the entrance, and the studio chose them before it chose booking software. Software that only drives one brand of lock turns a software switch into a hardware job.

There is a second, quieter version of the same problem. Some booking tools reach a door system through a person's login rather than a credential issued to the software, so the door path depends on a password a human owns. The vendor article quoted above warns its own customers that logging in may force a password change, and that the door link breaks when it happens. A door that stops working because somebody rotated a password is a door that fails at eleven at night.

How OpenTeeSheet does it

Six door systems are driven directly: igloohome, RemoteLock, Kisi, Seam, Salto KS and Avigilon Alta. Every one is exercised by the same end-to-end proof that a booking opens every door on the golfer's path.Pinned by automated tests: lock-brands-claim.test.ts, every-door-opens-realdb.test.ts
Locks reached through Seam or RemoteLock, including Schlage and Yale models, are driven as that hub's devices rather than being claimed as integrations of their own.Pinned by automated tests: lock-brands-claim.test.ts, lock-seam.test.ts
An Avigilon Alta keypad is driven through the vendor's documented API with a bot user the owner creates for OpenTeeSheet in the Alta Control Center, not a staff member's login, so rotating a person's password cannot break the door path.Pinned by automated tests: lock-alta.test.ts, lock-provider.test.ts
A lock outside the six can still be driven if it accepts a PIN over an API: the Custom Lock API posts the booking's code to the owner's own signed endpoint and reads back whether the lock took it, and it fails over to the same backup path as any brand.Pinned by automated tests: lock-custom.test.ts, lock-custom-realdb.test.ts
Several locks on one path, a street door, an inner door and the bay, are issued one credential per booking and opened in order.Pinned by automated tests: lock-multidoor-realdb.test.ts, lock-doors-crud-realdb.test.ts
A venue with no smart lock is handled honestly: no code is promised, and the confirmation tells the golfer to check in with staff.Pinned by automated tests: no-lock-honest.test.ts
If the lock refuses a code for a paid booking, the booking is flagged for staff entry, the owner is emailed and texted, and a backup code made in advance can go to the golfer instead.Pinned by automated tests: lock-failure-unattended.test.ts, lock-backup-realdb.test.ts

The bar we measure it against

OpenTeeSheet drives an Avigilon Alta keypad reader through Alta's documented API with a scoped API credential and no shared user password: a booking's PIN is valid for the booked window, revoked on cancel, re-issued on extend, with 0 failures over 100 synthetic bookings against a contract-faithful mock, and the existing lock-failure path applies unchanged.

Where it stands today: The Alta adapter is pinned request by request against the vendor's own published API contract, and the failure path is pinned by the tests named above. The 100-booking synthetic run and a check against a live Alta organisation are not published yet: the live organisation needs a bot identity only the venue's owner can create.

Not built or not measured yet

No run of 100 consecutive bookings against the Alta contract mock is published yet, and no live Alta organisation has been driven: the adapter is pinned against the vendor's published API contract with the HTTP faked, exactly as the other five brands were before their live checks.

Locks with no PIN or API of any kind, including a keypad that only stores codes typed into it by hand, cannot be driven by any software, ours included.

What owners report from other tools

A door link that runs on a person's login breaks when that password changes, by the vendor's own warning. Generic booking tools leave the door to a separate access product the owner connects and watches, and the owner is the integration.

Questions

Which locks does OpenTeeSheet drive directly?
igloohome, RemoteLock, Kisi, Seam, Salto KS and Avigilon Alta. Schlage and Yale locks are driven through Seam or RemoteLock.
My lock is not on the list. Is that the end of it?
No, if it takes a PIN over an API. The Custom Lock API posts the booking's code to your own endpoint, signed, and reads back whether the lock accepted it.
Does OpenTeeSheet need a staff login to my door system?
No. It uses a credential you create for OpenTeeSheet alone, so a password change for a person cannot break the door.
What if the lock refuses the code for a booking that is already paid?
The booking is flagged for staff entry, you are emailed and texted, and a backup code made in advance can be sent to the golfer instead.

Related