Black Friday
Skip to documentation content

Getting Started

Install Hotel Booking Pro and activate its license

Install the compatible Pro add-on after Free, activate one site license and verify feature and update entitlement.

Install Pro after compatible Free is active. Then activate the Pro license for the correct website and verify the specific premium workflow you need.

Before you begin

For this source-reviewed target, use Free 3.28.0 and Pro 1.36.0 from an approved package pair. Pro declares Free >=3.28.0-rc.7 <4.0.0; the WordPress dependency slug is kimorapro-hotel-booking. Pro’s folder is hotel-booking-pro, while its commercial license product slug remains hotel-booking.

Create a database/files backup. Keep your key private. Check that the site’s URL/domain is final for activation and that the host can reach the configured HTTPS license service. The latest source uses https://www.kimorapro.com; an older same-version ZIP can contain a different default, so check package release information rather than patching the plugin yourself.

Install Pro

  1. Confirm KimoraPro Hotel Booking is active on Plugins.
  2. Open Plugins → Add Plugin → Upload Plugin.
  3. Choose the approved Pro ZIP and select Install Now.
  4. Select Activate Plugin.
  5. Open Hotel Booking → License.

The dependency declaration does not silently install Free. Pro Page setup does not activate premium capabilities or supply gateway credentials.

Activate and verify

  1. Enter your key in License key.
  2. Select Activate license once and read the resulting status/error.
  3. After successful activation, select Check now and inspect the refreshed status.
  4. Check Pro features, Updates and Support independently.
  5. Use Check for updates when offered; open one needed Pro screen without changing live bookings or prices.

The plugin sends the key for activation and retains an installation token, not the raw key. Neither belongs in a screenshot, ticket, source file or frontend URL.

State and recovery

A previously successful activation can use the configured connection-error grace; a fresh failed activation does not become licensed. An authoritative expired-but-still-activated result can keep installed functionality available while updates/support are unavailable. Revoked, invalid, deactivated or incompatible states must be handled through their actual status rather than assumed to be expiry.

For a domain change, staging clone or identity mismatch, record the redacted error and correct installation identity through the supported license workflow. Do not copy tokens or edit options to bypass binding. Before permanently removing a site, use Deactivate and verify seat release. A normal update does not require releasing the seat. A theme purchase uses its own license workflow.

Was this article helpful?

Your feedback helps us improve the documentation.