White Label Vacation Rental Software Features: Seven Bookable Types
This is the platform underneath the vacation rental clones, and every feature below ships in it. Listing pages are the easy part. The work is in keeping calendars truthful, producing a total that holds after a coupon and a seasonal rate, and paying hosts what they are owed under a commission rate that never shifts after the fact. The list is grouped by the person who uses each piece.
Request a Live Demo →See PricingFeature Set by Role
Three people run a rental marketplace day to day: the guest who books, the host who lists and gets paid, and you, the operator, who sets the commission and the rules.
Guest App
- One search box spanning whichever service types you have enabled
- Narrow by place, dates, party size, price, amenities and rating
- Location and listing autocomplete beside a map view
- Order results by price, rating or recency
- Deposit-style part payment where a listing calls for it
- Balance reminders ahead of arrival, plus invoices
- In-app chat with the host, with read receipts and shared files
- Reviews, wishlists and a history of past bookings
Host Console
- Property profiles with a photo gallery and video
- Several room types per property, each priced on its own
- Seasonal and date-specific rate changes
- Length-of-stay discounts and per-extra-guest charges
- Minimum and maximum nights, plus an advance booking window
- A calendar with room-level sync that blocks clashes
- Earnings shown after commission, with payout requests
- Host-added fees such as cleaning and security deposits
Operator Admin
- Over twenty modules, each behind its own permission
- Custom roles with permissions chosen module by module
- Host approval with identity document review
- One moderation queue covering every service type
- Commission set for the whole platform or per host
- Coupons with usage caps and minimum totals
- A payout queue with review, approval and completion
- Paid featured placement, and service types you can switch off without code
Rented Platform vs One-Time Script vs Miracuves Platform
Three ways to put a rental marketplace in front of guests, compared on what each one does once real bookings arrive. Cells for other routes are hedged on purpose, because products vary.
| Capability | Rented / Hosted Platform | One-Time Script | Miracuves Platform |
|---|---|---|---|
| Accommodation booking | Often the core of the product | Usually a single listing type | Room types with their own occupancy, bed setup and check-in windows |
| Other bookable inventory | Limited to whatever the vendor has enabled | Extra types tend to be your own build | Cars, tours, boats, events and flights on the same engine |
| One checkout across types | Uncommon | Uncommon | A villa, a tour, a hire car and a boat paid for in one session |
| Pricing engine | The vendor's rules | Often a basic rate field | Seasonal rates, length-of-stay discounts, guest surcharges and coupons in one place |
| Calendar integrity | Managed by the vendor, so hard to inspect | Varies, and a cached availability flag is a common cause of double bookings | Rechecked on every request against date tables, with room-level sync |
| Commission handling | Bound to the vendor's terms, and some take a cut of their own | Yours to set, though few store it per booking | Yours, global or per host, stamped on each booking |
| Mobile apps | The vendor's app, often carrying its branding rules | Cheaper tiers often ship web-view apps rather than native ones | Flutter builds for Android and iOS on the same REST API as the web app |
| Source code | Stays with the vendor | Some vendors withhold it from every published tier | The full Laravel 10 codebase, no encrypted files |
| Recurring fee | Yes, and it may bundle hosting and licensing | Hosting you arrange yourself | No licence fee, no per-booking fee, no revenue share |
| Software price | A subscription that keeps running | Roughly $250 to $1,500 on the open market | $3,099, paid once |
Read the last row with care. A subscription often bundles hosting, so what you are weighing is a one-time software purchase against a fee that recurs, not a promise of a lower total on day one. The row that changes what you can build is the third: seven types share one booking model here, so adding tours beside stays never needs a rebuild.
One Booking, Traced From Search to Payout
Marketplaces tend to fail somewhere along this path, so it is worth following a single reservation all the way through.
A single search over every enabled type
Stays, spaces, cars, tours, boats, events and flights answer the same query, narrowed by place, dates, party size, price, amenities and rating. Autocomplete and a map view sit on top, and the guest never has to think about which kind of inventory a result is.
Dates are verified, not remembered
Each request goes back to the per-service date tables and the bookings already made, instead of trusting a stored flag. Minimum and maximum stay and the advance booking window are applied, and room-level sync catches a clash that a whole-property check would miss.
The price is worked out in one pass
Date-based rates, length-of-stay discounts, extra guest charges, platform service fees and the host's own add-ons resolve together. Only then is a coupon tested against its usage cap and minimum total, so the figure on screen is the figure that lands on the invoice.
Full or partial payment
Six payment options are pre-integrated, wallet included, and deposit-based listings can take part payment with a reminder for the balance before arrival. The gateway holds the card details, and the webhook confirming payment has its signature checked before a booking is marked paid.
Commission recorded, then paid out
Your rate is copied onto the booking at the moment it is created. The host's balance builds up after that stored rate, the host asks for a payout from the console, and your team works it through the queue. A rate change next quarter touches new bookings only.
Stage five deserves the most scrutiny in any platform you evaluate. If the rate is looked up when the payout runs instead of being stored per booking, a single change to your commission quietly re-prices everything hosts have already earned.
Why Each Feature Is on the List
A capability appears here only if leaving it out breaks a specific thing in production, not because it looks good in a demo.
| Capability | What goes wrong without it |
|---|---|
| Commission stored per booking | Raising your rate would silently re-price every earlier booking, and hosts would stop trusting your statements. |
| Availability checked per request | A cached flag drifts, and two guests end up holding the same dates. The date tables are the record, not a yes-or-no field. |
| Room-level sync | A property with four room types is really four inventories, so a check at property level cannot see a clash inside it. |
| One polymorphic booking model | Giving each service type its own model means seven payment paths, seven payout paths and seven homes for a bug. |
| Coupons with floors and caps | A code with no minimum or usage limit lets one shared link eat a month of margin. |
| Partial payment | Villas, boats and events usually run on deposits, and demanding the whole amount up front would shut those categories out. |
| Per-entity translation | Translating only the interface leaves a localized shell around listings that nobody in that market can read. |
| Byte-level upload checks | Hosts upload documents and photos constantly, and trusting a file extension trusts a name an attacker can choose. |
| Signature-verified webhooks | An unchecked payment callback can mark bookings as paid for anyone who finds the address. |
What the Features Run On
The stack is ordinary by design. The backend is PHP 8.1+ on Laravel 10, organized as a modular monolith of more than twenty domain modules, with Eloquent parameterized queries throughout and Sanctum tokens plus JWT guarding the API. MySQL 8 or MariaDB holds over forty tables, including the polymorphic booking model shared by all seven service types, with composite indexes on the polymorphic pairs and full-text indexes for search. The public marketplace is Blade, the admin uses Vue.js components, and the mobile apps are Flutter for Android and iOS from a single codebase on the same REST API. Chat and notifications use Pusher with Chatify. Redis carries cache, session and queue duties with workers under Supervisor, and media can sit on S3 or Google Cloud storage behind Nginx.
A mainstream stack means any capable Laravel developer can pick it up, so keeping the platform alive never depends on us.
What Is Not Included in the Base Package
Everything listed above is in the base platform and can be opened in the live demo. The items below are not, and we would rather you read them before buying than discover them afterwards.
Boundaries, stated next to the features
Where a control is a matter of configuration rather than code that ships, the security documentation says so. The Platform Trust section of the Provider page sets out the detail.
Compare the four kinds of seller before you choose
Rented platforms, script vendors, custom agencies and Miracuves, side by side, with the questions to ask each and a named client deployment in Italy on the Provider page.
Frequently Asked Questions
What carries my brand across the platform?
Do all seven service types have to be switched on?
How are double bookings prevented?
Can I change my commission later, and how do payouts work?
Which payment options come with it?
Can listings be offered in several languages?
Open the platform before you decide
Ask for a working demo of the booking engine, the host console and the operator admin, or go straight to the price.
Explore the White Label Vacation Rental Software
Ready to run a booking marketplace of your own?
Seven service types, four surfaces and the full Laravel 10 source, deployed in 6 days on hosting you choose.
Talk to Us →Miracuves is an independent software development company. We are not affiliated with, connected to, sponsored by, or endorsed by Airbnb, 9flats, or any other rental marketplace.
“White label vacation rental software” describes a category of product, not any one company. Brand names appear elsewhere on this site only to describe the kind of platform being built and the terms buyers search for.
The entire design and codebase is built by our own team. The product contains no code, design, graphics, or content originating from any third-party rental marketplace website or application.
All third-party names and marks are the property of their respective owners, referenced here solely to describe the category of software offered.
