A door that keeps scanning when the network drops.

Three hours at the door decide the event.

Everything else can be recovered from. A queue that stops moving cannot. The requirements are unglamorous and absolute: scanning that works offline, duplicates caught across every scanner and every gate, and a fallback that is another phone, not a printed list.

Around the door sits the rest: tiers, waves, promoter allocations, guest lists, the box office and refunds. After it comes the part promoters lose money on, which is reconciling what was sold against what was scanned against what settled.

Lineupo covers the tickets, the guest list and the door.

Lineupo is our own product for ticketing, guest lists and the door, built for club nights, concerts and private events. Before we quote a build for an events business, we check whether Lineupo already covers it. Its terms, as published on its own site:

• Ticket money goes straight into the organiser's own payment account, on the free plan too, so we never hold your payout.
• Lineupo takes no percentage of any ticket, on any plan, and starting is free.
• If the venue wifi fails, each phone keeps scanning from its own copy and syncs when the connection is back, without counting anyone twice.
• Guests on a list get a pass that scans like a ticket.
• The Pro plan runs the same build on your own server.

Plans and prices live on lineupo.com and nowhere else, so this page and that one cannot drift apart.

We build the settlement, contracts and refunds around it.

• Settlement and reporting. Gross, refunds and fees per tier and per channel, exported the way your accountant wants it, and booked in ERPNext if your books run there.
• Promoter and venue splits. Allocations tracked per promoter, and each statement generated from the same figures as the ticket sales, then read and accepted in a portal.
• Sponsor, performer and supplier contracts. Proposal, contract and invoice from one record, read and signed in the browser, and binding in the UAE under Federal Decree-Law No. 46 of 2021.
• Postponements and refunds. A moved or cancelled show triggers the refund rules and the customer notices through an approved template, and each refund is matched to its original payment. Workflow automation.
• The season after. Attendance history and repeat-buyer lists, used only within the consent buyers gave.
• A build where Lineupo does not fit. A flow Lineupo does not cover is quoted as a fixed-price build, and we say which it is on the first call.

The numbers reconcile on the night, gate by gate.

Every ticket is one record from sale to scan to settlement. Tickets sold minus tickets refunded, per tier and per gate, are set against tickets scanned, and the report shows the difference rather than hiding it.

Because buyers pay into your own account, the payment report comes from your payment processor, and it is matched line by line against the ticket records. A duplicate payment, or a refund that cannot be matched to its sale, is refused and queued for a person, and if a money check cannot run, the refund waits.

From the show model to the reconciliation.

• Show model. Capacity, tiers, on-sale plan, promoter allocations and comps.
• Payments. Your own payment account connected, then tested with a real card and a real refund before the on-sale.
• Door plan. How many scanners, which gates, and what happens when the network dies, rehearsed at the venue with the network unplugged.
• On-sale. Watched live, with someone from us reachable.
• Doors. Live numbers per gate, and support on the night of the first event.
• Reconciliation. Sold, scanned and settled matched, with every difference explained.

The work around Lineupo is quoted once, as a fixed price, and carries our 12-month warranty while we host it.