Skip to content

Tickets

An event has a date and a number of seats. When the seats are sold, sales close automatically, and at the door each ticket is checked in once.

Create the event

  1. 01Go to Events in the dashboard.
  2. 02Set name, date and price.
  3. 03Set the capacity, that is, how many people there is room for.
  4. 04Publish. The event is shown on your page.

Capacity is enforced

The system keeps track of the capacity, so nobody has to remember it. When the last seat is sold, no more tickets can be bought.

Two guests can take the last two places at the same moment. We check the places before payment opens, but both payments are already under way. The one who comes last gets the whole amount back straight away, handling fee included, and we do not keep our service fee either. No tickets are created, and you do not need to do anything. The guest gets an email saying exactly that: there were no more places when the payment went through, and the money has been sent back. The same 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 email, we send it automatically. The email contains a link to the guest's own ticket page with a QR code. If you issue tickets without an email, because you hand them out yourselves, 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 bounces, because the mailbox does not exist or the recipient rejects it, the ticket's row and the event's card say «did not arrive». That is worth knowing, because the guest rarely notices it themselves: if one person booked the table for seven others, the other six do not know a ticket was sent. Correct the address on the row and send again, and the mark disappears.

You can send guests a reminder before the event takes place. Under Settings you choose how long before (from one day to 7 days), and each guest then gets one email with the time, the place and their ticket again. If there is a collection, the guest's own time slot appears in the email instead of the event's start time. We only send to places that were actually delivered, and only for events that are still going ahead: 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 the guest's row shows when it has been sent.

The ticket page always shows the ticket's current state. If it has been used or cancelled, or the event has been cancelled, the page says so instead of showing 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 a connection on your side.

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, and the ticket is checked in straight away. The same screen also reads gift cards, so staff do not have to pick the right screen first. If the camera does not work, the code can always be typed in.

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, showing how many orders are waiting and how much they come to. One press sends the money back to all of them: the whole amount including the handling fee, to the card that paid. We do not keep our own service fee on an event that did not happen either. If there are many orders, it takes a few rounds, and the screen counts down along the way; it is always safe to press again, because an order that has been paid back is not included a second time. Each guest is told when the money is on its way, so you do not have to ring round.

Two kinds of orders are left behind, and both are shown on the screen: orders that were never paid, and orders with an open dispute. During a dispute the bank holds the money while it reaches its decision, and a refund on top of that would give the buyer the amount twice. You respond to the dispute in Stripe.

Multiple ticket types

One event can be sold at several prices at once, for example «New Year menu» and «New Year menu, vegetarian», or standard and VIP. Each type has its own name, its own price and its own description, and the guest enters a quantity for each. It becomes one order and one payment.

Each type can have its own number of places, for example «the first 100 at DKK 150, then DKK 200», 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 places, and more types cannot make the venue bigger. If you sell in releases, one type can open when another sells out: choose «Åbner når … er udsolgt» on the price, and release 1 only goes on sale once the early bird is gone, or on its own date if that comes first. That way two releases are never on sale at the same time.

Collection: where and when

If the guest needs to collect something, such as a menu or a hamper, the event can have collection times. Place and time slot are one choice: «Copenhagen · 14:00–16:00». If the event has collection times, the guest must choose one before they can pay, and the choice appears on the ticket and in your overview.

Each collection time can have its own number of places, and they count across the ticket types: 40 covers in Copenhagen is 40, however many of them are vegetarian. The event's capacity is still the overall ceiling, so more collection times cannot make the venue 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.

If places become free, because someone 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 as there are places, in the order they signed up. We do not hold a ticket for anyone, and the email says so: tickets are sold on a first come, first served basis. 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. The two numbers 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, tick the box next to the number and let the number be the ceiling. The table then becomes one document with the number the guest entered, and that is the number that leaves the room. A coffee bar with 55 chairs at 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 DKK 0. Then there is no payment step: the guest enters their email, gets the confirmation straight away, and the place is gone from the page. No handling fee is charged either, because no ticket under DKK 25.00 carries one. So «free» means free for the guest and not just the ticket price.

