Skip to main content

Line-Up Lingo

Key Terms & Concepts

Learn how to use the lingo of Line-Up - scroll down for the key terms and core concepts of our system.


Account Settings & Tools

  • The company you are selling Tickets from.

  • The fixed Roles you can invite your team members to join as, e.g. Owner, Admin, Box Office, Box Office Admin, Finance.

  • Roles you build yourself, setting exactly what each one can see and do. Managed by Owners and Admins from the Settings menu.

  • A restriction on an individual User, limiting them to certain Purchase Flows and so to the Events, Channels and Transactions connected to them.

  • The different ways Customers can pay for your Tickets, e.g. Stripe, Cash.

  • A device for taking card payments on Box Office sales.

  • Where Tickets are sold, e.g. Box Office, Call Centre, Website.


Venues

  • The location for your Event.

  • The categories for your seats, if you have Reserved Seating.

  • A Block on a Reserved Seating Venue Plan whose seats must be purchased together online, for example a theatre box or a dining table.

  • A Block on a Reserved Seating Venue Plan that sells a General Admission space. Customers select the area and are taken through the standard GA Ticket selection process.

  • A Reserved Seating Venue Plan that also contains one or more General Admission Blocks, for example seated tiers with a standing pit.


Events

  • The experience you're selling Tickets for.

  • The dates and times for your Event.

  • Allocations and/or locks on seats, if you have Reserved Seating.


Pricing

  • The commissions or fees that can be set inside or outside of your prices.

  • The pricing structure for your Event.

Band

  • A group of prices.

Variant

  • Type of price, e.g. Full Price, Concession.

  • A different Tax Rate applied to an individual Variant on a Price Table, instead of the Organisation default.

  • A discounted price for individual Tickets and Products, assigned to Variants on the Price Table.

  • A reduction applied to the total value of a Customer's basket, once the Delivery Method has been selected. Reported as an Add On.

  • The code a Customer enters to apply a Discount. One Coupon Code can only belong to one Discount.

  • Set how and when your prices are visible for Ticket buyers.

  • Rules and limitations that you can set for Tickets, i.e. what should be in the basket in order to check out.

  • How many Tickets are sold for each of your Bands. Add prices to seats if you have Reserved Seating or assign capacities if you have General Admission.


Ticket Delivery

  • How you would like your Customers to receive their Tickets, e.g. E-ticket, Collect at Box Office.

  • When you want your Barcodes to be generated and scanned.

  • What your Tickets look like to your Customers.

  • Custom templates to send to Customers, e.g. pre/post-show emails.

  • Transaction-specific data/code that you can insert into your HTML Email and Ticket Templates.

  • The marketing and/or terms and conditions available for your Customers to agree to when booking for your Events.


On Sale

  • Where Customers purchase Tickets on your Website.

  • Booking flows that you can use for selling Tickets, e.g. Box Office, Online Checkout.

  • Channel-specific booking links that you can create and send to Customers of your choice.

  • Upsells for your Event, e.g. Programme, Pre-show drink.

  • A tool you can use to select multiple seats on a Reserved Seating Venue Plan.

  • Where you can gather information from your Customers, either during or post-purchase.


Orders & Transactions

  • An individual record of sales activity for Tickets, Products and other items, with its own reference and status.

  • A group of one or more Transactions placed together, including any Refund or Exchange Transactions made against them.

  • A consolidated view of the current state of an Order, showing only live items. Voided and refunded items are netted out.

  • The drawer that opens when you click a Transaction, showing the details of that individual sale and the actions you can take on it.

  • Combining separate Orders for the same Customer into one, so they can be managed and delivered together.

  • The screen shown when starting a Refund or Exchange, where you tick the items to be returned before continuing to the Basket.


Customers

  • All Transactions for a Performance, listed by Customer.

  • A list of all emails sent, filterable by date and Customer.

  • The tab on a Customer or Transaction showing the emails sent to that Customer.


Attendee Management

  • Devices that you can use to scan and redeem Tickets.

  • Redeeming Barcodes for a Performance without using a scanner.

  • One row per guest for a Performance, with their Form responses and contact details.


Reporting

  • Individual aggregates of data that can be displayed as a table or chart.

  • Groups of Reports arranged in a customisable grid.

  • Auto-sends for a Report, according to a schedule of your choice.


Line-Up Network

  • A series of URLs that relate to data, which third-party agents integrate with. This is what they use to see and use data they have been given access to, i.e. to be able to sell Tickets for an Event.

  • Third-party systems can integrate with our API and we can integrate with theirs.

  • The different tracking events via the Line-Up Purchase Flow.

Did this answer your question?