Configuration
After installation, you can find the plugin settings at:
Each sales channel must be configured individually. The configuration under "All Sales Channels" is ignored by the plugin for some settings.
Basic Settings
Option | Description |
|---|---|
Send tickets to customers | Sends tickets to the customer via email after order completion. |
Ticket download on order confirmation page | Enables ticket download directly after order placement on the order confirmation page. |
Release ticket only after payment | The ticket is only provided after successful payment (status "Fully Paid"). |
QR code format (from v3.4.0, All Sales Channels) | Image format of the QR code. Useful if the QR code is not displayed correctly. |
Numeric ticket number (SSCC-18) (from v3.9.0) | Enables SSCC-18 format for ticket numbers (18-digit numeric ID with event ID, running sequence, random component, and GS1 check digit). Recommended for events with barcode scanner requirements. |
Cronjob
Option | Description |
|---|---|
Process orders from | All orders after this date will be processed automatically. Format: |
Cronjob enabled (not inheritable) | Enables the built-in cronjob to send ticket emails to customers. |
Export (from v3.9.0)
Option | Description |
|---|---|
Export only paid tickets | When enabled, only tickets with fully paid orders will be included in the CSV export. |
Automatic export enabled | Enables the scheduled cronjob export. CSV files are automatically written to the configured directory. |
Export interval | Interval for automatic export: Hourly, Every 6 hours, Every 12 hours, Daily, Weekly, Monthly. The change takes effect immediately — no Shopware restart required. |
Export directory | Relative path from Shopware root, e.g. |
All exported CSV files are output with . This allows Excel on Windows/DE systems to open the file correctly with a double-click — without a manual import dialog. The filename automatically contains the name of the sales channel and the export date, e.g. ExportTickets_Storefront_2026-04-13.csv.
Security (from v3.9.0)
Option | Description |
|---|---|
Export Access Token | Static token to secure CSV export routes. Automatically generated when the plugin is activated. The token must be passed as a |
The token appears as a URL parameter and is therefore visible in server access logs. It is designed as a temporary solution and sufficient for admin-only access. For sensitive environments, migration to an admin API route with ACL/Bearer authentication is recommended.
The token appears as a URL parameter and is therefore visible in server access logs. It is designed as a temporary solution and sufficient for admin-only access. For sensitive environments, migration to an admin API route with ACL/Bearer authentication is recommended.
Additional Settings
Option | Description |
|---|---|
BCC email for tickets | Tickets are sent in BCC to this email address(es). Separate multiple addresses with commas. |
Ticket footer | Company name and address for the ticket footer. |
Exclude shipping methods from processing | Tickets with these shipping methods are created but neither sent nor made available for download. After changes, tickets can be sent retroactively. |
Timezone (from v3.4.3) | Timezone for event times on the ticket. |
Setup (from v3.3.7)
Option | Description |
|---|---|
Remove email templates on deactivation | When the plugin is deactivated, the created email templates are deleted. |
Mark Product as Ticket
To create tickets:
open
Select the respective product
In the product settings, mark the product as a ticket
Each variant product must be marked as a ticket individually.
Personalization
The personalization feature can be configured in the settings of the respective product.
Option | Description |
|---|---|
Personalization | Enables the personalization feature for this product. |
Personalization with email | Tickets are sent to the email address(es) entered at checkout. In this case, no download is available on the checkout or order overview page. If the option is disabled, all tickets are bundled and sent to the buyer's email address and are also available for download. |
Free text fields for personalization (optional) | For additional information (e.g. name, table number). |
If an order was placed without email personalization and personalization is enabled between the order time and payment, the ticket cannot be sent because there is no personalization email.
FAQ
How can I enable/disable tickets?
There are two options:
In the database table
fgits_tickets_ticket, change the value in theactivecolumn between1and0.Via the UI automatically or manually through the Extras function (requires AutoInvoice plugin).
How can I export tickets?
Export all tickets per product of a specific sales channel on the product detail page.
Export all tickets of a sales channel at once under (requires Extras).
How do I reset "release without payment" for all products?
UPDATE product_translation
SET custom_fields = JSON_SET(custom_fields, '$.fgits_tickets_no_payment_required', 0);How can I display the available template variables?
Temporarily add the following in src/Service/Document.php in the generateDocument() method:
dump($tickets); exit;