Overview
The Automation rules section allows users to define automatic behaviours within a specific shop.
These rules enable the system to:
-
Automatically add tickets
-
Apply dependencies
-
Trigger logic based on selections
-
Enforce structured purchase flows
Instead of relying on manual configuration by the buyer, automation rules control how products interact during the ordering process.
This section is used to streamline the checkout logic and reduce configuration errors.
What You Can Do Here
If no rules have been created yet, the page shows an empty state with:
-
A central informational message
-
A + New rule button
This indicates that no automation logic is currently active in the shop.
+ New Rule
Automation Rules
The Automation rules section in your shop settings allows you to create rules that control how tickets interact with each other during the purchase flow. This helps you set up dependencies between tickets so that certain tickets only become visible or available based on what the buyer has already added to their order.
Creating a Rule
To create a new rule, click + New rule. Each rule follows a simple "When... Then..." logic:
When — Select a trigger ticket from the dropdown and set the amount. This is the ticket that the buyer needs to add to their cart first. For example: "When 1x Ticket Friday has been added..."
Then — Choose what should happen when the condition is met. You have two options:
Show ticket — This makes a hidden ticket visible in the shop once the trigger ticket has been added. Use this for things like day-based add-ons that should only appear in step 2 after the buyer has selected their main ticket. The ticket is hidden by default and only shows up when the rule is triggered.
Enable ticket — This unblocks a ticket so it can be added to the cart, but the ticket is already visible in the shop. Use this for parent-child ticket setups where, for example, a child ticket can only be purchased after an adult ticket has been added.
Examples
A camping add-on that should only appear after a festival weekend ticket has been selected — use Show ticket. A child ticket that is visible but greyed out until a parent ticket is added — use Enable ticket. A parking ticket that should only be offered when a specific VIP ticket is in the cart — use Show ticket.
When to Use This
Use automation rules when you want to enforce a structured purchase flow, such as mandatory add-ons, conditional extras, or ticket combinations that depend on each other. Without these rules, buyers might purchase incomplete combinations or miss required add-ons, leading to support requests and manual corrections.
Rules operate within the shop context only and do not affect event capacity, pricing, payment methods, or entrance validation.
What Automation Rules Typically Control
Automation rules can:
-
Automatically add required add-ons
-
Ensure compliance products are included
-
Link parking tickets to specific ticket types
-
Add service fees automatically
-
Enforce bundled ticket logic
-
Create conditional product relationships
They operate within the shop context only.
Why This Section Matters
Automation rules:
-
Reduce manual configuration by buyers
-
Prevent invalid ticket combinations
-
Enforce business logic
-
Increase operational control
-
Improve checkout accuracy
-
Reduce customer support cases
Without automation rules:
-
Buyers may forget required add-ons
-
Invalid combinations may be purchased
-
Manual correction may be needed
Automation rules provide structured purchase behaviour within the shop.
Scope Clarification
Automation rules do NOT control:
-
Event capacity
-
Pricing structure
-
Payment methods
-
Entrance validation
They control:
-
Product interaction logic inside the shop
When to Use Automation Rules
Use this section when you need:
-
Mandatory add-ons
-
Conditional product logic
-
Smart bundling
-
Automatic product linking
-
Controlled purchase flows
This section is typically used by:
-
Ticketing administrators
-
Event operations teams
-
Commercial managers