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 the final test is complete.
Screenshot
backoffice-dashboard-overview
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
- a safe customer email address and payment method for testing
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 workflow instead of normal back-office invitations.
3. Connect systems that own shared data
Open Admin > Integrations and connect the systems your operation uses before duplicating their data in KORONA Event.
KORONA.studio owns shared commerce configuration such as products and voucher configurations. KORONA Event adds event-specific scheduling and customer-facing content. Follow Connect KORONA.studio and run a synchronization before configuring offers that depend on Studio data.
If you use an external booking or entry system, confirm which system owns bookings, payments, refunds, tickets, and updates. Record that ownership for support staff.
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.
Do not announce sales until a complete test proves that the intended payment method appears and produces the correct order and invoice state.
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 | Repeated entry or access that is not managed as one named event. |
| 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. Add prices and sales channels
Set customer-friendly price categories, gross prices, quantity limits, and whether each price reduces capacity. Then add the Online shop, POS, Back-office, or other sales channels needed for the offer.
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. Run a complete test
Open the public shop URL and complete Test the customer checkout. Test the same quantity, price category, date or time, payment method, and customer fields that a real customer will use.
Open the test order in the back office and confirm:
- offer, date, time, price category, quantity, and total
- order, payment, and invoice states
- attendees and tickets
- confirmation email, attachments, and customer language
- resource allocation and capacity, when used
- POS visibility and receipt handoff, when counter sales are used
10. 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, the first offer is sellable through the intended channels, and a complete test creates the expected order, payment, ticket, email, and capacity result.
Troubleshooting
| 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 a channel | Publishing, hidden state, sales-channel rule, channel-visible price, date, capacity, and shop page or POS assignment. |
| 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 | KORONA.studio configuration, integration credentials, last synchronization, and which system owns the field. |
