Anatomy of a Booking
Bookings
A booking is where you manage the travel services ( reservations ) being provided to a passenger or group of passengers.
A booking will normally exist for each trip a customer is taking. If a customer is booking multiple trips, they will usually have multiple bookings.
Bookings are comprised of:
- A unique reference
- A status, which provides a top-level indication of the booking's current state
- An optional customer profile as the primary contact point for the booking
- One of more passengers, who are the people travelling om the reservations
- A sale currency, which determines the currency used for:
- Reservations which compose the travel services and other goods which are being sold
- Transactions which record any payments made against the booking
- As well as booking notes, an audit history and other features or information
Customers
A customer can be linked to the booking as the 'Booking Contact'. The customer can be linked to many bookings. A customer may be either a direct consumer or a third party agent. It represents the primary contact point for the sale.
The customer may be a passenger who is travelling on the booking or may be a non-passenger individual, a sales agent, or another type of partner.
Products
Products are all things which can be bought, sold, and reserved. A product can be anything from a package tour, a stay in a hotel, a flight, merchandise, or a discount.
All "types" of product in RezKit are represented as products, which depending on their type may have additional data or behaviours.
Reservations
A booking can have many product reservations. Each reservation represents a specific travel product for the booking. Each has its own status.
a product reservation may have zero or more passengers assigned to it.The number of passengers which may be assigned to a reservation is determined by the occupancy range of the associated product.
Reservations often have service dates, these are the specific dates that the services of the associated product will be provided to the assigned passengers.
Reservations have a fixed workflow which represents their lifecycle. The state transitions available on a reservation depend on its current state as well as validity checks for it to be moved to a new state.
Passengers
A passenger represents an individual person receiving services as part of a single booking. Passengers are specific to an individual booking, but may be associated with a customer to create a profile across multiple bookings.
Passengers can contain detailed information relevant to the booking and the reservations on which the passenger is assigned.
Product Providers
Most products within RezKit originate from product providers. These are external systems which are connected to RezKit via a standardized communication interface. This allows RezKit to query the provider about the products they offer, request reservations for those products, and make further requests on those reservations.
When a reservation is on a product which belongs to a provider, the reservation is owned by the provider. This means that while RezKit can make requests to modify or cancel the reservation, it is the provider and only the provider which decides if the request is accepted.
You can find more detail about how product providers work in our detailed guide
Transactions
A transaction represents a payment made in relation to the receivable account of the booking.
Each booking is a receivable account with a balance which is determined by the sum of the sale prices for all reservations which are in the confirmed state.
When a payment is made towards the sale price of the booking, it is recorded as a transaction. These transactions also include refunds and account adjustments.