Software for managing multi-day, multi-service itineraries
A group trip isn’t a standalone product: it’s a multi-day itinerary chaining flights, hotels, transfers, guides, meals and activities, often with several departure cities and options the traveller chooses. One of the bottlenecks is right there: keeping all that structure consistent departure after departure, so that a change on one day doesn’t force you to redo everything by hand. Tools designed to sell a single-day activity don’t model this; they end up forcing you to reconcile in spreadsheets what the software should be holding up.
TourKnife is the group travel software designed from the ground up for multi-day, multi-service itineraries: you define the structure once and every departure inherits it.
And if you’ve already sorted out itinerary design but you have other needs — selling online, coordinating suppliers or generating travel documentation — remember that TourKnife does everything a group travel operator needs. Discover all the features.
Product, itinerary and departures: the structure of a group trip
TourKnife separates three levels that reflect how you actually work. The tour is the commercial product — the name, the description, the destinations. The itinerary is the structure of the trip: how many days it lasts, what happens each day, which rooms are offered. And from each itinerary are born the departures, with their date, their places and their bookings. You design the itinerary once and schedule as many departures as you like from it, without duplicating the structure in each one.
The trip day by day, with all its chained services
The heart of the itinerary is its day-by-day plan. Each day brings together its activities — flights, hotel nights, transfers, meals, guides, excursions — each connected to the supplier service that covers it. Activities can be mandatory, part of the trip, or optional, so the traveller decides whether to book them. It’s the native multi-service model: not a product with extras bolted on, but a trip made up of chained services, which is exactly what a group trip needs.
Room options, packs and choices the traveller makes
The itinerary caters to the particulars of group travel. You define the accommodation options bookings can be made in, the room supplements, the packs of activities sold together and the flight packs by departure city — with the “no flights” option for those arriving on their own. And with mutually exclusive activity groups, you offer the traveller a choice of one among several. All the richness of a real group trip is modelled in the structure, ready to sell.
One change in the itinerary, propagated to every departure
Here’s the advantage of separating structure and departures: when you change the itinerary — add a day, reorder activities, change a room option — the change propagates to all the departures that inherit it. You don’t edit twenty departures one by one. And when a specific departure needs something of its own — a different service, an activity that doesn’t apply that day — you customise it without touching the rest. Restructuring a trip stops being a repetitive, error-prone job.
Several departure cities over the same itinerary
The same trip can depart from Madrid and from Barcelona, each city with its own flight. TourKnife handles this natively: you model the departure cities over the itinerary, and their availabilities add up, so the departure offers the combined capacity instead of being capped by the city with the fewest places. The traveller chooses their origin and the system assembles their trip with the services that apply to them.
Frequently asked questions
What does it mean that TourKnife is multi-day and multi-service?
That it’s designed for trips made up of several days chaining several services — flights, hotels, transfers, guides, activities — not for selling standalone activities. It’s the heart of the product and its difference from tools designed for day tours.
How is a trip structured in TourKnife?
In three levels: the tour (the commercial product), the itinerary (the structure of the trip: days, activities, rooms) and the departures (each specific date with its places). You define the itinerary once and schedule all the departures from it.
If I change the itinerary, do I have to update each departure?
No. Changes to the itinerary propagate automatically to all the departures that inherit it. You only customise a specific departure when it needs something different from the rest.
Can I have the same trip with several departure cities?
Yes. You model the departure cities over the same itinerary, each with its own flight, and their availabilities add up on the departure.