Choosing a ticketing platform is a bigger decision than it looks. You're not just picking a checkout tool — you're choosing who handles your attendees' payment data, who owns the customer relationship, and what happens when something goes wrong at 8pm on event night.
Most platforms look similar on the surface. The differences show up in the details, and those details matter a lot when you're running an event with 500 people expected at the door in two hours.
Here are the seven questions we'd ask before committing to any platform.
1. Who owns the attendee data?
This is the most important question and the one that gets the least attention. When someone buys a ticket through your event page, do you have access to their name, email address, and purchase details? Or does the platform hold that data and only share aggregated reports with you?
Some major ticketing platforms treat attendee data as their asset. They use it to market future events to your audience — including competitors. If your platform can send email to your ticket buyers about other events without your permission, that's a problem.
Ask for it in writing: "Do you share or market to our attendees' contact data for any purpose other than processing our event?" A clear yes-or-no answer matters here.
2. What are the actual fees?
The headline fee percentage is rarely the full picture. Common add-ons that inflate the true cost:
- Payment processing fees (separate from the platform fee)
- Payout fees or withdrawal minimums
- Fees for using offline or mobile scanning
- Fees for exporting attendee data
- Fees for refunds (charged to you, not the buyer)
Ask for a worked example: "If I sell 500 tickets at 80 PLN each, what will I actually receive after all fees?" If they can't or won't answer that clearly, assume the number is higher than you expect.
3. When do you get paid?
Cash flow matters. Some platforms hold funds until after the event — which means you spend money on venue deposits, staff, and logistics before you see any ticket revenue. Others release funds on a rolling basis as tickets sell.
For large events, a 30-day post-event payout schedule can genuinely create cash flow problems. For smaller organizers running events out of pocket, it can make certain events simply impossible to finance.
4. What does the scanning setup look like?
If the platform provides scanning software, test it before you commit. Specifically:
- Does it work offline?
- Can multiple devices scan simultaneously without conflicts?
- How quickly does it scan — under 1 second per ticket, or slower?
- Is it a dedicated app or a web-based tool? (Web tools are unreliable on-site)
Ask if you can do a test event with a small number of tickets before your main event. Any reputable platform will allow this.
5. What happens if the platform goes down during your event?
This is an uncomfortable question but a necessary one. If the ticketing platform's servers go offline when your attendees are at the gate, what's your fallback? Does the scanning app have a cached attendee list that works offline? Is there a phone number you can call for emergency support?
A platform's uptime claim in a sales pitch is very different from its incident response when you're standing at a gate at 8pm with 300 people in queue.
Check whether the platform publishes an uptime history. Look for a status page. If they don't have one, that tells you something about how seriously they take reliability.
6. Can you handle the payment methods your buyers expect?
For events in Poland, this is particularly important. International platforms often support card payments and PayPal, but not BLIK or Przelewy24. A significant portion of Polish buyers — especially younger demographics — prefer BLIK for quick mobile payments. If your ticketing platform doesn't support it, you're losing sales.
Check the full payment method list, not just the headline integrations. And verify that the payment options are actually available in Poland, not just listed as "coming soon" or available in other markets.
7. What does the support experience actually look like?
Most platforms have 24/7 support listed on their pricing page. What that means in practice varies enormously — from a dedicated account manager who responds in minutes, to an email ticketing system staffed during US business hours only.
For event organizers in Poland, a platform whose support operates primarily on US Eastern Time is only helpful for problems you discover well in advance. On-the-day issues won't get resolved in time.
Test support before you need it. Send a question to their support channel and see how long it takes to get a real answer. If the response is a link to a help article instead of an actual answer, that's what you'll get when you have a real problem.
The summary
| Question | What a good answer looks like |
|---|---|
| Who owns attendee data? | You do, unconditionally |
| Total fees? | Clear worked example provided upfront |
| Payout timing? | Rolling payouts during the sale period |
| Scanning? | Offline-capable app, under 1s per scan |
| Downtime plan? | Published uptime history + offline fallback |
| Polish payment methods? | BLIK + Przelewy24 supported today |
| Support? | Real-time response during European business hours |
The right platform for your events is the one that answers all seven of these clearly and without hesitation. If you're getting evasive answers, vague pricing, or "contact us for details" on basic questions — keep looking.