The guest can cancel from their own ticket page, and the place goes back on the page in the same second. If there is a waiting list, we write to it on the next run. On your side the booking shows as a cancellation by the guest, which is different from a voided booking: that means you gave the money back.

An amount for the bar

A ticket type can include an amount with a bonus on top. When the table has been 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 deduct from it 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, and the guest sees one figure on the page. Whatever is not spent is still the guest's: the card lasts 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 turn the purchase into a gift card, which has a 14-day right of withdrawal. The bonus on top may take the total higher, and does in the example above.

The same evening every week

If you hold the same evening every week, create it once and press «Gentag hver uge» on the event's row, or «Gentag hver måned» if the evening is, for example, the first Saturday of the month. 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 ahead with prices nobody had looked at would be exactly the kind of surprise this should not be. You open the draft, correct the line-up or price and press publish. If you are simply open every Friday and Saturday, turn on «Sæt nye aftener til salg med det samme» on the series, and each new evening goes straight on sale. And if you hold a special evening on a day the series would otherwise open, the series does not open its own evening on top of it. If you cancel the special evening, the ordinary evening comes back by itself. The evening you pressed «Gentag hver uge» on becomes the series' first evening. If you have since adjusted one of the evenings, such as the line-up, poster or prices, choose «Opdater serien fra denne aften», and the following evenings open with that content; the series does not touch the ones that are already open.

The series are at the top of Arrangementer. There you choose whether the evening repeats every week or once a month (the first, second, third, fourth or last of a weekday), which weekdays it falls on, how far ahead the diary should stay open (in weeks, and in months for a monthly series), and which days you are closed, such as Christmas Eve or the holidays. A closed day is skipped. If you pause the series, it stops opening new evenings; the evenings that already exist stay, because they are someone's Friday.

If you sell tables and booths for your nights, the booking page can show them together. Choose «Nightclub» under Table booking › Settings, and the booking page shows your upcoming nights with the table packages instead of times, and it does not cost a plan. See Table booking › For nightclubs.

Your programme on your own website

If you have a website, it can build its own event pages from Kuvert. No API key is needed, because it is the same information the shop itself shows. You create the evening in Kuvert, and the site fetches the rest: poster, text, times, prices, line-up and a button for the tickets.

CallReturns
GET /v1/merchants/{slug}The shop and the evenings on sale (events). With ?include=canceled, cancelled evenings are included too, until they would have ended, and with ?include=closed, the evenings where online sales have closed but the evening is not over. They have onSale: false and refusalCode: closed. Both can be used together: ?include=canceled,closed.
GET /v1/merchants/{slug}/events/{slug}One evening with prices, status and the fields below, including a cancelled evening.
GET /v1/merchants/{slug}/seriesYour recurring series with weekdays, the rule (recurrence) and a ready-made sentence to show (description, for example «Hver torsdag» or «Første lørdag i måneden»), and the evenings of each that are on sale.
GET /v1/merchants/{slug}/events/{slug}/planThe club's map for one night with table packages: the rooms, dancefloor and bar, and every table with its number of seats and whether it is free or sold. No guests' names.
FieldMeans
statuspublished or canceled, and draft on an evening that has not been published yet. The evening says itself where it stands, so the site never has to guess from its absence.
cancelNoteThe message you wrote under «Cancelled». Only on a cancelled evening.
series, seriesDateThe series behind the evening with name, weekdays (0 is Sunday), isRecurring, recurrence (every week, or one weekday a month) and description, and which of the series' days it is. Empty on an evening you created yourselves.
subtitleThe subtitle under the name.
lineupThe names in running order, each with name, role and time. time is a time with a date, so a set after midnight lands on the right day.
genres, dressCodeThe genres and the dress code, as you wrote them.
doorsAt, lastEntryAtWhen the doors open, and when the last guest is let in.
opensAfterTierIdOn a price in tiers: the price this release waits for. While that one is selling, this price’s availability is not_yet; it opens when the other sells out or closes, or at its own salesOpenAt if that comes first. Only present when the price waits.
priceModeOn a price in tiers: seat when priceOre is the price per person, for example a pub quiz at DKK 10 per person, where a team of five pays DKK 50 for one ticket. Only present when the price is per person; otherwise priceOre is the price of one ticket.

Was this page helpful?