European tour operator online distribution, sold direct

The operator this is written for runs ground product somewhere between Lisbon and Vienna: a coach circuit, a walking week, a river-and-city combination that agents in three countries have sold on commission for years. The agents are tired, the commission is going the wrong way, and the obvious answer is to sell the same product direct on your own site. Most operators then spend their first month arguing about templates. The thing that will actually shape your booking flow is not the template. It is the EU Package Travel Directive, and European tour operator online distribution that ignores it does not fail loudly. It fails in the inbox, one refund at a time, two seasons later.
This is a piece about building the flow around the obligation, not about the obligation in the abstract. Your lawyer owns the second part; what follows is what the first part looks like on a screen.
When a sale becomes a package, and why the screen has to say so
Agents never had to think about this, because the paperwork they handed over came from you. Online, you are the paperwork.
The Directive is built on a definition. Combine more than one kind of travel service for the same trip, sold together or selected by the traveller before a single payment, and you have organised a package. The moment your product page lets a traveller add a hotel night to the walking week, or your checkout bundles a transfer with the circuit, the sale changed character, whether or not your copy calls it a package. There is a second category, the linked travel arrangement, that catches a looser kind of combination; it carries fewer obligations, and it is also the category operators most often claim to be in when a regulator later decides they were not.
What the flow has to do is state the category plainly, before the traveller commits, in words that a court would accept as having been read. That means the product page and the summary step, not a clause inside the terms. It also means being honest with yourself about which category the product is in. A single multi-day tour with accommodation included is a package. There is no version of the booking flow that makes it something lighter.
Pre-contractual information at the step where it is read
The Directive lists the information a traveller must receive before they are bound, and it supplies a standard form for the package-rights part of it. The list is longer than most operators expect: the main characteristics of the services, the total price including taxes and any fees that cannot reasonably be calculated in advance, the itinerary, the identity and contact details of the organiser, general passport and visa information for the destination, the cancellation terms, the insolvency protection and who provides it, and whether the trip is suitable for travellers with reduced mobility.
Where most direct-selling operators go wrong is not omission. It is placement. The information exists on the site, in a PDF linked from the footer or a terms page the traveller is asked to tick, and the operator believes that counts. The Directive's standard is that the traveller receives the information before concluding the contract, clearly and prominently. A link nobody opens is a defence you do not want to run.
| Where operators usually put it | Where the obligation expects it | Why the first does not hold |
|---|---|---|
| Total price in the terms, with "excluding local taxes" in a footnote | On the product page and again on the summary step, as the amount the traveller will pay | The price shown is the price contracted; later surcharges have narrow grounds |
| Package-rights form as a PDF behind the terms checkbox | Its own block on the summary step, read before the payment button | Ticking a box is not receiving information |
| Insolvency protector named only on the invoice | Named before payment, with how the traveller contacts them | Protection the traveller cannot find does not protect your reputation |
| Cancellation schedule in a FAQ | Stated as part of the contract, at the step where the traveller decides | A schedule the traveller never saw is a schedule you cannot enforce |
| Passport and visa line left to the confirmation email | Before the contract, with the destination's general requirements | Post-contract information arrives after the decision it was meant to inform |
Read the middle column as a page layout and the design problem largely solves itself. The summary step is not a receipt. It is the contract being formed.
Cancellation and insolvency: the two disclosures travellers actually read
Travellers skim itineraries. They read two things with care: what it costs to cancel, and what happens if you disappear.
Cancellation is where your commercial terms and the Directive overlap. You set the fee schedule, and it should be reasonable and reflect what you actually save when a traveller withdraws. The Directive also gives the traveller a right to terminate without a fee when unavoidable and extraordinary circumstances at the destination significantly affect the trip. Both have to be visible before payment, and your admin side has to be able to apply them without a phone call to the owner. An operator who refunds by exception is an operator who refunds inconsistently, and inconsistency is the thing complaints are made of.
Insolvency protection is the obligation operators selling through agents often never handled personally, because the agent's guarantee or the national scheme sat in front of them. Direct, it is yours. The traveller must be told who protects their payments, and told in a way they can act on, before they pay. Name the protector. Say what the protection covers. If repatriation is included, say so. Do not make the traveller infer it from a logo.
Designing the checkout around the obligation instead of bolting it on
Here is the flow, step by step, as a tour operator rather than as a lawyer.
The product page states the category. One line, near the price: this is a package, and package rights apply. Beneath the price sits what the price includes and the general destination requirements. The accommodation and transfer options a traveller can add are presented as part of the same package, not as a separate basket that quietly changes the legal character of the sale.
The traveller details step collects what you need to perform the contract and nothing more. Passport numbers belong here only if a supplier genuinely needs them before departure; collecting them because the form had a field is a data problem you did not need.
The summary step is the heart of it. The full price, broken into what is paid now and what is due later with the dates. The itinerary in short. The organiser's identity and contact, the insolvency protector, the cancellation schedule, the standard package-rights information, each as its own readable block. One acceptance, recorded with a timestamp against the booking, that refers to exactly what was on the screen. The confirmation email repeats the same information, because the obligation is to provide the contract on a durable medium, and an email the traveller can keep is the cheapest durable medium there is.
Then the admin side, which is where "bolted on" shows most clearly. A cancellation arrives. Staff should see the schedule that applied to that booking, apply it, and issue the refund from the same screen, with a role that permits it and a record that it happened. A price query arrives. Staff should see what the traveller was shown. None of this is exotic. It is simply what a booking record has to carry when the booking is a contract rather than a reservation.
On this platform a tenant activates tour packages as a service alongside flights, hotels and attractions, and shows only what it sells, so an operator who sells its own circuits does not inherit a flight tab it cannot stand behind. The storefront ships in 40 languages, which matters more here than it first appears: pre-contractual information in a language the traveller reads is the difference between informed and notified. Each site chooses its default currency and the list it offers, and every tenant gets its own admin panel with role-based staff permissions, its own bookings, customers and reports. The disclosure text, the protector and the fee schedule remain yours to write and to verify; the platform gives them a place to be read and a record of having been read. If you want to see what that storefront provisions before deciding anything, start one from the signup wizard, which brings a site up on a platform subdomain without asking for a card. The go-live questions that follow are covered in our pre-launch checklist.
What this costs you if you get it wrong
Consider the operator who sold the circuit as "a tour with optional hotel" and never said the word package. A traveller who was not told they bought a package still has package rights; the omission does not remove them, it removes your defence. When the coach company fails mid-season, you carry performance liability for the whole trip, not for the part you ran. When a hotel you contracted cannot honour an allotment, the traveller's remedy is against you, and your recovery from the hotel is a separate, slower conversation.
Consider the price. An amount shown on the product page that excludes a fee later added at checkout is, in several member states, a price the operator is held to. Consider the cancellation schedule nobody saw, and the chargeback that follows when the traveller's bank takes their side. Consider the national enforcement authority, which in most countries acts on complaints rather than inspections, which means the cost arrives exactly when you have the least room to absorb it.
None of these are software problems, and a template will not fix any of them. They are flow problems, and the flow is yours.
Selling across borders inside the single market
The Directive is EU-wide, but it is transposed into national law, and the details differ: how insolvency protection is organised, what the enforcement body is, how the standard form is worded. An operator in Austria selling to a traveller in the Netherlands is dealing with a traveller whose expectations were formed by Dutch practice. The honest position is that you check the transposition where you are established and take advice on the markets you actively sell into, rather than assuming one text serves all.
The storefront can at least remove the language and currency excuses. A Dutch traveller reading your package-rights block in Dutch, with the price in EUR and the protector named, has been informed in a way the regulator recognises. The same traveller reading it in your language, with a conversion in their head, has been notified. The requirements that follow from running a storefront in a given market are the subject of our piece on regional requirements for agency software, written for the Gulf but with the same shape of argument.
Direct distribution gives a tour operator back the margin agents used to take and the relationship agents used to own. It also gives you the paperwork. Build the flow so the paperwork is the flow, and the Directive stops being a risk and becomes the reason a traveller trusts a site they found an hour ago.