Sell tickets and check people in, even offline

Event ticketing software sells tickets for your events, delivers them to attendees and checks them in at the door. Built for you, it runs on your own website under your own name: you set the ticket types and prices, take the payments into your own account and keep the attendee list.

Behind the ticket shop sit the parts people rarely notice until they fail: the rules that decide who can buy what and when, the invoices companies need, the scanning app at the gate, the badge printer and the screen that tells you how many people are inside. We build them as one system, so a ticket sold at midnight is on the right phone at the right gate the next morning.

It suits conferences, trade shows, concerts, college fests, Navratri garba nights, workshops, marathons and festivals: any event where people pay to come in and someone has to check them at the door.

Organisers usually move when their events outgrow the platform. The fee on every ticket adds up, the platform’s options stop fitting the passes you want to sell, and your attendee list sits in someone else’s system, where you can’t easily reach the people who came last year.

Your own ticketing changes those three things. The payment provider’s charge still applies, but there is no platform fee on top. Ticket rules follow your events instead of a form’s options. And the people who bought from you are your customers, with their consent on record, ready to hear about your next event.

It is not the right move for everyone. If you run a few small events a year, a platform is usually cheaper. Your own system pays off when you sell many tickets, run events again and again, or need rules, invoices or check-in that a platform can’t give you. We will tell you honestly which side of that line you are on.

A ticket type is a price with rules attached. Early bird tickets end on a date or after a set number are sold. Group tickets lower the price per person. Student tickets ask for proof. Sponsor, speaker, press and exhibitor passes are free but need approval. Partner codes unlock a discount, or a ticket nobody else can see.

Events with more than one day or space need more: day passes and full passes, workshops with their own capacity, seated halls with a seat map, standing zones, and passes that open the VIP lounge but not backstage. Each rule is checked when the ticket is sold and again at the door.

You set all of this in your own dashboard. Opening a new event, adding a ticket type or closing early bird doesn’t need a developer. Transfers to a colleague and refunds follow the policy you set, up to the deadline you choose.

Attendees pay the way they already pay. In India that means UPI, cards, net banking and wallets through a provider such as Razorpay. In Europe it means cards, Apple Pay and Google Pay, and local methods such as iDEAL in the Netherlands or Bancontact in Belgium, through a provider such as Stripe. The money goes into your own merchant account.

Companies often buy the most tickets, and they need invoices their accounts teams accept first time. In India, a company enters its GSTIN and receives a GST invoice in its own name, and where your turnover requires e-invoicing, the invoice carries its IRN. In Europe, VAT numbers are checked and businesses in other EU countries are invoiced under the reverse-charge rules. Companies can choose to pay by bank transfer, and their tickets are issued as soon as the payment arrives.

Refunds, part refunds and cancelled events go back through the same provider, with a credit note where one is needed.

Check-in has to work without a connection, because the door is where ticketing is judged. Most people arrive in the same short window, and the venue Wi-Fi is at its worst exactly then, when every phone in the building joins at once.

Before doors open, the staff app on each phone downloads the guest list. Every ticket’s QR code is signed, so the phone can tell a genuine ticket from a made-up one without asking a server. Scans are saved on the phone and shared with the other phones over Wi-Fi or mobile data whenever there is a signal. If a gate is cut off completely, it keeps scanning, and any ticket used twice is flagged as soon as the phones catch up, with the time and gate of first entry.

Staff can use their own phones or a few shared ones, so there is no special scanner to hire. People whose phone has died are found by name or booking number in seconds.

Fake tickets fail because the code is signed: a code your system didn’t issue won’t scan. Shared tickets are the harder problem, because a real ticket can be photographed and forwarded.

Each ticket is accepted once, so the second person through the door is stopped, and the scan shows when and where the ticket was first used. For high-demand events, the ticket can live in an app whose code refreshes every few seconds, so a screenshot is useless. Names on tickets, limits per buyer and a phone number confirmed by OTP make bulk buying for resale harder, and transfers can go only through your own site, so a ticket that changes hands does so on the record.

The minute tickets go on sale is the other moment that tests the system. A popular concert or a garba pass can bring a crowd to the shop all at once.

We prepare for it in three ways. Pages are built ahead of time and served from a content delivery network close to each buyer, so the shop stays quick under load. A ticket is held for the buyer for a few minutes while they pay, so it can never be sold twice. And for the biggest on-sales, a fair queue lets people in in order, instead of letting the site slow down for everyone. Before your first big on-sale, we test the shop with far more traffic than you expect.

For conferences and trade shows, badges print on arrival rather than weeks ahead. Each badge carries the name, the company and a colour for the pass type, and only people who actually come get one, including those who registered that morning.

Zones and sessions are checked at their own doors: the workshop room scans for workshop tickets, the VIP lounge for VIP passes. Exhibitors can scan visitors’ badges on their stands, with the visitor’s agreement, add a note and download their leads after the event, and visitors can see who they shared their details with.

We start with your last event. Your ticket types and prices, an export of past sales from your current platform, the venue plan with its gates and how many staff stand at each, and the questions attendees asked most tell us more than a long requirements document.

You will also need a merchant account with a payment provider in your business’s name, your GSTIN or VAT number for invoices, and your brand and website, because the shop should feel like part of them. Most of all we need one person on your side who decides: someone who knows how your events run and can say yes to a rule.

Ticketing doesn’t end when the event does. Your dashboard shows who came and who didn’t, which ticket types sold, how fast each gate moved and which exhibitors collected leads, with exports for your accounts team and your partners.

Attendee data is kept only as long as you need it and deleted on the schedule you set, under the GDPR or India’s data protection law as your events require. Between events we read your team’s notes, fix whatever slowed anyone down and add what the next event needs, so each one runs a little more smoothly than the last.