One System From Ticket Sale to Door Entry

The queue at the door keeps growing, the same QR code turns up on two phones, and because the sales list lives in a spreadsheet nobody knows which seats are still free. An event ticketing app solves all three in one place: seat locks held on the server, single-use QR codes, and door devices that keep scanning even when there is no signal.

How many separate apps does this need?

  • 01

    Audience app (iOS + Android)

    Event listings, seat selection from the venue map, a timed basket lock, card payment, a QR ticket that can be added to the phone wallet, ticket transfer, and refund status tracking when an event is cancelled.

  • 02

    Door scanning app (Android first)

    Runs on the steward's device: scans the QR code, stamps the ticket as used, writes to an offline queue and syncs once the connection returns. Permissions are separated by gate, block and session.

  • 03

    Organiser admin panel (web)

    Create events and sessions, define the seat map and price categories, manage allocations and complimentary tickets, watch a live sales screen and door entry counter, and run revenue reports and the invoicing flow.

  • 04

    Venue manager screen (web, optional)

    A shared calendar for operators with several halls: clashing sessions, door staff assignments, occupancy per hall and the end-of-day cash summary all on one screen.

What the app includes

  • Find adjacent free seats on the hall plan
  • Restricted-view seats flagged before checkout
  • Presale code opening an early access window for your own list
  • Group purchase sends a separate QR to each seat holder
  • Per-gate and per-session staff permissions with shift handover
  • Continuous scan mode for handheld gate devices
  • Standing-area capacity counter with re-entry stamping
  • Ticket transfer instantly voids the previous code
  • Add-ons such as cloakroom or parking attached to the ticket
  • Season pass tracked session by session
  • Live entry counter per gate plus late-arrival share
  • Artist revenue-share report based on contract percentages

State of the sector

Ticket sales run largely through a handful of large platforms; the organiser pays commission and still cannot reach the contact details of the person who bought the ticket. That means spending an advertising budget again every time the next event needs announcing. A venue with its own app keeps its own audience list, announces the second concert by push notification and opens presales to loyal fans. At the door, meanwhile, a hall still working from a printed list delays the session on busy nights and loses audience goodwill directly.

Metrics that matter here

  • Basket-to-payment completion rate — A sensible seat lock duration, a streamlined payment step and fewer 3D Secure errors cut abandoned purchases.
  • Average scan time and queue length at the door — Fast QR validation that works offline shortens entry times and stops sessions starting late.
  • Share of allocation sold per session — Presales, low-availability alerts and final-day notifications lift occupancy session by session.
  • Share of returning ticket buyers — Notifications and early access for your own audience list sell the second ticket without ad spend.

Common mistakes in this sector

  • Holding the seat lock only on the phone If the selection is only marked in the app, the same seat gets sold twice and the argument happens at the door. The lock must be held on the server, with an expiry and a named owner, and the payment result must be matched back to that lock.
  • Building door scanning on the assumption of constant connectivity Signal at venue entrances is usually weak. An app built without offline validation seizes up at the busiest moment. The session's ticket list must be downloaded to the device in advance and entries synced afterwards.
  • Leaving refund and postponement flows until later At the first cancellation, hundreds of refunds get attempted by hand and nobody can track whose money went back. Bulk refunds, refund status tracking and automatic notifications to ticket holders belong in the first release.
  • Generating static QR codes with no stamping A ticket shared as a screenshot lets several people in. QR codes must be signed, stamped on the first scan, and the old code must be invalidated the moment a ticket is transferred.

Regulation and compliance

