Moving from the old shop to the new shop

Availability
Beta
Last verified
Last verified Nov 16, 2026

Use this guide when your venue is preparing to move from the old KORONA Event online shop to the new shop. It highlights differences that affect your setup and your guests' buying experience.

New in the new shop

  • Theme controls with drafts and contrast checks: adjust typography, spacing, borders, and colors before publishing, with checks that block publication of theme colors that fail the supported contrast requirements; see Theme and custom CSS.
  • Configurable booking calendars and time slots: choose whether to show prices and remaining capacity, and add translated legends and styling rules to help guests choose a date and time; see Configure the current online shop.
  • Order history in the customer account: signed-in guests can browse their orders and download available tickets and vouchers from their account.
  • Memberships in the customer account, when activated: signed-in guests can view their memberships, status, and validity dates in their account.
  • Express checkout from the cart, Lynck only: eligible carts can offer PayPal and Amazon Pay, plus Apple Pay and Google Pay when activated. The buttons shown depend on your configured payment methods and the guest's browser or device.
  • Goods-voucher redemption page: guests can enter a voucher code on the shop's Redeem your code page. If the cart has no matching items, the page shows eligible offers so they can choose what to book.
  • More Stripe payment methods: besides cards, the new shop can offer the other Stripe payment methods active on your Stripe account and supported by KORONA Event. The standard old-shop Stripe checkout offers only cards. Available methods also depend on your KORONA Event payment settings.
  • Shop-specific interface wording: change editable button labels and messages per language in Text & translations, without changing the wording of other shops; see Customize online shop wording.
  • Structured questions, when activated: reuse form sections to collect information per booking, attendee, or contact instead of the old shop's fixed personalisation steps; see Collect customer and attendee information.
  • Page Builder, when activated: compose custom pages from blocks, arrange offer lists, and choose which pages appear in navigation; see Customize shop page content and ordering.
  • Visual editor, when separately activated: edit page blocks in a visual workspace and publish a saved draft when it is ready; see Edit shop pages visually.

Performance, mobile use, accessibility, and discoverability

Page weight and load times

The new shop's offer cards and supported image blocks provide responsive image variants, so the browser can choose an image size for the available space. Non-priority offer-card images load lazily, while priority images load eagerly. These are loading optimizations, not a measured speed comparison: no comparable end-to-end measurements of total page weight or load times are available for the two shops, so no percentage reduction or time saving is claimed.

Eligible public pages for visitors without cookies can also be cached by the content delivery network (CDN). Account, cart, checkout, and preview pages are excluded from this shared cache.

Public page content and navigation are rendered on the server, so guests can read and browse before JavaScript loads. Interactive booking and payment controls still require JavaScript.

Mobile-first layouts and accessibility

The new shop has a dedicated mobile navigation panel and layouts that adapt to wider screens. The booking calendar reduces detail on small screens, for example hiding per-day prices while retaining configured availability information.

Keyboard users can skip directly to the main content in the storefront and checkout. The mobile menu can open and close without JavaScript. Banner blocks hide background videos when the device's reduced-motion preference is enabled. The mobile menu supports Escape and focuses the panel when it opens; time-slot buttons expose their selection state and descriptive labels to screen readers. Dynamic booking and cart status messages use screen-reader announcements. Theme publication also checks supported color-contrast combinations. These are specific accessibility measures, not a claim that every page, custom theme, or embedded widget meets a complete accessibility standard.

Search engines and AI search (SEO/GEO)

Both shops support server-side rendering. The new shop adds page- and offer-specific search metadata, canonical URLs, language alternatives, and social-sharing metadata to the rendered HTML, rather than relying only on the old shop's general shop title.

Public, indexable pages include structured data describing the website, online store, and organization when configured, with breadcrumbs on inner pages. Offer pages provide Event or Product structured data in JSON-LD format, including price and availability when applicable and available. A generated /sitemap.xml lists eligible public pages and offers in the shop's languages; /robots.txt advertises it when shop indexing is allowed. Preview, restricted, and transactional pages are excluded from indexing.

