Configure production type overrides

Use a production type override when the same ticket should behave differently at a KORONA point of sale and in the KORONA Event back office or online shop. For example, a venue sale can validate a ticket immediately while an online sale activates it for a later scan at the entrance.

Before you start

Confirm:

the production type and its normal method and trigger are configured in KORONA
a KORONA synchronization has imported the production type into KORONA Event
you have permission to update products in the back office
you know whether online tickets should be activated, printed, or validated and which workflow controls payment timing

Understand the three configurations

The Production types list shows three values for every imported production type:

KORONA configuration is imported from KORONA and remains the configuration used at the venue.
Back-office override contains the optional method and trigger selections stored for the back-office and online-shop workflow.
Effective back-office configuration combines overrides with any fields that still use the KORONA value. KORONA Event uses supported ticket methods for local fulfillment; other methods and triggers remain visible configuration.

An override is stored separately from the imported KORONA configuration. A later KORONA import can update the KORONA value without removing your back-office override.

Understand method compatibility

KORONA provides the full method catalog shown below. For fulfillment started in the KORONA Event back office or online shop, KORONA Event currently interprets only the ticket activation, printing, and validation methods. Other method overrides remain visible in the effective configuration, but they do not make KORONA Event run the corresponding generic print, prepaid, voucher, or external-system action.

Production type methods

The complete KORONA production-method catalog. The guidance describes KORONA POS behavior. KORONA Event stores and displays every method override, but local fulfillment currently interprets only ticket activation, printing, and validation methods; selecting another method does not make KORONA Event run that POS action.

Option	What it does	When to use it	Watch out for
Print	In KORONA POS, this prints the configured production output without changing a linked ticket's activation or validation state.	Use it in KORONA POS for output-only workflows that do not need to activate or validate a ticket.	The required printer, template, and production type assignment must be configured in KORONA.
Print merged	In KORONA POS, this combines matching production output into a merged print job.	Use it in KORONA POS when related output should be printed together instead of as separate jobs.	Grouping and layout depend on the KORONA printer, profile, and template configuration.
Activate ticket	In KORONA POS, this activates the linked ticket for later validation without printing it.	Use it in KORONA POS for digital delivery or when a ticket will be printed by another workflow and scanned later at the entrance.	Activation does not mark the ticket as used and does not produce a physical ticket.
Print ticket	In KORONA POS, this prints the linked ticket without activating or validating it.	Use it in KORONA POS when physical ticket output is required and activation is handled separately.	A printed ticket may not be ready for entry until another workflow activates it.
Activate and print ticket	In KORONA POS, this activates the linked ticket and prints a physical copy.	Use it in KORONA POS when the customer receives a printed ticket that will be validated later at an entrance.	The printed ticket remains unused and still needs validation at the point of entry.
Validate ticket	In KORONA POS, this marks the linked ticket as used immediately without printing it.	Use it in KORONA POS when admission happens as part of the sale or fulfillment flow and no later entrance scan is required.	A later scan is normally rejected because the ticket has already been used.
Validate and print ticket	In KORONA POS, this marks the linked ticket as used immediately and prints a copy.	Use it in KORONA POS when check-in happens at the point of sale but a printed ticket or record is still required.	The printed ticket represents an admission that is already used and is not intended for a later entrance scan.
KORONA prepaid	In KORONA POS, this books credit to the configured KORONA prepaid account without a separate production printout.	Use it in KORONA POS for prepaid cards or stored-value workflows that do not need an additional printed output.	The prepaid account, payment method, and product setup must already be configured in KORONA.
KORONA prepaid and print	In KORONA POS, this books credit to the configured KORONA prepaid account and prints the configured output.	Use it in KORONA POS when a prepaid or stored-value sale also needs a printed voucher or transaction document.	Both the prepaid configuration and the assigned KORONA printer must be ready.
Call external system	In KORONA POS, this calls the configured external system without using returned feedback to continue the production flow.	Use it in KORONA POS for a one-way notification or integration action that does not need to return a result.	Do not use it when the sale or fulfillment decision depends on a response from the external system.
Print voucher	In KORONA POS, this prints the configured voucher output.	Use it in KORONA POS for voucher workflows that issue a physical voucher or deposit slip.	The voucher definition and assigned printer must be configured in KORONA; prepaid-account vouchers use the prepaid methods instead.
Call external system with feedback	In KORONA POS, this calls the configured external system and uses its response in the production flow.	Use it in KORONA POS when the external integration must confirm or return information before production can continue.	An unavailable or invalid external response can delay or stop the production action.

