Check the host, package identity and exact Free/Pro pair before installation. Minimum requirements describe what a package accepts; they do not certify every newer WordPress, PHP, browser or integration version.
Package requirements
| Requirement | Current source declaration |
|---|---|
| WordPress | 6.5 or later |
| PHP | 8.1 or later |
| Free identity | kimorapro-hotel-booking/hotel-booking.php |
| Pro identity | hotel-booking-pro/hotel-booking-pro.php |
| Pro’s Free compatibility range | >=3.28.0-rc.7 and <4.0.0, with the supported add-on API/capabilities |
| Documentation source target | Free 3.28.0 and Pro 1.36.0 |
Use the exact supported package pair supplied for your release. Do not substitute a legacy Free folder merely because its displayed version is similar. Source revisions newer than a delivered ZIP can contain changes without a different version header.
Hosting and operational needs
- A working WordPress database with the transactional table support required by booking operations and the normal plugin upgrade lifecycle.
- Enough upload/storage capacity for the approved plugin/theme ZIPs and your own room media.
- WordPress mail transport and a reliable cron arrangement for queued/scheduled work. Transport success is not a guarantee of inbox delivery.
- Public booking and account paths excluded appropriately from full-page/CDN caching; private or signed booking data must not be served to another visitor.
- HTTPS for production guest forms and configured external services.
Free offline booking needs no WooCommerce, paid theme or Pro license. Online payments, iCal imports and particular gateways have additional environment/configuration requirements in their own guides; installing PHP or a payment plugin alone does not establish compatibility.
Verify before installing
- Open Tools → Site Health → Info and record the WordPress, PHP and database versions.
- Record current plugin/theme versions and any object/page cache.
- Compare the proposed packages with their supplied compatibility and checksum information.
- Confirm a database/files backup and a recoverable previous package exist.
For an unsupported environment, use an isolated supported host or contact support before changing production. See upgrade and rollback and the compatibility matrix; historical matrix entries are not fresh certification of your installation.
