Keep one operational truth
Bókun can keep selling while Operator remains authoritative for the real departure, participants, tickets, and check-in.
Channel Integration
Keep Bókun sales connected to the operation you actually run.
Reconcile future Bókun bookings into Operator and protect Bókun availability without allowing background synchronization to expand capacity.
Free companion integration for every UltimaTour Operator edition. Requires the operator’s own Bókun API credentials.
Overview
Future Bókun bookings are reconciled into exact mapped Operator departures without duplicates. Operator remains the operational source of truth. Background synchronization can close unsafe Bókun slots but never expands capacity; only an administrator’s explicit opening of one mapped public departure can reopen that exact public Bókun slot. Private departures never open in Bókun, ambiguous mappings fail closed, and cancellations remain operator-reviewed.
What it helps you do
Protect scarce seats
If Operator has fewer seats than Bókun could sell, the mapped Bókun slot closes instead of risking overbooking.
Fail safely
Unknown products, missing departures, ambiguous times, and cancellations do not silently mutate Operator records.
Features
- Reconcile future Bókun bookings into matched Operator departures
- Prevent duplicate imports across Bókun and Viator references
- Close Bókun slots when Operator has fewer remaining seats
- Never expand Bókun capacity during background synchronization
- Reopen only one exact mapped public slot after an administrator explicitly opens it in Operator
- Keep private departures closed in Bókun
- Fail closed on missing, conflicting, or ambiguous mappings
- Surface freshness, failures, and unresolved items in WordPress administration
How it works
Install the companion beside Operator, enter credentials from the operator’s own Bókun account, configure the exact product identity and any required time mappings, then enable booking intake and availability protection.
Who it is for
Tour and activity operators who use Bókun for distribution while running guest preparation, tickets, check-in, attendance, and follow-up in UltimaTour Operator.
Requires
Works With
Recommended For
Availability
FAQ
Is this unrestricted two-way synchronization?
No. Booking intake flows from Bókun into Operator. Background availability protection can only close unsafe Bókun slots; it never expands capacity.
Can Operator reopen Bókun availability?
Only after an administrator explicitly opens one exact mapped public Operator departure. Private departures are never opened in Bókun.
Does it work with every Operator edition?
Yes. It uses the same governed Operator intake contract in every edition.
Does it include Bókun service or API access?
No. The operator supplies and remains responsible for their own Bókun account, API access, credentials, and Bókun charges or terms.
Technical Details
Uses Bókun’s API with administrator-supplied credentials. Booking import is idempotent by external reference. Mapping is explicit and fail-closed. Background availability synchronization is downward-only.