Numbered raffle tickets need two things a plain document does not: a matching number printed on both the ticket and its tear-off stub, and a page order that keeps sequential numbers together after cutting. Both come from a numbering merge plus a cut-and-stack imposition step, rather than from manually retyping hundreds of numbers. The paired number is what makes the stub function at all, since the stub is the claim and the ticket is the receipt, so both must carry the same value and both must be legible after tearing. The imposition step is what makes the printed stack usable, because a numbered job imposed in reading order produces piles that jump in increments rather than counting upward. Do the numbering first and impose the numbered file, then cut a short test stack and check the pile boundaries before committing the run, since a mis-imposed numbered job cannot be sorted afterwards.
This guide explains variable-data preparation. PDFImpose arranges the resulting PDF for printing; create and verify the data merge in another tool first.
What do you need to make numbered raffle tickets?
Three things, in this order: a one-ticket template with the stub attached, a numbering sequence (prefix, start number, digit padding, quantity), and an imposition step that arranges the numbered tickets onto sheets for cutting. Skip the imposition step and you'll still get 500 correctly numbered tickets — just not in an order that keeps them sequential once they're cut apart.
The template itself is simple: a ticket panel and a stub panel, usually separated by a perforation guide, each with a number field in the same position. Everything else — event name, date, prize description — stays static across the whole run.
Two decisions worth making before you set up the template: how many tickets fit per sheet at your chosen trim size, and whether the stub needs a barcode in addition to the printed number. A 4-up layout on a standard letter or A4 sheet is common for a compact ticket; a barcode adds a field to the merge but otherwise follows the same matching-number logic as the printed digits.
How does ticket-stub number matching work?
A numbering merge places the same generated value into two fields on one page: the ticket number and the stub number. Because both fields pull from the same counter for that record, they should match when both fields are mapped correctly — still proof the export for mismatched mappings or counters, which is the exact failure a manual numbering stamp is prone to.
This matters for the drawing itself. Whoever draws a winning stub needs to hold a number that corresponds to exactly one ticket in circulation. A one-digit mismatch between ticket and stub either invalidates a draw or forces a manual cross-check against every ticket sold.
How should you set up padding and prefixes?
Digit padding keeps every number the same width by filling with leading zeros — 1 becomes 0001 in a four-digit scheme. A prefix is optional text before the number, useful when running multiple ticket types or events through the same numbering scheme (RAF-0001 vs VIP-0001).
| Run size | Minimum digits | Recommended digits | Example |
|---|---|---|---|
| Up to 99 | 2 | 3 | 001 |
| 100 – 999 | 3 | 4 | 0500 |
| 1,000 – 9,999 | 4 | 5 | 05000 |
| 10,000+ | 5 | 6 | 010000 |
Padding one digit past the minimum is cheap insurance — if a 500-ticket raffle grows to 650 tickets after the template is already set, 4-digit padding (0001–0650) still works, while 3-digit padding (001–650) would have broken at 999 anyway but reads inconsistently below 100.
Where does the perforation line go?
The perforation sits between the ticket panel and the stub panel, and it needs to be marked as a guide, not printed as visible ink. Most shops expect either a dashed line on a clearly labeled spot-color layer, or a position specified separately in the job ticket rather than drawn on the artwork at all.
Leave enough margin on both sides of the perforation guide for the stub to remain legible after tearing — a number set too close to the perf line risks being clipped by an imprecise cut or a slightly crooked tear.
A safe working margin is 3-4mm of clear space between any text or number and the perforation itself, on both the ticket and the stub side. That buffer absorbs the small positional drift that's normal for mechanical perforation, whether it's done on a digital press finishing unit or a separate perforating blade pass after printing.
What does the number sequence need from the data?
A ticket run is a merge like any other, so the sequence usually comes from a generated column rather than from a hand-typed list. Producing it as data means the range, the padding and any prefix are decided once and applied uniformly, instead of being retyped and mistyped.
Gaps and duplicates are the two faults worth guarding against, because both destroy the guarantee the ticket is supposed to provide. A quick check that the row count equals the numeric range, and that the column contains no repeats, catches both before anything is printed.
Reserved and void numbers belong in the data too. Runs that skip unlucky numbers, hold a block back for complimentary tickets, or start at a value continuing from a previous event all need those decisions represented as rows rather than handled at the press.
How do you proof a numbered merge?
Proof the boundaries rather than a random sample. The first record confirms the starting value and the prefix, the last confirms the range ended where it should, and the record where the digit count changes confirms that padding is holding rather than collapsing.
Check both instances of the number on the same proof. Because ticket and stub are populated from one record, a template error that drops or misplaces one of them appears identically on every piece, which makes it easy to overlook when only one half is inspected.
Merge a short set to PDF and read it rather than trusting the preview panel, since preview modes commonly show only the first record. A twenty-record proof exported and paged through takes a minute and exercises the same code path as the full run.
Common questions
Do the ticket and stub need the exact same number?
Yes. The stub is the half a buyer keeps or the half dropped in a drum for the drawing, and it has to match the ticket exactly so a winning stub can be verified against a specific ticket. A numbering merge should place the same value in both fields on every page.
How many digits of padding should I use?
Pad to at least one digit more than your run size requires — a 500-ticket run needs 3 digits minimum, but 4 digits (0001–0500) reads more consistently and leaves room if the run grows before printing.
What line weight should the perforation guide use?
Use a dashed guide around 0.5pt in a spot color or clearly labeled layer, not a solid black line meant to print — most digital and offset shops perforate along a supplied guide line or a position you specify in the job ticket, and a heavy black rule can be mistaken for design content.
Can I number tickets without buying dedicated numbering software?
Yes. A numbering merge that accepts a prefix, start number, and digit padding covers standard sequential ticket numbering without a dedicated press-side numbering unit, which is typically only needed for on-press variable numbering at very high volumes.
Why must the ticket and stub carry the same number?
Because the stub is the claim and the ticket is the receipt, so the pair only works if both show the same value. The number also has to remain legible after tearing, which means keeping it clear of the perforation and of any area likely to be handled or folded.
What order should the two steps happen in?
Number first, then impose the numbered file. Imposing first produces a layout that the numbering step fills in reading order rather than stack order, which looks correct on any single sheet and is wrong across the stack. The reverse order cannot be corrected after cutting.
1. Wikipedia, "Numbering machine," for background on mechanical sequential numbering that VDP replaced for most runs.