AudienceView Unlimited Product Guides

 

---

 

•Print-at-Home/PDF Tickets

•Bar Codes

•Ticket Numbering

•Issues with UPC and 2 of 5 Bar Codes

 

---

 

Print-at-Home/PDF Tickets

•When tickets are sent in an email to customers, the email includes a copy of the invoice and the tickets.

•Print-at-home tickets printed on ink-jet printers can be difficult to scan. It is recommended to use a larger font for the bar code. For additional bar code notes, refer to Bar Codes.

•When designing a PDF ticket with a bar code, consider including the bar code twice in different locations, once with vertical orientation and once with horizontal orientation. In this way, if one bar code is damaged or cannot be read, the other may not be affected. For additional bar code notes, refer to Bar Codes.

•Do not place the bar code too close to the edge of the ticket. Printers can truncate the code or customers can tatter or ruffle the paper and damage the code.

•You can update the tickets.pdf file name using the Registry - Registry::EN::Application node's 'Tickets Filename' field. Do not use special characters (' < > : " / \ | ? *). This filename is used for all PDF tickets.

 

Bar Codes

•It is recommended that you use either Code 128 or Code 39 fonts for printing bar codes. Code 39 generates a longer bar code than Code 128. Bar codes vary in length depending on the length of the data being printed and the specific bar code font being used. A 20-digit Code 128 bar code is about 1.5", while a 20-digit Code 39 bar code is about 3" in length.

•Whichever font is used, test your scanners with a sample printed ticket to ensure that bar codes can be read successfully.

•For FGL devices, bar code fonts are built into the BOCA printer. For Windows devices you may need to download and install the font. For more information on installing fonts, refer to Adding a Windows Font.

•To ensure successful scanning, the background of the bar code must be plain white and should include a small amount of white space on all sides.

•Do not frame the bar code with a printable box. As bar codes increase in length, they may overlap the box making it difficult to scan.

•For Windows devices (including those running on a BOCA printer), if you use the Code 39 font, you must insert an asterisk (*) at the beginning and end of the number. For more information, refer to Bar Code Formatting for Windows Devices. Also refer to Issues with UPC and 2 of 5 Bar Codes.

 

Ticket Numbering

When assigning ticket numbers, the system adds the total number of admissions in the system (regardless of print status), plus the total number of reprints and the total number of printed miscellaneous items, charges and passes, and then adds three digits to the number to determine the number of digits that are used for the ticket number.

 

For example, the ticket number for the first ticket sold in a new installation would be four digits long (1 plus three digits). If 5,000,000 historical admissions ticket numbers are migrated into the system, the ticket numbers could be ten digits long.

 

If you print a ticket from the first event ever created and one from the most recently created, the first ticket number could be four or five digits and the last could be ten.

 

The ticket numbers grow faster in new installations as the number admissions, reprints and printed items grows quickly from single to double to triple digits (particularly in a migrated system). Plan room for growth in new systems, we recommend ten digits to start. Once ticket numbers get up above 11 digits, the growth slows. It would be difficult for the number to surpass 15 digits (more than 100 million admissions, reprints and other tickets).

 

Issues with UPC and 2 of 5 Bar Codes

When using UPC or 2 of 5 bar code fonts, consider the following notes.