Travel booking technically executed incorrectly: liability for input and system errors

If the travel date, name or booked service differs from the instruction after an online or travel agency booking, the booking process must be reconstructed first. Section 17 of the Austrian Package Travel Act, or PRG, deals with liability for technical defects in a booking system and certain errors made while an undertaking is arranging a booking. Booking errors attributable to the traveller and unavoidable and extraordinary circumstances are excluded.

The relevant questions are what the traveller entered and confirmed, what the system displayed, who undertook to arrange the booking and when the discrepancy first became visible. This article deals with an error in the booking process. A correctly booked room that later becomes unavailable requires the separate assessment in hotel overbooking. The distinction between a package and a linked travel arrangement is addressed in the article on the booking flow.

Section 17 PRG names the travel organiser, the travel intermediary, the undertaking that facilitates linked travel arrangements and the undertaking providing travel services. Each is liable for errors caused by technical defects in the booking system to the extent that the defect is attributable to that undertaking.

A further rule concerns an undertaking to arrange the booking. If an undertaking agrees to arrange a package travel booking or a travel service forming part of linked travel arrangements, it is also liable for errors it makes during that booking process. The concrete instruction therefore matters more than a label such as portal, travel agency or supplier.

The provision addresses attribution within the booking process. It does not mean that every later discrepancy is automatically a booking error. Non-availability, overbooking or a later change to the service may occur after the booking and require a separate contractual assessment.

A technical defect may exist where the booking system fails to transfer an input, stores a different service or produces a confirmation that differs from the request. A mere suspicion of a software defect is not enough for attribution. The process must be made traceable through the available records.

The original request, input mask, visible summary, confirmation, payment data and later communications should be compared. In a travel agency case, it is also important which information was passed to the traveller and which booking was actually sent to the organiser or service provider.

The technical cause may lie in the undertaking’s own system, an interface or a booking step operated by another business. That fact alone does not settle liability. The question remains which undertaking is responsible for the defect on the basis of the concrete process.

An undertaking that arranges a booking at the traveller’s request takes on a concrete activity. A travel agency may do this when it receives the travel details and services and carries out the booking. Another undertaking may take on the same role if it agrees to arrange the booking.

The instruction, advice, questions, input data and confirmation must be read together. An advertising page or the technical provision of a website does not by itself prove that an undertaking accepted the booking within the meaning of section 17 PRG. Calling the business an intermediary also does not remove the need to examine the actual process.

Liability for an undertaking’s own error during the accepted booking is distinct from liability for a technical defect in the system. Both bases may concern the same booking, but they require different evidence. The travel contract and the role of each undertaking should therefore be recorded separately.

Section 17 PRG excludes booking errors attributable to the traveller. This may apply where the traveller entered the wrong date, name or departure airport and the error was clearly displayed before confirmation. The fact that the traveller made the input does not decide every case, however.

It must also be examined whether the input was clearly labelled, whether the summary showed the correct content and whether the confirmation matched the previously confirmed instruction. If the final booking differs despite correct input or confirmation, a premature attribution to the traveller is inappropriate.

The exception must be connected to the concrete process. An undertaking cannot rely only on a general notice if the data transfer, display or confirmation identifies a different service. Technical records and communications are therefore as important as the input itself.

Save the booking confirmation in the form received. This includes the instruction, written input, screenshots of the summary, payment records, emails, chat messages and the time of booking. After a phone call, record the date, participants and a factual summary of what was said.

Complain to the undertaking that accepted the booking process or issued the confirmation. Describe the requested service and the service actually shown. Ask for a traceable review of the booking data. A general narrative without a comparison of the two data sets makes attribution more difficult.

Section 17 PRG does not set a general special deadline for every complaint in this context. Contractual conditions, imminent travel services and other legal bases may still require a prompt response. The absence of a special deadline does not mean that documents or messages can be kept indefinitely without care.

A booking error concerns the route to the contractually confirmed travel service. In an overbooking case, the service was initially booked correctly but is later not provided. Replacement accommodation, extra costs and a possible price reduction then become central. This is the separate issue addressed in hotel overbooking.

The classification as a package or linked travel arrangement is also a prior question. It identifies the contractual structure and the undertakings involved. The article on the booking flow deals with that distinction. Section 17 PRG then focuses on the concrete booking and its technical or organisational execution.

A later change to the travel contract, a travel defect at the destination or an organiser’s insolvency is therefore not simply another version of a booking error. Timing is an important criterion: what did the confirmation state immediately after booking, and what changed only later?

For an initial legal assessment, a clear booking file and a short chronology are often enough. Arrange the original instruction, input, system display, confirmation, payment records and each complaint by time and sender. Mark which points are undisputed and which are only assumptions.

If several undertakings were involved, record their roles separately. Note who advised, who entered the booking, who confirmed it and who supplied the travel service. This separates the technical booking process from later performance of the trip.

An individual assessment depends on the concrete booking route and the preserved communications. The overview of package travel and organisers explains the main roles. The package travel check can also help prepare the facts.

Receive new articles and legal information from the firm through BRANDaktuelle legal updates.