By default, Tickera automatically generates a unique ticket code for every ticket sold. Those codes are then used to create barcodes and QR codes for check-in.
That works for most events. But some organizers need to use a predefined list of ticket codes instead — for example, when codes are printed in advance, generated by another system, or tied to an external access process.
Short version: the Predefined Ticket Codes add-on lets you upload your own pool of ticket codes, assign them to new tickets, stop sales when the pool is empty, and still use Tickera barcodes or QR codes for check-in.
When Predefined Ticket Codes Make Sense
Most event organizers can use Tickera’s automatic code generation. Predefined codes are useful when your ticketing process needs to match something outside Tickera.
- You already printed codes on physical tickets, wristbands, badges, or cards.
- A venue, partner, or access-control system supplied a required code list.
- You need a fixed number of codes and want sales to stop when they are used.
- You want ticket codes to follow a specific internal format.
- You are migrating from another system and need to preserve existing codes.
Getting Started
To use this workflow, install the Predefined Ticket Codes add-on like any other WordPress plugin. After activation, go to Tickera settings and look for the Predefined Ticket Codes tab.
You can download the add-on here:
Download Predefined Ticket Codes add-on
Available Settings
| Setting | What it does |
|---|---|
| Enable | Turns predefined ticket codes on or off. |
| Stop ticket sales | Stops sales when all imported codes have been used. |
| Import ticket codes | Uploads your code list into the available code pool. |
| Available codes | Shows how many imported codes remain unused. |
| Used codes | Shows which codes have already been assigned to tickets. |
The most important option is whether to stop sales when the imported pool runs out. If your code list represents a fixed physical inventory, turn this on. If you only want preferred codes first but are comfortable with generated codes later, leave it off.
Preparing Your Code List
Before importing, clean your code list. Remove duplicates, blank rows, unnecessary spaces, and codes that are too similar to read clearly at the door.
- Use one code per line or the format required by the add-on.
- Avoid confusing characters such as O and 0 if staff will read codes manually.
- Keep a backup copy of the original list.
- Import more codes than you expect to sell only if that matches your event rules.
- Test the import with a small sample before using a full production list.
Barcodes, QR Codes, and Check-In
Once a predefined code is assigned to a ticket, Tickera can use it to generate the barcode or QR code for that ticket. From the attendee’s perspective, the ticket still behaves like a normal Tickera ticket.
Before launching sales, run a full test: import codes, purchase a test ticket, confirm the assigned code, open the ticket PDF or email, and scan it with your check-in tool. This is especially important if you plan to use Checkinera at event entry.
Does It Work With WooCommerce?
If you sell Tickera tickets through WooCommerce, test the full WooCommerce purchase flow as well. Confirm that the predefined code is assigned after checkout and that ticket emails, downloads, and check-in all behave as expected.
For WooCommerce-specific ticket display customizations, see our guide on displaying Tickera event data in WooCommerce pages and emails.
Predefined Ticket Codes Checklist
- Decide why predefined codes are required.
- Clean and back up the code list.
- Install and enable the add-on.
- Import a small test batch first.
- Decide whether sales should stop when codes run out.
- Buy a test ticket and confirm the assigned code.
- Scan the ticket before opening sales to the public.
Frequently Asked Questions
Can Tickera use my own ticket codes?
Yes. With the Predefined Ticket Codes add-on, you can import your own code pool and have Tickera assign those codes to new tickets.
What happens when all imported codes are used?
That depends on your settings. You can stop ticket sales when the pool is empty, or allow Tickera to continue generating codes depending on how you configure the add-on.
Will imported codes work with QR codes?
Yes. Once assigned to a ticket, the imported code can be used for the ticket’s barcode or QR code just like a generated Tickera code.
Final Thoughts
Predefined ticket codes are not necessary for every event, but they are extremely useful when you need Tickera to match an existing code system or fixed physical inventory.
Clean your list, test the flow, and decide what should happen when codes run out. Once that is done, predefined codes can fit naturally into the normal Tickera ticket and check-in experience.
