These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Tour Operator Software
- Features
- Tour packages
Tour packages
Sellable packages with itinerary, duration and base price.
OverviewTour packages×
Tour Operator Software · Tour packages
New
Tour packages
Tour packages
| Package name | Duration days | Base price | Operational record | |
|---|---|---|---|---|
| Package 314 | 4 | 780 | TRP-8578 | |
| Package 417 | 24 | 940 | TRP-6494 | |
| Package 746 | 12 | 80 | TRP-5965 | |
| Package 162 | 26 | 370 | TRP-6983 | |
| Package 450 | 5 | 640 | TRP-9244 |
6 of 6 records
Package 314Tour packages · TP-56339
Duration days4
Base price780
Operational recordTRP-8578
What you can do
Sell tours you know how to run
A tour package is what your customers buy: a name, a day-by-day itinerary, a duration in days and a base price. Every package is built on the operational trip record that delivers it, so the route, vehicle and timings behind the itinerary are never a guess. When sales promise a coastal two-day tour, operations can see exactly which trip runs it.
Packages are captured by the dispatcher through a form that checks the whole submission before anything is saved. The person creating the package is taken from their login, not typed in, and the real date of the event is kept separately from when the record was created. A package that fails a check is not half-saved.
How the work is organized
The dispatcher builds packages; the operations manager keeps the trips behind them runnable.
- Package on a trip. Each package names the trip record that delivers it.
- Itinerary in one place. The full itinerary lives on the package, so everyone sells and runs the same tour.
- Checked before saved. Missing references or invalid values reject the whole submission.
What to agree during setup
Agree your package list, how itineraries are written and how base prices are set by season. Agree which trip record each package uses and who may change a package once it is on sale. Prepare examples of a day tour, a multi-day tour, a package moved to a different trip and a package withdrawn from sale.
Check the handoff on an actual case
A new three-day mountain package is created on the trip record that already runs the route with the minibus fleet. The dispatcher enters the itinerary, three days and the base price. Sales can book it straight away, and the dispatcher knows from the package which trip and vehicles will deliver it. When the route changes next season, the package is moved to the new trip record and the itinerary updated in one place.
What your team sees
- Tour packages — Packages with duration, base price and the trip that runs them.
- Booking pipeline — How each package is selling.
Follow the work through
- Package setup: From a new tour to a package on sale.
- Booking to departure: How packages are booked.
Review the implementation plan before loading packages.
What it keeps track of
Data model- Tour packages
- Sellable tour packages built on an operational trip record.
- Trips
- Planned and executed transport trips with customer, vehicle and driver.
Who uses it
Permissions- Dispatcher
- , Operations Manager.
- The dispatcher builds packages; the operations manager keeps the trips behind them ready.
Set up Tour Operator Software your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.