Most refund disputes start not because a buyer had an unreasonable expectation, but because the policy they agreed to was vague enough to support two different interpretations. The buyer reads it one way, you meant it another way, and now you're spending an hour on a support conversation that shouldn't exist.
A good refund policy isn't the most generous policy or the strictest policy. It's the clearest one.
The legal baseline in Poland
Before writing your policy, understand the minimum legal requirements. Under Polish consumer law (implementing EU directives), buyers of event tickets purchased online typically do not have a standard 14-day withdrawal right — entertainment services with specific dates are explicitly excluded from that right.
That means you have more latitude than buyers sometimes claim. But this doesn't mean "no refunds ever" is a defensible position. It means your policy has to be clearly communicated before purchase and consistently applied.
The key legal requirement: your refund policy must be visible before the buyer completes the purchase. Not in a terms document buried three clicks deep — at the checkout stage, where a buyer can read it before confirming their order.
The four scenarios your policy must address
- The buyer wants to cancel for personal reasons (can't attend, changed plans)
- The event is cancelled by the organizer
- The event is postponed to a new date
- The event changes significantly (different lineup, venue change, major format shift)
Scenario 1 is where organizers most often disappoint themselves by being vague. "No refunds" without any exceptions creates a hostile experience and generates the most complaints. A structured policy with clear windows and conditions serves everyone better.
Scenarios 2 and 3 are where you need to be unambiguous. If you cancel, buyers are legally entitled to their money back in Poland — this isn't discretionary. Your policy can specify the mechanics (how long refunds take, whether booking fees are returned), but it cannot deny the refund itself.
A practical refund window structure
| Request timing | Refund | Notes |
|---|---|---|
| More than 30 days before event | Full ticket price (minus booking fee) | Easy to resell the seat |
| 14–30 days before event | 75% of ticket price | Partial recovery of operational costs |
| 7–14 days before event | 50% of ticket price | Hard to resell at this stage |
| Less than 7 days / no-show | No refund | Resale window effectively closed |
| Event cancelled by organizer | Full ticket price | Required by law |
| Event postponed | Ticket valid for new date, or full refund | Buyer's choice within 14 days |
This kind of tiered structure is standard in the event industry and buyers generally understand it. The declining refund with notice makes sense — your costs and resale difficulty increase as the date approaches.
Ticket transfers as an alternative to refunds
Many refund requests come from people who can't attend and just want to recover their money. Offering a free ticket transfer option — where the buyer can give their ticket to someone else — reduces refund requests substantially.
We switched from paper tickets last season. Refund handling alone saved us 15 hours per event. — Agnieszka P., Theater Production Manager, Warsaw
If your platform supports ticket name transfers, mention it prominently in your policy. "Can't attend? Transfer your ticket to a friend for free" before the refund window information. Many buyers will use that option rather than requesting a refund.
Writing the policy itself
A few principles for the language:
- Use specific timeframes, not vague terms. "In advance" means nothing. "More than 30 days before the event date" is unambiguous.
- Specify whether booking fees are refundable. Most organizers keep booking/processing fees on refunds. Say so explicitly.
- State the refund method and timeline. "Refunds processed to the original payment method within 5–10 business days."
- Address force majeure. What happens if the event can't proceed due to government restrictions, extreme weather, or circumstances beyond your control? This should be covered separately from voluntary cancellation.
Keep the policy under 300 words at the checkout stage. A longer document belongs on your FAQ page or linked as a separate document. The checkout version needs to be skimmable in 30 seconds.
Where the policy lives
Your refund policy should appear in three places:
- At the ticket checkout stage — inline, not hidden behind a link
- In the booking confirmation email — buyers will reference this when they want to cancel
- In your FAQ or help section — for buyers who look before contacting support
Consistency across all three locations matters. If the checkout says "14 days" and the confirmation email says "30 days," you've created a dispute before one ever happens.
