Ticketing - Shops – Advanced Settings

Everything about shop settings: Private access, secure ticketshop with access keys. To lock a shop: Ticketing → Shop → Edit → Advanced Settings → Private access

Overview

The Advanced settings section allows users to configure additional behavioural and visibility settings for a specific shop (sales channel).

These settings control:

  • How the shop is accessed

  • What visitors see before, during, and after sales

  • Optional functionality (such as discount fields)

  • Promotional upsell behaviour

This section is used to fine-tune the customer journey beyond the basic ticket configuration.


What You Can Configure Here


Channel Specific Description

What it does:
Allows you to define a shop-specific description that overrides the default event description.

Why use it:
Different sales channels may require different messaging. For example:

  • Partner sales

  • Member pre-sale

  • Corporate ticketing

  • Special campaigns

How it works:

  • Enable the toggle

  • Enter a custom description

  • Save changes

  • This description will appear only in this specific shop


Private Access and secure shop

What it does:
Locks the shop so only visitors with an access key can enter.

Why use it:
For:

  • Pre-sales

  • Invite-only sales

  • Sponsor allocations

  • Exclusive campaigns

How it works:

  • Enable the toggle

  • Configure the access key

  • Only visitors with the correct key can access the shop

This prevents public visibility.


Display Discount Field

What it does:
Enables or disables the discount code input field in the shop.

Why use it:

  • Hide the field if no discounts are active

  • Show the field when running campaigns or promotional codes

How it works:

  • Toggle ON → Visitors can enter a discount code

  • Toggle OFF → Discount field is hidden

This keeps the checkout clean when discounts are not relevant.


How Discount Codes Are Processed

With the server-side cart, discount codes follow a three-step process:

  1. Validation — When a customer enters a code, it is validated immediately against active discount campaigns. Invalid codes are rejected on the spot.

  2. Pending — During shopping, the discount is shown in the cart as pending. The cart total reflects the expected discount, but it is not yet applied definitively. The customer can still modify their cart at this stage.

  3. Application — At checkout, the discount is applied to the final order total. This is the confirmed, binding amount the customer pays.

This approach ensures:

  • Customers can see their discount before committing to checkout

  • Pricing confusion is prevented during the shopping phase

  • The final total at checkout is accurate and confirmed

Note: The discount field must be enabled in Advanced Settings (toggle ON) for customers to enter discount codes. If the toggle is OFF, the field is hidden and no codes can be entered, regardless of active campaigns.


Link to the CM.com Resale shop

What it does:
When enabled and a product is sold out, a link to the CM.com Resale shop is shown to visitors. This setting also overrides the CM.com Resale availability shown on Schedule pages for this shop.

Why use it:

  • Give sold-out visitors a legitimate way to still find tickets

  • Keep resale availability consistent between the shop and Schedule pages

  • Reduce demand for unofficial resale channels

How it works:

  • Enable the toggle

  • When a product sells out, the Resale shop link is shown automatically

  • Schedule page availability for this shop reflects the Resale override


First shop step is mandatory

What it does:
When enabled, the ticket buyer is required to purchase a ticket in the first step before proceeding to the next step.

Why use it:

  • Prevent visitors from skipping straight to add-ons or upsells without a ticket

  • Ensure every order in this shop always contains at least one ticket

  • Keep the buying flow structured for multi-step shops

How it works:

  • Enable the toggle

  • The buyer cannot advance past step 1 without adding a ticket

  • Once a ticket is added, the buyer can continue to the next step


Maximum tickets in order

What it does:
You can configure the maximum number of tickets a ticket buyer can purchase in a single order for this shop.

Why use it:

  • Prevent bulk-buying or scalping

  • Keep ticket distribution fair across visitors

  • Match order limits to venue or event rules

How it works:

  • Enable the toggle

  • Enter the maximum number of tickets allowed per order (e.g. 5)

  • Ticket buyers cannot exceed this number in a single order


Success callback URL

What it does:
When enabled, the ticket buyer is redirected to a configured URL after successfully completing their order.

Why use it:

  • Send buyers to a custom thank-you or confirmation page

  • Trigger follow-up logic on an external system after purchase

  • Integrate the shop's checkout flow with other websites or tools

How it works:

  • Enable the toggle

  • Enter the redirect URL (e.g. https://example.com)

  • After a successful order, the buyer is automatically redirected to this URL


Hide price in shop for certain ticket statuses

What it does:
When enabled, the price in the shop is hidden for the selected ticket statuses.

Why use it:

  • Avoid showing pricing for tickets that aren't actually purchasable (e.g. sold out or not yet on sale)

  • Keep the shop visually clean when a status isn't relevant to buyers

  • Control price visibility per status without hiding the ticket type entirely

How it works:

  • Enable the toggle

  • Select the ticket statuses for which the price should be hidden (On sale, Not on sale, Scheduled, Sold out)

  • For the selected statuses, the price is hidden in the shop; other statuses still show the price


Countdown Page

What it does:
Displays a countdown page before sales officially start. This could be convenient, so your shop will open at a specific time and if buyers go to the shop already they see a timer/countdown. So they know when they can buy tickets.

Why use it:

  • Build anticipation

  • Prevent early access

  • Create structured sale launches

How it works:

  • Enable the toggle

  • The shop shows a countdown instead of ticket selection until the sale time

  • Once the sale begins, the shop opens automatically


After Event

What it does:
Allows you to configure a custom page that appears after the event or after sales have ended.

Why use it:

  • Redirect visitors to future events

  • Display thank-you messaging

  • Provide additional information

  • Maintain engagement

How it works:

  • Enable the toggle

  • Configure custom content

  • This page remains active for up to 30 days after sales/event end


Upsell Events

What it does:
Promotes other events to customers who completed an order in this shop.

Why use it:

  • Increase repeat purchases

  • Cross-promote events

  • Boost customer lifetime value

How it works:

Two options:

Select event

  • Choose another event within the platform

  • Automatically link it for promotion

Add shop URL manually

  • Enter a direct URL

  • Redirect customers to an external or specific shop

This appears after order completion.


Timeline Panel (Right Side)

The Timeline shows:

  • Current shop status (e.g., Public sale)

  • Scheduled closing date and time

  • What page will be shown after closing

This gives a quick operational overview of the shop lifecycle.


Important Notice

Changes in Advanced Settings:

  • May take up to 15 minutes to update for returning visitors

  • Are visible immediately for new visitors

  • Can be tested in an incognito window for instant preview


Why This Section Matters

Advanced Settings control:

  • Access control

  • Messaging per channel

  • Promotional behaviour

  • Checkout cleanliness

  • Pre-sale and post-sale experience

  • Revenue optimisation

It does not control:

  • Ticket types

  • Pricing

  • Capacity

  • Payment methods

It controls how the shop behaves as a sales channel.