Tour operator reservation software: the booking record from creation to travel.
For a multi-day trip, a booking is not a line in a calendar. It is a record that lives for months and is touched by sales, operations, guests, vendors, and finance. This guide explains what that record has to hold, how bookings enter the system, and how Tourcube's booking screen is built.
Tour operator reservation software manages bookings for multi-day trips: the record that connects a client to a trip or departure, holds the passengers and every service in the trip, tracks each service's vendor confirmation, carries the payment schedule and cancellation terms, and stays open from the first deposit until the group returns and the books close.
It is the core of tour operator software rather than a separate product, and it is not the same thing as an online booking engine. The engine creates bookings from the website. The reservation system is where every booking, however it arrived, is operated until the trip is over and paid for.
Data model
Anatomy of a multi-day booking
A booking for a week-long trip has to answer questions from five different people: the salesperson who made it, the operations coordinator who confirms it, the guest who travels on it, the vendor who provides part of it, and the bookkeeper who reconciles it. The table below is the set of panels a Tourcube booking carries, and why each one exists.
Panel
What it holds
Who needs it
Header
Trip code and departure, dates, adults, children, rooms, brand, lead source, flags such as private or auto-emails disabled, client and contact details, trip developer and support
Everyone
Segments
One line per service with vendor, dates, quantity, status, confirmation number, gross price, and net cost
Operations, finance
Passengers
Each traveler on the booking with their details, forms, and preferences
The Header panel of a Tourcube booking: the services and their status, the pricing summary, the client, and the operations contacts on one screen, with controls to release final documents and portal forms.
The record
One booking, thirteen panels, no second copy
The identity strip at the top of a Tourcube booking answers the first questions anyone asks: who, which trip, which date, how many, how long until departure. Below it, thirteen panels hold everything else. Sales, operations, and finance open the same record; there is no handoff spreadsheet between them.
Instant invoices and email confirmations from the booking
Follow-up tasks, full communication history, and change history on the record
Per-user grid layouts on every table
Services
Segments: every service is its own record
The part of a multi-day booking that general booking systems do not model is the segment. A booking for a hiking trip might hold an arrival transfer, a pre-trip hotel night, the trip itself, and a travel protection policy: four services from four vendors, each with a different cost, price, confirmation, and cancellation rule. Treating the booking as one item hides all of that.
A segment has a vendor and a status. Requested, availability confirmed, booking confirmed, pending, or not required, with the confirmation number and a comment stream recorded as the vendor responds.
A segment has money on both sides. The gross price the guest pays and the net cost the vendor charges, loaded from vendor rates or set privately for this booking.
A segment has its own deadline. Cancellation cutoffs and penalties are tracked per segment, so a change close to departure shows exactly which services still carry a cost.
A segment carries operational detail. Vouchers, pickup points and seats, transportation, manifest entries, itinerary blocks, forms, and vendor payments hang off the segment, not the booking as a whole.
In Tourcube a segment drills open into a record with fourteen panels: prices and costs, confirmation, comments, communications, vendor payments, vouchers, itinerary blocks, history, forms, header, pickup point and seats, custom fields, transportation, and manifest. On an FIT booking, those segments arrived from the accepted proposal with their confirmations intact. How proposals become bookings →
Segments panel
Four services, four vendors, one booking
The Segments panel groups services by date and shows, for each one, the vendor, city, status, confirmation number, stage, gross price, and net cost. From here staff add products or options, download the segment list, view the segment's passengers, load loyalty discounts, and drill into any line.
Status and confirmation number visible per line
Gross and net side by side, totaled for the booking
Filter by product type or supplier
SUMMIT TRAILSCtrl K?✨Support RequestLog Out
Booking
Booking 197144 — REYES,DANIEL
BKAug 2 – Aug 7, 2026 (5 nights)•15 days to departure
The Segments panel of a Tourcube booking. Each service has its own vendor, status, confirmation number, gross price, and net cost, grouped by the date it starts.
Entry points
How bookings enter the system
A reservation system has to accept bookings from several directions and end up with the same kind of record regardless of the source. There are four common doors.
Staff, from a scheduled departure
A coordinator shops departures by date, destination, activity, and availability and creates the booking against live inventory. This is the fastest path and the most common one for group operators. Scheduled departures →
A converted proposal
An accepted custom quote converts to a booking with its segments, prices, and confirmations already in place. FIT and custom travel →
The website
A traveler books online against live inventory. The booking lands in a review queue where staff check it against existing records, including duplicate-client detection, and approve it. Online booking engine →
A travel agent
Agents book through portal access, with guest prices suppressed for wholesalers, and the agency's commission group applies to the booking automatically. Selling through the trade →
Whatever the door, the result is one booking record, linked to one client record, joined to one departure or built from one proposal, and visible to operations and finance the moment it exists.
Lifecycle
A booking's life, from deposit to closed
Created and deposited
The booking is created with its passengers and segments, the payment schedule is generated from the trip's terms, and the deposit is taken by card, pay link, or staff charge. A confirmation and invoice go out from the record.
Confirmed with vendors
Each segment is requested from its vendor and moves to confirmed as responses arrive. For scheduled departures, most services are covered by the departure's group allocations; for custom trips, each service is confirmed individually.
Forms and questionnaires
Passenger waivers and traveler information forms are sent, chased by rules, and captured into the booking, feeding manifests and rooming lists. Guest forms and communications →
Installments and final payment
Scheduled payments come due and are collected, automatically where a card profile is stored. Reminders go out before and after due dates.
Final documents
The itinerary, pre-departure information, and final details are released to the guest portal at the document stage the operator chooses. Itinerary documents →
Changes and cancellations
A change is made on the booking and written to its history. A cancellation applies the booking's terms by days before departure and shows which segments still carry vendor penalties.
Travel and after
The group departs. Afterward a welcome-home message and evaluation go out, refunds or credits are recorded if needed, and the booking's receipts and vendor payments are exported to the ledger. Accounting for tour operators →
Evaluation
What to expect from a reservation system for multi-day trips
Segments, not a single line item. Each service with its vendor, cost, price, status, and deadline, and a record of its own to drill into.
Passengers as people. Names, forms, preferences, and air per traveler, not a headcount on the booking.
A payment schedule generated from terms. Deposit, installments, and final payment with due dates, status, and automatic charging where a card is stored.
Cancellation terms that compute. Penalties by days before departure on the booking and cutoffs per segment.
Every entry point ends in the same record. Staff, proposal, website, and agent bookings are the same kind of booking once inside.
Communications and documents on the record. What was sent, when, to whom, and what stage the booking has reached.
A complete history. Every change to the booking, by whom and when, without asking anyone.
The departure and client one click away. The booking is joined to its date and its client, so counts, rooming lists, and history are never out of step.
How Tourcube does it
The booking screen in Tourcube
Every Tourcube booking carries thirteen dedicated panels: header, segments, passengers, accounting, air itinerary, itinerary, comments, documents, communications, tasks, status, history, and custom fields. The same record is used whether the booking came from a scheduled departure, a custom FIT quote, an agent, or the Web Booking Queue. Invoices and email confirmations are produced from it at the click of a button, client payments run through Authorize.net or Stripe, split invoices and complex payment allocations are supported, and vendor confirmations and outgoing payments are tracked per booking.
Segments drill open into fourteen-panel records with the vendor confirmation workflow, and count badges on the record's rail show comments, communications, payments, and history at a glance. Quick search on the home page jumps to any booking by ID, and Ctrl K opens any screen by name.
Tour operator reservation software manages bookings for multi-day trips: the record that connects a client to a trip or departure, holds the passengers and every service in the trip, tracks each service's vendor confirmation, carries the payment schedule and cancellation terms, and stays open from the first deposit until the group returns and the books close. It is the core of tour operator software rather than a separate product.
Is a reservation system the same as an online booking engine?
No. A booking engine is a website component that lets a traveler or agent create a booking. The reservation system is where that booking, and every booking made by staff or converted from a proposal, is operated: segments, confirmations, passengers, documents, communications, and money. The engine is one door into the reservation system.
What is a segment?
A segment is one service inside a booking: a hotel stay, a transfer, a guide day, an insurance policy, or the trip itself. Each segment has a vendor, dates, a quantity, a net cost and a price, a confirmation status and number, and its own cancellation deadline. In Tourcube a segment opens as a full record with fourteen panels of its own.
What happens when a client cancels or changes a booking?
The booking's cancellation terms, inherited from the trip and adjustable per booking, determine the penalty by days before departure. Each segment carries its own vendor cutoff, so the operator can see which services can still be released without cost. Changes such as an added passenger or a different departure are made on the booking and recorded in its history.
Can a booking be moved to another departure?
Yes. Tourcube records booking transfers on the client record, so a party moved from one date to another keeps its history and its payments.
How do agent and online bookings reach the reservation system?
Bookings made on the website land in a Web Booking Queue for staff review and approval against live records, with duplicate-client detection. Travel agents can book through portal access, with guest prices suppressed for wholesalers, and their commission is calculated on the booking.
Is Tourcube reservation software?
Yes. Bookings in Tourcube carry thirteen panels: header, segments, passengers, accounting, air itinerary, itinerary, comments, documents, communications, tasks, status, history, and custom fields. The same booking record is used whether the sale came from a scheduled departure, a converted FIT proposal, an agent, or the website.
These guides explain how multi-day tour operations work and what software should do about it. Start with the overview, or go straight to the part of the business you are thinking about.
