Variable Data Printing — Interactive Demo

Six real-world VDP use cases, each with a recorded walkthrough, downloadable sample CSV, expected output, and prepress pitfalls written by a print operator. Click any tile below to explore — every demo dispatches the exact same wizard the homepage tiles open, so 'Launch in PDF Press' is a one-click jump from learning to producing.

Event Tickets

Unique scannable tickets in three clicks — sequential numbering + QR for gate check-in.

Sample CSV
Canvas
105 × 148 mm (A6 / Postcard)
Bleed
3 mm
Symbology
QR Code, error-correction M (~15% damage tolerance)
Sheet layout
4-up on A4 portrait
EVENT TICKETS — RECORDED FROM PDF PRESS

Step-by-step walkthrough

  1. 1
    Click the Tickets tile on the homepage. Pre-seeds the canvas to A6 / Postcard and primes the wizard with the tickets template hint.
  2. 2
    Drop your Eventbrite / box-office export CSV. Streaming parser shows the first 50 rows in <100 ms; full dataset finishes loading in the background while you map fields.
  3. 3
    Confirm the field mapping (auto-detect handles it). Order-ID columns become Text; ticket-URL columns auto-detect as QR; we suggest Code 128 fallback for short alphanumerics.
  4. 4
    (Optional) skip image library. Tickets rarely need per-row photos. The step auto-skips when no column resolves to image role.
  5. 5
    Verify A6 / Postcard is highlighted, click Open Editor. Wizard fills in a Cards step with 4-up A4 imposition + 3 mm bleed + crop marks. Counter and QR placements are pre-positioned on the lower-left third of the card.
  6. 6
    Drop your blank-PDF or designed template; export. Each row becomes one A6 page → 4-up arrangement on A4 sheets. 50 rows = 13 A4 sheets at 4-up.

What the output looks like

8 unique tickets (one per row). Each carries Ticket #0001…#0008 (counter) + a scannable QR linking to the unique check-in URL.

CSV columns used in this demo
order_idattendee_nameemailsectionrowseatticket_url

Prepress pitfalls

  • If your CSV's QR column is named confirmation_url or order_url instead of qr_url, the wizard still binds it — fuzzy matching covers 13+ synonyms.
  • EC level M is fine for clean printers. Use H (~30% damage) if tickets are likely to be folded or stickered over.
  • Sequential numbering uses the row index, not a CSV column — so an Eventbrite export's 'Order #' is decorative, not the counter source.

Pro tips from real print shops

  • Add a composite field for `attendee_name + ' • Sec ' + section + ' Row ' + row` to print the seat assignment directly on the ticket.
  • If you need duplex tickets (front = scannable, back = T&Cs), upload a 2-page source PDF — placements bind to sourcePageIndex 0 (front) by default; add a second batch on page 1 for the back.
  • Print-shop reality: 4-up on SRA3 yields 8 tickets per sheet at zero bleed waste vs. A4's 4-up.

VDP terminology — quick reference

Counter placement
A field whose value is the row index ({1, 2, 3…}). No CSV column needed — perfect for sequential tickets, raffle stubs, certificates.
Composite field
A single placement built from multiple parts: column references + string literals. E.g., '{first_name} {last_name}' or 'Order #{order_id}'.
Symbology
The barcode encoding format. QR Code (2D, dense, URL-friendly), Code 128 (1D, retail), DataMatrix (2D, tiny, industrial), EAN-13 (1D, retail products).
Error Correction (EC) level
How much barcode damage can still be read. M = ~15% (default), Q = ~25%, H = ~30%. Higher EC = larger barcode at the same payload.
Bleed
Ink area extending past the trim line. Standard 3 mm. Without bleed, any cut tolerance shows the paper-white edge.
Safe area
Inset zone (3–4 mm) inside the trim where critical content lives. Anything outside risks getting trimmed off during finishing.
N-up imposition
Arranging multiple finished pieces on one press sheet to minimize paper waste. Cards tool = step-and-repeat; Grid = uniform grid; Monkey = cut-and-stack.
Cut-and-stack
A specific imposition order where after the press sheet is guillotine-cut into stacks and the stacks are collated, the final pieces come off in sequential order (critical for numbered tickets).

Beyond the six presets

The six tiles on the PDF Press homepage cover the most common VDP jobs, but the wizard is general-purpose: any CSV/XLSX file with up to ~100,000 rows runs through the same flow. The wizard auto-detects URLs as QR codes, numeric SKUs as Code 128 / EAN, image-filename columns as photo placements (matched against your uploaded image library). For custom layouts — Aztec barcodes, GS1-128 with application identifiers, multi-page front/back tickets — drop your placements manually after Open Editor.

All processing happens in your browser — your data never leaves your machine. Privacy-first by design, which matters when the CSV contains attendee emails, customer addresses, or employee photographs.