Work with BookingKit bookings
Use this when an order in KORONA Event was sold through BookingKit and you need to know which system to change. Bookings made on BookingKit are pushed into KORONA Event through the API by a connector; KORONA Event does not pull bookings from BookingKit itself.
Before you start
Confirm:
- the order in question shows the payment type Booking Kit
- you know whether your venue's BookingKit connector is managed in-house or by a partner
How BookingKit orders appear
A booking transferred from BookingKit arrives as a normal order with tickets and an invoice. The payment on the order shows Paid with Booking Kit and is recorded as already settled, because the customer paid on the BookingKit side. Tickets from these orders behave like any other tickets, including entrance scanning.
To make external bookings easy to filter, the connector can set an order channel on each order. Order channels are managed under Settings > Order Channels, where each channel has a Channel ID and a Name and can set a Default payment method and a Default point of sale for orders from that channel.
Ownership boundaries
Apply changes in the system that owns them:
- Refunds, payment disputes, and payout questions: BookingKit.
- Ticket, attendee, and check-in questions: KORONA Event back office.
- Booking changes (dates, quantities): change them where the booking was made; if the connector does not push updates, the systems can diverge.
Verify a changed BookingKit booking
After changing a date, time, or quantity in BookingKit:
- Record the BookingKit reference, old date and time, new date and time, quantity, and change timestamp.
- Wait for the connector's normal update interval.
- Find the matching KORONA Event order using the external reference or configured order channel.
- Compare the service date, start time, quantity, attendees, and ticket state with BookingKit.
- Confirm the old start time is no longer represented as a valid booking and the new start time has enough capacity.
- If possible, verify a replacement ticket against the new date before the customer arrives.
Do not also use KORONA Event's manual move action unless the connector owner confirms that this is the intended recovery. Editing both systems independently can create a duplicate booking, incorrect capacity, or tickets for different dates.
Identify and correlate a booking
When comparing the two systems, collect from the KORONA Event order:
- the order number and invoice number
- the BookingKit booking reference or external ID, recorded as the order's External reference when the connector provides it
- the customer name and email address
- the order channel, when your connector sets one
- the ticket numbers, for gate or scan questions
Use the BookingKit booking reference or an explicit KORONA Event order/channel mapping as the primary correlation key. Use customer email and booking date only to confirm the match; they are not unique enough to identify a booking safely on their own. If the connector stores neither reference nor mapping, collect the BookingKit reference and KORONA Event order number and ask the connector owner to trace them before changing either record.
Expected result
You can tell for any BookingKit-sourced order which system owns the payment, where a refund must be processed, and which identifiers to use when comparing both systems.
Troubleshooting
| Problem | What to check |
|---|---|
| A BookingKit booking is missing in KORONA Event | Whether the connector is running and whether the booking was completed in BookingKit; collect the booking reference and time for support. |
| Refund attempted in KORONA Event does not work | Payments of type Booking Kit cannot be refunded from KORONA Event; refund in BookingKit and document it on the order. |
| External orders are hard to filter | Whether the connector sets an order channel, and the channel setup under Settings > Order Channels. |
| Customer data looks incomplete | External bookings may carry less customer detail than shop orders; correct the customer record in the back office if needed. |
| Date changed in BookingKit but not KORONA Event | Compare the external reference and change timestamp, then ask the connector owner to trace the update before editing either record again. |
