What an Airbnb smart lock needs that a home smart lock doesn’t

A lock on a short-term rental does a job the one on your own front door never has to. It admits people you have never met, on a schedule set by a booking calendar, while you are somewhere else and quite possibly asleep. A lock that behaves perfectly well on a family home can fail at this in ways that only surface in month four, on a Friday night, when the guest standing on the step reports that the code you sent does nothing.

The way to shop for one is against a checklist rather than a ranked list. Every item below can be confirmed from a manufacturer’s spec sheet, manual or developer documentation before you spend anything, and most of them are missing from the product page entirely.

One thing comes ahead of all of it: whether you are allowed to change the hardware at all. Hosts who are themselves tenants, and hosts in condo or HOA buildings, are often working under a clause that settles the question before any spec sheet gets read, so it is worth working out what your own lease actually says first. Rules differ by state, city and building, so check locally rather than assuming what applies.

How many codes the lock can hold at once

This is the first number to find and the one most reliably buried in an appendix. Consumer keypad deadbolts often store somewhere between six and thirty user codes. Models aimed at rentals and light commercial use run to a hundred or several hundred. Thirty sounds generous until you count what a working listing consumes: one per stay, a standing code for the cleaner, one for the co-host, one for the handyman who turns up twice a year, one for you, and every code you issued once and never removed.

Two failure patterns come out of a small code table, and both are quiet ones. In the first, the lock refuses new codes once it is full while the app still reports success, so nothing looks wrong until somebody is outside the door. In the second, the host starts recycling codes between stays, which removes most of the reason for fitting the lock, because a guest from March still has a working code in July.

Ask the documentation for the code slot count, then ask separately whether codes created in the app share the same table as codes programmed at the keypad. On several locks they do not, and the two limits are different numbers.

Codes that start and stop without you

A home lock loses codes when the owner gets around to deleting them. A rental lock has to do it by itself, because a code that outlives a stay is a key you handed to a stranger and did not get back.

Three levels of this are sold, and the vocabulary is not consistent between brands:

• One-time or single-use codes work once and then stop. Useful for a viewing or a delivery, wrong for a five-night stay where the guest goes out for dinner.
• Recurring or scheduled codes are valid inside a repeating window, such as Tuesdays between nine and one. This is the cleaner’s code.
• Date-ranged or temporary codes are valid from a start date and time to an end date and time. This is the one a booking maps onto, and the feature to insist on.

Where the schedule is actually enforced

Worth asking separately, because one feature name covers two different mechanisms. Some locks write the schedule into their own memory, so the code expires on the door’s own clock whether or not anything else in the house is working. Others keep the schedule in the manufacturer’s cloud and push a delete command when the time arrives, which means a lock that is offline carries on honoring a code that should already be dead.

The second arrangement is not a scandal and plenty of hosts run on it without incident. It does change what a network outage means, though, and it is the difference between an expired code and a code that has expired but has not been told.

Getting the code to the guest without typing it yourself

At one listing, sending codes by hand is fine. At three, it becomes the chore that eventually gets forgotten at eleven at night. There are three routes out of it, in ascending order of setup effort.

A native booking-platform integration

Some lock makers publish a direct connection to the major booking platforms, so a confirmed reservation creates a code inside the guest’s own date range without anyone touching an app. These connections appear and disappear as platform APIs change, so check the manufacturer’s current integrations page and the platform’s own documentation rather than a review written two years ago.

An API, or middleware in between

If the lock exposes a documented API, a property management system or a rental automation service can drive it. This is where most multi-unit hosts end up, since the same tool is already sending the check-in message. Check whether the API is public and documented or partner-only, and whether both code creation and code deletion are exposed. Read-only access to lock state is not much use on its own.

Doing it by hand, which is fine at one listing

Create a date-ranged code from the app once the booking confirms, paste it into the saved check-in message, and let the lock expire it on its own. Put a monthly reminder in the calendar to look at the code list and clear anything stale. This works perfectly well, it just stops scaling past a handful of turnovers a month.

What the lock does when the Wi-Fi drops mid-stay

Rental Wi-Fi goes down. Guests reset routers, providers have outages, and the cheap access point in the hallway hangs on a Sunday afternoon. Two questions decide how much that matters at the door.

The first is whether the keypad still accepts a code that was already programmed. On essentially every lock worth buying it does, because codes live in the lock’s own memory. The second is whether a scheduled code already written to the lock still starts and expires on time with no connection, which depends on where the schedule is enforced. That is the question from the previous section, and it separates an outage that is merely annoying from one that leaves a guest outside.

