Glossary¶

These are the Blaqbook-and-Odoo-specific terms you'll bump into across the rest of the docs. If a section uses one you haven't seen, jump back here.

10DLC A2P registration¶

The carrier-required approval that lets a business send SMS to US numbers from a 10-digit phone. Without it, sends are blocked. Your administrator handles this — operators don't touch it.

Attended state¶

A registration that has been checked in at the door, either by a successful QR scan or a manual click on the Attended status label on the registration form. P&L attendance counts only update once registrations land in this state.

Developer Mode¶

An Odoo backend toggle that exposes administrative settings normally hidden. You'll need it for one specific task (assigning Blaqbook role groups). It doesn't enable anything dangerous on its own — it just unhides the menu.

Draft state¶

A registration that exists but isn't paid yet (for example, someone started checkout and abandoned it). Draft registrations won't scan at the door.

Journal¶

Odoo's name for a category of money movement (Sales, Bank, Cash). You usually don't touch journals directly; they sit underneath your invoices and payments.

KPI (key performance indicator)¶

A single number on a dashboard meant to summarize health at a glance (tonight's check-in rate, total revenue this month, attendance score).

Loyalty program¶

A points-or-rewards system attached to an event. Powers referral rewards.

Merge field¶

A placeholder like {{contact.first_name}} inside an SMS or email template that gets swapped for the real value when the message sends.

P&L (profit-and-loss report)¶

A per-event summary of money in (tickets, bar, merch) minus money out (DJs, security, supplies). Generated automatically after the event closes.

POS (Point of Sale)¶

The in-venue cash drawer or iPad-style sale screen. Separate from the public online store, but shares the same inventory.

A discount code attached to a ticket tier (for example, "FRIENDS20" for 20% off).

Referral code¶

A unique short URL given to each ticket buyer. They share it, others buy through it, and the original buyer earns a reward.

Registration¶

The record created when someone signs up for an event, whether they paid or were comped. Different from a ticket tier — the registration is a person; the tier is the price they paid.

Segment¶

A saved filter on your contact list (for example, "everyone who came to a techno event in the last 90 days"). You use segments to target SMS blasts and automated emails.

Stripe¶

The payment processor Blaqbook uses to take credit cards online and at the door. Test mode means no real charges.

Stripe payout¶

A bundled bank deposit Stripe makes to your account, usually covering multiple events' worth of card sales. The reconciliation walkthrough covers how to match the payout back to your Event Financial Summaries.

Ticket tier¶

A named price level on an event (Early Bird, GA, VIP). One event can have many tiers.

Twilio¶

The SMS provider Blaqbook uses to send text messages.

Upgrade¶

Installing the newest version of a Blaqbook feature. Your administrator runs this from the command line; you'll see it flagged as a step in any prose that mentions a recent change. (Sometimes called a "module upgrade" in Odoo terminology — same thing.)

Vendor slot¶

A line on the event form for a DJ, photographer, sound engineer, or other paid talent. The fee on the vendor slot feeds into the event P&L.

Webhook¶

A small message that Stripe sends Blaqbook the instant a payment lands, so the registration flips from Draft to paid without anyone clicking anything.

Events — uses Registration, Ticket tier, Draft state, Attended state, Promo code, Referral code, Vendor slot.
Finance — uses P&L, Journal, Webhook, Stripe, Stripe payout.
Door & Scanner — uses Attended state, Registration.
CRM & SMS — uses Segment, Merge field, 10DLC A2P registration, Twilio.