A longtime supporter books a private behind-the-scenes tour, buys a stack of gala tickets, and brings a school group every spring. Add it up and they’ve spent more with you than half your donor wall. Then you open their recognition level in Altru and they’re sitting at the bottom tier, or not in the program at all.
That gap is common, and it usually comes down to what kind of revenue Altru is willing to credit. This guide explains why sales orders tend to fall outside recognition programs, how to confirm what your own database is doing, and the realistic options for giving those buyers credit anyway.
Why sales order revenue often doesn’t count
Recognition programs in Altru are built around giving. They’re designed to total up gifts and related revenue (donations, pledge payments, and in many setups membership payments) and place a constituent at a level based on that total. Revenue that comes through sales orders, meaning daily sales, advance sales, group sales, and online ticket or merchandise purchases, is treated as earned income rather than contributed income.
From an accounting point of view that distinction makes sense. A $200 tour ticket isn’t a $200 gift, and your finance team and auditors care about the difference. The trouble is that recognition isn’t only an accounting exercise. Development staff use it to decide who gets invited to the preview party, whose name goes on the wall, and who gets a thank-you call. Big buyers who never “donate” in the strict sense drop out of that picture.
We’re not aware of a setting that simply tells a recognition program to include sales orders. Because Altru’s behavior can vary with configuration and updates, confirm it for your own database before you build workarounds: check your recognition program setup for which revenue types are counted, run a test sales order against a test constituent in a sandbox if you have one, or ask Blackbaud support directly.
Check how your data actually looks first
Before choosing a fix, find out whether the problem is big enough to need one. A few questions to answer with a revenue or sales order query:
- How many sales orders are tied to a constituent at all? Walk-up daily sales are often anonymous. If most of your ticket revenue isn’t linked to a constituent record, no recognition approach will catch it until you change how those sales are captured.
- Who are your top sales order buyers? Sort constituents by total sales order revenue over the last year or two. You may find a short list of people who matter, which can be handled by hand.
- Are those buyers duplicated? A supporter who buys online under one email and donates under another may be two records. Merge first, or every total you calculate will be wrong.
Options for giving sales order buyers credit
1. Split the gift portion at the point of sale
For gala tickets, benefit dinners, and similar purchases where part of the price is a contribution, the cleanest fix is to record that part as a donation. That way the deductible portion counts toward recognition naturally, and the fair market value stays as earned revenue. Talk to your finance team about how they want this handled, since it affects receipts and reporting, and test it before an event rather than during one.
2. Track sales order totals separately with a smart field
If you want visibility rather than formal credit, a smart field that sums sales order revenue per constituent over a rolling period gives you a number you can put in queries, lists, and prospect reviews. Pair it with a constituency or attribute such as “Top ticket buyer” so it shows up when staff look at the record. This doesn’t change anyone’s recognition level, but it puts those people in front of the development team.
3. Run a parallel tier outside the recognition program
Some organizations stop trying to force everything into one program. Recognition stays strictly about giving, and a separate “patron” or “friends” tier is defined by a query that combines giving and sales order totals. You manage invitations and perks from that query instead of from the recognition level. It takes more upkeep, but it keeps your giving data clean and lets you be generous with benefits.
4. Adjust credit by hand for a short list
If your top-buyer query turns up a dozen people, a manual approach may be all you need. Depending on how your recognition program is set up, you may be able to add or adjust recognition credit directly on a constituent. If you’re not sure that’s available or appropriate in your database, check with Blackbaud support, and either way document who approved it and why so the next admin isn’t puzzled by it.
Picking the right approach
- Mostly gala or benefit tickets? Split the contribution portion (option 1).
- Want development staff to notice big buyers without changing levels? Smart field plus constituency (option 2).
- Want benefits based on total relationship value? Parallel tier from a query (option 3).
- Only a handful of people involved? Manual adjustment with notes (option 4).
Whichever you choose, write the rule down. “Recognition counts gifts and the deductible part of event tickets; admissions and retail don’t” is a sentence your development, membership, and finance staff can all agree on, and it heads off the awkward moment when a loyal buyer asks why they weren’t invited.
Quick answers
Do membership payments count toward recognition?
That depends on how your recognition program is configured. Many organizations include membership revenue; check your program’s revenue settings to see what yours does.
Will a smart field slow down my queries?
Smart fields are calculated on a schedule rather than live, so they’re usually fine in queries. Just remember the value is only as current as the last refresh.
