---
title: "Venue Access and Barcode Relay Console | Mitrix Technology"
description: "Barcode retrieval and a venue console for ticketing: access codes at the gate, offline fallback, isolated sessions, retries, monitoring and an audit trail."
url: "https://mitrix.io/industries/ticketing/venue-access/"
industry: "Ticketing"
---

# Access codes at the gate, on time.

We built time-sensitive barcode retrieval for a ticketing platform, with a lightweight console for venues. Access codes reach the gate when they are needed, including from unattended sales points. When a connection drops, offline fallback keeps scanning. Isolated accounts, sessions, proxy rotation, retries and monitoring keep the relay steady, and every action ends up in an audit trail.

- Gate delivery
- Offline fallback
- Isolated sessions
- Audit trail

## Results

- **Gate** codes issued on demand
- **Local** fallback when links drop
- **Relay** retries and proxy rotation
- **Audit** every action recorded

## What we build

### Access code retrieval

Codes are fetched per request and tied to the order, the venue and the session that asks for them. The console shows what was issued, what was used and when a code expires.

- Access codes
- Timing
- Traceability

### Venue console

A lightweight screen for venue staff: issue a code, confirm a relay, scan a ticket and see fallback state. It runs on hardware a venue already has, with roles that limit what each person can do.

- Console
- Venues
- Roles

### Offline fallback

When the network or the upstream service is unavailable, scanning continues against codes held locally and reconciles when the link returns. Gate staff see which scans are pending instead of a blank error.

- Offline
- Scanning
- Recovery

### Isolated accounts

Each venue or sales point works inside its own account and session. Credentials stay scoped, sessions expire, and one venue's traffic cannot read another venue's codes. When a session ends, its access ends with it.

- Isolation
- Sessions
- Access

### Proxy rotation and retries

Requests rotate across proxies with backoff and retry budgets, so a throttled endpoint does not stall a gate. Failures are logged with a reason rather than dropped silently, and the console shows which venue saw them.

- Retries
- Proxies
- Resilience

### Monitoring and audit

Dashboards track relay latency, scan failures and fallback use by venue. Every issue, relay and scan writes to an audit trail, and alerts reach the team before a gate slows down.

- Monitoring
- Audit
- Alerts

## How it works

1. **Map the gate flow** — We trace how a ticket becomes a code at the gate, including sales points, relays and the software already in place.
2. **Connect the source** — Retrieval is wired to the platform under its terms and the client agreement, with scoped accounts for each venue.
3. **Build the relay** — Proxy rotation, retry budgets and timeouts are tuned per endpoint, then tested against throttling and slow responses.
4. **Ship the console** — Venue staff get issue, relay, scan and fallback views, with roles that match how the venue is staffed.
5. **Add offline mode** — Codes are held locally for the window a gate needs, with a reconciliation pass when the connection returns.
6. **Monitor and audit** — Dashboards, alerts and the audit trail go live with a runbook for the venue and support teams.

## Where access fails

Venue access fails in small ways that cost a queue. A code arrives late, a connection drops at the turnstile, a shared login gets throttled. Each failure looks local until it repeats across venues. We built the relay and console so the gate keeps moving and the record stays complete.

- **Codes arrive after the queue** — A code requested at the gate can take seconds that feel like minutes when a line is waiting. Without timing controls, the request may also arrive after the ticket has been used.
- **A dropped link stops scanning** — Venues lose connectivity more often than back offices do. If scanning depends on a live call, a brief outage turns into a manual check of paper lists and a record that never reconciles.
- **Shared logins get throttled** — One account used across several venues draws rate limits and lockouts. The result is intermittent failure that looks like a venue problem and takes hours to trace.
- **No one can reconstruct the gate** — When a scan is disputed, the venue needs to know who issued the code, which session relayed it and what the gate saw. Without an audit trail that history is gone.

## Modules

- **Code issuance** — Per-request codes bound to order, venue and session, with expiry and use state.
- **Relay service** — Proxied retrieval with retry budgets, timeouts and clear failure reasons.
- **Venue console** — Issue, relay, scan and fallback views for staff on existing hardware.
- **Offline store** — Locally held codes for the window a gate needs, with reconciliation.
- **Session isolation** — Scoped accounts and expiring sessions per venue and sales point.
- **Audit trail** — A record of every issue, relay and scan, searchable by venue.

## Evidence

- **Case** Online ticketing platform — We built time-sensitive barcode retrieval and the venue console inside a live ticketing platform. The work covers unattended sales points, gate delivery, offline fallback and an audit trail for every access action. ([Read the case](/portfolio/online-ticketing-platform/))
- **Channel** Marketplace distribution — Tickets sold through marketplace partners still need to reach the gate. Retrieval runs under platform terms and client agreements, and the console shows which channel a code came from. Channel changes do not alter the gate flow. ([Marketplace distribution](/industries/ticketing/marketplace-distribution/))
- **Service** Cloud-native development — The relay is built to run unattended: retries, proxy rotation, isolated sessions and monitoring are part of the service from the start. The same setup keeps working when a venue stops responding, and the audit trail records what happened. ([Cloud-native development](/services/cloud-native-development/))

## Technology

Stack: Scoped credential store, Session isolation layer, Proxy rotation pool, Retry and backoff budgets, Local code cache, Reconciliation pass, Relay monitoring, Audit log, Alerting rules, Venue role model
Platforms: Turnstile scanners, Handheld scanners, Box office points, Unattended kiosks, Web console, Mobile web, Marketplace channels, Relay infrastructure

## Run the relay in house or with us

Access at the gate depends on a relay that stays within platform terms and reacts to throttling. Some operators keep that service in house; others want it run for them. We scope the work either way, with the same attention to isolation, retries and the audit trail.

- Build when gate access sits at the center of your product and you want the relay in your own stack.
- Adopt when you would rather not run proxies, retries and monitoring for every venue.
- Either path documents fallback behavior and the audit trail before the first gate goes live.
- We test against real throttling and dropped links, then hand over with a runbook.

Venue access is a small surface with a long tail of failure modes. A short pilot at one venue usually shows whether the relay belongs with your team or ours.

## FAQ

**How do access codes reach the gate?**

Codes are retrieved per request through the relay and shown in the venue console or handed to the scanning device. Each request is tied to an order, a venue and a session, with an expiry time and a record of use.

**What happens when the connection drops?**

Scanning continues against codes held locally for the window the gate needs. When the link returns, the console reconciles the scans and flags anything that cannot be matched. Staff see which scans are pending, so the audit trail stays complete.

**Does this work at unattended sales points?**

Yes. Unattended points request and issue codes without staff, inside isolated accounts and sessions. Retries and proxy rotation handle throttling, and monitoring shows when a point stops responding so someone can act before a customer arrives.

**How are accounts and sessions protected?**

Every venue or sales point runs in its own account with scoped credentials. Sessions expire, traffic stays separate, and the audit trail records which session issued or relayed a code, so an incident can be traced to one venue.

**Can we roll it out one venue at a time?**

Yes. The console and relay can start at a single venue or sales point, then extend to the rest of the estate. Each venue carries its own settings, so a pilot does not block the wider rollout.

**How long does it take to go live?**

The first venue depends on how access codes are produced today and what the platform allows under its terms. Retrieval and the console are usually the quick part; offline behavior and reconciliation need testing before a busy gate.

[See the ticketing case](https://mitrix.io/portfolio/online-ticketing-platform/) · [Book a ticketing call](https://mitrix.io/contacts/)
