Setting up pricing configuration
Ticketmatic supports advanced pricing configuration. Following concepts are used:
Price type
Price types describe the different types of prices that exist for an event and are used in price lists to define actual prices. Price types are global for an account.
There are 5 categories of price types:
Category | Description |
---|---|
Normal | Used for regular prices |
Reduction | Used for prices that have a reduction |
Special | Used for prices that fall out of the normal, like VIP tickets |
Free | Used for free tickets |
Subscription | Used for prices that are contained in a subscription |
Price list
Price lists are used to define the actual prices that will be available for one or more events. In each price list prices are defined for a selection of price types. Per price you can decide for which sales channels the price is active. Additionally, conditions for each price type can be defined.
By linking a price list to an event, the prices for the event are defined. The same price list can be linked to multiple events. Changing the price in a price list will automatically change the price in all events that have linked this price list. (Remark: the new prices will only be applied for new orders, prices for tickets that are already sold will not change)
Ticket fee
Ticket fees are schemes that define what fee will be added to the ticket price, depending on the price type and the sales channel used when the ticket is sold. The fee can either be a fixed cost or a percentage cost.
By linking a ticket fee scheme to an event, the fees that will be applied to tickets for that event are defined. The same ticket fee can be linked to multiple events. Changing a ticket fee scheme will automatically update this for all linked events. (the new fees will only be applied for new orders, fees for tickets that are already sold will not change)
Setting up pricing for an account
The pricing configuration is handled in the Pricing module in the Settings app, under Pricing
. Click the button below to go there:
Using price conditions
Price conditions allow you to refine when a certain price can be used. Price conditions can be defined in a pricelist or for an event-specific price. You can have multiple conditions active on a single price.
To add a price condition to one or more prices in a pricelist:
To add a price condition to an event-specific price:
Price condition Date
You can specify a start and/or end date. The price will only be available between these dates. This can be used for example to define an ’early-bird’ price or a ’last-minute’ price.
You can specify the date either as absolute dates, or as number of days relative to the start of the event.
Price condition Promocode
This price condition is only used in web sales channels. You can specify a promocode. The price will only be available if the user gives this promocode when he is buying the ticket. The promocode can be any string. This promocode is valid for an unlimited number of times, so anybody that knows the promocode can use it. It you need individual codes that can only be used a limited number of times, you can use voucher codes instead (see below).
Price condition Order limit
You can specify a limit that defines the maximum number of tickets a user can buy for this specific price per order.
Price condition Order threshold
You can specify a limit that defines the minimum number of tickets a user can buy for this specific price per order.
Price condition Multiple of
You can restrict the number of tickets a user can buy for a specific price per order to a multiple of a specified number. (e.g. 3, 6, 9, …)
Price condition Ticket limit
You can specify a limit that defines the maximum total number of tickets that can be bought for this specific price.
Price condition Voucher code
You can specify one or more Vouchers of type Pricetype
. The price can only be used if the buyer gives a valid voucher code for one of these vouchers for each ticket. More info on vouchers
Price condition Relation type
You can specify one or more relation types. The price can only be used if the buyer has one of the selected relation types.