Set up a new KORONA Event account
Use this guide for the first setup of a KORONA Event account. It gives you one recommended sequence and links to the detailed instructions for each step.
Keep the shop restricted and offers hidden until their customer-facing content and launch settings are ready.
Before you start
Prepare:
- your legal organization name, address, customer contact details, and time zone
- the people who need back-office access and the work each person should be allowed to do
- legal texts approved for your market
- payment-provider credentials and the payment methods you want to accept
- the first service you will sell, including its schedule, capacity, prices, and sales channels
- your shop domain, logo, colors, customer fields, and launch languages
You need account-administrator access. Payment credentials and KORONA.studio settings may require a colleague with access to those systems.
1. Set account identity, language, and time zone
Complete Set account language, timezone, and contact details before creating dated offers. The account time zone controls event start times, sales periods, tickets, emails, reports, and connected systems.
Check the organization's language, foreign shop languages, invoice address, customer email, phone number, website, and social links.
2. Invite users and assign access
Follow Invite a user and choose their role. Give each person the least access needed for their daily work, then confirm that at least one other administrator can support the account.
Resource users such as guides or instructors use the resource user workflow instead of normal back-office invitations. They can answer an inquiry from its email link without a login; enable login access only when they also need the resource dashboard or calendar.
3. Review connected systems
KORONA Event support connects ecosystem modules such as KORONA.studio before the account is handed over. Open Admin > Integrations to see which systems are connected before creating data that another system owns.
KORONA.studio owns shared commerce configuration such as products, prices, point-of-sale records, and voucher configurations. KORONA Event adds event-specific scheduling and customer-facing content. Read Understand KORONA.studio synchronization before configuring offers that depend on Studio data.
If you use an external booking or entry system, agree which system owns bookings The reservation of one or more offers for a customer. In KORONA Event it is represented by an order and its service items, attendees, payment state, and documents., payments, refunds, tickets, and updates so staff make changes in the correct place.
4. Add legal texts and configure payments
Add the required terms, privacy information, withdrawal information, and other legal notices with Add legal texts before launch.
Then follow Payment setup overview. Confirm the provider, credentials, live or test mode, payment methods, refund ownership, and who reconciles provider payouts.
Before announcing sales, select the intended live provider and payment methods and agree who owns refunds and provider reconciliation.
5. Choose the first offer type
Use Choose between an event, event template, admission, product, and voucher before creating the offer.
Common choices are:
| Offer type | Use it for |
|---|---|
| Event | One fixed date and time. |
| Event template | A repeated activity where customers choose a generated date or time slot. |
| Admission | General admission or day tickets without a separately managed fixed event; timed entry is optional. |
| Product | Merchandise or an add-on without an event schedule. |
| Voucher | A value or entitlement configured in KORONA.studio and sold for later use. |
This choice affects scheduling, capacity, customer selection, reporting, and later maintenance, so make it before building prices or shop pages.
6. Create the offer, schedule, and capacity
For a fixed date, follow Create a sellable event.
For repeated sessions, follow Create an event template and Create a time pattern. Add time pattern periods when high season, low season, holidays, or another date range needs a schedule that can be activated as one unit.
If staff, rooms, vehicles, or equipment limit sales, create the resources and use Limit event capacity with resources.
7. Assign prices and review sales defaults
Maintain commercial product prices in KORONA.studio, synchronize them, then assign customer-friendly price categories and quantity limits in KORONA Event. Make every participant who occupies a place — including infants, toddlers, carers, or free-ticket holders — use a product that reduces capacity.
New offers are available to all configured points of sale and use the offer's full remaining capacity by default. Change the Sales channels rules only when you need a sales start or end, want to restrict specific points of sale, or must reserve part of the capacity for counter sales.
Read How sales channels and visibility work before troubleshooting an offer that appears in one channel but not another.
8. Configure the shop and customer communication
Follow Configure your online shop to set branding, pages, page-builder content, checkout fields, calendar and time-slot presentation, legal links, and access during testing.
Review the automatic email templates, ticket PDFs, and scheduled communication assigned to the offer. Use a customer-facing language and keep supported placeholders intact.
9. Go live
Run Run a go-live readiness check. Remove staff-only shop access and hidden offer states only after the test passes. Give cashiers, admissions staff, support, and finance the workflows they need before customers arrive.
Expected result
The account uses the correct identity and time zone, staff have appropriate access, payments and integrations have clear ownership, and the first offer is configured for the intended sales channels.
Troubleshooting
For a missing offer, use Troubleshoot an offer missing from the shop.
| Problem | What to check |
|---|---|
| Event times are wrong | Account time zone, offer time zone, connected-system time zone, and whether dated offers were created before correction. |
| Offer is missing from the shop | Publishing state, shop page, sales channel, sales period, price, date, inventory, and capacity. |
| Payment method is missing | Provider connection, live or test mode, method eligibility, shop default, and offer checkout policy. |
| Customer receives the wrong email | Template type, order transition, customer language, offer communication assignments, and order History. |
| Studio data is missing or inconsistent | Open Admin > Integrations and contact support; do not recreate Studio-owned data locally. |
