---
title: "Ticketing Software Development | Mitrix Technology"
description: "Ticketing software for the secondary market: multi-marketplace inventory, autopricing, order and settlement reporting, barcode fulfilment and venue access tooling. Built on .NET, Angular and Azure."
url: "https://mitrix.io/industries/ticketing/"
---

# Every ticket, every channel, in sync.

We build the systems behind ticket distribution: one inventory reconciled across marketplaces, pricing that moves with demand, fulfilment that lands in the buyer's account — and the access tooling that gets people through the gate.

- Secondary market
- Multi-marketplace
- Venue access

## Results

- **38%** ticket sales lift
- **2×** operational capacity
- **24/7** inventory reconciliation
- **10k+** tickets in one console

## What we build

### Marketplace distribution

One inventory, many channels: list, update and withdraw across marketplaces and your own storefront, with per-channel rules and a single source of truth.

- Marketplace
- Syndication
- Rules
- Delist

### Inventory & fulfilment

Seat-level inventory with duplicate and gap detection, delivery-method rules, transfer retries and a replacement flow when a buyer needs a new link.

- Seat-level
- Dedupe
- Delivery
- Replacement

### Pricing & autopricing

Rules by event, section, seat and time-to-event with floors, ceilings and a review queue — so prices move with demand, not with the loudest spreadsheet.

- Autopricing
- Floors
- Demand
- Review

### Orders & settlement

Every sale in one view: what sold, where, at what price, on which account, with which delivery method — reconciled against payouts and fees.

- Orders
- Payouts
- Fees
- Reconciliation

### Reporting & tax documents

Profit by event, month and channel; purchase and sales detail for finance; tax documents and exports that an accountant will actually accept.

- Profit
- Tax documents
- Exports
- BI

### Aggregation at scale

Purchases and prices pulled from primary vendors and third-party platforms: isolated accounts, proxy rotation, retries and monitoring — inside the terms you are allowed to operate under.

- Ingestion
- Sessions
- Proxies
- Monitoring

### Venue access & relay

Time-sensitive barcode retrieval and a lightweight venue console: unattended sales points, access codes at the gate, offline fallback and an audit trail.

- Barcode
- Gate
- POS
- Fallback

### Quality & releases

UI, API and desktop automation inside the release gate: Playwright and C# suites, seeded inventory data, flake budgets and quality gates in Azure DevOps.

- Playwright
- API
- Desktop
- CI gates

## How it works

1. **Ingest** — Purchases, season passes and multi-day events land in one ledger; duplicates and gaps are flagged before they reach a buyer.
2. **List** — Inventory is syndicated to every channel with its own rules, then updated or withdrawn the moment it sells.
3. **Price** — Autopricing keeps offers competitive by event, section and seat, inside floors and ceilings you set.
4. **Sell** — Direct, marketplace, reseller and unattended POS channels capture the order with account, price and delivery method.
5. **Fulfil** — Tickets move as PDF, QR, barcode, mobile link or box-office pickup — with retries, replacement and proof of transfer.
6. **Settle** — Sales, fees and payouts reconcile per event and channel; finance gets profit reporting and tax documents.

## Modules

- **Inventory ledger** — Events, sections, seats and splits; duplicates, gaps and holds.
- **Channel sync** — List, update and delist with per-channel mapping and retries.
- **Autopricing engine** — Rules, floors, ceilings and a queue for anything unusual.
- **Order desk** — Orders, buyer accounts, delivery method and timing in one view.
- **Transfer hub** — PDF, QR, barcode and mobile delivery with replacement flows.
- **Access relay** — Barcode retrieval, venue console, unattended POS and fallback.
- **Reseller portal** — B2B distribution to rights holders and professional resellers.
- **Finance & tax** — Profit by event and channel, payout reconciliation, tax documents.

## Evidence

- **Distribution** One inventory, every channel — A multi-user platform that lists, updates and withdraws inventory across marketplaces, with per-channel pricing rules and one reconciliation layer instead of five spreadsheets. ([See the platform](https://mitrix.io/portfolio/online-ticketing-platform/))
- **Pricing** Autopricing with a human brake — Prices respond to demand and time-to-event inside floors and ceilings. Anything outside the rules waits for a person, and every change keeps an audit trail. ([See the pricing work](https://mitrix.io/portfolio/online-ticketing-platform/))
- **Venue access** Codes at the gate, on time — Isolated accounts and sessions retrieve time-sensitive barcodes and hand them to a lightweight venue console — including unattended sales points and a fallback when the network drops. ([Explore cloud delivery](https://mitrix.io/services/cloud-native-development/))
- **Quality** Release gates that hold — UI, API and desktop suites run on every merge: Playwright and C#, seeded inventory scenarios, flake budgets, and a report that names the failing business flow, not just the test.

## Team

- **Delivery** — Team lead / architect
- **Backend** — .NET / APIs
- **Frontend** — Angular / NgRx
- **Desktop** — WinUI / WPF
- **Quality** — SDET / automation
- **Analysis** — Systems analyst
- **Cloud** — Azure / DevOps
- **Finance** — Reporting / BI

## Technology

Stack: .NET 6 / 8, ASP.NET Web API, Blazor WebAssembly, WinUI, WPF, Angular 2–21, NgRx, TypeScript, Hangfire, IBatisNetCore, SQL Server, Azure Functions, Azure Service Bus, Azure Blob Storage, Azure DevOps, Playwright, Selenium, PuppeteerSharp, MSTest, FlaUI UIA3, DevExtreme, AG Grid

## FAQ

**Can you integrate with our marketplaces and primary vendors?**

Yes. We build listing, update and delist flows, order and inventory import, and per-channel pricing rules. Where an official API exists we use it; where it does not, we work inside the platform's terms and your agreements.

**How do you keep inventory accurate across channels?**

Event-driven sync with idempotent updates, duplicate and gap detection, and reconciliation jobs that compare our ledger against each channel. When a ticket sells anywhere, it is withdrawn everywhere.

**Do you build dynamic pricing?**

Yes — rules by event, section, seat and time-to-event, with floors and ceilings, a review queue for exceptions and an audit trail for every price change.

**How do you handle barcodes and ticket delivery?**

PDF, QR, barcode, mobile link and box-office pickup, with retries when a transfer fails and a replacement flow when a buyer needs a new ticket. Venue consoles keep working when the network does not.

**Is web scraping acceptable?**

Only where your agreements and the platform's terms allow it. We isolate accounts and sessions, rotate proxies, rate-limit and monitor. Scraping is an integration of last resort, not a business model.

**Can you take over an existing platform?**

Yes. We start with a read-only audit of inventory, sync and release process, then replace the legacy parts module by module while releases keep shipping.

**How do you test ticketing flows?**

UI, API, integration and desktop tests in CI: Playwright and C# for the web, FlaUI for the desktop tools, seeded data for inventory scenarios, and flake budgets so a red build means something.

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