Because ticket sales involve processing names, contact details and purchase history, KVKK (Turkey's data protection law, aligned with GDPR) requires a privacy notice, separate explicit consent for marketing messages and a defined data retention period; commercial SMS and email also require İYS registration and consent management. The obligation to issue an e-Arşiv invoice for the ticket price and transmit it to GİB still applies, and cancellation and refund document flows are designed accordingly. For remote sales, a distance sales agreement and pre-information form must be provided, and for dated events the exemption from the right of withdrawal must be stated clearly. Card data is never stored in the app; payments are taken through a licensed payment institution.

The real challenges in this sector

  • Seat clashes and timed locks

    Two people can pick the same seat at the same moment. The instant a seat is selected, a timed lock with a named owner is written on the server; if payment is not completed the lock expires and the seat returns to the map. The countdown is shown to the buyer, and late success responses from the payment provider are matched back to that lock so the same seat is never sold twice.

  • The traffic spike when sales open

    For a high-demand concert, all the traffic arrives in the second sales open. The seat map graphics and static data are served from a CDN while seat availability comes from a separate, fast layer; a virtual waiting room can be switched on when needed. Showing users their place in the queue stops them refreshing the page repeatedly and adding to the load.

  • Single-use QR codes and offline door scanning

    A ticket can be shared as a screenshot. QR codes are generated signed, stamped on the first scan and flagged with a warning on the second. Because signal at venue entrances can be weak, the scanning app downloads the session list in advance and holds entries locally; after syncing, the same ticket scanned at two different gates appears in a conflict report.

  • Cancellations, postponements and bulk refunds

    When an event is postponed, tickets have to move to the new date; when it is cancelled, bulk refunds have to start. The panel runs bulk operations per session, queues refund requests to the payment provider, lists the ones that fail and notifies ticket holders. The credit note flow for e-Arşiv invoices already issued (part of e-Fatura, Turkey's mandatory e-invoicing system) is triggered from the same screen.

  • Complimentary, guest-list and concession tickets

    Student, guest-list and artist tickets are generated under different rules. The panel issues personalised codes with usage limits and expiry dates; where a student ticket requires ID to be checked at the door, the scanning screen shows a prompt. That reduces concession tickets changing hands and arguments at the gate.

Required integrations

  • 3D Secure card payments and instalment options via iyzico or PayTR (Turkish payment providers)
  • Bank virtual POS, plus bank-transfer reconciliation for corporate and bulk sales
  • e-Arşiv invoice issuing and transmission to GİB (Turkish Revenue Administration), with cancellation and refund document flows
  • İYS registration for marketing consent (Turkey's commercial message permission registry) and a local SMS provider for reminders
  • Apple Wallet / Google Wallet ticket passes and adding sessions to the phone calendar
  • Meta and Google ad conversion tracking, with UTM-based sales reporting per session

Who this page is for

  • A single-hall theatre or music venue

    The same layout repeats weekly, so the seating plan is digitised once; the real value sits in season passes, a repertoire calendar and presale access for regulars. One scanning device is often enough at the door.

  • A new promoter working in rented venues

    Every show sits in a different room, so fast plan setup, standing-area counting and offline gate scanning that works out of town come first. Artist revenue-share reporting belongs in the first release.

  • A cultural centre or an organisation running free, limited-capacity events

    There may be no payment flow at all; the problem is free tickets claimed and never used. Per-person limits, a waiting list that releases no-shows and real admission counts at the door come first, while invoicing can be switched off.

A phased plan that splits the budget

  1. 1

    Phase 1 — Working core: one hall, from sale to gate 6-8 hafta

    Delivers event creation for a single hall and price tier, timed seat locks, card payment, signed QR tickets and an offline-capable gate scanning app. This alone can sell and admit a real show; everything later is built on top of that loop.

  2. 2

    Phase 2 — Plan editor, invitations and refund handling 5-7 hafta

    Adds a seating plan editor for blocks, rows and price tiers, rules for invitations and discounted tickets, postponement and bulk refund flows, e-invoicing (Turkey's e-Arşiv system) and wallet passes. This block should be ready before the first cancellation, otherwise refunds get tracked by hand.

  3. 3

    Phase 3 — Multi-venue, season passes and revenue sharing 4-6 hafta

    Brings a shared calendar across halls and cities, standing-area capacity counting, season passes, presale windows, artist revenue-share reporting and continuous scan mode for turnstiles or handheld readers. It pays off only once a steady schedule of shows exists.

Typical scope and timeline

Typical scope: audience app (iOS + Android), door scanning app, organiser web panel, seat map editor, timed seat locks, 3D Secure payment integration, e-Arşiv invoice flow, signed single-use QR generation and offline scanning, postponement and bulk refund management, revenue and door entry reports, plus store assets and the release process.

Estimated timeline: 12-18 weeks

Off-the-shelf or custom build?

Topic Off-the-shelf Custom build
Reach and audience discovery Large ticketing platforms bring their own traffic; people who have never heard of your venue can discover the show there, which is a real advantage. Your own app serves people who already look for you; discovery is on you, through ads and your existing list, which is why many venues run both channels side by side.
Audience data and re-announcing Buyer contact details stay with the platform, so announcing the next show usually means paying for reach again. Purchase history stays with you, so the next concert can be announced by push and loyal fans get presale access. In return, data-protection notices and marketing consent records become your responsibility.
Hall plans and unusual layouts Standard hall templates are set up quickly and are often enough for small stages; the off-the-shelf box office works from day one. Box seats, cabaret tables around the stage, partial standing areas or a layout that changes per show can only be modelled properly with an editor built for your venue.
Cost model: per-ticket cut or project budget There is no upfront investment and no cost when nothing sells, which makes sense at low or irregular show volume. A one-time build budget plus optional maintenance, with no per-ticket cut; takings land directly in your own payment provider account. The more regular the schedule, the more predictable this becomes.

Sector glossary

Manifest (gate list)
The list of valid tickets for one session, downloaded to the gate device in advance. Scanning runs against it when the network is weak; if it is not refreshed before doors open, late sales will not appear at the gate.
Seat hold window
The period a chosen seat is reserved until payment completes. Too short and buyers cannot finish checkout; too long and, in a busy on-sale, the plan looks sold out while those seats are still unpaid.
General admission (unnumbered area)
A section sold by headcount rather than seat number. Sales run against a counter instead of a plan, and at the gate the re-entry stamp and live occupancy count become the things that matter.
Season pass (combined ticket)
One ticket covering several sessions of a season or festival. The same ticket is stamped separately at each session, so both the remaining entitlement and true per-session attendance stay visible.
Settlement (revenue share)
After the show, comparing tickets sold, refunds, complimentary tickets and actual admissions to calculate the artist's or venue's share. Unless the contract percentage, comps and refunds are itemised, the split turns into an argument.

Frequently asked questions

Let us talk about your project

A free 30-minute call to scope it out, then an itemised quote within 48 hours.

Get a Free Quote

This page explains the problems an app must solve in this sector. We share references and comparable projects during the call.

Other sectors

All sectors →