Event Ticket Generator

One of three things, and the sidebar prints the finished string for ticket one before you build anything. “Ticket number” encodes the number by itself, so a phone scanner reads TKT-0042. “Full details” joins event, number, seat and date with pipe characters. “Check-in URL” takes your own address and appends the number as a t= parameter, using & instead of ? when your URL already carries a query string. Every code is generated from text printed on the same ticket, nothing is looked up remotely, and there is no ticket database behind this.

No, and no printed code can. It carries an identifier, not a signature, so a photocopy scans exactly like the original. That is what the stub is for, take it on entry and the duplicate has nothing left to hand over. For anything high-value, scan into something that records the first use of a number and refuses the second.

500. Past that, run a second batch with the start number set beyond the end of the first.

The padding is the digit count of the highest number in the run, with three as the floor. Eight tickets from 1 gives TKT-001 to TKT-008; a run starting at 998 widens to four digits throughout. Fixed width is what keeps the stubs sorting in order when someone stacks them at the end of the night.

No. The standard PDF fonts reach Latin-1, so an emoji or a CJK character has no glyph and is replaced with a question mark, with the count shown under the download button. Accented Western European letters are fine.