JetBooking plugin review and common issues

Availability blocking requires: (1) the booking calendar widget is connected to the correct apartment/property unit in the widget settings; (2) the booking status of existing reservations is “Confirmed” or “Pending” — only non-cancelled bookings block dates; (3) in JetBooking → Settings → Booking, verify “Block booked dates in calendar” is enabled; (4) the calendar widget must refresh its availability data when loading — check for JavaScript errors that might prevent availability data from loading; (5) clear all page caches and test with an incognito browser to ensure fresh availability data.

iCal sync imports external bookings (from Airbnb, Booking.com) to prevent double-booking. Setup: (1) in JetBooking → Apartments → [unit] → Calendar Sync, add the Airbnb iCal URL (from Airbnb → Calendar → Import/Export → Copy Link); (2) set the sync frequency (hourly, daily); (3) manually trigger a sync to verify it imports correctly; (4) imported bookings appear as “Unavailable” blocked dates in the JetBooking calendar; (5) for two-way sync (export WordPress bookings to Airbnb), use the iCal export URL from JetBooking and add it to Airbnb’s calendar import settings.

JetBooking creates a WooCommerce order and redirects to WooCommerce checkout for payment. If orders remain in Pending Payment: (1) verify WooCommerce payment gateways are active and configured; (2) in JetBooking → Settings → Payment, verify the WooCommerce integration is enabled and the correct product is mapped; (3) check if the customer completed checkout after being redirected — sometimes customers abandon the WooCommerce checkout step; (4) test the full booking flow end-to-end with a WooCommerce test payment gateway (enable “Cash on Delivery” temporarily for testing); (5) check for WooCommerce checkout page errors.

In JetBooking → Apartments → [unit] → Pricing, create pricing rules. Add a rule for the peak season: set date range (July 1 – August 31), price per night for this period (higher rate). Add another rule for shoulder season (June, September) with medium rates. The default price applies for all other dates. JetBooking applies the most specific matching rule to the date range selected by the customer. Weekend surcharges can be added as separate pricing rules targeting specific weekdays.

Create a JetEngine Listing Grid displaying property posts. Add a JetSmartFilters Check-In/Check-Out date range filter connected to the listing grid. When visitors select dates, JetSmartFilters queries JetBooking availability data and filters the listing to show only properties available for the selected dates. Add additional filters (location, property type, number of bedrooms) using JetSmartFilters taxonomy and meta filters. This creates an Airbnb-style property search interface within WordPress.

JetBooking handles the booking logic, but multi-vendor functionality (property owners managing their own listings) requires additional setup. Combine JetBooking with Dokan or WC Vendors for vendor marketplace architecture, giving each property owner access to their own listings and bookings through the vendor dashboard. This is an advanced configuration that requires developer expertise to integrate correctly. For a simpler solution, platforms like Dokan with a booking module or a dedicated WordPress rental marketplace plugin may provide a more integrated approach.

Yes — JetBooking supports unit-based capacity where a property can have multiple units. For example, a hotel can configure 10 rooms as 10 units of the same property — when one is booked, 9 remain available. Configure capacity in JetBooking → Apartments → [property] → Units/Quantity. This enables JetBooking for multi-unit properties without creating a separate property post for each room.

Yes, that can happen, especially on older sites with many plugins. This usually happens when the plugin, theme, and add-ons are updated out of sequence. In most cases, testing on staging catches the issue before it reaches the live site. From experience, backups and changelog reviews save a lot of cleanup time.

Start by checking whether another plugin already does the same job. In most cases, overlap is what creates avoidable conflicts and performance issues. A common issue is installing a plugin because it looks convenient without checking the stack first. From experience, a short compatibility review avoids most of the pain later.