Korona.Events is an additional application that can be linked to your Korona.Cloud account and your Korona POS
KORONA EVENTS is still under development at this time. As new features become available this page will be updated. At this time some features that you see in the backend of KORONA EVENTS are not fully functional yet. If you have any issues setting things up or questions about how to do something that is not clear do not hesitate to email us at firstname.lastname@example.org
First, you will need to sign up for Korona.Event. Korona.Event is an additional application that interfaces with your Korona Cloud and Point of Sale. You can sing up here:
Once you have opened the sign up wizard you can log in. In the next step you will be asked the name of your account. Keep in mind that this name will be used for the sub-domain of your webshop so choose wisely. If your account name is Toasted Ravioli, your webshop url will be ‘https://toasted-ravioli.shop.koronaevent.com’.
Once the account is created you will be redirected to the login page and you can begin setting up the rest of your account details in the admin section.password go in the login/pswd boxes of the external system call.
Both of these external system calls will be buttons on the POS.
The first thing you want to setup is your Korona.cloud connection by going to your Korona.cloud account. Under Settings>Data Exchange add API by typing ‘API’ into the top bar and hitting ‘Enter’. You will then have APIv3 integration. Under the APIv3 integration create a User and Password with all of the permissions and hit ‘Save’.
Next, navigate to Sales>Points of Sale. You may need to expand your account to add two more POS licenses. You will then create two new Points of Sale:
Number: 007 Name: BackOfficeExternal
Number: 008 Name: OnlineShopExternal
The numbers of the POS are important, the names can be whatever you want them to be. If the numbers for the new POS are not 007 and 008 the Integration will not work.
On the Korona.Event side navigate to Admin>Integrations
Plug in your API login/pswd information along with your API Key and hit ‘Synchronize’.
From this page we will also grab the information for the external system calls. We put these calls on the POS in order to sell .Events from the POS.
Connecting the to the POS
Next navigate to Settings>External System Calls
In order to see orders or book events from the POS itself you will need to set up these external system calls.
Copy the information to three external system calls. The URL goes to display URL and the KORONA.event and password go in the login/pswd boxes of the external system call.
Both of these external system calls will be buttons on the POS.
These are active orders that you have and where you can create new orders manually.
These are orders that you have created from the back office in .Event.
Customers who have been added or emailed tickets.
An event is something that happens once at a specific time that customers can book and attend. They include prices, required resources, quotas, etc.
Does not exist yet
Event templates can be used to create events. The only difference is they have no start and end time, but instead a duration which is used to define the end time once a start time is defined. You can create single events, multiple events, or assign a time patter to enable on-demand creation of events from the template.
Admissions are tickets. They are configurable like an event but can only be limited by date/quota. They do not have any resources. The idea is to provide entry, and nothing else. If you are limiting your capacity in any way do not use this.
This allows multiple rules to define potential start times for on-demand events.
Resources can be assigned to events or event templates to keep from overbooking your area/staff.
Agents are individual or groups of employees. They have a role, and can have skills attached to that role. Here you see we have Donald that is an Employee that can Lead Tours of up to 100 people.
Functions that an agent or Space can have. Say you have a tour path, you would want to have the skill ‘Lead Tour’ assigned in the properties of the space you hold the tour.
Spaces have a property(skill) and /or a feature along with function assigned to them with a changeable capacity.
Functions can have multiple events happen at the same time or be exclusive. If you have a tour group, the function would not be exclusive. If you were booking a haircut or movie, it would be exclusive.
Skills are qualities of people, features are qualities of areas.
A material is a physical resource such as an audio guide or paint brush set that can be required or booked for an event.
Price categories provide a unified, human readable label to the product the customer is buying and can define whether the price is an individual or group price.
Freely definable tags are assigned to services. They currently differ from tags in Korona.Cloud but behave similarly in that you can categorize service to easily find them later.
Back End Purchases
When customers call to reserve an Event Template or an Admission(most of the time this will be for groups), you can do this for them on the backend. Navigate to Sales>Orders and click ‘Create New’. You can then add whatever they want to purchase and if there is a time requirement you will be prompted to pick when. You will only see what is available for the amount of products you’ve selected. This could be blocked off by the event template being marked as exclusive and someone already booked it or there are not enough spaces left if a resource or capacity has been reached.
Invoice: Tickets are ACTIVATED AND VALID IMMEDIATELY regardless of payment.
Collective Invoice: same as above, combine multiple customers
Online Payby Link: Tickets are reserved but will not be activated until the payby link has been paid.
Onsite: They will have to pull up the order on site and have it paid there either through Agendas or Orders external system calls. DOES NOT SEARCH BY TICKET NUMBER so this is not recommended, only searches by order number and customer search is broken as of today 10-12-22 so this is strongly not recommended. Recommend using online payby link.
Sometimes you want to encourage additional purchases with an Event someone is booking.
This is possible by tagging the product that you want to be upsold, and on the product it should be linked to put that same tag in ‘related products’ field.
Here is where you put in your Stripe Account information or your PayPal information.
Here is where we connect our Korona.Cloud instance, Entry System integration, and bLoyal key.
Here is where we upload our ticket logo and fonts if you like.
Sometimes even if an event isn’t booked, you may need to block off the ability for someone to book an event. You can edit the availability of Spaces and Agents by going to the specific Space or Agent, click and drag over the time frame you want to block off. You will then be prompted whether or not you want this to repeat or change the hours you want to block off.
Refunding from .Event
To return money to the customer in the instance of a cancelled event, you will need to refund them through stripe. After you’ve refunded them through Stripe you can cancel the event on the .Event side. After the event is cancelled you can mark it as refunded under Invoices. The customer will receive an email from .Events that the order has been refunded.
- Find invoice, and click ‘view order’
- Cancel Order
- Mark as Refunded
Change a Booking
Sometimes you may want to change a booked time or day. To do this you will first need to add the new booking to the order.
- Find the order and click it. Then click ‘Add Services’
- Add the new booking selecting the new date and or time.
- Then hit initiate payment. Then you can hit ‘Finalize’ and the new tickets will be emailed to the customer.