Alura Booking Wordpress Plugin - Rating, Reviews, Demo & Download
Plugin Description
Alura Booking helps hotel and accommodation businesses manage inventory and accept reservations through their WordPress website.
Features include:
- Manage accommodation inventory, room types, rates, and availability.
- Let visitors search for accommodation and proceed through a multi-step booking flow.
- Collect guest details and review booking information at checkout.
- Manage reservations and booking status from the WordPress dashboard.
- Configure supported payment methods, including manual payment and available gateway integrations.
- Set up booking notifications and customer emails.
- Use frontend shortcodes to display booking forms, search results, room information, and booking-related pages.
- Synchronise availability with Airbnb, Booking.com, Vrbo and other platforms through iCalendar (.ics) import and export. Sync is periodic, not real-time, and only blocks dates; it does not exchange guest data, rates or reservations.
Some features require configuration of the relevant settings or third-party services. Payment gateway availability depends on the gateway credentials and setup.
External services
This plugin can connect to the following third-party services. Each one is used only when the site owner enables or configures it in the plugin settings.
Stripe (online card payments)
Used when Stripe is enabled as a payment gateway. When a guest pays, the booking reference, amount, currency and guest email are sent to Stripe (https://api.stripe.com) to create and verify the payment.
Terms: https://stripe.com/legal/ssa | Privacy: https://stripe.com/privacy
Razorpay (online payments)
Used when Razorpay is enabled as a payment gateway. The Razorpay checkout script is loaded from https://checkout.razorpay.com only when a guest chooses to pay with Razorpay. Booking reference, amount, currency and guest contact details are sent to Razorpay (https://api.razorpay.com) to create and verify the payment.
Terms: https://razorpay.com/terms/ | Privacy: https://razorpay.com/privacy/
Twilio (SMS notifications)
Used when Twilio is selected as the SMS provider. The guest phone number and the notification message text are sent to https://api.twilio.com.
Terms: https://www.twilio.com/legal/tos | Privacy: https://www.twilio.com/legal/privacy
MSG91 (SMS notifications)
Used when MSG91 is selected as the SMS provider. The guest phone number and the notification template variables are sent to https://control.msg91.com.
Terms: https://msg91.com/terms-of-use | Privacy: https://msg91.com/privacy-policy
Custom SMS webhook
If the site owner configures a custom SMS endpoint, the guest phone number, message text and event details are sent to the URL the site owner enters.
Frankfurter (currency exchange rates)
Used when multi-currency display is enabled. Only currency codes (for example USD, EUR) are sent to https://api.frankfurter.dev to retrieve exchange rates. No guest or booking data is sent.
The service is operated by the open-source Frankfurter project. It does not publish a separate terms of service or privacy policy; its statement that it does not collect or log personal data, IP addresses or request URLs is in the FAQ at https://frankfurter.dev, and its license is at https://frankfurter.dev/license/. Rates are stored on your site and refreshed at most about every two days, not on every page view.
iCalendar feeds (calendar synchronisation)
Used only when the site owner adds a calendar connection (for example an Airbnb, Booking.com or Vrbo iCalendar export URL). The plugin downloads the feed from the URL the site owner enters, to block dates that are already booked elsewhere. Your own availability is exposed to those providers only through the private export URL the plugin generates, which the site owner chooses to share. No guest data is sent by the plugin when importing a feed. The terms and privacy policy of the provider whose URL you enter apply.
Source code
All JavaScript and CSS shipped with this plugin is human-readable and unminified. There is no build step, so no separate source repository is required: the files in admin/assets/ and frontend/assets/ are the source. No third-party JavaScript libraries are bundled. The Razorpay checkout script is loaded from Razorpay’s own servers only when a guest chooses Razorpay (see External services).
Screenshots
No screenshots provided