The related choice, whether the lock uses Wi-Fi directly or Bluetooth with a plug-in bridge, is a larger subject covered in the guide to picking a smart lock connection. The short form for a rental is that a Bluetooth-only lock cannot be managed from anywhere except the property, which puts you back to driving over with a code.

Cleaners, co-hosts and everyone who is not a guest

The people who visit most are not guests, and they need a different kind of access. A cleaner arriving weekly on a guest-style one-time code will be calling you weekly. Give the cleaner a recurring window on their own code instead, and give the co-host, the maintenance contact and yourself separate codes as well.

The reason is the access log rather than the courtesy. A lock that records which code opened the door and when turns “the cleaner says they came Tuesday” into something you can check, tells you whether a guest actually left before the turnover, and gives you a specific thing to look at after a neighbor complains about people arriving at three in the morning. None of that works if everyone shares one code, and one shared code is the default outcome unless separate ones are handed out deliberately.

Revoke on the day a working relationship ends rather than at the end of the month. A cleaner’s standing code is the longest-lived credential on the property and the easiest one to forget about.

Batteries, and the lockout you cannot drive to

A dead lock two hours away is a different problem than a dead lock in your own hallway. Three things make it likelier at a rental than at home. The door cycles far more often. Guests pull on the handle while the bolt is still moving, which makes the motor work harder than it should. And nobody hears the low-battery chirp for days, because nobody lives there.

What to build into the routine: batteries changed on a schedule rather than on a warning, a full set of fresh cells of the same type and brand each time rather than one or two swapped out, and low-battery alerts routed to your phone instead of to a keypad nobody is listening to. Cell chemistry matters more here than at a family home, since a lithium cell’s flat discharge curve makes the warning arrive later and more abruptly than an alkaline’s does. The battery guide covers which type suits which situation. A line in the turnover checklist asking the cleaner to report any beeping is worth as much as any of it.

The backup entry route you publish before you need it

Every lock fails eventually, and it will not wait for a vacant night to do it. Decide the fallback in advance and write it into the guest message, because improvising one at midnight, over the phone, with somebody who has been travelling since dawn, goes about as well as you would expect.

Most hosts settle on a key in a lockbox held as a documented backup, a trusted neighbor or co-host within fifteen minutes of the property, or a local locksmith or handyman already on call whose number is saved. The lockbox is the common answer, and the trade-offs between running one as the primary check-in method or purely as a fallback are set out in the comparison of a key lockbox against a keypad lock. Check building and HOA rules before mounting one, since some prohibit boxes on railings, gas piping and street-facing walls.

Whichever route you choose, keep a working mechanical key in the system. A lock whose cylinder was left out for a cleaner-looking exterior has removed the one method that needs no power, no network and no code.

Common questions

How many codes do I need for one listing?

Plan for one per active and upcoming stay, plus four or five standing codes for the cleaner, co-host, maintenance and yourself. A lock with thirty slots handles that comfortably as long as expired codes get cleared. A lock with six does not, once you allow for overlapping bookings and codes issued days before check-in.

Can the booking site send guests a door code automatically?

Only through an integration between the lock, or the software managing it, and the platform. The platform has no idea your lock exists otherwise. Check the maker’s current integration list before buying, because these connections come and go with platform API policy.

What do I do if a guest’s code stops working at midnight?

Check the app for whether the lock is online and whether the code is still listed, then read the code back to the guest slowly, since a mistyped digit is the most common cause by a wide margin. If the code has genuinely gone, issue a new one from the app while the lock is still reachable, and go to the backup entry route if it is not. This is the situation the fallback exists for.

Is a keypad lock enough, or do I need a camera as well?

They do different jobs. The lock controls who gets in; a doorbell camera tells you somebody arrived. Booking platforms set their own rules on cameras and monitoring devices at a listing and those rules change, so read the current policy and any local law before installing anything that records.

The short version

Find the code slot count and the expiry mechanism before looking at anything else, because those two decide whether a lock can run a listing at all. Insist on date-ranged codes, and confirm whether the schedule is held on the lock or in the cloud. Give cleaners, co-hosts and contractors their own codes so the access log means something. Change batteries on a calendar rather than on a warning chirp nobody is there to hear, and write the backup entry route into your guest message long before the night you need it.