Illustrative Scratch-Off Ticket: Controlled scratch mask, exposed undamaged reveal symbol, perforated stub and distinct visible identifier area.

Ticket & Voucher Printing · Formats & construction

Scratch-Off Ticket Printing

Scratch-off tickets hide a result or redemption code beneath a removable panel.

  • Visible serials, hidden values, reveal mask and bundle sequence
  • Coated card
  • Code redemption
Compare specifications

Start with the intended use, finished size and quantity. The material and construction can follow.

The product in use

Visible tracking and concealed information in one ticket

A scratch-off ticket connects visible identification with concealed information and a removable reveal area. Serial data and hidden values may require a shared record key. Distribution bundles and the reveal mask form separate parts of the specification from the printed ticket size.

Illustrative Scratch-Off Ticket: Controlled scratch mask, exposed undamaged reveal symbol, perforated stub and distinct visible identifier area.
Illustrative product configuration.

What makes up the finished product?

Visible ticket
Artwork, serial identification and any detachable stub describe the distributed piece.
Hidden content
The hidden value is mapped to the reveal area through a controlled data manifest.
Release and scratch layers
The material combination must hide and reveal the content without damaging the printed layer.

Specifications and materials

Scratch-Off Ticket Printing specifications

Use these reference options to build the project brief. Dimensions are design examples; material availability, tooling and production timing depend on the confirmed specification.

Scratch-Off Ticket Printing reference specifications
ParameterReference or optionWhy it matters
Finished dimensions70 × 140 mmThis design example leaves room for a reveal panel and terms; detachable stubs need their own geometry. Design reference, not a factory limit.
Ticket dataVisible serials, hidden values, reveal mask and bundle sequenceA correct-looking ticket can still contain a duplicated code; validate data separately from coating.
Data and batch manifestVisible serials, hidden values, duplicate rules and controlled batch quantitiesValidate code relationships independently from the appearance and removal of the scratch layer.
Delivery sequenceStub arrangement, perforation, bundle sequence and count per bundleDistribution and reconciliation depend on the agreed numbering and packing rules.
Material constructionCoated card or Uncoated cardCompare the actual grade and construction. Compare a trimmed sample for stiffness and surface handling.
Format and order unitcomplete tickets per controlled data batchList components and versions separately so quantities refer to the same finished unit.
Finishing choiceScratch coating alone is not a certified security system; access controls and game compliance are separate.Approve the proposed material and process combination on an appropriate sample.

Compare the material and its effect.

Choose the surface and construction for the way the finished product will be used. The options below are selection references, not a guaranteed inventory list.

Coated card

300 or 350 g/m² supplier reference grades

Smooth coated card supports printed illustrations. Equal GSM does not ensure equal thickness, rigidity or opacity.

Sample check: Compare a trimmed sample for stiffness and surface handling.

Uncoated card

White or colored uncoated card

An open surface suits handwriting and a tactile finish. Ink appearance and fine detail change with the surface.

Sample check: Test the intended pen or stamp on the finished surface.

Selected sample focus — Coated card: Compare a trimmed sample for stiffness and surface handling.

Format & usable space

Ticket Size, Reveal Mask & Serial Sequence

70 × 140 mm

This design example leaves room for a reveal panel and terms; detachable stubs need their own geometry.

This is a design reference, not a required size or a manufacturing limit.

Ticket data

Visible serials, hidden values, reveal mask and bundle sequence

A correct-looking ticket can still contain a duplicated code; validate data separately from coating.

View the original format reference
Reference format for scratch-off ticket printing: 70 × 140 mm; design example, not a production dieline
70 × 140 mmThis design example leaves room for a reveal panel and terms; detachable stubs need their own geometry.Design reference. This outline shows the format, not a production dieline or a tested construction.

Surface finish options

Artwork outside the scratch panel

The removable scratch layer is a separate functional coating, not decorative foil. Keep these finishes outside scratch panels, validation codes and writing areas; approve removal, concealment and readability on a finished sample.

Illustrative finish samples, not photographs of this product. Final suitability follows the confirmed stock, construction and approved sample.

Compare all surface finishes
Illustrative Scratch-Off Ticket: Controlled scratch mask, exposed undamaged reveal symbol, perforated stub and distinct visible identifier area.
Illustrative construction and printed finish; final materials and effects are selected in your quote.

Details that change the finished product

Inspect the reveal and the controlled batch

Link the reveal panel to the controlled data batch

