From the Order details page in Teller you can use the ''Change barcode'' action to replace a ticket's entry code. The ticket itself stays exactly the same — same ticket, same order, same seat and price. Only the code used for entry and validation changes.
The feature now works consistently for all ticket setups:
Barcode tickets — the existing behavior, unchanged
QR tickets — the old QR is replaced by a new one, everywhere it appears
Tickets with a myDATA provider — the fiscal document is cancelled and re-issued automatically
Sports tickets with gov.gr wallet personalization — the QR is re-sent to gov.gr for a new, valid personalization
What happens when you change a code
Every time you run ''Change barcode'':
A new active code (barcode or QR, depending on the event setup) is generated for the ticket.
The old code is invalidated — it can no longer be used for entry, scanning or validation.
All views and documents are refreshed to show the new code (see the "Where the new code appears" section below).
An audit trail is kept: who made the change, when, and the old and new codes.
TIP : You can change the code of the same ticket more than once. Each change invalidates the previous code — only the most recent one is ever valid.
Tickets with a myDATA provider
If the organizer is connected to a myDATA provider, changing the code also triggers a full fiscal re-issuance:
A cancellation is sent to myDATA for the original fiscal document.
A new fiscal document is issued and transmitted for marking (φοροσήμανση).
The new document, with its new fiscal identifiers, becomes the only active document shown on both the website and the Teller order details. The old one is kept for audit purposes only.
Sports tickets with gov.gr wallet
For sports clubs whose tickets require personalization through the gov.gr wallet:
A cancellation is sent to gov.gr for the original QR.
The new QR is sent to gov.gr for a new personalization.
The ticket's verification status is reset and reflects the personalization status of the new QR — on both the website and the Teller order details.
After a successful change, only the new QR is valid for stadium entry; the old one is rejected at check-in.
Where the new code appears
After a successful change, the new code (and, where applicable, the new fiscal document) is shown in all of the following:
Area | Updated touchpoints |
Website | Order details page, online tickets, ticket template on the order confirmation page, downloadable ticket PDF |
Teller | Order details page, printable/downloadable ticket PDF, ticket-related exports and download links |
Integrations | Scanning / entry validation accepts only the new code · myDATA shows the new active fiscal document · gov.gr wallet holds the new personalized QR |
Re-downloading an old PDF or revisiting the order confirmation page always shows the new code — the old one is never displayed as active anywhere.
If something goes wrong
If a step with an external system fails, the change is never left in a silent "half-done" state:
Failure | What you will see |
myDATA cancellation or new document fails | A clear status in the order details showing that the fiscal part failed and which document/state is currently active |
gov.gr cancellation or new personalization fails | The new QR is not shown as fully active; a clear failure / pending / action-needed indication is displayed |
In case of a persistent failure, retry the action or contact our support team before re-issuing anything manually.
Frequently asked questions
Does the customer get a new ticket? No — it is the same ticket with a new entry code. No other order or ticket data changes.
Can the old code still be scanned? No. Once the change succeeds, only the new code is accepted at entry.
Does it work when all barcodes have already been issued? Yes — codes are replaced normally even if the "Issue barcodes" feature has issued them all.
Why is it still called "Change barcode"? The name is kept for backward compatibility, but the action handles both barcode and QR tickets.