J-BSSJ-BSS
Products ↳ Video Intercom ↳ Smart Locks ↳ Access Control Solutions ↳ Apartments & MDU ↳ Serviced Apartments ↳ Offices ↳ Villas ↳ Government ↳ Co-Working Markets ↳ Middle East ↳ Europe ↳ United States ↳ Saudi Arabia OEM & ODM↳ White Label App↳ Certification Support Distributor Program Case StudiesInsights Request a Quote
Short-term rental access planning

Set access rules for every stay, from check-in to checkout.

For short-term rentals, access should follow the stay, not the property. Set guest credentials, permitted doors, exception ownership and checkout expiry before selecting hardware.

01 / BOOKING

Confirm the Booking

Review stay dates, guest role, permitted doors and the credential window.

02 / GUEST STAY

Manage Arrival and Service

Keep guest, host, cleaning and maintenance access distinct throughout the stay.

03 / CHECKOUT

Close Access at Checkout

End the guest credential under the checkout rule before turnover begins.

Turnover access rules

Three decisions shape the access plan.

For short stays, access must be clear at booking, controllable during the stay and closed before the next arrival.

01

Stay Setup

Set the stay dates, permitted doors and credential expiry before issuing access.

Stay setup
02

Exception Ownership

Assign who can change an arrival time, replace failed credentials or authorise service access.

Exceptions
03

Checkout Closure

Define when guest access ends, who confirms it and what handover record is needed.

Checkout

Information needed to scope a short-term rental deployment.

A clear operating brief avoids a generic feature list and keeps hardware selection tied to the property.

PROPERTY MAP

Unit and Door Inventory

List guest entries, shared doors and any routes that need different permissions.

ACCESS POLICY

Role and Credential Policy

Define who needs access, the approved credential type and the fallback method for each role.

BOOKING INPUT

Booking and House Rules

Share stay dates, arrival and departure rules, permitted doors and property instructions.

Confirm the turnover model before selecting hardware.

Share the property layout, role rules and checkout policy to receive a deployment brief tailored to your operation.

Request a Scope Review

Smart Lock for Airbnb &
Short-Term Rental Operators

Time-limited guest PIN codes · Tuya app remote management · booking workflow API integration · multi-property dashboard. CE and FCC certified. OEM wholesale from MOQ 200 units.

⏱ Time-Limited PIN Codes 🔌 booking workflow API Integration 🏠 Multi-Property 🌍 Global Market
booking workflow & Channel Integration
Lodgify Hostaway Guesty Smoobu Zapier Tuya IoT API
100
PIN Codes per Lock
Properties per Account

How It Works for Property Managers

Zero key handoffs. Zero site visits for check-in. Complete audit trail.

1
Booking Confirmedbooking workflow creates a time-limited PIN via Tuya IoT API — valid only during the guest's exact check-in and check-out times.
2
Guest Receives PINPIN delivered automatically by booking workflow message template. Guest uses PIN on arrival — no app download required.
3
Access During StayGuest uses PIN or optional Bluetooth (Tuya app). Manager sees all access events in the management dashboard.
4
Automatic ExpiryPIN expires at the programmed check-out time. Lock auto-re-secures. No action required from the manager.
5
Manager Reviews LogFull access event log available in the app: when the door was opened, by which PIN, and how many times.

Key Features for STR Operators

Designed for the operational realities of managing 1 to 500+ short-term rental properties.

Time-Limited PIN 100 independent codes per lock, each with custom validity window
📱
Remote Management Generate/revoke codes instantly from anywhere via Tuya app
🏠
Multi-Property Manage unlimited properties from one account with role-based access
🔌
API Integration Tuya IoT Open API connects to any STR booking workflow with webhook support
🔋
12-Month Battery Low battery alerts via app before failure. Emergency USB backup port
📋
Audit Trail Complete event log: who opened the door, when, and with which credential

OEM Opportunity: STR Smart Lock Brands

The short-term rental market (Airbnb, Vrbo, Booking.com) represents over 1.5 billion accommodation nights annually. Property management companies (PMCs) managing 20+ properties are the high-value B2B buyers — they need reliable, remotely manageable locks at volume pricing. This is the OEM opportunity.

🏷 White-Label Brand

Your lock brand name, logo on hardware, branded app (iOS + Android), and custom packaging. PMCs in the US, UK, and Germany actively seek a supplier that brands specifically for the STR market.

MOQ 200CE + FCC

🔌 Embedded Software OEM

If you are building a STR rental operations platform, Trudian provides the Tuya IoT API integration guide and sample code so your platform can control Trudian-hardware locks under your platform brand.

API accessUnder NDA

📦 B2B Wholesale

Stock our CE/FCC certified smart locks under your brand or the Trudian label and supply directly to rental operations companies in your region. Exclusive territory available for qualifying distributors.

MOQ 200Exclusive territory

