Strawberry helps event teams work through orders, tickets, attendee data, check-in lists, box-office quotas, and on-site exceptions. It can prepare an operational brief from the event workspace you have open, so the people at the door, in customer support, and in event operations share the same picture without anyone changing a live configuration by accident.
01
Give the event team one operational picture before doors open.
Orders, tickets, and check-in lists answer different questions, and the event lead should not need to reconstruct them across several views on the morning of the event. Strawberry can prepare one visible-status brief covering sales activity, attendee exceptions, check-in readiness, and issues requiring a decision.
02
Check the check-in logic before a ticket reaches the scanner.
Multiple check-in lists can support complex entry rules, but they also create room for confusing product scope and manual exceptions at the entrance. Strawberry can inspect the lists you expose and prepare a practical door-team note that identifies the policies needing a human confirmation.
03
Keep quota decisions with the person who owns the room.
Ticket availability affects capacity, revenue, and the promise made to attendees.
Strawberry can help the event owner see the visible sales and quota context, but it should only prepare the decision note, not alter a product, price, or allocation.
04
Prepare the doors-open brief once, at the point the venue needs it.
An event-morning review is useful because it captures the final overnight orders and exposes problems while organisers can still brief staff. Record the event scope in a pretix skill and let a routine prepare the read-only opening brief at 07:30 on each event day.
pretix Strawberry