First event setup checklist
Use this checklist when you are preparing the first event that customers or staff will sell through KORONA Event.
The checklist follows the first go-live path: create the event, make it sellable, configure the online shop, test checkout, confirm point of sale (POS) readiness, and verify the order in the back office.
Before you start
Confirm these decisions before you create the event:
| Decision | What to prepare |
|---|---|
| Event basics | Customer-facing name, description, date, start time, end time, image, venue, and address. |
| Capacity | Total number of places, whether the event is exclusive, and whether resources also limit capacity. |
| Prices | Price categories such as adult, child, reduced, group, or member, plus gross prices and quantity limits. |
| Sales channels | Whether the event should be sold in the online shop, POS, back office, or another channel. |
| Checkout details | Required customer fields, attendee questions, waiver requirements, and legal confirmations. |
| Payments | Payment provider, payment methods, payment-link expectations, and invoice handling. |
| Operations | Staff who need access to orders, attendees, tickets, reports, resources, and POS sales. |
You need back-office access that allows you to create events, edit prices, manage sales channels, configure the shop, and review orders.
1. Create the event
In the back office, open Services > Events, then select Create event.
On Create new event, enter the event name, description, date, Start time, End time, capacity, venue, and image. Use the same wording customers should see in the online shop, tickets, and confirmation email.
Check these setup points before you save:
| Field or state | Why it matters |
|---|---|
| Name | Appears in the shop, order, attendee list, tickets, reports, and POS. |
| What time details should customers see? | Controls whether customers see Date only, Start time only, or Start and end time. |
| Capacity | Controls the event-wide availability before sales channel or resource limits are applied. |
| This is an exclusive event | One booking blocks the whole event, no matter how many participants are booked. |
| Hide from shop | Keeps the event out of shop listings and search. Use it for tests or private direct-link flows. |
| Ticket is valid only for the exact duration of the event | Controls whether entry is limited to the event time or has an entry window. |
Select Create.
2. Add sellable prices
After the event is created, open the Prices tab and select Add pricing.
For each ticket type, choose the Price category, Product, Visible on the following sales channels, Min quantity, and Max quantity. Then select Update prices.
Use customer-friendly price category names. Names such as "Adult", "Child", "Reduced", and "Group" are easier for customers, cashiers, and support staff than internal abbreviations.
3. Add sales channels
Open the Sales channels tab. If the list is empty, select Add sales channel.
Choose the channels where the event should be sold. Common choices are Online shop, POS, and Back-office.
For each rule, confirm:
| Setting | Use it when |
|---|---|
| Event capacity | The channel can use the event's full remaining capacity. |
| Limited and Capacity | You want to reserve only part of capacity for this channel, such as a POS allocation. |
| Unlimited | The channel should not limit sales by participant count. Use this only when the offer should not consume capacity through this rule. |
| Sales start and Sales end | Sales can open before the event and close before, at, or after the event starts, or remain open until the event ends. |
Select Update sales channels.
4. Add checkout information
If you need extra customer or attendee information, open the event's data collection or personalization setup and add only the questions your team actually needs.
Use Collect this information per to decide whether the question is asked once per booking or once per attendee. Turn on Must answer only for fields that must be complete before the order can continue.
If the event requires a waiver, check the Waiver signature setup and test with more than one ticket so you can see whether the customer experience matches your policy.
5. Configure the online shop
Open Shops and select the shop that will sell the event. Review the Branding, Pages, Page Builder, Checkout, Calendar, Time Slots, Code snippets, and Theme tabs that apply to your launch.
Before launch, confirm:
- the shop has the correct Domain name and Sales channel
- Shop pages are active for the offer types you sell
- the event appears in the intended offer list or page builder block
- Checkout configuration asks for the right customer fields
- required legal documents are available and linked from the shop
- payment methods are active and appropriate for the event
- the shop can be tested on the same URL customers will use
6. Test customer checkout
Open the public online shop, not only the back-office setup page. Find the event, select the date or time if shown, choose ticket quantities, and use Add to cart.
Open View cart, then select Proceed to Checkout. Complete Contact information, required attendee or booking details, legal confirmations, and payment or confirmation steps.
For live payment accounts, follow your team's test-payment policy. Do not create unnecessary real charges.
7. Confirm POS readiness
If staff will sell this event at the POS, open the POS and confirm the event appears under Offers or Agenda for the correct date and venue.
Select the event, choose the Price category and Quantity, then verify that Add to receipt is available. The cashier should know whether tickets print immediately, whether receipt output comes from the connected POS, and what to do if payment is interrupted.
8. Review the order in the back office
After the test checkout or POS sale, open Orders in the back office and find the test order.
Review:
- Overview for the customer, services, gross total, payment state, and order state
- Attendees for ticket or attendee records
- Documents for invoice number, payment state, and Payment link when relevant
- History for emails, payment events, cancellations, or automatic state changes
Expected result
Your first event is ready for launch when customers or staff can sell it through the intended channel, checkout reaches the expected payment or confirmation step, and the back office shows the resulting order, related Documents, attendees, tickets, and email history.
Check your work
The setup is ready for launch when all of these checks pass:
- the event is published only when it should be visible
- the Hide from shop setting is not accidentally turned on
- at least one active price is visible for each intended sales channel
- the intended shop or POS can sell the event
- capacity and resource limits match the operational limit
- checkout fields, waivers, and legal documents match your policy
- a test customer can reach payment or confirmation
- the back office shows the expected order, Documents, attendee, ticket, and email state
- cashiers know the POS path and fallback process
Troubleshooting
| Problem | What to check first |
|---|---|
| The event is missing from the online shop | Publishing state, Hide from shop, Sales channels, active prices, future date, shop page setup, and capacity. |
| The event appears but cannot be added to cart | Remaining capacity, Min quantity, Max quantity, resource limits, required included options, and checkout policy. |
| The shop asks for the wrong fields | Checkout configuration, event questions, attendee questions, waiver setup, and required legal documents. |
| A POS cannot sell the event | The POS sales channel, date, capacity, active price rules, and whether the cashier opened the correct POS or agenda. |
| A payment or confirmation step fails | Payment provider status, payment method availability, invoice state, payment-link state, and any customer-visible error text. |
| The order exists but tickets are missing | Payment state, order state, document generation, attendee records, and whether the order was canceled or auto-canceled. |
