Configure the current online shop

The online shop The customer-facing sales channel where customers browse offers, select tickets, enter checkout details, and complete payment or confirmation. is the customer-facing surface where people browse offers, select tickets, enter checkout details, and complete payment or confirmation.

Use this article when you are preparing a shop for launch or reviewing why customers cannot find or buy an offer.

Before you start

You need back-office The administrative area where staff create offers, manage orders, configure prices, assign resources, and review operational data. access to the Shops area and at least one offer that should be sold online.

Confirm:

• which shop domain customers will use
• which sales channel is assigned to the shop
• which events, admissions, products, or vouchers should appear
• which legal documents must be shown or accepted
• which payment methods are approved for the account
• whether the shop should be public or restricted during testing

Open Shops

In the back office, open Shops. If there is more than one shop, select the shop by Name, Domain name, and Sales channel.

Use the tabs in the shop settings to review the customer experience:

Use the tab that owns the change you need:

For translated legend labels and other customer-facing shop text, see Change labels or translated shop content.

Set shop access

Use Access to decide who can open the shop.

Turn on Require staff login when the shop is still being prepared or reviewed. When this is enabled, shoppers must sign in with a back-office user that can read the shop before they can view catalog, availability, or checkout.

Turn it off before public launch unless the shop is intentionally staff-only.

Configure branding and theme

Open Branding and check:

• Logo
• Favicon
• Primary color
• Secondary color
• fonts
• Show flags in the language switcher

Open Theme when the shop needs more detailed control over Colors, Typography, Spacing, Borders, Button Colors, Semantic Colors, Media, and WCAG contrast checks.

If the theme editor shows unpublished changes, use the theme publish action only after you test the shop on desktop and mobile.

Open SEO to set the public site name, title template, default description and social image, organization identity, and search-engine indexing. Follow Configure search and social sharing for the fallback and indexing rules.

Configure pages and navigation

Open Pages and confirm which shop pages are active. Standard page types include Tickets, Events, Products, and Vouchers.

Use Activate this page to control whether a page is available. Use Display the filter bar underneath the page title when customers need filtering for larger catalogs.

Open Page Builder for custom pages and navigation. Check:

• page order in the page builder list
• whether important pages are Shown in navigation
• whether the home page contains an offer list or clear route to the first offer
• whether offer lists include the events, admissions, products, or vouchers customers need
• whether page titles, descriptions, and call-to-action labels are customer-friendly

For block types, offer-list filters, page ordering, navigation, and the legacy Pages fallback, follow Customize shop page content and ordering.

Configure checkout

Open Checkout and review Checkout configuration.

For an external analytics provider, tag manager, advertising platform, or cookie banner, follow Configure external analytics and consent. The analytics mode does not block code that you add under Code snippets.

Keep required checkout fields limited to information your team actually uses. Required fields can block checkout if customers do not understand why they are needed.

The billing address mode controls how the address appears during checkout:

• Automatic keeps the billing address hidden unless a checkout rule makes it required for the current cart.
• Optional shows a closed Add a billing address disclosure. The address fields appear only after the customer opens it.
• Required keeps the address fields open and requires the customer to complete them.
• Hidden keeps the billing address out of checkout unless an active checkout rule makes it required for the current cart.

The shipping address is not an optional checkout setting. KORONA Event collects it automatically whenever delivery is required:

• If the billing address is visible, including when a checkout rule makes Automatic visible for this cart, the customer can use it as the shipping address or enter a different shipping address.
• If the billing address remains hidden because Automatic does not require it for this cart, or because Hidden is selected, checkout shows a separate required Shipping address section.
• If the cart does not contain products that must be shipped, checkout does not show shipping address fields.

Choose the checkout result

For choosing a workflow and handling the next steps, see Manage booking requests and reservations.

A checkout policy A setting that controls the result and payment handling when a customer submits checkout for an offer. controls two independent choices: Checkout result determines whether the customer submits a request, reserves unpaid, or books; Payment method determines how payment is handled. A checkout hold instead controls how long an active cart or eligible unpaid checkout keeps capacity.

Set a checkout policy on an offer

You need permission to edit the offer. Decide whether staff must review it before booking and how payment should be collected.

