Why GuestsKey Over PMS-Native Lock Automation

If you host on Hospitable, OwnerRez, or Lodgify, you've probably seen the smart-lock feature buried in the settings somewhere and thought what every host thinks: "great, my PMS does this — one less vendor to deal with." The promise is real and it's tempting. One bill. One support team. One dashboard. Whatever guest code your PMS schedules, it's right there in the same interface you already use to message the guest and check the calendar.

I'm going to argue you should think harder about that toggle before you flip it. And I'm going to do it from a position you might not expect: GuestsKey is an official OwnerRez partner and an official Hospitable partner. We're plugged into the same product directories as the PMS-native features I'm about to critique. If anyone in this space has a conflict of interest pointed at being kind to PMS-native lock automation, it's us.

We're not being kind to it anyway, because the math doesn't work out for most operators. Here's the honest case.

What "PMS-Native" Actually Means in May 2026

Before we critique it, let's be specific about what each PMS actually ships:

Hospitable. Native smart-lock automation, gated behind the Professional ($59/mo) and Mogul ($99/mo) plans. If you're on Essentials (free) or Host ($29/mo), the feature is invisible to you — you can't even see the toggle. Professional includes 2 devices per property with $5 per extra device; Mogul includes 4. Hospitable's own supported-locks list is wide: Schlage, Yale, August, SmartThings, Nuki, igloohome, Kwikset, and KeyNest — so SmartThings hub locks (Z-Wave, Zigbee) are covered, with Hospitable noting that SmartThings codes are sent about 30 minutes before activation.

