Group event templates under one public offer

Use a parent and child relationship when customers should see one public offer, but your team needs separate event templates for different schedules, prices, capacity, or resource requirements. KORONA Event combines the available dates and times on the parent offer, then books the template that supplied the selected time.

For example, one guided tour can use separate child templates for weekday and weekend schedules or guide pools. Customers still see one tour in the online shop.

When to use a parent and child relationship

Use this setup for operational variants of the same customer promise.

Situation	Recommended setup	Why
The same activity uses separate time patterns or resource pools	One parent with child templates	Customers get one offer while each child keeps its operational setup.
The same activity has prices that depend on the selected date or time	One parent with child templates	The selected child supplies the actual price after the customer chooses a time.
The activities have different names, descriptions, locations, durations, languages, or inclusions that customers should compare	Separate public event templates	Each experience needs its own customer-facing explanation and booking choice.

How the relationship works

A parent event template is the public offer. A child event template is one of its bookable operational variants.

Setup area	Parent event template	Child event template
Public presentation	Supplies the name, description, images, tags, and public booking entry point.	Does not appear as a separate public offer while assigned to a parent.
Customer and attendee information	Supplies fields that apply across bookings made through the grouped offer.	Can add fields that apply only when the customer selects a start time from that child. The booking uses the child that supplied the selected time for operations.
Dates and times	Can supply its own start times and also combines start times from its children.	Keeps its own time pattern and duration.
Prices and sales availability	Defines the public price categories and can supply prices for its own start times.	Supplies the matching active price, point-of-sale coverage, and sales availability for its start times.
Capacity and operations	Keeps its own capacity and resources for any parent start times.	Keeps its own capacity, quotas, resource requirements, and generated events.

The relationship supports one level only. A child cannot have its own children, and a parent that already has children cannot be assigned to another parent.

Before you start

Prepare:

the public name, description, images, and customer information that should apply across the group
one child template for each schedule or operational setup that needs to remain separate
the time pattern, duration, prices, sales channels, capacity, and resources for every child
any intentional child-specific customer or attendee information, with duplicate and stale questions removed
matching price categories and points of sale across the parent and children

Create the templates with Create an event template before linking them, or select the parent while creating a new child.

Set up the parent

In the back office, open Services > Event templates.
Create or open the template that customers should see.
Add the customer-facing Name, Description, images, tags, and customer or attendee information.
Add the price categories customers should be able to choose.
Keep Hide from shop on while the grouped offer is incomplete.
If the parent should supply bookable start times of its own, also configure its time pattern, prices, sales channels, capacity, and resources.
Select Create or Update, then use Publish now or Set publishing date if the template is not already published.
When the parent and its intended children are ready, turn off Hide from shop on the parent and select Update.

A parent can be directly bookable, can act only as the public entry point for child availability, or can do both.

Assign each child

Create or open the child event template.
In the template form, select the public template in Parent event template.
Configure the child's Duration, time pattern, prices, sales channels, capacity, and required resources. Keep Hide from shop on while the child is incomplete.
Select Create or Update.
Use Publish now or Set publishing date if the child is not already published.
When the child is published and ready to book, turn off Hide from shop and select Update. The parent relationship still hides it as a standalone public offer automatically.
Repeat these steps for each operational variant.

The parent selector lists only templates that can form a one-level relationship. It excludes the current template and templates that are already children.

Check prices across the group

Open the parent template after assigning the children. The side panel lists its Child event templates.

For every price category and point of sale used by the parent, add a matching active price rule to every non-archived child. The amount can differ by child because KORONA Event uses the price from the template that supplied the selected time.

If coverage is incomplete, the parent shows Child templates are missing matching prices. Select Open prices and add the missing categories or points of sale to the listed children. The warning checks every non-archived child, including a child that is currently hidden from the shop.

Test the public offer

In the back office, confirm that the parent and every child being tested are published and have Hide from shop off.
Open the online shop and find the parent template.
Confirm that no child appears as a separate offer.
Open the parent and check dates and times supplied by each child.
Select at least one start time from every child and confirm its price, availability, and customer or attendee fields.
Complete a test order.
In the back office, confirm that the order uses the correct date, time, price, capacity, and resources while the customer-facing name remains the parent's name.

Expected result

Customers see one parent offer with the combined eligible availability of the parent and its children. Each booking uses the schedule, price, capacity, and resources of the template that supplied the selected time. Parent data-collection fields apply across the group, and only the intentional fields from the selected child are added.

Troubleshooting

Problem	What to check
A child's start times are missing from the parent	Hide from shop, time pattern, active prices, sales channels, sales periods, capacity, and resource availability.
A child's start time appears but cannot be booked	Whether the child is published. If it is not ready to publish, turn on Hide from shop to remove its start times from the public parent offer.
The parent is missing from the shop	Parent publishing and Hide from shop, plus whether the parent or at least one visible child has bookable availability.
A child appears as its own public offer	Whether Parent event template was saved on that child and whether the page is showing current shop data.
The parent shows a missing-price warning	Add the parent's price categories and point-of-sale coverage to the children named in the warning.
The wrong name, description, or image appears	Edit the parent template; it supplies the public presentation.
Customer or attendee fields are missing or duplicated	Review the parent fields that apply across the group and the fields on the child that supplied the selected time. Remove duplicate or stale child questions.
The intended parent is not available in the parent selector	It may already be a child or be the current template. A template that already has a parent cannot become a parent itself.
The relationship cannot be saved	The template you are editing may already have children, or the selected parent may already be a child. Parent and child groups cannot be nested.