Supported Barcode types
Tickera generates barcodes alongside QR codes on every ticket, using the open-source TCPDF library under the hood. Below is the full list of barcode standards Tickera supports for ticket generation — what each is for, and how to choose between them if your scanner setup expects a specific format.
The default
If you don’t change anything in the ticket template, Tickera renders Code 128 (C128) — the most widely-supported 1D barcode standard, with broad scanner compatibility. For 99% of events, leave it on the default.
All supported types
| Code | Standard | When you’d use it |
|---|---|---|
C39 | Code 39 | Industrial / inventory legacy scanners. Older, alphanumeric, less dense than Code 128. |
C39E | Code 39 Extended | Code 39 with full ASCII range. Same use case as C39 but with broader character support. |
C93 | Code 93 | Compact alternative to Code 39 — denser, smaller footprint on the ticket. |
C128 (default) | Code 128 | The standard for modern retail and event scanners. Full ASCII, dense, universally supported. |
C128A | Code 128 Subset A | Code 128 restricted to uppercase + control chars. Rare specialty use. |
C128B | Code 128 Subset B | Code 128 restricted to upper/lowercase + symbols. Rare specialty use. |
EAN2 | EAN-2 add-on | 2-digit EAN add-on — used as a supplement on book/magazine barcodes. |
EAN5 | EAN-5 add-on | 5-digit EAN add-on — used on book ISBN barcodes for price/issue info. |
EAN-13 | EAN-13 | 13-digit European Article Number — retail / global product barcode. |
UPCA | UPC-A | 12-digit Universal Product Code — North American retail barcode. |
UPCE | UPC-E | Compressed UPC — short version of UPC-A used on small products. |
MSI | MSI Plessey | Inventory and warehouse barcoding. Numeric-only, rare for events. |
MSI+ | MSI Plessey with checksum | MSI with a check digit for error detection. Same use case. |
RMS4CC | Royal Mail 4-State | UK postal barcode — used by Royal Mail for sorting. Rare for events. |
IMB | Intelligent Mail Barcode | USPS US postal barcode. Rare for events. |
How to change the type
In the ticket template builder (guide), select the barcode element you placed on the layout. In its settings panel, pick the type from the dropdown. The next PDF you generate uses the new type.
Recommendation
Unless you’re matching an existing scanner setup that explicitly requires a different standard, stay on C128 (default). Every modern phone-based scanner app (including Checkinera) and every standard retail-style USB scanner reads C128 reliably. The other types exist for specific legacy setups.
QR codes as an alternative
For phone-based scanning (which is most modern events), the QR code is usually the better choice than any 1D barcode — denser, 2D matrix, faster to focus, scans at any angle. Most ticket templates include both QR and barcode side by side for maximum scanner compatibility. See Can I include QR and barcode on the ticket? and Barcode vs QR — which to use.
Related
- Can I include QR and barcode on the ticket?
- QR-code check-in workflow
- Barcode vs QR code — which to use
- Ticket templates
Was this article helpful?
Yes — great. No or partially? Tell us what was missing — we read every message and use it to improve these docs.