Worksheet Use this worksheet to plan your ticket template configuration before you start building them.
For more information about configuring ticket templates, refer to General Configuration - Tickets. |
Ticket templates represent admissions, gift certificates, receipts, address headers and vouchers. There are eight ticket template types that align with various items and functions:
•Seat: A ticket for events.
•Delivery Method: A header for mail and will call orders.
•Gift Certificate/Card: A printed stored value item.
•Miscellaneous Item: A parking pass, concession or merchandise voucher.
•Pass: Tickets for many events on a single barcode.
•Payment Method: A transaction receipt for the merchant and customer.
•Service Charge: A separate receipt for a specific charge.
•Void: A receipt for a canceled item.
You can create a different design and layout for each the types of printers (or devices) that will be used for the ticket:
•FGL2/FGL4: Friendly Ghost Language devices are typical thermal ticket printers from BOCA or Stimare. While they offer similar functionality, there are specific font sizes you’ll need to keep in mind when designing your tickets. If you’re unsure which to pick, consult your printer’s documentation or print a test ticket by pressing the ‘Test Ticket’ button.
•PDF: A ticket emailed to customers or available as a download.
•Windows: A ticket printed with a Microsoft Windows-compatible printer driver.
When you’re setting up the devices, use the same DPI as the printer:
•FGL: The DPI for most FGL printers is 200 or 300.
•PDF: The DPI for PDFs should be 100 to ensure a balance between the file size and the clarity of your ticket.
•Windows: While many Windows printers can have a DPI of up to 600, a device configured at 300 DPI will provide excellent results.
The height and width of the ticket are measured in pixels related to the DPI of the device. Further details on calculating the dimensions of the are available in our product guides.
You’ll need to pick the ‘Stock Type’ too. Selecting a specific stock doesn’t automatically populate the width or height. You can set different preferences when more than one printer is available or if you have two different stock sizes. The addition of another Stock Type results in a third option on the Desktop settings dropdown. You can add additional stock types by adjusting the stock list.
The design principles are the same for all devices. When you’re on the Tickets|Basic page, one of the devices will have editing next to it. That is the active device. Clicking on the Tickets|Elements page will load the ticket template design for that device.
Elements make up all of the information on the ticket. An element can either be a fixed value or a variable (computed value). Fixed values don’t change. What you enter will show up on the ticket. Computed values use information from the order/admission, such as the event name, start date and seating information.
When you’re working with elements, there are a handful of settings you’ll likely use more frequently:
•X/Y: These represent the horizontal and vertical location of the element. The point where the coordinates meet based on the element and its impact on text is illustrated in our product guides.
•Width/Height: This is only necessary if the element contains an image or you plan on bordering the text in a box.
•Point Alignment: The point used based on the X/Y coordinates. Either the top left corner, the top center or the top right corner of the element.
•Depth: Allows you to layer elements on top of each other. When crafting your PDF ticket, ensure that your background image has a depth of 0, and all of the other elements have a depth of at least 1.
•Rotation: Use this field to rotate elements.
•Computed Value: Select the information from the order/admission you want to print on the ticket.
•Value Location: If you include text in the ‘Display Text’ field, this setting allows you to offset the computed value by the number of characters you enter.
•Display Text: Use this field to print static text or identify what computed value you’re printing on the ticket. If you don’t specify a value location, any computed value will display immediately following the displayed text.
•Left Condition/Conditional Operator/Right Condition: These three fields determine whether to display the element based on meeting the conditions.
•File Attachment: This allows you to upload an image to print on the ticket or to serve as your background image for your PDF tickets.
When creating your background image you’ll need to ensure the DPI of your image and dimensions match what you’ve configured for the PDF device.
If, for example, you have the PDF device configured:
•Width: 850
•Height: 1100
•DPI: 100
Your image will need to be 850 x 1100 pixels at a resolution of 100 DPI. Any differences and the system may not render the PDF correctly, resulting in files that your customers can’t open.
When creating a ticket template for an FGL2 device, we recommend using the following font sizes or multiples of them (Orator would be 91, 182, 273…).
Font Name |
Recommended Size |
Font1 |
7 |
Font2 |
16 |
OCRB |
31 |
OCRA |
8 |
Font5 |
31 |
Large OCRB |
52 |
Large OCRA |
29 |
Tight Courier |
28 |
Small ORCB |
20 |
Prestige |
41 |
Script |
49 |
Orator |
91 |
Courier |
28 |