Regional Compliance for STR Markets

🇪🇺 Europe
CE REDUKCARoHS 3

CE marking required for EU market supply. DoC and test reports provided. GDPR: on-device access log storage — guest data stays at the property, not in a Chinese cloud.

🇺🇸 United States
FCC Part 15ANSI/BHMA G2

FCC Part 15 required. ANSI/BHMA Grade 2 mechanical standard. Suitable for all US residential STR properties. HOA documentation package available.

🌙 GCC / Middle East
SASOArabic UI+60°C

SASO CoC for KSA. Arabic app available. Operating range to +60°C. High demand from Dubai, Riyadh, and Jeddah short-term rental operators serving Vision 2030 tourism growth.

Supply Smart Locks to the Short-Term Rental Market

CE · FCC · SASO certified. Time-limited PIN. Tuya IoT API. White-label available. MOQ 200. Tell us your target market and volume — we respond within 24 hours.

Request Wholesale Quote OEM Program
FAQ

FAQ — Smart Lock for Short-Term Rentals

The manager creates a time-limited PIN valid only during the booking dates and times via the app or booking workflow API. The guest uses the PIN to enter — no app download required, no key handoff, no in-person meeting. The PIN expires automatically at checkout. All access events are logged in the management dashboard with timestamp, door, and credential type. The entire guest access lifecycle is managed remotely without the rental operator needing to visit the property.

Via Tuya IoT Open API, the lock integrates with Lodgify, Hostaway, Guesty, Smoobu, and any platform supporting Zapier or native webhooks. When a booking is confirmed, the booking workflow automatically generates a time-limited PIN and delivers it to the guest via SMS or email — zero manual intervention from the rental operator. For operators using TTLock-based locks, direct booking workflow integrations with additional platforms are available. Custom booking workflow integration documentation is provided to OEM and wholesale partners under NDA.

The manager generates a new PIN remotely in under 30 seconds via the mobile app — no site visit required. The old PIN is simultaneously revoked. Bluetooth unlock from the manager's smartphone is available as an emergency option for managers within Bluetooth range. For properties managed by a remote team, the management platform supports role-based PIN generation — front desk or support staff can generate replacement PINs without full admin access to the property's other settings.

Yes. Unlimited properties per account. Each property appears as a separate home with its own device list, access log, and PIN management. For operators managing 50 or more properties, the Tuya IoT platform provides a full API and web dashboard with role-based access for staff members managing specific properties or regions. Bulk PIN generation, cross-property reporting, and automated booking sync are all available at scale. For professional conciergerie businesses managing 100 or more properties, contact our B2B team for enterprise platform pricing.

Yes. CE marking (RED 2014/53/EU, RoHS 2011/65/EU) for EU27, UKCA for UK, FCC Part 15 for USA, and RoHS 3 compliance. SASO CoC available for Saudi Arabia and GCC market supply. Full compliance documentation package included with distributor orders — Declarations of Conformity, test reports, and regional approval certificates. For PSTI Act 2022 compliance in the UK (mandatory for consumer IoT devices from April 2024), documentation confirming unique default passwords, vulnerability disclosure policy, and minimum security update period is provided.

PIN codes and RFID card credentials are stored locally on the lock hardware — they do not require WiFi or cloud connectivity to function. Guests can continue entering with their PIN during WiFi outages without any interruption. WiFi is only required for remote management functions: generating new PINs, revoking PINs remotely, syncing access logs to the management platform, and receiving firmware updates. For properties in areas with unreliable internet, ensure guests are provided with their PIN at booking confirmation — not dependent on a real-time app delivery at check-in.

Three OEM tiers for STR market operators: white-label brand (your logo on hardware, branded packaging, white-label app in App Store and Google Play — MOQ 200 units), embedded software OEM (integrate our lock API directly into your existing STR management platform under your brand — no separate app required, MOQ 500 units with API license), and B2B wholesale (distribute under Trudian brand to your network of rental operators — MOQ 50 units, fastest time to market). For STR software platforms seeking to add hardware as a product line, our embedded API model allows you to offer smart lock functionality within your existing app without building hardware or separate firmware.

FAQ

Short-Term Rental Access: Common Project Questions

The operator confirms the stay dates, permitted doors and access window, then issues the guest credential. The credential closes under the checkout rule agreed for the property.

Assign a responsible host or operator for changed arrival times, replacement credentials and urgent service access. The same plan should state the approved fallback method and the record required after the exception is resolved.

Cleaning, maintenance and host access should use separate credentials and defined time windows. This keeps a guest credential from becoming an open-ended property key.

Offline behaviour depends on the selected lock and credential method. Confirm local access options, credential availability and the limits of remote changes for each property before procurement.

Provide the property map, door count, user roles, credential policy, number of properties and typical turnover schedule. This lets the project team recommend hardware and commercial terms against the actual operating model.