How a Ticket Distribution Platform Should Work

By Barnaby Clark, CEO at Line-Up

‍

In the previous post on the problem with ticket distribution today, we argued that live entertainment is the only major commerce category that hasn't solved ticket distribution, and that the missing piece is not technology but a demand-side network capable of consuming the APIs ticketing systems already expose.

This post is about what that demand-side network has to do, and why it turns out to be a harder problem than it first appears.

What ticket distribution actually requires

The simplest version of ticket distribution is middleware: a thin layer that connects to a ticketing system's API on a seller's behalf and lets them resell its inventory. That can be useful, but it is some way from what the industry needs. A seller working through a thin distribution layer inherits whatever commercial limits that layer imposes - on pricing, on fees, on the customer journey, on the data they own. The seller is, in effect, transacting on someone else's terms.

What we wanted to build was different: a ticket distribution platform on which external inventory behaves like inventory the seller owns. The venue's ticketing system remains the system of record. The seller retains the full commercial layer - pricing, fees, upsells, custom forms, branded checkout, customer database, reporting - across both their own inventory and inventory sourced from elsewhere.

In practice, a venue group can sell their own shows and third-party shows under one brand and one customer database. A producer can run a tour across venues on several different ticketing systems and never expose any of that complexity to the audience. An agent can build a modern commerce platform on aggregated inventory without inheriting the limitations of a thin distribution layer.

Making that work required solving a particular architectural problem first.

Ticket inventory as a shipping container

Before the standardised shipping container, every type of cargo had its own handling - barrels, sacks, crates - and was loaded and unloaded differently at every port. International trade was slow and fragmented. The container changed that not by altering what was carried, but by abstracting it. Once the cargo was inside the box, any ship, port or truck could handle it identically.

Ticketing has a structurally similar problem. Every system speaks its own language - different data shapes, different sync semantics, different vocabularies for the same underlying concepts (a "performance" in one system is a "session" in another and an "occurrence" in a third). Connecting to each system bespoke produces a fragmented stack: every integration is its own special case, and every feature has to know which system it is talking to.

Reach is built around a universal protocol translation layer that sits between the underlying ticketing systems and the Line-Up commerce flow. Each connected system is mapped to the protocol once. After that, it becomes interchangeable with any other source, including Line-Up's own primary inventory. The full Line-Up flow then operates on top of the protocol rather than on top of the underlying systems, so it behaves identically regardless of where the inventory originated.

That layer is what makes the rest of the platform possible, and it is the part we think is genuinely new.

What it allows

• Full commercial control. Base inventory and pricing come from the venue's system. Everything that sits on top - additional fees, promotions, discount codes, upsells, custom checkout fields, branded confirmation flows - is the seller's. The seller is not a reseller; they are running their own commerce platform that sources some of its inventory from another system.
• A clean separation between system of record and customer relationship. The venue's ticketing system remains the source of truth for inventory and sales, and Reach syncs transactions back to it in real time so the venue's reporting and stock counts stay accurate. The customer relationship - first-party data, marketing consent, repeat-buyer behaviour, segmentation - sits with the seller. What flows back to the venue is granular and configurable: we pass through what the integration requires, and nothing more.
• Integration timelines in days rather than months. Historically, adding a new underlying ticketing system has meant weeks or months of bespoke development per source. Because everything in Reach is built against the same internal protocol, a new integration is a mapping exercise: how does this system's notion of "performance" correspond to the protocol's? With AI-assisted tooling for that mapping work, timelines have collapsed from months into days. Each new system becomes available across every Line-Up feature automatically.
• A unified API across primary and external inventory. From the perspective of anything consuming Line-Up's API - the seller's website, a partner's app, a downstream distribution channel - inventory is simply inventory. There is no separate Reach API. Primary and externally-sourced inventory sit alongside each other, behave identically, and can be packaged together. Going outwards, a distribution partner reading from Line-Up gets unified access to everything we are connected to, without needing to know what's underneath.
• Setup that requires almost nothing from the venue. The venue shares API credentials; the seller enters them in the Line-Up dashboard with some basic configuration. There is no software to install, no bespoke engineering and no change to existing workflows. Events, schedules and base pricing pull in automatically and stay in sync. From that point on, the inventory behaves like any other source in Line-Up.

In summary

The technically interesting thing about Reach is not any individual integration; it is the protocol layer those integrations are built against - the shipping container. That layer is what allows external inventory to be a first-class citizen inside Line-Up, and what allows new sources to come on line quickly without disturbing the rest of the platform.

The venue's system continues to work as it always did. The seller runs a complete commerce platform. The audience experiences a single, coherent purchase.

===

This is the second in a series of posts exploring ticket distribution in live entertainment.

Next: Who Reach is built for. What changes for venues, producers and agents.

Find out more at Reach by Line-Up

‍