When selling event tickets, it is important to formulate clear and comprehensive general terms and conditions (GTCs). These GTCs protect both the company and the participants and create a transparent basis for the business relationship. Here are the most important points that must be observed in the GTCs when selling event tickets.
Description: Clear definition that the terms and conditions (T&Cs) apply to the sale of event tickets. It should specify which events and types of tickets are covered by these terms.
Example: “These General Terms and Conditions apply to the sale of tickets for all events offered by [Your Company].”
Description: Explanation of how the contract between the ticket seller and the buyer is formed. The ordering process should also be described in detail.
Example: “The contract is concluded once the customer completes the order and receives an order confirmation via email.”
Description: Information on ticket prices, any additional fees (e.g., shipping or processing fees), and accepted payment methods.
Example: “The stated ticket prices include the statutory VAT. Additional fees may apply. Accepted payment methods are credit card, Twint, and instant bank transfer.”
Description: Information on how and when the tickets will be delivered to the buyer, whether by email, post, or collection at the box office.
Example: “Tickets will be sent according to the selected delivery method either by email for self-printing or by post within 5 business days after payment is received.”
Description: Rules regarding the cancellation and refund of tickets. It should be clearly stated under what conditions a refund is possible.
Example: “A refund of the ticket price is only possible if the event is canceled. In other cases, there is no entitlement to a refund.”
Description: Notices about possible changes in the event program and the rights of ticket buyers in such cases.
Example: “[Your Company] reserves the right to make changes to the program, date, or venue. In the event of a significant change, participants will be notified immediately.”
Description: Definition of the limits of the organiser’s liability, particularly for failures or delays beyond their control.
Example: “[Your Company] is only liable for gross negligence or intentional misconduct. No liability is assumed for failures or delays beyond our control.”
Description: Statement on the handling of customers’ personal data in accordance with data protection laws.
Example: “Customers’ personal data is stored and processed in accordance with applicable data protection regulations. Data will only be shared with third parties as part of contract processing.”
Description: Information on the right of withdrawal, if applicable, and how it can be exercised.
Example: “There is no right of withdrawal for the purchase of event tickets according to the respective legal article per country. For example, in Germany '§ 312g Abs. 2 Nr. 9 BGB.'”
Description: Additional general provisions, such as applicable law, jurisdiction, and severability clause.
Example: “The law of the Federal Republic of Germany applies. The place of jurisdiction is [Your Company’s Location]. Should any provision of these T&Cs be invalid, the remaining provisions shall remain unaffected.”
The T&Cs for the sale of event tickets should be clear, understandable, and comprehensive. They regulate the contractual relationship between the seller and the buyer and provide legal certainty for both parties. Careful drafting of these terms helps to avoid misunderstandings and legal issues.
To store your own terms and conditions in Oniva for the sale of event tickets, proceed as follows.
By capturing the general terms and conditions at the workspace level, you ensure that the stored T&Cs are activated for all events. Alternatively, the T&Cs can be disabled at the event level in the permissions group if you are conducting an event without payment.
No general terms and conditions for ticket sales at hand? Fill out our form to download our free, editable Word template.
Discover exciting articles about creating unforgettable events.
.svg){kind=icon}
