Booking platforms do not talk to your door lock. Not Airbnb, not Booking.com, not directly. Every automated check-in setup in Dubai runs through something in the middle that holds the reservation and tells the lock what code to accept and for how long. Once you know that, the choices get clear, and most operators with fewer than about five units should not automate at all. This article is about the plumbing, not about which lock to buy.
The three tiers, honestly
Manual, per booking. You get the reservation, you create a code valid for the stay dates, you message it to the guest. Two minutes per booking. For one to four units this is genuinely the right answer, and operators who skip straight to automation at this scale usually spend more on software than they save in time.
Booking platform, then channel manager or PMS, then lock. The middle system already holds your reservations for calendar sync and pricing. It calls the lock platform and creates a code for the stay window automatically. Guests get it in their check-in message. This is where most professional Dubai operators sit once they pass roughly five to ten units.
Custom build. Your own software holds the bookings and issues the codes. Only worth it if you already have a platform for other reasons.
The jump that matters is from one to two. It is not a hardware upgrade, it is a subscription and a configuration afternoon.
What the middle layer is actually doing
Four things, and it helps to name them because this is what you are evaluating when you compare tools.
It reads the reservation, so it knows the guest, the check-in date and the check-out date. It creates a credential valid for exactly that window, usually with a buffer, opening a few hours before check-in and expiring a few hours after check-out. It delivers the code to the guest, normally inside the message the platform already sends. And it cleans up, so the code stops working when the stay ends rather than living on the lock forever.
That last one is the whole point. The security value is not the automation. It is that access expires without anyone remembering to remove it.
The two mechanisms, and why the difference bites
Codes come in two flavours and they behave differently when something goes wrong.
A calculated code is worked out by an algorithm the lock already knows. Your system can generate one without any connection to the door at all, and it will work on a villa in a poor-coverage pocket of Al Furjan or a basement-level apartment. The tradeoff is that you cannot cancel it early. It dies when its window ends and not before.
A pushed credential is sent to the lock over the internet. You can revoke it in seconds. The tradeoff is that it needs a gateway plugged in near the door and a live connection at the moment you issue or cancel it.
For normal bookings, calculated codes are the safer default because they survive a Wi-Fi outage on turnover day. For a cancellation, a dispute, or a guest who has to be removed mid-stay, you need the pushed kind. Serious operators run both.
What breaks in practice
The gateway loses power and nobody notices. A cleaner unplugs it, a socket gets switched off at the wall, and the unit goes silent. Bookings still work if you are on calculated codes, which is the argument for them, but you lose live logs and remote control. Check gateway status as part of your turnover checklist, not when a guest complains.
Date and time zone drift. A code that starts at 15:00 in the wrong time zone starts at 11:00, and a guest is standing outside a locked door in August. Confirm the lock clock and your middle system agree on Gulf Standard Time, and confirm it again after any firmware update.
Early arrivals. A guest lands at 06:00 from a long haul and their code starts at 15:00. This is not a technical fault but it generates most of your check-in messages. Build a buffer, and give your team a way to extend a window from a phone.
Ownership of the account. If a property manager set up the locks under their own account, you do not control your own doors and you will discover it when you change managers. Make sure the master account is in the owning entity’s name.
The UAE-specific parts
Holiday home operation in Dubai is licensed, and DTCM rules cover guest registration and how you run the unit. Automated door codes do not change any of that. Verify current requirements with DTCM directly, because they are updated and no supplier should be your source of truth on licensing.
Multi-property structure is worth setting up correctly on day one. One master account owned by your company, with per-property access for the staff and cleaners who need it, and per-building groups if you run several units in the same tower. Retrofitting that structure across twenty units already registered on four different phones is a bad week.
And connectivity varies more than people expect. A villa in a mature community with fibre behaves differently from a new-handover apartment where the router is whatever the previous tenant left. If the unit does not have reliable internet, build on calculated codes and stop trying to make live control work.
When not to automate
If you run one or two units, automation costs you a monthly fee and a system to maintain in exchange for saving four minutes a week. Do it manually.
If your units have no reliable internet and you cannot fit a gateway, most of the live benefits disappear. Use calculated codes manually and skip the middle layer.
If you are about to change booking platforms or property manager, wait. Building the integration and then migrating it is doing the job twice.
Where Altix comes in
We supply and install the locks and gateways across the UAE, and we set the account structure up in the owning company’s name at handover so you are not locked out of your own portfolio later. We are not a channel manager and we do not sell booking software, so we have no reason to push you up a tier you do not need.
What we do bring is the deployment pattern for a UAE portfolio: which code mechanism suits which unit, how to group properties so cleaners and managers get the right access without holding the master account, and where connectivity will let you down before you build a workflow that depends on it. That saves most operators one expensive restructure.
If you are running holiday homes and want a straight answer on whether automating is worth it at your unit count, message us on WhatsApp. The first read costs nothing.
Frequently asked questions
Can Airbnb send a code to my lock directly?
No. There is no direct connection between the booking platform and the lock. Something in the middle, usually your channel manager or property management system, has to hold the reservation and create the code.
Will the code still work if the internet is down?
If it is a calculated code, yes, because the lock validates it on its own. A pushed credential needs the connection at the moment it is issued or revoked.
Can I cancel a guest’s access early?
Only for pushed credentials on a connected door. A calculated code runs until its window closes. If early cancellation matters to you, say so before you choose your setup.
How many units before automating is worth it?
Around five to ten in our experience. Below that the manual route is faster than maintaining the integration.
Do I need a different lock for this?
Usually not. Most app-controlled locks sold here support time-limited codes already. The gap is more often the gateway and the account structure than the lock itself.
Altix supplies, installs and configures smart locks for holiday homes and serviced apartments across the UAE, and hands the master account to the owner. Tell us your portfolio size on WhatsApp.
