The booking engine is the product, not the design
The vendor's description treats Nuss as a front end for a companion booking system. Uxper Booking supplies real-time availability, flexible pricing, room management and online reservations; Uxper Metabox and Elementor appear in the same supported-plugin list. If you are choosing Nuss, the question is less whether you like the demo's look and more whether your property's rules fit what that booking layer can express.
That distinction matters because a hotel site that cannot answer "is this room free from Thursday" is a brochure. Everything downstream — search, room detail pages, checkout — depends on the booking data being correct.
Calendar sync with Airbnb and Booking.com, and the work it has needed
The vendor states the theme supports calendar synchronisation with Airbnb and Booking.com. The point is familiar to anyone letting rooms on more than one channel: a booking taken elsewhere should remove those nights from your own availability, and vice versa.
The changelog shows this is the part of Nuss that has taken repeated attention. Version 1.1.5 updated the iCal sync calendar; 1.3.2 fixed the export sync URL in the iCal Sync tab and added a filter to the Blocked tab; 1.3.8 fixed booking calendar synchronisation; 1.4.1 fixed booking status problems arising during iCal sync. Read as a group, those entries describe a feature that works but has had real edge cases around status and exported feeds. If channel sync is central to your operation, test a two-way exchange with your actual channel accounts before relying on it.
Seasons, blocked dates and rooms that should not appear
Two rules in the changelog describe how availability is modelled. Version 1.1.2 made it possible for a single reservation to apply to multiple seasons, and changed blocking so that blocking one date blocks it from check-in. A long stay across a rate change, or a maintenance block that silently left the previous night bookable, are exactly the situations small properties trip over.
Version 1.3.0 added a new room blocked system, and 1.3.1 fixed a blocked room still showing when availability was checked. That last one is the failure that matters most: a room that appears available but is not produces a reservation you have to cancel.
Pricing levers: seasons and headcount
Pricing is seasonal according to the vendor's flexible-pricing description, and the change history fills in the detail. Version 1.3.7 added a discount based on the number of people, so a rate can respond to occupancy rather than room alone. The same release fixed an error when a room price was entered as 0 — relevant if you take enquiries for a room whose rate is quoted on request.
Correct display took longer to settle: 1.3.3 corrected room pricing based on season in search results, and 1.3.6 fixed seasonal prices on the room details page. Both fixes concern the same problem from two angles — the price a visitor sees in the listing matching the price on the room they open — so a current copy should be quoting seasonally adjusted rates consistently. Earlier releases also touched season price and reservation booking display, and minimum and maximum stay lengths per room.
Booking runs over AJAX, and 1.4.0 was the security release
Searching rooms, calculating a price and adding to cart in Nuss are AJAX requests, and version 1.4.0 is best read as a hardening pass on those endpoints. The entry records fixes for security vulnerabilities in the AJAX requests for booking, price calculation and add-to-cart; missing nonce verification in the booking print feature (booking_print_ajax); nonces attached to all AJAX requests in room.js and template.js; improved input sanitisation; and nonce authentication added to all booking-related AJAX endpoints.
A later release, 1.3.7.1, is listed only as a security fix. Version 1.4.1 also reworked template URL escaping and external link security in 1.4.2. The practical takeaway is not alarm but version selection: booking routes handling guest data and prices warrant running a build that includes the 1.4.0 work, and the changelog is where to confirm it.
Where layout and payment sit
Pages are assembled in Elementor, with Elementor Pro named in the marketplace compatibility list, and the theme is built on Bootstrap 5.x. WooCommerce handles the money: the changelog records Woo templates updates, a related Woo Order ID shown on the booking table, and a Woo Order ID added to the email template. Checkout and payment-completed pages are selected in Theme Options rather than assumed.
WooCommerce compatibility is declared across 5.x through 8.x. Elementor has its own trail: version 1.3.4 fixed a break when the Elementor plugin was updated to 3.26 or higher, and 1.1.4 moved slider widgets to Swiper 8 and fixed Elementor lazy loading preventing images from showing in Chrome. Before a theme switch, check what happens to an existing Elementor-built page against the version you install.
Gutenberg optimisation is marked No in the listing. That records the vendor's declared focus on Elementor; it does not mean the block editor cannot be used.
What the listing declares
Observed on 4 November 2026, the marketplace attributes list WordPress 5.4.x through 7.0.x, browsers as Firefox, Safari, Opera, Chrome and Edge, and the theme as responsive, widget ready, high resolution and well documented. Files include PHP, CSS, SCSS and JS. Translation support appears in the change history as optimisation for WPML, Polylang and similar plugins, and a 2021 release added an RTL demo.
Those are vendor and listing declarations, not results from your server. They are useful for a first filter and not a substitute for running a test booking — search, price, reserve — on a staging copy with your PHP version and plugins in place.
Questions & answers
Do I need WooCommerce to take bookings with Nuss?
The vendor's supported-plugin list includes WooCommerce, and the changelog refers to Woo templates, Woo Order IDs on the booking table and Woo Order IDs in email templates. That makes WooCommerce the payment path described for the theme. Withholding booking without payment is a separate question — the changelog mentions an "Auto Booking Status" option and a "Checkout Only" label added in 2021, so confirm the available options in the settings rather than assuming.
Can I sync the same rooms with Airbnb, Booking.com and my own site?
The vendor says calendar synchronisation with Airbnb and Booking.com is supported, and the changelog records several fixes to iCal sync, including booking status during sync and the export sync URL. The mechanism is described in terms of syncing calendars, so treat a live test with your own channel accounts as the way to confirm behaviour, especially around cancelled or amended bookings.
Is Nuss suitable for a small guest house rather than a hotel?
The vendor lists hostels, homestays, cabins, chalets, apartments and co-living spaces alongside hotels and resorts. The booking features — seasonal rates, per-person discounts, minimum and maximum stay, blocked dates — are the kind of rules a small property needs. Whether the demo designs suit your property is a separate judgement you can make from the live demo.