These give search engines and AI search services machine-readable information about your venue and offers; they do not guarantee rankings, rich search results, or inclusion in an AI answer. Supply accurate translated descriptions, organization details, and sharing images using Configure search and social sharing.

Access for AI agents

For live, unrestricted shops with indexing enabled, /llms.txt provides a text introduction and links to the localized shop, sitemap, eligible browse pages, and published policies. It guides agents to find public offers and share an offer page with the customer, who continues booking in the shop. This is discovery support, not an agent booking or payment API. The file is unavailable for restricted, non-live, or indexing-disabled shops. Eligible public shop pages and offers also provide a Markdown representation for AI assistants that request text/markdown, giving them readable content and links without running page scripts. The same live-shop, access, and indexing restrictions apply. See Improve shop readiness for AI agents for content preparation.

Works differently

Settings, branding, and fonts

Open Shops in the backoffice and select your shop. The new shop uses Theme for its appearance, replacing the old shop's Branding tab once a theme has been published. Calendar and Time Slots have their own settings. Depending on activation, page content is maintained in Pages or Page Builder.

The old shop uses primary and accent colors and a regular font file. The new theme has separate heading and body font settings, font weights, and more detailed color controls. Review those choices in Theme rather than expecting the old settings to reproduce the same layout. Theme edits save as a draft; select Publish theme to apply them to the shop. See Theme and custom CSS.

Copy new offer links from the shop itself. With Page Builder rendering activated, the new shop uses name-based page addresses; otherwise it keeps the numbered offer addresses. Links such as /events/123 keep working. Support helps you redirect the old shop's offer links (/offers/…) as part of the switch. Give the website maintainer your existing links and iframe embeds when planning the switch. Confirm the intended domain and target pages before replacing them. When the shop's security policy is enforced, iframe embeds work only from websites listed under Websites allowed to embed the shop. See Deep links from marketing pages and Custom shop domains.

Interface wording and booking buttons

Text & translations is available only in the new shop. Each change applies to one message across that shop in the selected language, not to selected offers or admissions. Switching shops or changing a shared message does not provide admission-specific button labels.

A separate call-to-action link can have its own text and destination. The Booking Flow control derives its label from the offer type and booking state; it has no offer-specific label setting. A separate link does not replace its booking behavior. See Customize online shop wording.

Custom CSS, widgets, and tracking

The new shop has different page markup. Custom CSS and JavaScript that target old elements need a compatibility review, including consent banners, tracking tags, and third-party widgets. Use the supported CSS hooks described in Theme and custom CSS.

External ecommerce events require consent-managed analytics and a consent manager that reports the guest's analytics choice. The default privacy-preserving mode sends no KORONA Event ecommerce events to a tag manager. Existing tracking snippets need to follow the new event and consent contract; see Configure external analytics and consent. KORONA Event does not supply a built-in cookie banner.

Checkout steps and customer information

The old shop separates cart details and confirmation into their own steps. The new shop uses a checkout page for customer details and legal agreements, followed by the applicable payment or confirmation flow. Guest checkout, required accounts, and the information requested depend on your configuration and the offers being purchased.

Review your customer fields, billing and shipping requirements, and required legal documents in Checkout before the switch. Support migrates your personalisation and waiver setup to form sections as part of the switch. See Collect customer and attendee information and Add a waiver to checkout. Use Review the customer checkout before launch for the preparation checklist.

Not (yet) in the new shop

  • Dedicated bLoyal snippet pages: the old shop's bLoyal pages for embedded loyalty journeys have no equivalent in the new shop.
  • Dedicated bLoyal coupon entry: the integration-specific bLoyal coupon input available when enabled in the old shop is absent from the new shop; this is separate from ordinary KORONA Event coupon entry.

If your venue uses either bLoyal flow, agree an alternative with support before switching. Include any bespoke widget or customization in that conversation, because its compatibility depends on how it was built.

Arrange the switch

Contact KORONA Event support with your shop domain, brand and font requirements, website links and embeds, custom snippets, and any bLoyal flows you use. Support can coordinate activation and the domain handoff. Prepare your content and checkout choices using Configure the current online shop.

Ready to Get Started?

Book a free demo or reach out — we’d love to hear from you.