1. Open Services and select Events, Event templates, Admissions, Products, or Vouchers.
2. Open the offer's edit form. For products and vouchers, open Online display.
3. Find Checkout policy.
4. Set Checkout result to Request only, Reserve unpaid, or Book and continue to payment, using the choices above. Select Inherit default to remove this field's override.
5. Set Payment method using the table below, or select Inherit default to keep the inherited payment handling.
6. Save the offer.

Choose invoice, collective-invoice, or delivery-note handling only when your team has the corresponding collection process. Book and continue to payment does not force an online payment when a different payment method is selected, and Booked does not mean Paid. Request only and Reserve unpaid submit without collecting payment immediately; the selected payment method still applies to the order.

For example, choose Reserve unpaid with On-site payment when customers should reserve places and pay at the venue. Set the reservation deadline to match how long those places should remain reserved.

Understand inherited settings

Inherit default applies separately to each field. You can override the checkout result while inheriting the payment method, or the other way around.

• An event uses its own explicit value first, then the value on its event template.
• An event template uses its own value first, then its direct parent template's value, if present.
• Admissions, products, and vouchers use their own explicit values.
• If no offer or template value sets the checkout result, the shop default applies; the system fallback is Book and continue to payment.
• If no offer or template value sets the payment method, an already assigned order payment method takes precedence, followed by the order-channel default and the shop's Default payment method under Shops > your shop > Checkout. Changing the shop default does not replace an explicit offer override or an already assigned order payment method.

For an event that should follow its template again, select Inherit default for the relevant field on the event. To use the shop or channel fallback, also remove any relevant explicit template value. Changing a shared template or default can affect other offers that inherit it.

Keep mixed carts compatible

All items in one shop cart must resolve to the same Checkout result and Payment method. Different checkout-hold durations are allowed; they do not by themselves create a checkout-policy conflict.

For example, an offer set to Request only cannot share checkout with an offer set to Book and continue to payment. Two booked offers also conflict if one requires Online payment and the other On-site payment.

If these differences are intentional, customers need separate orders. If the offers should be bought together, align the relevant offer or template settings, including inherited values. See Resolve incompatible cart items for the recovery steps.

Add legal documents

Open the account legal notice area when you need terms, privacy, imprint, withdrawal instructions, accessibility statements, or other legal documents.

For each legal document, confirm:

• customer-facing Name
• whether it is Required to accept at checkout
• Checkbox label
• language variants
• whether the document is shown as text in the shop or linked by URL

Confirm offer visibility

An offer appears in the shop only when its own setup and the shop setup agree.

Check the offer first:

• it is not archived
• it is published at the right time
• the Hide from shop setting is not unintentionally turned on
• it has future availability or an active sellable state
• it has at least one active price
• the price is visible on the shop's sales channel
• capacity and resources allow the selected quantity

Then check the shop:

• the shop has the right Sales channel
• the relevant standard page is active or the custom page contains the offer
• the page builder offer list or navigation lets customers find it
• search and category/filter settings match how customers will browse

Open the customer booking flow with a realistic ticket quantity and price selection. The calendar and time-slot picker recalculate availability for that selection, so a date can be unavailable even when the offer itself is visible.

Add snippets only when needed

Use Code snippets for controlled customizations such as consent managers, analytics tags, trusted-shop badges, small custom CSS adjustments, or partner scripts.

Use Add custom CSS for styling changes that cannot be handled by theme settings. Use Add HTML/JavaScript snippet only when the script is approved and tested.

Expected result

The shop has the intended access, domain, languages, branding, pages, offer lists, checkout fields, legal documents, payment choices, and customer-facing content.

Review customer-facing content

Review the content and policy choices your team controls:

• the domain loads without requiring staff login, unless the shop is intentionally restricted
• logo, colors, fonts, and language controls look correct
• navigation and pages lead customers to the right offers
• offer cards show the expected name, image, price, date, availability, and status
• offer cards and detail pages show prices in the account's configured currency
• required checkout fields and legal agreements are clear
• a merchandise order shows a required shipping address, either with the visible billing address or as standalone fields when billing remains hidden
• intended live payment methods are configured

Troubleshooting

Related articles

• First event setup checklist
• Create a sellable event
• How sales channels and visibility work
• Review the customer checkout before launch
• How capacity and availability work
• Troubleshoot availability and capacity
• Customize shop page content and ordering
• Configure search and social sharing
• Change shop labels and translations
• Customize theme and CSS
• Configure external analytics and consent