Create the event
- 01Go to Events in the dashboard.
- 02Set name, date and price.
- 03Set the capacity — how many seats there are.
- 04Publish. The event is shown on your page.
Capacity is enforced
Capacity is a ceiling the system maintains — not a note someone has to remember. When the last seat is sold, no more tickets can be bought.
Two guests might grab the last two seats in the same instant — we check the seats before opening payment, but both payments are already on the way. The one who comes second gets the whole amount back straight away, handling fee and all, and we don't keep our commission either. No tickets are created, and you don't need to do anything. The guest gets an email saying exactly that: there were no more seats when the payment went through, and the money is coming back. The same thing appears on the guest's receipt page if they go back to it.
The guest gets the ticket
If you issue a ticket with a recipient's email, we send it automatically. The email contains a link to the guest's own ticket page with a QR code. If you issue without an email — for an agreement to share them yourself — the link to each ticket is in the dashboard, ready to copy or print.
If an email address is wrong, you correct it on the guest's own row under Tickets and send again from there. The 'Send missing tickets' button cannot help here: it only sends what was never sent, and a ticket that has been sent to the wrong address shows as sent. The same button on the row sends the ticket again to the address already there if the guest has simply deleted the email.
We follow up on whether the email got through. If it's rejected — the mailbox does not exist, or the recipient rejects it — it shows on the ticket's row and on the event's card: 'did not arrive'. It's worth knowing, because the guest rarely notices it themselves: if one person booked the table for seven others, the other six don't know a ticket was sent. Fix the address on the row and send again, and the mark disappears.
You can send guests a reminder before the event happens. Under Settings you choose how long before — from one day to 7 days — and each guest gets one email with the time, place and their ticket again. If there is a collection time, the guest's own time slot appears in the email instead of the event's start time. We only send to seats that have actually arrived, and only to events that are still being held: if an event is cancelled, the guests have already had that message, and a reminder on top of it would be the one they acted on. The reminder is sent once, and it shows on the guest's row when it's been sent.
The ticket page always shows the ticket's current state. If it's used, cancelled or the event is cancelled, it shows on the page instead of the QR code — so the guest knows before they reach the front of the queue.
From the ticket page the guest can save the ticket to Apple Wallet or Google Wallet with one tap. The ticket then sits in their phone with the same QR code, so it can be shown without finding the email again — and without the guest's own phone needing signal. Check-in still happens from your screen and needs connection from you.
At the door
Each ticket has its own code, even when several are bought in the same order. The guest shows the code, you check it in, and an already checked-in ticket cannot be used again.
Open Scan in the dashboard and point the camera at the guest's QR code — the ticket is checked in straight away. The same screen reads gift cards too, so staff don't have to choose the right screen first. If the camera doesn't work, the code can always be entered.
If you need to cancel
Cancel the event under Events. Everyone with a ticket gets straight away word that there is nothing doing, and the tickets stop working at the door. If the guest has saved the ticket to Wallet, it updates itself.
After that, 'Refund' opens on the event, and it says how many orders are waiting and how much it is. One press sends the money back to them all — the whole amount, handling fee and all, to the card that paid. We don't keep our own commission on an event that didn't happen either. If there are many orders it takes a couple of rounds, and the screen counts down as you go; it is always safe to press again, because an order that has been paid back is not taken along next time. Each guest gets word themselves when the money is on the way, so you don't have to ring round.
Two kinds of orders stay behind, and both show on the screen: orders that never managed to get paid, and orders with a live dispute. With a dispute the bank holds the money while it makes its decision, and a refund on top of it would give the buyer the amount twice — you answer that one in Stripe.
Multiple ticket types
One event can be sold at several prices at once — 'New Year dinner' and 'New Year dinner, vegetarian', or standard and VIP. Each type has its own name, its own price and its own description, and the guest enters a number for each. It becomes one order and one payment.
Each type can have its own number of seats — 'the first 100 at 150 kr., then 200 kr.' — and its own sales window, so one type can show as coming soon or close before the others. The event's capacity is still the door: the types share the seats, and several types cannot make the building bigger.
Collection: where and when
If the guest needs to pick something up — a menu, a hamper — the event can have collection times. Place and time slot is one choice: 'Copenhagen · 14:00–16:00'. If the event has time slots, the guest must choose one before paying, and the choice shows on the ticket and in your overview.
Each time slot can have its own number of seats, and they count across the ticket types — 40 plates in Copenhagen is 40, no matter how many of them are vegetarian. The event's capacity is still the total ceiling, so several time slots cannot make the building bigger.
Waiting list
If the event is sold out, the guest can put their name on the waiting list instead of simply leaving. It asks nothing of you: the field appears on the page by itself when there is no ticket to buy, and disappears again when there is one.
When places come free — somebody gets their money back, you raise the capacity, or you open another ticket type — we write to the people at the top of the list. As many of them as there are places, in the order they signed up. We do not hold a ticket back for anybody, and the email says so: tickets are first come, first served. Each person hears from us exactly once about the event they asked about.
The list itself sits on the event under “Waiting list”, and the number is on the event's card. It is the figure that tells you whether the night should be run again: a sold-out Friday with forty names behind it is not the same as a sold-out Friday with two.
Tables and table bookings
A ticket type can admit more than one person. «Booth for 6» is one document, six chairs and one QR code at the door. The number sits on the TYPE and not on the event, so the same evening can sell single tickets, tables and booths side by side — and the two numbers on the type mean different things: the quantity is how many booths there are, while the event’s capacity is how many people there is room for.
If the guest should say how many they are, you tick the box beside the quantity and let the number be the ceiling. The table then becomes one document with the number the guest wrote — and that is the number that leaves the room. A coffee bar with 55 chairs across 13 tables puts 13 on the type and 55 on the event.
A collection time can also have a number of TABLES beside its number of places. The two are not the same: 27 parties of two fill 54 chairs and twice as many tables as exist. The shop page shows whichever of the two runs out first.
Table bookings without payment
A ticket type may cost 0 kr. Then there is no payment on the way: the guest writes their email, gets the confirmation straight away, and the place is gone from the page. No handling fee is charged either — no ticket under 25.00 kr. carries one — so «free» means free for the guest, not only the ticket price.
The guest can cancel from their own ticket page, and the place goes back on the page the same second — if there is a waiting list, we write to it at the next pass. On your side the booking reads as a cancellation by the guest, which is something other than a voided one: the latter means you gave the money back.
An amount for the bar
A ticket type can come with an amount — and a bonus on top. When the table is paid for, the amount is issued as a perfectly ordinary gift card to whoever holds the ticket: «pay 2.000, drink for 2.200». You draw it down on your own screen like any other gift card, and the guest can watch the balance count down on their own ticket page. It is a minimum spend without anything having to read your till.
The amount sits on the ticket type as what you want to give, and the bonus as a percentage — the guest gets one figure to look at on the page. What is not spent is still the guest’s: the card lives as long as all your other gift cards. The amount itself cannot be larger than the price — a ticket for a specific date is exempt from the right of withdrawal, and an amount larger than the price would make the purchase a gift card, which carries 14 days of it. The bonus on top may carry the total higher, and does in the example above.
The same evening every week
If you hold the same evening every week, you create it once and press «Gentag hver uge» on the event’s row. The evening becomes a series: it remembers the evening’s shape — prices, times, age limit, capacity — and opens the coming weeks by itself.
The new evenings arrive as drafts. That is deliberate: a series that put evenings on sale eight weeks out with prices nobody had looked at would be exactly the kind of surprise this is not meant to be. You open the draft, correct the line-up or the price, and press publish.
The series sit at the top of Arrangementer. There you choose which weekdays the evening falls on, how many weeks ahead the diary should stay open, and which days you are closed — Christmas Eve, the holidays. A closed day is skipped. If you pause the series, it stops opening new evenings; the ones that already exist stay, because they are somebody’s Friday.