Understand trigger compatibility

The trigger list contains the full KORONA timing catalog. KORONA Event stores and displays a trigger override, but currently does not use that value to schedule local ticket fulfillment. A payment-related trigger override is therefore not a payment-safety control for fulfillment started by the back office or online shop.

Production type triggers

The complete KORONA trigger catalog. The guidance describes KORONA POS timing. KORONA Event stores and displays every trigger override but does not currently use the effective trigger to schedule local fulfillment; selecting a payment trigger is not a payment-safety control in KORONA Event.

Option	What it does	When to use it	Watch out for
After payment	In KORONA POS, this starts production after payment is recorded for the transaction.	Use it in KORONA POS when production should follow the payment step.	Confirm the expected behavior for partial, deferred, or account-based payments before using it operationally.
Immediately	In KORONA POS, this starts production as soon as the production item is created.	Use it in KORONA POS when output or an integration action must happen without waiting for booking or payment.	Production can happen before payment succeeds or the transaction is finalized.
After booking	In KORONA POS, this starts production after the transaction is booked or finalized.	Use it in KORONA POS when production should be based on the booked transaction rather than an earlier cart state.	Booking does not always prove that payment completed; use a payment trigger when successful payment is required.
Before payment	In KORONA POS, this starts production when the transaction reaches the payment step, before payment is completed.	Use it in KORONA POS when an external action or output must happen before payment is taken.	Payment can still fail or be canceled after the production action runs.
Manual only	In KORONA POS, this prevents automatic production and waits for a manual Trigger production action.	Use it in KORONA POS when staff must decide when to print, activate, or call the configured integration.	The required POS function or operational step must be configured; otherwise production does not run.
After payment only	In KORONA POS, this starts production only through the completed-payment path and skips booking-only paths.	Use it in KORONA POS when unpaid, deferred, or merely saved transactions must never produce output.	Transactions that do not complete the normal payment path do not trigger production.

Configure an override

In the back office, open Settings > Production types.
Select the production type you want to change. The list displays its KORONA, override, and effective configuration without exposing system identifiers.
Compare the read-only KORONA configuration with the Back-office override.
For supported ticket fulfillment, select a ticket activation, printing, or validation method in Method override. Clear the field to keep using the KORONA method.
If you need to record a different trigger selection, choose a Trigger override. KORONA Event displays this choice but does not use it to start or delay local fulfillment. Clear the field to keep displaying the KORONA trigger.
Check Effective back-office configuration at the bottom of the page.
Select Save.

To remove an override, clear Method override or Trigger override. The effective configuration immediately falls back to the corresponding KORONA value.

Find products that use a production type

Open Services > Products.
Open the filter menu.
Select Production types, then select one or more production types.
Review the filtered product list. The filter can also be included in a saved view when the same group of products needs regular review.

Expected result

Venue sales continue to use the production type configuration imported from KORONA. For fulfillment started by the back office or online shop, a supported ticket-method override affects local ticket activation, output, or validation. Other method overrides and all trigger overrides remain stored and visible, but do not run those KORONA POS actions or schedule local fulfillment. Future KORONA imports do not remove the overrides.

Troubleshooting

Problem	What to check
Production types is empty	A KORONA synchronization has completed and active production types exist in KORONA.
The fields are read-only	Your role includes permission to update products.
An online ticket is already marked as used	The effective method is an activation method rather than Validate ticket.
A changed KORONA value is not used online	An override is still active. Clear that override if the online workflow should follow KORONA again.
A product is missing from the filtered list	The product is assigned to the selected production type in KORONA and the latest import has completed.
A non-ticket action did not run	Configure and test printing, prepaid, voucher, or external-system production in KORONA POS.
Fulfillment ran before the selected trigger	Trigger overrides do not schedule local KORONA Event fulfillment. Check the workflow that started it.