When should one person register a whole team?
By Donghui Qian (Milo)Updated 8 October 20263 min read
Short answer
Use one group order when a single payer is buying several places on one invoice and the names can follow later. Have each person register when you need their own approval, their own consent, or their own employer to pay. On BagEvent a group ticket is one payer at a bulk rate that unlocks at a minimum quantity you set; attendee details can be filled in after payment so the sale is not blocked on names.
A company, an association chapter, or a table host often wants one invoice and a list of names that is still incomplete. Forcing every person through their own checkout loses the booking. Taking one payment and never collecting the names loses the door.
The decision is who is the buyer, not how big the discount looks. This page is the rule. If you never buy anything from us, it still applies.
One order when the buyer is the organisation
Use a group ticket when all of these are true:
- One payer. Finance wants a single charge and a single receipt, not twelve card statements.
- Several places. A team, a chapter, or a table—not a couple buying two seats as a courtesy.
- Names can lag. The buyer can commit before every attendee has replied.
- The same entitlement. Everyone on the order gets the same ticket type. Speakers, exhibitors, and press do not belong on a staff group order.
On BagEvent that is one payer at a bulk rate. The bulk price unlocks at a minimum quantity you configure. Attendee details can be filled in later, so the booking is not blocked waiting on names. A gala table is the same mechanism: one buyer pays for the table, and guest details follow.
Separate registrations when the person is the buyer
- Approval is per person. An invite list or an application is a decision about that human, not about a purchase order.
- Consent is per person. Marketing email, and whether exhibitors may see their details, cannot be accepted by a colleague.
- The employer is not the payer. If people expense their own ticket, a group order creates a refund argument.
- Entitlements differ. A day pass, a workshop add-on, or a member rate has to be chosen by the person who will use it.
A discount code for “employees of X” is not a group ticket. The code attributes a campaign. The group order attributes a payer. Use the code when you want each person on their own record from the start.
Set the name deadline before you set the price
Payment without names is fine. Badges without names are not. Publish the date by which every place must have a name, a meal choice if you asked for one, and the consent you actually need. Put that date on the buyer’s confirmation, and again in the chase. The door should not be the first time someone discovers a seat is still “Guest 4”.
| Moment | What you need | What can wait |
|---|---|---|
| Payment | Payer, quantity, ticket type, invoice details | Every attendee’s name |
| Name deadline | Name and anything printed on the badge | Session picks that are not access-controlled |
| Badge print | A person record the scanner can find | Nothing that identifies them |
| Door | That record on the device, including offline | A new person who was never named |
A brand-new walk-in still needs the network, because only the server can issue a ticket. Plan the unnamed seats as a desk job while you are online, not as an offline save.
What usually goes wrong
- The buyer is not the attendee. Confirmations and the chase go to the payer. Say so, or the names never arrive.
- One order, mixed roles. A sponsor’s staff and the sponsor’s customers are different ticket types and different data rules. Split the order.
- Bulk price with no floor. If two colleagues get the “group” rate, you do not have a group. Set the minimum quantity to the size you actually meant.
- Refunds of one seat. Agree before you sell whether a named person can drop out without unwinding the whole order. The refund policy page is the place that rule has to match.
Frequently asked questions
When one organisation is paying for several places on one invoice and the names can follow later. When each person needs their own approval, consent, or payment, they should register themselves.
Yes on BagEvent. A group ticket is one payer at a bulk rate that unlocks at a minimum quantity you set, and attendee details can be filled in after payment.
No. A table is a group ticket: one buyer pays for the table, and guest details can follow rather than blocking the sale.
No. They need their own ticket type, their own form, and usually their own approval. A group order is for people who share one entitlement.
Read next
- Registration and ticketingGroup tickets, bulk quantity, and forms that differ by ticket type.
- How to price conference ticketsStages, codes, and when a discount is not a group rate.
- Controlled-list registrationWhen someone must approve the person, not the purchase order.
- Refunds and cancellationsAgree how one seat leaves a group order.
- Awards and gala dinnersA table is a group ticket.