Raves
One room.The whole night.
A rave needs one shop, one pass, and a door that does not wait on CRM logins. Early bird, door price, and guest list sit in the same checkout. Buyers add the pass to Apple or Google Wallet before they hit the door.
- One shop for early bird, door price, and guest list.
- The ticket is an Apple or Google Wallet pass in your colors.
- Pair a phone for the door. Staff do not need a CRM login.
- After the night, Finance shows gross, fee, and net, then pays out.
Festivals
Days and types.One door.
A weekend is more than one ticket. Sell the full pass, Saturday, Sunday, and add-ons like parking or shuttle in the same cart. Each type can carry its own Wallet art. At the gate, paired phones scan the same way they do at a rave.
- Weekend tickets, day tickets, and add-ons in one shop.
- Each ticket type can have its own Wallet pass.
- Pair door phones for the gate. Staff do not log into the CRM.
- Finance stays one page for the whole site, then pays out to the house bank.
Venues
The house.Many nights.
The room runs many nights. Keep seating, scanners, and payouts on the house account. Publish the next lineup from Overview. Buyers still get a Wallet pass. Door staff still pair a phone. The shop look and the €0.49 + 2% fee stay with the house.
- One company for a catalog of nights you run in the same room.
- Reuse reserved seating or GA on the house setup.
- Payouts and the €0.49 + 2% fee stay on the same Finance page.
- New nights pick up the shop, pass, and door you already run.
