A parent signs up three kids for a week of summer camp. The receipt that comes out of Altru lists the event, the price type, a quantity of three, and a total. What it usually doesn’t say is which three children are registered. Two weeks later the parent calls to check that the right kids are enrolled, and someone on your team has to open the constituent record and go looking.
Getting registrant names onto the receipt line items is a reasonable thing to want. Here is what to know about where Altru stands on it, how to check your own setup, and what workarounds hold up in practice.
Why the names are missing
An Altru receipt is built around the transaction: who paid, what was sold, how it was paid for. Registrants are attached to the event registration, which is related to the sale but stored separately. The receipt’s line-item grid pulls from the sale side, so it describes the product and quantity rather than the people tied to each registration.
The same gap shows up for the patron. When a staff member sells registrations on behalf of someone, the receipt reflects the purchaser, and there isn’t an obvious place for “registered for: Maya, Leo, and Sam” or “attending on behalf of the Garcia household.”
Check what your receipt layout can actually do
Receipt options in Altru are limited compared with a fully customizable document, and what’s available can vary with your configuration and how your organization has set up receipts for daily sales, advance sales, and online orders. Before you assume it can’t be done, confirm it:
- Review your receipt configuration with an administrator who has rights to it, and note which fields the line-item area can display.
- Test in a sandbox or on a test order. Register a test constituent for an event with two named registrants and print or email the receipt. That tells you exactly what a real customer will see.
- Ask Blackbaud support directly whether registrant or patron names can be added to receipt line items in your version, and whether any custom receipt work is possible. Ask for the answer in writing so the next administrator doesn’t repeat the research.
If the answer is no, you’re not stuck. You just need to put the names somewhere the customer will see them.
Workarounds that hold up
Send a registration confirmation alongside the receipt
The receipt proves payment; a confirmation proves enrollment. Build a query on event registrations that returns the purchaser, their email, the event name and date, and each registrant’s name. Use it to send a confirmation letter or email after each batch of sales. Customers tend to keep confirmations longer than receipts anyway, because that’s where the “who, when, where” lives.
Use descriptive price types or event names where it makes sense
This won’t add names, but it can make the line items more meaningful. “Camp Week 1 – Ages 6–8” tells a parent more than “Youth Registration.” Keep it short, since long labels can wrap awkwardly on printed receipts.
Capture the registrant at the point of sale, every time
None of the workarounds help if registrants are left as “guest” or attached to the purchaser by default. Make naming each registrant a required step in your front desk procedure for programs, camps, and classes. Spot-check with a query that lists registrations where the registrant is the same as the purchaser for multi-quantity orders; those are often the ones where staff skipped the step.
Give staff a fast lookup for “who’s registered on this order?”
Phone calls are where the missing names hurt most. A saved query or report that takes an order or constituent and returns the registrants means staff can answer in seconds without clicking through registration records. Share it with everyone who answers the phone.
Add a note for the exceptions
For high-touch situations such as a grandparent buying for several families or a school group, a short comment on the transaction or the constituent record listing who the registrations are for saves a lot of guesswork later. It’s manual, so reserve it for orders that are likely to generate questions.
Decide what the receipt is for
It helps to agree internally on what each document does. A common split:
- Receipt: payment record. Amount, method, date, items purchased.
- Confirmation: who is registered, for what, when to arrive, what to bring.
- Reminder: sent a few days before the program, again listing registrant names.
Once staff and customers know the confirmation is where names appear, the receipt matters less, and you aren’t waiting on a layout change to fix the customer experience.
Quick answers
Can I edit the receipt to add a registrant column myself?
Not that we can promise. Receipt customization in Altru is limited, so test what your layout supports and confirm with Blackbaud support before planning around it.
Where are registrant names stored?
On the event registration, linked to each registrant’s constituent record. That’s why a registration query, not a sales query, is the right starting point for confirmations and lookups.
