This may be because Loop tags are being placed outside of Loops, or there's an incorrectly formatted Merge Tag/bit of HTML code.

NOTE - As the ticketing software provider, we deliver and maintain the ticketing system. We do not provide template design and as such we would suggest going to an external HTML designer for detailed help with HTML templates.

We recommend unlayer for designing HTML templates.

​ChatGPT is also very helpful for specific HTML queries.

If Submit appears to do nothing, the Template has not passed our checks and has not been saved. The most common cause is a groupby on a list built inside the Template (see Is there a way to group tickets together in a template? below).

Go back to the last version that saved and re-add your changes one at a time to find the one that stops it saving, or contact Support with the Template name.

By adding an if loop.first statement, followed by the Event Merge Tags you don't want to appear for every ticket.

Example:

This ensures that Venue Name and Address only appears once/for the first ticket.

You'd then need to remove {{ ticket.EVENT.VENUE_NAME }} and {{ ticket.EVENT.VENUE_ADDRESS }} from the Event information in your template.

By adding this bit of HTML before your Event/Ticket information:

You just have to make sure to close the loop with an {% endfor %} Merge Tag.

Here's an example whereby you'd only want the customer to see the Performance Date/Time for their new tickets, not the old tickets they exchanged:

NOTE - be careful using this filter in a Template that may receive Exchanges. Your Transaction total comes from {{ TRANSACTION.GROSS }}, which already nets off the returns, so if the returned items are hidden the item lines will no longer add up to the total. Filtering to sales is right for a sales-only Template, or inside an if statement that decides what to say. For Exchanges, group the items by TRANSACTION_TYPE instead, so returned items show on their own labelled line (see Is there a way to group tickets together in a template? below).

By adding this bit of code, then printing the value wherever you need it:

Yes, just need to remove the img section from the default templates:

Yes, you just need to change img src from the logo URL:

To the {{ ORGANISATION.IMAGE }} Merge Tag :

This will mean that the Organisation image from your Settings page will pull through onto the Email Template instead of the Line-Up logo.

NOTE - if you are using your Org image in your template, this Merge Tag is safer to use than a hosting link. This is because some email servers may treat external hosting links as cold domains and may block the emails from being received.

Here's a video of these steps:

By adding a "Qty" column in your Items table and using our {{ count }} Merge Tag. Below are the steps to add this to your Items table in your Template.

NOTE - this will group tickets together by Price Variant. Because of this, it works best for GA events, where there is no Seat Label for your tickets.

We don't have a specific Merge Tag for Day of the Week, however we do have {{ ticket.PERFORMANCE_START_DATE }} which you can use for if statements.

If you wanted to only show text only if a Transaction contains tickets for a certain Performance Day, e.g. Tuesday, then the code you would want is:

Yes, you can use a groupby filter as part of your code. groupby allows you to group tickets that have the same characteristics together in sections.
​
You can choose which field to group by. Use the field name in the groupby, not the display Merge Tag:

NOTE - groupby only accepts a collection that comes straight from TRANSACTION.TICKETS or TRANSACTION.PRODUCTS, or from another groupby of one of them. A list you build yourself in the Template (with selectattr, list, or by joining lists together) cannot then be grouped, and the Template will not save. If two sets of tickets need to display differently, add the field that separates them (for example TRANSACTION_TYPE) to the groupby chain rather than splitting the list first.

For example, if grouped by Event, the line of code would be:

A common setup in templates is grouping by event, then performance, then band and ticket type. This displays one line per price band with the rows listed beneath.

So the code would look like this:

NOTE - the != '' checks matter for General Admission tickets: their Area, Row and Seat Type are empty strings (not null), and their Seat Label is the literal "GA", so without the checks a GA Transaction prints "Row , Seats GA-GA". Test for != '' rather than is not none. And always print the Band alongside the Variant, otherwise two lines at different prices look like duplicates.

And it would appear in your email like this:

If you have Reserved Seating and want seats to appear in one seat range rather than individually (as above), then make sure you add this line:

This also ensures that each row of seats are grouped as separate lines but underneath their Area and Band.

NOTE - the range prints the first and last ticket in each seat block, which assumes the seats come out in ascending order; a block has been seen to produce "Seats 6-1". If an Area has several Sections, add groupby('SEAT_GROUP_SECTION') to the chain, otherwise two blocks in different Sections collapse into one line (for example "Row B, Seats 1-4, 1-5").

Exchanges - on an Exchange, the Transaction holds both the returned and the new tickets. Without a split they land in the same Band and Variant group and net against each other (a real example rendered as one line, "Standard - Adult Quantity: 7 £-45.99", for 4 returned and 3 new tickets). Add TRANSACTION_TYPE to the chain and label anything that is not a sale:

This keeps quantities and values separate, and the item lines still add up to {{ TRANSACTION.GROSS }}.

NOTES - a few things grouping cannot fix on its own:

If you'd like to use a full example template with ticket grouping, our Example Templates all include ticket grouping.

Yes, we have Order Merge Tags you can use for this.

Learn more - Full List of Merge Tags (Order Tags section)