Concepts & Data Model
Concepts & Data Model
This page explains how Buzz organizes its data so you can make sense of every form you
see in Desk and every screen in the dashboard (/b/...). You do not need to be a
developer — the goal is to give you a mental map of the core pieces and how they connect.
The center of everything: Buzz Event
Almost everything in Buzz hangs off a single record: the Buzz Event. When you create an event, you are creating the parent that owns your ticket types, add-ons, sponsorship tiers, schedule, custom forms, payment gateways, sponsors, talks, bookings, and tickets.
Think of the Buzz Event as the folder, and every other record as a document filed inside
it. Each ticketing, sponsorship, or proposal record carries an event link back to its
Buzz Event, which is how Buzz keeps one event's data cleanly separated from another's.
A Buzz Event directly holds (or points to):
- Ticket Types and Add-ons — what people can buy.
- Bookings and Tickets — what people actually bought.
- Sponsorship Tiers and Sponsors — sponsorship packages and the companies on them.
- Talk Proposals and Event Talks — submitted and accepted sessions.
- Schedule items, featured speakers, custom forms, and payment gateways — configured as child tables directly on the event.
Glossary of key DocTypes
A "DocType" is just Frappe's word for a record type (a table). Here are the ones worth knowing, grouped by module.
Events module
| DocType | What it is |
|---|---|
| Buzz Event | The central event record everything else links to. |
| Event Category | A reusable label/grouping for events (e.g. Conference, Meetup). |
| Event Venue | A physical or online location, reusable across events. |
| Event Host | The organizing person or company behind an event. |
| Sponsorship Tier | A sponsorship package (e.g. Gold, Silver) priced per event. |
| Event Sponsor | A company confirmed as a sponsor at a given tier. |
| Event Talk | An accepted session in the schedule, with its speakers. |
| Event Check In | A record that a specific ticket was scanned at the door. |
| Event Template | A pre-filled blueprint to spin up new events faster. |
| Additional Event Page | An extra public content page attached to an event. |
Ticketing module
| DocType | What it is |
|---|---|
| Event Ticket Type | A category of ticket you sell (e.g. Early Bird, VIP) with its price and inventory. |
| Ticket Add-on | An optional extra (e.g. T-shirt, workshop) attached to an event. |
| Event Booking | One purchase transaction by one buyer; can cover several attendees. |
| Event Booking Attendee | One attendee row inside a booking. |
| Event Ticket | A single admission credential issued to one attendee (with QR code). |
| Event Payment | A payment recorded against a booking. |
| Buzz Coupon Code | A discount code scoped to an event, category, or ticket type. |
| Ticket Cancellation Request | A request to cancel one or more tickets in a booking. |
Proposals module
| DocType | What it is |
|---|---|
| Talk Proposal | A session submitted by a speaker for an event's call for talks. |
| Event Proposal | A proposal to run a whole event (host, category, details). |
| Sponsorship Enquiry | A company's request to sponsor at a chosen tier. |
Buzz (settings) module
| DocType | What it is |
|---|---|
| Buzz Settings | Global configuration (windows for transfers, cancellations, etc.). |
| Buzz Custom Field | An event-scoped custom field shown on booking, ticket, or custom forms. |
Buzz Marketing module
| DocType | What it is |
|---|---|
| Buzz Campaign | A marketing campaign linked to an event (e.g. register-interest drives). |
Booking vs Ticket vs Ticket Type vs Add-on
These four are the ones organizers mix up most often. Here is the plain-language version.
- Event Ticket Type is the menu item — "VIP ticket, ₹5,000, 100 available". You define these up front. They are the templates buyers choose from.
- Add-on (Ticket Add-on) is an optional extra on the same menu — "Conference T-shirt, +₹500". Add-ons attach to the event and are offered during booking.
- Event Booking is the receipt for one purchase. One person checks out once and gets one booking, even if they bought five tickets for their team. The booking holds the buyer, the currency, any coupon used, and the list of attendees.
- Event Ticket is the individual admission pass. Buzz generates one ticket per attendee after the booking is paid. Each ticket links back to its booking, points to the ticket type it was sold as, carries any chosen add-on values, and gets a QR code used at check-in.
In short: a buyer picks a Ticket Type (and maybe an Add-on), completes one Booking, and Buzz issues one Ticket per attendee from that booking.
Booking (1 purchase)
├── Attendee A ──> Ticket A (Ticket Type: VIP, Add-on: T-shirt M)
├── Attendee B ──> Ticket B (Ticket Type: VIP, Add-on: T-shirt L)
└── Attendee C ──> Ticket C (Ticket Type: Regular)
Data model diagram
This shows the key DocTypes and how they link. Lines follow the actual link fields in the
records: ||--o{ reads as "one owns many".
Where to go next
- To create the central record, see Create an Event.
- To set up what people buy, see Ticket Types & Inventory and Add-ons.
- To understand the buyer's path, see Book Tickets and Manage Your Ticket.