esedark
Menu
Back to notes

events / QR tickets / integration

Event access control software: buying and integration criteria

Define what must happen at the door before buying: who gets in, what happens to a repeated QR code and how staff work when connectivity fails.

Buying event access control software involves more than a camera reading a QR code. You need to know what the ticket permits, who confirms admission and what happens when the same ticket appears at another entrance. I would define those decisions before choosing an application or commissioning a build.

This guide focuses on buying or integrating ticket validation for an event organizer, from receiving a valid ticket to resolving an admission exception. For a complete venue platform, the nightclub software guide also covers sales, promoters and customer relationships. The delivery assessed here is the door operation.

Define what each ticket permits and who can decide

Prepare a test event with individual tickets, invitations, cancellations and any ticket types with different rules. Specify the session, admission window, zone and number of permitted uses. For a group purchase, clarify whether each person receives a separate credential or how partial group admission is recorded.

Separate a sale, admission entitlement, scan attempt and confirmed admission. Reading a QR code should not automatically count as admitting a person. If you need current occupancy, define exits and re-entry too: a total of validations does not replace those records.

Identify the door manager, scanner operator, administrator and promoter viewing their sales. Agree who can cancel, correct or authorize an exception and which reason they must record. An operator needs enough information to make a decision without automatically receiving access to all commercial data.

Existing product, integration or custom development

Configure an existing product if its validation covers your ticket types, permissions and devices. Request a demonstration with your event and the edition you would actually buy. The engagement may only require configuration, imports, testing and training.

Commission an integration when you want to retain the current sales system and connect tickets, cancellations and admission records. Before requesting a quote, confirm the interfaces each system provides, who authorizes access and the applicable terms. A one-off export does not demonstrate that cancellations reach the door during an event.

Build a specific component when a necessary rule cannot be supported by verified alternatives. Identify the limitation and the future maintainer. I would not rebuild ticket sales to fix one missing connection, or begin development before agreeing who decides when a ticket is in doubt.

I manage goCrush, a ticketing platform covering QR admission and promoters. That relationship provides context, not an independent product comparison. The criteria below are proposed requirements for your engagement. They do not attribute proprietary hardware, specific compatibility or completed test results to goCrush.

A buying and acceptance matrix for admission

Give each supplier the same matrix. Add included, configurable, additional development or excluded; cost; an owner; and outstanding evidence. Use fictional credentials and the intended devices. Agree load and response-time limits using information from your operation.

Proposed checks from a valid ticket to resolved admission exceptions
ScenarioWhat the engagement must defineAcceptance criterion
Ticket and sessionTicket identity, permitted uses, zones and admission windows.A valid ticket is accepted for its session; a different session or zone produces an understandable rejection without consuming the valid entitlement.
Repeated or simultaneous scansConsumption rules and coordination between connected entrances.The same ticket is presented on two devices simultaneously: the outcome respects the agreed number of uses and both operators can inspect the final state.
Cancellation or replacementThe authoritative source of changes and an agreed maximum propagation delay.A canceled ticket is rejected after the update arrives; replacing a ticket leaves a clear active credential and history.
Connection lossPermitted mode, visible warning, limitations and fallback procedure.When connectivity is cut, the operator distinguishes local information from shared confirmation and follows the agreed policy; recovery preserves and reconciles attempts.
Exceptions and permissionsWho authorizes manual admission, corrects an error or permits re-entry.An unauthorized operator cannot change the rule; an approved exception records its owner, reason and effect on permitted uses.
Closeout and handoverExports of admissions, rejections, pending cases and corrections with their references.Another manager reconstructs the test cases outside the scanning interface and locates discrepancies without confusing sales with admissions.

Record expected and observed results, the accepting owner and limitations. An unproven requirement remains unresolved or excluded. The matrix alone does not establish that a product has passed these checks.

Example: the same QR code at two offline entrances

Hypothetical example: two operators download the ticket list before opening. Both lose connectivity and receive the same ticket at different entrances. A proposal promises “offline operation” without explaining how ticket use is coordinated. I would ask to rehearse that exact case, as well as canceling a ticket after the list was downloaded.

I would not accept a single-device demonstration as proof of duplicate prevention across all entrances. Ask the supplier to explain its coordination mechanism and limits. If it cannot demonstrate mutual exclusion during a disconnection, the business needs an explicit policy: stop automatic validation, direct exceptions to a coordinated checkpoint, or accept a bounded risk with authorization and records.

After reconnection, check that closeout shows what happened at each entrance and which cases require review. Later reconciliation cannot undo physical admission. The staff procedure and information shown to operators therefore belong in the purchase alongside the software.

First-release scope, exclusions and deliverables

I would scope a first delivery around one event, one ticket source, the agreed entrances and ticket types, and closeout. Unless separately quoted, exclude sales and payments, CRM, promoter settlements, campaigns, turnstiles, electrical installation and network equipment. If hardware is required, name its supplier, installer and maintainer; do not assume it comes with the application.

Request a state map, exchanged fields, permissions, agreed configuration or code, acceptance evidence, incident instructions and training. The engagement should specify account control, usage rights, source access where applicable, exports and transfer terms. Identify who sets requirements for retention and access to event data.

When changing systems after tickets have been sold, require a sample import, reconciliation of valid and canceled tickets, and a cutover rule. Avoid two systems consuming the same ticket independently without demonstrated coordination. Rehearse returning to the previous process while retaining admissions made during the trial, and name the person who authorizes opening.

Implementation, maintenance and exit costs

Separate discovery, any initial license, configuration or development, integration, migration, device testing and door-team training. Effort depends on ticket sources, ticket types, permissions, connectivity and data quality. The software quote guide helps compare milestones and exclusions.

For operations, confirm the billing unit: event, ticket, user, device or another unit specified in the offer. Add hosting, communications, equipment rental or replacement and support where applicable. These are categories to ask about, not charges every platform applies. Compare the same event calendar and usage; there is no universal price that replaces that calculation.

Maintenance should distinguish defect fixes, changes to the ticketing source, device compatibility and new features. Agree coverage while doors are open, an escalation contact, response commitments and what staff should do while an issue is investigated. A quick response does not guarantee a resolution.

Include exports, agreed historical retention, access removal and the transition of future events. The total-cost model helps compare those obligations with the initial price without assuming unmeasured savings.

For ongoing access to rented units, the workflow includes agreements, renewals and move-outs. The self storage software matrix defines that relationship between occupancy and credentials.

What to send me about your admission process

Describe how you sell tickets, which system owns them, the entrances you need and your devices. Add ticket types, re-entry rules, known connectivity and one sanitized incident. Include the event date, constraints and the person who would accept the tests. Do not send valid QR codes, attendee lists or credentials.

I can review a business software development or integration engagement with you to connect sales and admission through a verifiable first delivery. You can share the event context so we can decide what to keep, what to integrate and what the trial must demonstrate before you commission the work.

Review my event admission process