Event creation with ticket tiers
Dates, venue, tiers, quantities, sale windows and refund terms for general admission events.
Solutions · Event ticketing
An organiser hands a ticketing platform the riskiest hour of the whole event: the moment tickets go on sale and thousands of people arrive at once. This model is for primary ticketing, where organisers create events themselves, sell at face value within a fixed capacity and admit holders by scanning at the door, rather than a box office with daily showtimes or a resale exchange.
Professional plan. Enterprise customization is quoted on scope.
Capacity that cannot be oversold
Timed holds released back to sale
Offline scanning at every entrance
V1
Dates, venue, tiers, quantities, sale windows and refund terms for general admission events.
Atomic stock holds, card payment, a confirmation email and tickets in the buyer’s account.
Transfer that reissues the code, refund requests within policy and organiser approval of them.
Valid codes downloaded before doors, scanning without signal and sync when a connection returns.
Operating loop
Venue, date, door time, ticket types with prices and quantities, sale windows, per-order limits and refund terms. Seated events attach a seat map with sections and price zones; standing events use a capacity per tier.
When demand exceeds what checkout can serve, buyers wait in a queue. Choosing tickets places a timed hold, payment turns the hold into an order, and a hold that expires puts those tickets back on sale.
Each ticket carries a unique barcode or QR code, shown in the app or saved to a phone wallet. Holders can pass a ticket to a friend, which cancels the old code and issues a new one, or ask for a refund within the organiser’s policy.
Staff scan at each entrance with handheld devices or phones. A valid code admits once, and a second scan shows when and where it was used. After the event the organiser receives a settlement of ticket revenue less fees and refunds.
Roles
Wants the full price before checkout, a queue that keeps their place and a proper way to send a ticket to a friend without passing screenshots around.
Creates events, sets prices, watches sales by tier and by day, messages ticket holders and needs settlement early enough to pay the venue and the acts.
Scan quickly in poor light and patchy signal, see at once whether a ticket is valid, already used or meant for another entrance, and check names on a guest list.
Approves organisers, sets fees, handles cancelled events and chargebacks, and keeps the system standing on the busiest on-sale mornings.
Hard parts
Thousands of buyers selecting the last tickets together will oversell any system that reads stock and writes it in separate steps. Use atomic holds with expiry on each seat or tier counter, and test them at the load of the largest on-sale you expect to host.
A virtual waiting room protects checkout, but buyers who refresh and lose their place complain loudly and publicly. Issue a place token on arrival, show honest progress and let a buyer pick up their place on another device.
Automated buyers can clear an allocation in seconds and relist it at a markup. Limits per account and per card, checks before checkout and releasing the scannable code close to the event make that far harder.
A static code can be screenshotted and sold several times. Rotating codes generated with time-based one-time passwords, wallet passes and transfers that reissue the code cut this down, and offline scanners still need the valid list and must sync used codes once signal returns.
When an event moves or is called off, every holder needs a message, a choice where the policy allows one and a timely refund. Bulk refunds hit the payment provider and the organiser’s balance at once, so plan where that money comes from before the first cancellation.
Operator controls
Identity and business checks before a first payout, capacity caps for new organisers and settlement holds on higher-risk events.
Booking fees per ticket or per order, who pays them, and all-in pricing for markets that require the full price upfront.
Queue switch, presale codes, limits per order and per account, and a pause that stops new sales without voiding holds already in checkout.
Scans per entrance per minute, admissions against capacity, scanner sync status and alerts for duplicate scans.
Revenue
A per-ticket or per-order fee paid by the buyer or absorbed by the organiser, shown before payment.
Free for small events with fees per ticket, or a paid plan for venues and promoters with lower fees, seat maps and deeper reporting.
Parking, merchandise, refund protection or upgrades sold with the ticket, with the organiser or a partner taking a share.
Later
Seat-level inventory is the hardest piece to build; begin with general admission and add maps when you sign seated venues.
Needed once organisers bring on-sales larger than checkout can absorb; until then, load-test and cap quantities per order.
A face-value exchange keeps tickets inside your system, but it carries its own rules and price caps in several markets.
Next decision
Choosing between organiser self-service, a cinema-style box office and reserved-seat sales? The ticketing overview compares how each one runs.
Open registerFor cinemas, theatres and attractions selling many sessions of the same show, the entertainment booking model fits better than one-off events.
Open registerTo have us build it, the app clone development service sets out how we would plan on-sale load testing, payments and the scanner app alongside you.
Open registerLive demo
Open each app or panel in a new tab and sign in with the demo login shown. The demos run on shared sample data, carry our demo product names, and show the ready-made product before any customization.
Customer Web App
user@mxbms.mimeld.com | user123Vendor Portal
vendor@mxbms.mimeld.com | vendor123Box Office Backend
admin@mxbms.mimeld.com | admin123Android App
Artifact register
Reference screens illustrate workflows, not a contracted feature list. Sample prices, data, and responses are demonstration content; confirm the current scope during a walkthrough.
Deployable Product Architecture
Community event workflows / system register
Product delivery loop
Conference event for community app planning
Discover
Blueprint
Build
Operate
Deployable Product Architecture
Professional network systems / system register
Product delivery loop
Professional community meetup for networking app strategy
Discover
Blueprint
Build
Operate
Deployable Product Architecture
Workflow automation planning / system register
AI delivery loop
Operations notes for business workflow automation
Collect context
Generate
Evaluate
Human review
Deployable Product Architecture
Remote collaboration systems / system register
Content platform
Remote work setup for SaaS collaboration content
Publish
Discover
Deliver
Moderate
Most days a ticketing platform is quiet. Then a popular act goes on sale and checkout sees more traffic in ten minutes than in the month before. Design for that hour: atomic holds, a queue in front of checkout, cached event pages and payment retries that can never charge a buyer twice.
Rehearse it as well. Load-test with realistic behaviour, including buyers who hold tickets and walk away, before any organiser trusts you with a big sale.
Organisers judge a ticketing platform at the entrance as much as at checkout. Fast scans, unmistakable valid and invalid screens, offline operation and a live admissions count make the night run smoothly. Give door staff a scanner they can learn in two minutes.
Cancellations, postponements and changed line-ups will happen. Decide who refunds fees, how quickly money goes back and whether holders may keep tickets for a new date, then make the system apply those choices to every affected order at once.
FAQ
Selling tickets for the first time, on the organiser’s behalf, at the price the organiser sets. Resale between fans is secondary ticketing, which brings different rules, price caps in some markets and payouts to individual sellers.
Hold stock atomically when a buyer selects tickets, release holds when they expire and confirm the sale only on successful payment. Then test the whole path at the load of your largest expected on-sale.
They should not depend on it. Load valid codes onto each device before doors open, scan offline and share used codes between devices as soon as a connection appears, so a code cannot be reused at another gate for long.
Yes. Both support event ticket passes with barcodes and updates, which buyers find convenient and which let you push a new time to the pass if the event moves.
A common pattern is full settlement once the event has run, with an advance for organisers who have a track record. Paying everything upfront leaves the platform funding refunds if the event is cancelled.
Primary sources
Dated official documentation, standards, and research that support the factual claims on this page.
Time-based one-time passwords, the basis for rotating ticket codes that resist screenshots.
How event tickets are issued and updated as Wallet passes on iPhone.
Google’s documentation for event ticket passes on Android.
How to read this page
Scope, cost and timeline figures are planning guidance until confirmed in a written proposal. Diagrams and screens are illustrations, not client deliverables, and source-code rights and handover follow the signed agreement. See the delivery process and the full disclaimer.
Next decision
Define outcomes, constraints, evidence, rights and handover before delivery begins.
Commercial rights, repositories, environments, documentation, acceptance and handover remain contract-defined.