OwnerRez. Three OwnerRez-powered integrations that carry a per-lock fee, each $4 per lock per month as of August 2026 (OwnerRez's Costs and Fees page): Schlage (the Wi-Fi Encode family), igloohome, and Hubitat — a Zigbee/Z-Wave hub that OwnerRez itself says is "only recommended to users who are comfortable with such technology," needs a Hubitat Elevation C-7 or newer plus Hubitat's Remote Admin subscription, and must be online at check-in for codes to land (OwnerRez's Hubitat article). Beyond those three, a directory of other lock systems OwnerRez does not bill per lock, including RemoteLock and GuestsKey. Want a Yale Assure on a SmartThings hub? Outside the native footprint — Hubitat is a different hub. Want a Lockly or a Wyze? Not on any of the three lists. (An Ultraloq U-Bolt Pro is, but only its Z-Wave variant, paired to a Hubitat hub.) And OwnerRez allows only one lock system per property.

Lodgify. A paid Smart Locks add-on (~$7/device/month) layered onto your Lodgify PMS subscription. Supported lock brands as commonly cited are Nuki, 4Suites, August, and Samsung SmartThings — the narrowest list of any option here. Verify the current brand list and pricing with Lodgify before committing.

That's the PMS-native landscape. Three products, three different shapes, one shared pitch: "it's already in your PMS, so just use it."

Why "Free" Isn't Really Free

The strongest argument for PMS-native is the price tag. Two of the three options here have an asterisk on that:

• Hospitable's automation isn't free if you're not already paying for Pro. Hospitable Professional starts at a meaningful upcharge above their Host and Essentials tiers. If the only reason you're upgrading is to unlock the lock feature, you're not paying $0 — you're paying the price of a plan upgrade. Compare that against a focused tool's per-lock cost and the math gets a lot less obvious.
• OwnerRez native is a paid per-lock add-on on top of your OwnerRez subscription: $4 per lock per month for Schlage, igloohome, or Hubitat, and on the Hubitat and igloohome paths a second vendor fee on top. Per-lock economics in the same neighborhood as a dedicated tool, with three integrations to choose from, one of which is a hub you administer yourself. You're paying similar money for less flexibility.
• Lodgify Smart Locks is a paid add-on, around $7/device/month, on top of your Lodgify PMS subscription. It's not bundled — it carries its own per-device fee in the same per-lock economics neighborhood as every other option here, with the narrowest lock-brand list.

That means the "free with your PMS" framing is misleading for all three of these vendors when examined closely. Hospitable's lock automation requires the Professional plan (a paid upgrade). OwnerRez native is a per-lock add-on. Lodgify is a per-device add-on. The only "free" is the Hospitable Professional/Mogul user who'd already paid for that plan and would treat any included feature as no marginal cost.

The Six Places PMS-Native Breaks Down

Here's where the gap shows up for working operators. Every one of these is something we hear about in support tickets from hosts who tried PMS-native first.

1. Brand Lock-In

This is the biggest one and the least obvious until you've already bought the wrong hardware.

• OwnerRez native = Schlage Encode, igloohome, or a Hubitat hub. Buy a Yale Assure 1 on a SmartThings hub because that's what's in your existing property? OwnerRez native can't drive it: its hub path is Hubitat, an advanced-user option by OwnerRez's own description, and a property can use only one lock system.
• Hospitable native = Hospitable's partner list. Schlage, Yale, August, SmartThings, Nuki, igloohome, Kwikset, KeyNest — a genuinely wide list that does include Z-Wave and Zigbee locks on a SmartThings hub. Brand lock-in is the weakest argument against Hospitable native; the real gaps are the plan gate (Host and Essentials get nothing) and the workflow gaps covered below.
• Lodgify native = 4 brands. Nuki, 4Suites, August, SmartThings. If your lock isn't in that list, you don't have a native path.

GuestsKey covers both the SmartThings world (Yale Assure 1, Schlage BE469, Kwikset 914/916, older Z-Wave and Zigbee locks on a SmartThings hub) and the Seam world (Schlage, Yale, August, Kwikset, Lockly, igloohome, TTLock, and dozens of others). A host with mixed hardware across a portfolio — which is most multi-property operators after a few years — can drive every lock from one dashboard. PMS-native automation forces you to either standardize your hardware to match the PMS's supported list, or carry multiple tools.

2. No Cleaner, Owner, Vendor, or One-Time-Key Workflows

PMS-native lock automation handles guest codes. That's the entire scope. Cleaner codes, owner codes, maintenance vendor codes, one-off delivery access — none of that is in the native product.

If your cleaner comes Tuesdays and Fridays, you have a recurring access problem that PMS-native doesn't solve. You'll end up texting the cleaner a permanent code, or rotating manually, or buying a second product to handle just that one thing.

GuestsKey has cleaner code automation with recurring schedules and a dedicated slot (slot 99) that never collides with guest codes. One-time keys for vendors and deliveries. Owner codes for the property owner. The full lifecycle is in one tool because that's what the tool is designed around.

3. No Shared-Lock / Multi-Listing Support

A duplex with a shared exterior front door and two separate suites behind it has one physical lock. You list Suite 1 and Suite 2 separately on Airbnb. Each has its own bookings, its own guests, its own check-in times.

PMS-native automation generally assumes 1:1 listing-to-lock. OwnerRez's property mapping is the exception on paper: it allows one lock across several properties and documents a Common Doors setup for a shared exterior door (Door Locks overview). The hard part is what happens next, when two listings' bookings want a PIN on the same physical device: codes collide, the lock's duplicate-PIN protection kicks in, and something has to reconcile them.

GuestsKey handles this natively, including the magic case where the same phone number books both suites — the code is generated once, adopted for both bookings, and lives on the shared front door for the combined stay. We wrote a whole post on this: How to connect an Airbnb property to GuestsKey. If you run a duplex, a fourplex, or a small inn, this is the difference between a working integration and an evening of debugging.

4. No Proactive Emergency-Backup Layer

When the lock goes offline, when the SmartThings hub loses Wi-Fi, when the Seam connection drops, when the Z-Wave network has a glitch — PMS-native automation generally finds out the same time you do: when the guest calls.

On properties where you've turned on the emergency backup layer (it's opt-in, off by default), GuestsKey runs two automatic checks before every check-in: a lock-health check 15 minutes out, and a code-verification check 5 minutes out, after the guest code activates at 10 minutes out. If either fails, the guest is emailed a backup code and you're notified, so the guest gets in and you know what to fix. The feature is still labeled Beta on our features page, and we're being honest about that — it's still maturing — but the architecture is in place and it catches problems before they become guest complaints.

PMS-native automation doesn't have a layer like this and isn't planning to build one. It's not their core product, so it's not where their engineering investment lives.

5. Repeat Guests Get Locked Out

This one is specific to OwnerRez's native Schlage integration and it's a failure mode we've watched play out in real customer migrations. OwnerRez native derives guest codes from booking data (often the last 4 of the guest phone) and writes them straight to the Schlage. When a repeat guest books a second stay and the derived code is the same code they had last time, Schlage's duplicate-PIN protection rejects the write — and the guest arrives at a door their old code no longer opens and their new code was never set on.

One of our largest customers — a 50+ property manager — came to us after this exact pattern. She'd left RemoteLock for OwnerRez+Schlage native to escape RemoteLock's hardware-and-software friction, then started getting locked-out repeat guests because the duplicate-code case wasn't gracefully handled. GuestsKey handles this case: when a derived code would collide, we detect it, rotate to a different slot or regenerate, and write the working code to the lock without losing the previous reservation's access window. It's the kind of edge case that's easy to dismiss until it's happening to a guest standing in your driveway in the rain.

6. PMS Lock-In Destroys Portability

This is the long-tail risk most hosts don't think about until they hit it.

If you build your lock automation inside Hospitable and decide two years from now to switch to OwnerRez (or vice versa), you are rebuilding from scratch. Different lock-brand list, different settings, different workflow, different support. The investment you made in setting up codes, mapping locks to listings, training cleaners on the system — it doesn't come with you.

GuestsKey rides on top of whichever PMS you use. Switch PMSs and the GuestsKey side keeps running with the new PMS plugged in as a data source. The lock automation, the cleaner schedules, the one-time keys, the historical code data — all of it is portable because it lives in a tool whose job is locks, not in a tool whose job is bookings.

When PMS-Native Is Actually the Right Answer

Now the part we have to be honest about, because the rest of this post is worthless if it reads like a hatchet job.

There are three scenarios where PMS-native is a perfectly sensible call, and we'll tell you to use it:

1. You're a Hospitable Professional/Mogul subscriber already. One property. One keypad lock on Hospitable's supported list. One Airbnb listing per door. No cleaner code needs (or the cleaner uses a permanent code you don't mind sharing). Hospitable native works fine here. You're paying for Pro anyway. Use what's included.

2. You're an OwnerRez user with one Schlage Encode (or an igloohome, or a Hubitat you already run) at one property and zero appetite for adding vendors. OwnerRez's $4-per-lock add-on fee is the cost of simplicity. If you'd rather pay that than learn another tool, that's a reasonable trade. We'll be here when you grow into a second property or buy a different lock brand.

3. You're brand-new on Lodgify with no portfolio yet, one Nuki or August lock on the supported list, and you just want guest codes working. The Lodgify Smart Locks add-on (~$7/device/month) is workable until you outgrow it — and at one device the per-lock economics are the same neighborhood as a dedicated tool, so the deciding factor is "stay inside Lodgify" vs. "carry a separate tool."

GuestsKey isn't the right tool for everyone, and pretending otherwise wastes your time and ours. If you fit one of those three profiles cleanly, the honest recommendation is to flip the toggle in your PMS and not think about it again until your situation changes.

What we see in support tickets is that most operators don't fit those profiles cleanly. They have a cleaner. Or a duplex. Or a Yale Assure 1 on a SmartThings hub that OwnerRez's native option can't see. Or they're on Hospitable's Host plan and the native feature is gated behind an upgrade. Or they've got mixed hardware across five properties because they bought what was on sale at different times.

For those operators, PMS-native is the wrong tool for the job.

What GuestsKey Looks Like Instead

One paragraph, no sales pitch.

GuestsKey is a dedicated smart-lock automation platform built for short-term rental operators. It covers SmartThings (Z-Wave, Zigbee) and Seam (Schlage, Yale, August, Kwikset, Lockly, igloohome, TTLock, and more). It handles guest codes, cleaner codes, owner codes, one-time keys, and shared-lock multi-listing setups. It runs proactive backup health checks before check-in. It's an official partner of both OwnerRez and Hospitable, it integrates directly with Lodgify, and Airbnb-only hosts can onboard for free via Hospitable Connect without buying a PMS subscription. Pricing is transparent on our site: SmartThings starts at $4/lock/month (scaling down to $2 at portfolio sizes), Seam starts at $5/lock/month (scaling down to $3). Fourteen-day free trial; a credit card is required to start, and you can cancel before it ends to avoid charges.

That's the whole pitch. No bundle math. No "free with another plan." No vendor lock-in to a PMS you might switch away from.

The Honest Takeaway

If you're on Hospitable Pro with one lock and one listing, use Hospitable's native automation. We won't try to sell you a tool you don't need.

If you have a cleaner, a duplex, mixed lock hardware, a SmartThings hub, a portfolio that crosses PMSs, or any other operational complexity that the simple "one lock, one listing, one PMS" model breaks on — you're going to outgrow PMS-native automation, and the question is whether you outgrow it before or after a guest has a bad check-in.

The post that compares us to the rest of the dedicated tools, not just the PMSs, is here: The 2026 STR Smart Lock Automation Platform Comparison. It covers every dedicated competitor in our category, treats GuestsKey with the same honest-weaknesses lens, and ends with a decision matrix that tells you what to use based on your situation — including the cases where the answer isn't us.

You can start a 14-day GuestsKey trial at guestskey.com — a credit card is required to start, and you can cancel before the trial ends to avoid charges. If you're an Airbnb host without a paid PMS, the onboarding guide is here: How to connect an Airbnb property to GuestsKey.

Originally published May 2026; Hospitable and OwnerRez corrections added August 2026 (see the note above). Pricing and feature availability for third-party products are as of May 2026 — verify with the vendor before making a purchase decision.