Glossary
Understand the core concepts of Spektrix with our bite-size videos. A flossary is also available below.
Event and Ticketing Glossary
| Term | Description |
|---|---|
| Attribute | Most objects in Spektrix can have attributes associated with them to provide additional information. Attributes are custom fields that are defined by the client and are provided as name/value pairs. For example: name=genre, value=drama. Attributes can be used to filter both API calls and Iframes. |
| Event | An event in Spektrix can be thought of as a ‘show’. It encapsulates the descriptive data about an event, such as its Name and Description. It is a container for instances. |
| Instance | An instance represents an occurrence of an event and contains the Start time, Duration and status of that occurrence of the event. It references the price list and plan that are being used at that time. |
| Seating Plan | A seating plan determines what seats are available for a particular instance. Plans can be made up of one or more areas, each of which can be either reserved (with allocated seating) or unreserved (general admission). Each seat within a plan has a price band assigned, which is used to determine its price. For unreserved areas, all seats share one band. |
| Price list | A price list gives a price for combinations of ticket type and band. Unreserved plans reference a band. An instance’s price list then dictates which ticket types, and which prices, are available in that area. |
| Price Band | Banding is used in price lists to assign different prices for a particular ticket type to particular seats. |
| Ticket Type | A ticket type defines the concession level of a ticket, i.e. ‘Adult’, ‘Student’ etc. These are referenced by price lists and tickets. |
| Ticket | A ticket entitles the customer to a seat at an instance. It references a plan, a band and a ticket type. It can be discounted as part of an offer. |
Glossary of Other Sellable Items
| Term | Description |
|---|---|
| Donation | A donation is Spektrix is made into a fund, which defines what the donation will be used for. |
| Fixed Series | A Fixed Series subscription allows customers to book the same seats across a number of different Instances, usually for a discounted price. That booking becomes a subscription which can be renewed, giving that customer the right to keep their seats for next season or choose other seats available to them when setting up their subscription for the following season. |
| Gift Vouchers | Gift Vouchers (and Gift Memberships) can be sold through the system and can be redeedmed and used during the checkout process. Each voucher can be bought for a custom amount and generates a unique code, which can be redeemed by any customer to receive the appropriate amount of credit. |
| Membership | Memberships in Spektrix are items that customers can purchase, to become a member for an period of time defined by the venue. Memberships can then provide access to benefits such as offer eligibility or priority booking, and can be used as criteria in reporting or customer segmentation. |
| Merchandise Item | A merchandise item entitles the customer to a single stock item. It can be discounted as part of an offer. |
Customer Account Glossary
| Term | Description |
|---|---|
| Customer | In Spektrix purchasers are universally referred to as customers. Customer records can belong to either an Individual or Organisation, though only Individual records are available in web integrations. |
| Addresses | Customer addresses encapsulate everything related to an address format and can be marked as a default Billing or Delivery Address. |
| Attribute | Most objects in Spektrix can have attributes associated with them to provide additional information. Attributes are custom fields that are defined by the client and are provided as name/value pairs. For example: name=genre, value=drama. |
| Statement | A statement object represents a Contact Preference. A customer can agree to any, all or none of the statements in the system. |
| Tag | Tags are useful for storing yes/no type information against a customer record. They are customisable by each client and can be also set to be viable editable by a customer. |
| Tag group | Tags are organised in groups, each of which has a name. |
Purchase Path Glossary
| Object | Description |
|---|---|
| Basket | A basket (or cart) contains all the items a customer wants to buy. Items can be tickets, merchandise items, memberships, donations or fixed series. An offer can be applied to a basket under certain conditions which results in certain items having a discount. A complete basket also has delivery methods associated, one for tickets and one for merchandise items. Not all delivery types can be used depending on the system setup and the items in the basket. |
| Delivery | The delivery method defines how a customer has chosen to receive certain types of items. There are 3 delivery types: Postal, Print At Home or Will Call/COBO (care of box office). The availability of each delivery type can be customised at event level. |
| Offers | Certain items in a system can be discounted by an offer for customers who are eligible. The discount and eligibility are calculated automatically by Spektrix as items are added to a basket. An offer can also be 'unlocked' by a Promo Code. |
| Order | An order is created when a basket is paid for. |