Pop-up supper · long table · dinner night

Sell tickets for a dinner eventAll your attention on guests. Admission already arranged.

A dinner evening starts long before the first course. Sell clearly described admission in advance, agree quantities with the kitchen and let guests know exactly what their evening includes.

  • Know quantities in advance
  • A recognisable ticket page
  • Separate payment from admission
Interactive example

At the long table

Explore the offer

Dinner€39.00 per ticket
2
Example subtotal€78.00

Not a real booking. Fictional prices, excluding service and payment fees. No seat selection.

From the first click to welcome.One clear ticket journey

Example of admission including dinner. No automatic table reservation, seat selection or dietary-preference collection.

01 · A clear offer

Explain what visitors receive.

02 · A tested ticket journey

Check the order and confirmation.

03 · A prepared entrance

Welcome with one agreed process.

01

Explain exactly what the dinner ticket includes

Publish the number of courses, arrival time and which drinks or other elements are included or excluded. A clear description prevents guests expecting something different from what the kitchen prepared. Identify the organiser and explain where menu questions should go. Create a separate ticket type only when it represents a genuinely different offer. Admission is not a restaurant reservation system and does not automatically assign a guest to a particular chair or table.

Before moving on
  • Publish the start time, venue and inclusions before purchase.
  • Arrange requests to sit together through a separate process.
02

Let the kitchen define the sales limit

Your capacity depends on more than chairs. Consider the kitchen, service team, course changes and equipment. Match admission quantities to the tightest limit and account separately for organiser guests in your plan. If you sell several menu variants, check their combined quantities yourself. Separate events can keep different dinner sittings or dates apart. Close sales at a point where you can still purchase ingredients and prepare reliably rather than accepting bookings the kitchen cannot fulfil.

Before moving on
  • Agree a workable maximum with the kitchen and service team.
  • Before purchasing, check paid orders rather than reservations alone.
03

Give dietary questions a clear contact route

A QR ticket does not automatically contain the information needed to prepare an adapted meal safely. Publish a contact and a deadline for questions on the event page. Let the kitchen assess what is possible and confirm the arrangement directly with the guest. Do not collect sensitive details in public group lists. Never promise an allergen-free menu or automatic dietary-preference processing unless you have explicitly arranged that with the people preparing the food.

Before moving on
  • Explain where to send menu and accessibility questions.
  • Share essential arrangements only with the people carrying them out.
04

Connect the ticket email to a calm welcome

Complete a sample order before sharing the sales link. Check the date, ticket quantity and arrival instructions. Scan QR tickets on arrival and handle table questions away from the entrance so the queue keeps moving. Agree beforehand what happens when a guest cancels or the schedule changes. Budget separately for platform fees and payment-provider charges; ticket revenue is not the amount remaining after ingredients, venue and service expenses have been paid.

Before moving on
  • Test scanning with your host at the actual venue.
  • Make cancellation and change conditions visible with the offer.

Good to know

A few clear answers.

From a plan to the first ticket

Set the table. Get ticket sales ready first.

Tell us what you are organising. We will explore the ticket journey, identity and settings that fit.