Tickets numbered 0001 upward, automatically
No numbering machine and no manual editing: set a start, a width and a prefix, and every ticket in the run gets its own number at the position you choose.
Load a file to start.
No upload — everything runs in your browser
How the numbering works
The first ticket takes the starting number and each following ticket increments by one. With a width of four, 1 prints as 0001; a number that outgrows the width, such as 12345, prints in full rather than being truncated. A prefix such as No. or A- lets you separate one batch from another. Because the numbers are plain ASCII they are drawn with a built-in PDF font, so the file barely grows.
Placing the number
Position is given as a percentage across the card and a percentage down it. On a 180 mm ticket, 12 percent across is about 22 mm from the left edge, and 85 percent down is 51 mm from the top. If the stub tears at 45 mm, 12 percent keeps the number safely on the stub. Eight to twelve point type reads well; four digits at 10 pt occupies roughly 20 mm.
Reconciling on the day
The point of serial numbers is that issued and collected counts can be compared. Record the first and last numbers before printing, then check the stubs you collect against that range to get an attendance figure and spot duplicates. For a multi-day event, change the prefix per day — A- for day one, B- for day two — and the tally becomes trivial.
Frequently asked questions
Can I start from a number other than one?
Yes, anywhere from 0 to 999999. If the last batch ended at 120, start this one at 121 and no number repeats.
Can I add a seat number alongside the serial?
Serial mode fills one field only. For a second varying value, switch to the CSV merge and supply two columns — the serial in the first, the seat in the second. A spreadsheet fill-series produces the numbers in seconds.
How many pages is a run of twelve?
A 60 by 180 mm ticket fits four to a landscape A4, so twelve tickets is three pages: 0001-0004, then 0005-0008, then 0009-0012.