Choose templates for tickets and vouchers

Use different designs for a product, voucher, event or event template. For example, a membership can have an A4 customer PDF and a separate card-sized PDF for a print service.

Assign a design

You need permission to update the offer and read its PDF or Wallet templates. Create the designs under Comms before assigning them. A print-service PDF must have the correct ticket or voucher type, the physical-card purpose and positive custom page dimensions. For tickets, the print-service PDF field appears only when the Memberships add-on is available.

Open the product, voucher, event or event template in the back office.
Open its communication settings and find Ticket templates or, for a voucher, Voucher templates.
Choose a template for each output you want to change:

Customer PDF for documents customers download or receive by email.
Print-service PDF (physical card) for a separate card layout.
Apple Wallet for Apple passes.
Google Wallet for Google passes.

Select Save templates to save all changed outputs together.

Choosing a print template does not choose a printer; select the destination in the printing workflow.

Use inheritance

Outputs without their own choice show Inherited: followed by the template that applies and where it comes from, for example _Inherited: Standard ticket (account default)_. Choose that option and save to remove an assignment. If nothing can be inherited, the field says so. For an issued ticket, selection follows this order:

An authorized staff member's explicit choice for that output.
The event's assignment.
The actual product's or voucher's assignment.
The event template's assignment.
The account default for that output.

Each settings page explains where its choice sits in this order. A product can still override an event-template default when a ticket is generated. Bundle components use their own product assignments. A missing card design does not fall back to the customer PDF.

Built-in voucher designs

Accounts provisioned with voucher defaults include a customer PDF, separate Apple and Google voucher designs, and a CR80 print-service PDF. Voucher Wallet defaults are separate from ticket defaults. Edit the supplied voucher designs under Comms, or assign another design to an individual voucher.

The card PDF measures 85.60 × 53.98 mm. Its layout includes the voucher name, number, QR code, value at issue and validity date when present. Match the print destination's media settings to this size. The Value at issue field shows the original value, not the remaining balance; redemption checks the current voucher record. Older accounts can continue to inherit their existing shared Wallet design until voucher defaults are configured.

Existing documents and Wallet passes

Saving an assignment affects newly generated output. Previously saved PDFs and retained email attachments keep their existing design. Regenerated output uses the current assignment. Saving an assignment does not send a style update to installed Wallet passes.

Voucher customers can open their order in their shop account and choose Add vouchers to Apple Wallet or Add vouchers to Google Wallet. Staff find Download all vouchers (Apple Wallet) and Download all vouchers (Google Wallet) in the order overview. Apple downloads support up to ten vouchers at once. The Wallet barcode contains the existing voucher number; adding a voucher to Wallet does not create credit or redeem it.

Voucher Wallet layouts use the selected design's branding and supported fields. Google vouchers use the design's logo, background color, hero image and content modules; event dates, seats and gates do not appear. Apple fields that exceed the store-card front layout move to the back. Use voucher placeholders for voucher-specific content. A Wallet pass is a presentation of the voucher: redemption still checks its current validity in KORONA Event.

If a template is unavailable

Check that it belongs to your account and has the right document type and purpose. If the list cannot load, use Try again. If saving fails, the message names the output that was not saved; check your permissions and choose a compatible design. If no inherited design exists, assign one or set an appropriate account default under Comms.