Provide a controlled data-to-ticket manifest and distinguish printed serial numbers from hidden values. Test the reveal and the scanner or redemption method.

Ticket data

A correct-looking ticket can still contain a duplicated code; validate data separately from coating. A controlled sample batch checks reveal, numbering, code matching and stub removal.

Surface and finishing compatibility

Scratch coating alone is not a certified security system; access controls and game compliance are separate. Smooth coated card supports printed illustrations. Equal GSM does not ensure equal thickness, rigidity or opacity. Compare a trimmed sample for stiffness and surface handling.

Code Redemption & Numbered Ticket Distribution

Code redemption

Reconcile hidden values, visible serials and scan results in a controlled batch.

Numbered distribution

Define stubs, bundle ranges and counting independently from the scratch coating.

Solve the risk before production

Check Duplicate Codes, Pairing & Bundle Counts

The critical finished-product check

Duplicates or mismatched codes can break redemption even when the ticket looks correct. Validate a representative data batch against the supplied sequence and packing counts.

Visible and hidden numbers disagree

Why it happens: Two data layers or artwork versions are paired without a shared record key.

Fix and check: Check visible serial, concealed value and bundle sequence against the same approved data manifest.

When to choose another format

Scratch Tickets, Reveal Cards & Raffle Tickets

Alternatives to Scratch-Off Ticket Printing
AlternativeUse and trade-off
Scratch-Off Card PrintingA loose promotional reveal may not need ticket serials or distribution bundles.
Raffle Ticket PrintingA numbered detachable raffle uses a different reveal and tracking system.

Sample and approval

Check a Controlled Reveal & Numbering Sample Batch

Free samples are available, with preparation completed within 15 days. Confirm the sample scope; courier arrangements and transit time are separate.

Structural sample

Checks dimensions, fit and assembly using unprinted or representative materials. It does not establish final color.

Printed proof

Checks text, image reproduction and artwork on the agreed proof medium. It may not reproduce final assembly or every finish.

Complete finished sample

A controlled sample batch checks reveal, numbering, code matching and stub removal.

From brief to delivery

Order Details for Scratch-Off Ticket Printing

Build and approve the order in five steps

  1. Send the project brief

    Send hidden values, numbering range, validation rules, stubs and bundles. Include finished dimensions, quantity by version, destination and required arrival date. If a configuration is undecided, describe the intended use.

  2. Compare the quoted configuration

    Compare the same quantity basis: complete tickets per controlled data batch. Check that the quote identifies materials, finishing, included components, sample scope, packing and freight.

  3. Approve the appropriate sample

    A controlled sample batch checks reveal, numbering, code matching and stub removal. A print proof checks artwork and color; a complete finished sample also checks assembly. Record what the selected sample does and does not reproduce.

  4. Confirm files and release production

    Approve the final artwork revision and the ticket data specification. Record the agreed quantity, payment conditions, packing and production schedule in the order.

  5. Confirm packing and dispatch

    Confirm numbered sequence, bundle ranges, batch labels and reconciliation counts. Confirm production completion and transit as separate dates, using the delivery destination and required arrival date.

File preparation

Artwork checklist for Scratch-Off Ticket Printing

Artwork and production workflow
  • Provide visible artwork, hidden data and scratch masks as separate files or layers with matching IDs. Define numbering and redemption rules without exposing live credentials in samples.
  • Extend edge-to-edge trim artwork by 3 mm unless the approved template specifies a different bleed. Use approximately 300 effective ppi for continuous-tone images at their placed size; keep fine linework as vectors where possible.

Project questions

Planning Scratch-Off Ticket Printing

Can a visible serial be different from the hidden value?

Yes, if that relationship is defined in the approved data file. Validate the pairing, duplicate policy and bundle sequence before production, and restrict access to sensitive campaign values through an agreed transfer process.

How should I specify quantities and versions?

Count complete tickets per controlled data batch. State hidden values, numbering range, validation rules, stubs and bundles; components, language versions and different structures must be listed separately.

What determines the minimum quantity and delivery schedule?

The selected stock, construction, finishing, version count and sample scope determine production planning. Request quantity breaks for the same configuration and an arrival-date plan that separates sampling, manufacturing and transit. No minimum or lead time is implied by the design examples above.

Specify the finished product.

Send hidden values, numbering range, validation rules, stubs and bundles. Include finished dimensions, quantity by version, destination and required arrival date.