For prepaid events
A prepaid event is a booking: a client - a company, a club, a couple getting married - hires a vendor for a set window and pays for what the guests eat and drink, on whatever terms the two of them agree.
On the day, guests order from their own phones. Anything the client covers costs the guest nothing. If a guest wants something beyond what is covered, they can pay for that part themselves, in the same flow. The order goes straight to the vendor, and the guest gets a message when it is ready to collect.
It is the same ordering flow Slipp runs at festivals, with the client paying instead of the guest.
Who pays whom
The client
A company, a club, a couple getting married
The vendor
Serves the event on the menu they agreed
The guests
Order from their phones, pay only for anything extra
After the event, Slipp invoices the vendor: 1000 DKK + 20 DKK per guest the client covers. Guests are only ever charged for what the client does not cover.
The company and the vendor agree the window, what is on the menu and what each guest gets. The vendor sets it up in Slipp as a prepaid event.
On the day, a guest opens the vendor’s page and signs in with their email. Anyone on the guest list gets in too, and new guests can be added straight from the live dashboard.
Prices can be hidden, and anything the allowance covers takes no payment step. If the guest adds something beyond it, they pay for that part in the same flow. Either way, they get a message when the order is ready to collect.
When the event is over, the vendor ends it and pulls the consumption report - what the client actually covered, item by item.
Access to ordering is based on email addresses. You can set an email domain - every address at @company.com, say - and/or a list of individual addresses that are allowed to order.
A guest list covers everyone else: consultants, partner-agency staff, plus-ones, or someone whose Slipp account is on a personal address. Domains and the guest list work together, not instead of one another.
And if someone is standing at the counter who is on neither, the vendor adds them straight from the live dashboard. Everyone else orders and pays as usual.
An allowance group is a plain description of what the client has agreed to cover per head - for example "1 burger" and "3 drinks per guest". Each group covers a set of items on the menu the event runs on, with a quantity per guest.
Guests see what they have left while they order, so the counter never has to say no. Anything the groups do not cover, the guest simply pays for at checkout - and a group that covers every item, with no limit, puts the whole menu on the client’s tab.
For example
Slipp records every order placed through it at the event, so nobody has to reconstruct it afterwards. The report runs live during the event and is final once it ends: how many distinct guests, how many orders, and how many of each item went on the client’s tab.
How the vendor bills the client is between the two of them - the report is there if it helps. It covers what went through Slipp, so anything handed over at the counter outside Slipp will not appear. It lists, item by item, the covered value at the vendor’s own menu prices. What a guest paid for themselves is not in those numbers - that is an ordinary paid order.
What it costs
Slipp invoices the vendor 1000 DKK per event plus 20 DKK for every guest the client covers, both excl. VAT, once the event has ended. There is nothing up front and no subscription.
How you bill your client for the event is between you and them - we invoice you the same either way.
Tell us about the event and we will help you price it.
See the full cost of a prepaid event: what we invoice you
Looking for standard pricing? See how the attendee-paid fee works
Tell us about your stall and the events you trade at, and we'll get back to you within 24 hours.