Skip to main content

Chapter 6 — Ticketing Fundamentals: Section, Row & Seat

Attend onboarding guide · ~6 min read · ↑ Back to contents

Welcome to the technical half. From here we're under the hood, learning how ticketing systems actually model the world. It's the foundation everything else is built on — and once it clicks, a lot of Attend's complexity turns out to be simple ideas reused.

Let's start with the smallest building block.

Everything is a section, row, and seat​

Strip away the marketing and every ticket is just three things: a section, a row, and a seat — Section 119, Row 12, Seat 7. A stadium is one big grid of section/row/seat, and selling a ticket means selling one position in that grid.

Even suites are just seats​

Here's the first surprise: ticketing systems have no concept of a "suite."

A suite — the private box from Chapter 4 — isn't a thing the system stores. The team takes a group of real seats that add up to the box's capacity (if a suite holds 40 people, that's 40 real seats) and sells them as one block. Often these sit in a section created for the purpose. The seats are real; what's invented is the suite — the grouping, plus the rule that they're bought all together.

Why this matters: when you work on Premium (suites), you're really manipulating ordinary section/row/seats that the team has grouped into a box. There's no special "suite" object underneath — Attend just remembers which real seats make up which suite (the full story is in Chapter 11).

Venue → Manifest → Event​

Real seats live inside a three-level structure in the ticketing system:

  • Venue — the building itself (the Warriors' arena).
  • Manifest — a specific layout of section/row/seats; think of it as a seating template. A venue can have several.
  • Event — a specific game or show. Each event is linked to one manifest, which tells it exactly what seats exist.

Why have more than one manifest? For sports, you usually don't — the layout is the same every game, so every game links to the same manifest. For concerts, the layout changes: one artist puts the stage at the end, another in the middle; the number of sections and seats shifts. Each setup is a different manifest.

And even after an event is linked to a manifest with, say, 50,000 seats, the team decides how many to actually sell — they might release only 20,000. (How they control that is the next chapter.)

A note on seat maps​

Those slick 3D seat maps you see when buying are built by a separate company (3D Digital Venue), and they're tied to the manifest, not the event — sections not on sale for a given event just show up greyed out. Live Nation, whose venues keep changing, uses simpler static image maps instead.

Recap​

  • Every ticket is a section, row, and seat — a stadium is a grid of them.
  • Suites are real seats sold as one block — there's no "suite" object; it's section/row/seats grouped and sold all together.
  • Venue → Manifest → Event: a venue has one or more manifests (seat layouts); each event links to a manifest. Sports usually reuse one manifest; concerts vary.
  • The team still chooses how many of a manifest's seats to sell.

Next → Chapter 7 — Access & Price: Class Name, Price Code, Ticket Type Code