A host I know in Lisbon ran four apartments for two years with a Schlage keypad on every door and a spreadsheet of codes. Every Friday she generated the weekend's codes by hand, pasted them into Airbnb messages, and on Monday she walked to each building to delete them. It took about ninety minutes a week, which does not sound like much until you count the two Fridays she forgot, the one guest who arrived to a code that had already been recycled, and the review that followed. The locks were smart. The system around them was not.
That distinction is the whole point of this guide. A smart lock on its own is a keypad with a battery. A smart lock connected to your property management system is a piece of automation: the code is generated when the booking confirms, delivered at the right hour before arrival, activated at check-in time and deleted at checkout, with no human touching any of it. The hardware gets the attention; the integration does the work.
My opinion, after setting these up for hosts on most of the major platforms, is that lock integration is the highest-return automation after scheduled messaging, and the one most often botched because people buy the lock first and think about the software second.
How does smart lock integration with vacation rental software actually work?
Smart lock integration works by letting your property management system talk to the lock manufacturer's cloud (or to a hub like Seam, RemoteLock or Jervis Systems) through an API, so that each confirmed booking automatically generates a unique access code that is valid only between check-in and checkout and is pushed into your guest messages as a variable. The PMS knows the reservation dates and the guest's name; the lock cloud knows how to create and delete codes; the integration connects the two so a booking on Airbnb at 11pm on a Tuesday produces a working code on the door in Porto without anyone waking up.
There are three layers, and sales pages blur them together.
The first layer is the lock itself: a battery-powered deadbolt or lever with a keypad, and a radio. Wi-Fi locks (Schlage Encode, Yale Assure 2 with the Wi-Fi module, August Wi-Fi) connect straight to the internet. Z-Wave and Zigbee locks (many Yale, Kwikset and Schlage models) need a hub in the property. Bluetooth-only locks require a phone nearby and are, for hosting purposes, nearly useless.
The second layer is the manufacturer's cloud or a middleware provider. Schlage, Yale, August, Nuki, TTLock and Igloohome each run their own cloud with their own API. Middleware such as Seam or RemoteLock sits in front of dozens of brands and exposes one consistent interface, which is why many PMS vendors integrate with the middleware rather than each brand directly.
The third layer is your PMS, which owns the booking data and the messaging engine. When the vendor says "smart lock integration," what they mean is that their software can ask layer two to create a code, receive it back, store it on the reservation, and merge it into a message template as something like {{access_code}}.
If all three layers are in place, the sequence for every booking is: reservation confirmed, code generated within minutes, code inserted into the check-in message scheduled for 24 hours before arrival, code active from your check-in hour, code deleted at checkout. Break any one link and you are back to the spreadsheet.
Lodgify4.5/5
Build your own vacation rental website and manage bookings from one place
From $17/moBest for: Hosts who want a direct booking website
Which vacation rental automation systems have smart lock integration?
As of writing, every major vacation rental platform supports some form of smart lock integration, but the depth and price differ sharply: Hostaway and Guesty connect the widest range of brands (Guesty through its paid Locks Manager add-on), Hospitable includes lock automation on its Professional plan at $5 per extra device, Uplisting sells it as a GBP 10 per month add-on, and Lodgify, Smoobu and OwnerRez rely on third-party connectors such as RemoteLock, Seam or Jervis rather than a native module. Here is how I would summarize the landscape for a host choosing today.
Platform
Lock integration model
Typical brands covered
Cost of the lock feature
Hostaway
Marketplace integrations, native code-in-message
Schlage, Yale, August, Nuki, Igloohome, plus RemoteLock and Seam
Included in quote; platform is quote-based, 2-listing minimum
Guesty
Locks Manager (native)
Major brands via direct and Seam connections
Paid add-on; Lite from $9/listing/mo for 1 to 3 listings, Pro on quote
Professional plan; $5 per additional device per month
Uplisting
Native smart lock add-on
Main brands via direct and middleware connections
GBP 10/mo add-on on top of plan
Lodgify
Via integrations marketplace
RemoteLock, Jervis and similar connectors
Connector's own fee; Lodgify from about $20/mo
Smoobu
Via integrations
Nuki, TTLock-based locks, connectors
Connector's own fee; EUR 29/mo Flex or EUR 35/mo Prepaid
OwnerRez
Via integrations and API
RemoteLock, Jervis, Seam-based tools
Connector's own fee; base about $88/mo, no booking fees
Hostaway is the platform I point to when someone manages more than ten doors across mixed lock brands. The integrations are two-way, the code appears as a variable in the message builder, and if a lock goes offline the task engine can fire an alert to whoever is on call. That said, you do not get a public price, you go through sales, and there is a two-listing minimum, so it is not a fit for the owner of one cabin. Our Hostaway property management review covers where the platform earns its cost. If you are at that scale, explore Hostaway and ask the sales rep specifically which lock brands are supported natively versus through Seam.
Hospitable has, in my view, the best lock automation per dollar for small portfolios. The catch is the plan: lock and thermostat automation lives on Professional, not the free Essentials tier, and each device beyond the included allowance is $5 a month. For a five-unit host that is a trivial line item compared to the ninety minutes a week from my opening story. Try Hospitable if you are under twenty units and mostly on Airbnb and Vrbo.
Lodgify takes the integration route. There is no native lock module; you connect a service such as RemoteLock, which then reads Lodgify's calendar and manages codes on its own schedule. This works, and for a host who chose Lodgify for its direct booking website it is the pragmatic path, but it means a second subscription and a second dashboard. The Lodgify integrations ecosystem article maps what connects to what. If the direct booking site is what you want and locks are secondary, start with Lodgify and budget for the connector.
Uplisting's GBP 10 per month lock add-on is refreshingly transparent and the implementation is clean. With plans at GBP 40 per month for up to four units, or GBP 16 per property on Operator, it suits lean teams in the five to fifty range. See Uplisting if you want the lock feature priced as a line item rather than buried in a quote.
Guesty's Locks Manager is capable and, on the Pro tier, connects the brands a growing manager is likely to have inherited from owners. The add-on pricing is where hosts get surprised, so read the Guesty pricing analysis and get the lock module quoted explicitly. See Guesty when you are past four listings and expect to keep growing.
Which smart locks should you buy for a vacation rental?
For most vacation rentals in North America, the best bets are the Schlage Encode or Encode Plus (built-in Wi-Fi, no hub, broad PMS support) and the Yale Assure Lock 2 with the Wi-Fi module; in Europe, the Nuki Smart Lock (which fits over an existing cylinder and is supported by most European-facing platforms) and TTLock-based keypads are the practical choices. Buy the lock your PMS supports natively, not the one with the best reviews on a retail site, because a five-star lock that only talks to your software through a workaround will eventually cost you a check-in.
What matters, ranked in the order I weigh it:
Native support in your PMS. Check the vendor's integrations page before purchase, and confirm whether the connection is direct or via Seam, RemoteLock or Jervis. Direct is simpler; middleware is fine but adds a fee and a dependency.
Wi-Fi or hub. Wi-Fi locks are easier for a single property. For a building with six doors, a Z-Wave hub with six Z-Wave locks is more reliable and kinder to batteries, because Wi-Fi radios drain them fast.
Keypad plus physical key override. You want a mechanical key slot for the day the electronics fail. Keyless-only models look sleek and create emergencies.
Battery life and reporting. Ask whether the lock reports battery level to the PMS. Hostaway and Hospitable can both surface low-battery warnings; a lock that cannot report will die silently.
Door compatibility. Retrofit models like Nuki and August work over an existing cylinder and suit rentals where you cannot replace the door hardware. Full deadbolt replacements like Schlage Encode need a standard bore.
For a deeper device-by-device look, including installation on different door types, the smart lock setup guide for vacation rentals goes into detail on hardware. This article stays on the integration side.
Guesty4.3/5
The property management platform for short-term and vacation rentals
From Custom pricingBest for: Professional property managers with 20+ listings
Once the lock is installed and registered in its own app, the PMS side takes under an hour if you do it in order. I will describe the pattern generically because the screens vary, but the logic is identical everywhere.
Step 1: Connect the lock account to the PMS. In the integrations or marketplace section of your software, authorize the lock brand (or the middleware provider). You will be sent to the manufacturer's login to grant access. If your platform uses Seam, you connect Seam once and then add brands inside it.
Step 2: Map each lock to a listing. The PMS shows a list of discovered devices; you assign "Front door, Apt 3B" to the listing for Apt 3B. Get this right, because a mismapped lock will send Apt 2A's guests a code for 3B, and that is exactly the failure you cannot detect until a guest calls.
Step 3: Define code timing. Set when a code becomes active and when it expires. My defaults are: active from your published check-in time minus 60 minutes (early arrivals waiting in a hallway are the single most common support message), and expiring at checkout time plus 60 minutes. The buffer costs nothing and prevents the edge cases.
Step 4: Choose the code format. Some integrations let you generate a random code, others let you use the last four digits of the guest's phone number. I prefer the phone digits: guests remember them, and it removes one item from the message. Random codes are more secure in theory, but a code that lives three days and is then deleted does not need to be; memorability wins.
Step 5: Insert the variable into your check-in message. Open the scheduled message that goes out 24 hours before arrival and add the code variable. Write the sentence so it still reads correctly if the variable is empty ("Your door code is {{access_code}}. If you do not see a code above, reply to this message and we will send it immediately."). That one line is your safety net for an API failure.
Step 6: Add a backup code and a backup message. Every lock should have a permanent owner code known only to you and your cleaner, plus a second scheduled message at check-in time that repeats the code. If you are also looking at how to structure the whole arrival sequence, the guide on sending automated check-in instructions covers the timing and wording that reduce guest questions.
Step 7: Test with a real booking. Create a manual reservation for yourself, tomorrow, and walk through it. Check that the code appears on the reservation in the PMS, that it shows in the message preview, that it opens the door at the scheduled time, and that it stops working after the expiry. Hosts skip this step constantly. Do not.
What can go wrong with smart lock automation, and how do you prepare?
The most common failures are a lock that drops off Wi-Fi so the code never syncs, a dead battery, a booking modified after the code was generated (a guest extends by a night and the code expires mid-stay), and a PMS-to-lock connection that silently lapses when a password changes. None of these is rare; over a year with ten doors you should expect several. The goal of a good setup is not zero failures but zero failures the guest notices.
Here is the mitigation list I give every host I set up.
Wi-Fi drops are the top issue with Wi-Fi-native locks, particularly in older buildings where the router is far from the door. Put a mesh node within a few meters of the lock, or switch to a Z-Wave hub. Most PMS integrations show an "offline" status; Hostaway can trigger a task from it, and Hospitable surfaces device status in its smart devices view. Check it weekly until you trust it.
Batteries fail predictably. Wi-Fi locks last three to six months on a set of AAs; Z-Wave locks often a year. Put a calendar reminder to replace batteries every quarter regardless of the indicator, and keep a spare set inside the property for your cleaner.
Booking changes are the sneaky one. If a guest extends, the PMS should regenerate or extend the code automatically. Most modern integrations handle this, but older connector setups may not. Test it: extend your own test booking by a day and confirm the code still works on the new final night.
Connection lapses happen when someone changes the lock brand's account password, or when an OAuth token expires. Your only defense is the empty-variable safety line in the message and a habit of checking the integration status page after any account change.
Finally, keep the physical key handy. Not in a lockbox you have given up on, but somewhere a local contact can reach it in ten minutes. The contactless check-in technology guide has a fuller section on backup plans, and it is worth reading before you remove the last keybox.
Hospitable4.4/5
Automate your vacation rental business
From $29/moBest for: Hosts who want maximum automation
Do smart locks pay for themselves in a vacation rental?
For a host managing three or more units, a PMS-integrated smart lock typically pays for itself within the first few months by removing key handovers, lockbox resets and code administration that add up to roughly one to two hours per unit per month, and by eliminating the after-hours calls and refunds that follow an access failure. The math is straightforward even with conservative assumptions.
Take a modest example. A Schlage Encode costs a bit over two hundred dollars installed. The software side on Hospitable's Professional plan adds $5 a month per extra device; on Uplisting it is GBP 10 a month flat. Against that, a host with five units who spends ninety minutes a week on code logistics, as in my Lisbon example, recovers around six hours a month. Value that time at whatever you charge for your own labor and the hardware is paid back in a quarter, with the recurring software cost covered many times over.
The less visible return is the failure you no longer have. One botched check-in tends to produce a refund request, a one-star review on cleanliness or communication that has nothing to do with either, and a day of anxious messaging. Removing the manual step removes the class of error. That is the argument for doing the integration properly rather than just buying the lock.
Once locks are connected, the same integration usually opens the door to cleaner codes that rotate with turnovers and thermostat schedules that follow bookings; the complete vacation rental automation guide shows where locks fit in the larger stack.
Practical recommendations by portfolio size
My advice is shaped by how many doors you manage, because the right software is different at each scale and the lock is the easy part.
If you run one to four units, buy a Wi-Fi lock your platform supports directly, and choose software where the lock feature is included or a small line item. Hospitable's Professional plan with $5 per extra device is my default recommendation for hosts on Airbnb and Vrbo, and its free Essentials tier lets you set up the messaging first and add the lock plan when you are ready. Try Hospitable. If your priority is a direct booking site and locks are a secondary concern, Lodgify plus a RemoteLock-style connector is a workable pair.
At five to fifteen units, transparency on pricing starts to matter and you probably have mixed lock brands. Uplisting's GBP 10 per month lock add-on on top of its Operator plan keeps the cost legible; see Uplisting. Guesty Pro with Locks Manager is the alternative if you expect to keep growing and want the widest brand coverage, with the caveat that the add-on is quoted; see Guesty.
Past fifteen units, or the moment you manage for owners who have already installed whatever lock they liked, Hostaway is the platform I would put the integration on. The task engine, the offline alerts and the breadth of native and Seam-connected brands are built for exactly that mess. Explore Hostaway and go into the sales call with your list of lock models in hand.
Whatever you choose, do the test booking. The host in Lisbon did, eventually, and has not touched a code in a year.