“Members get free admission for up to four people” sounds simple until someone asks what “up to four” actually means. Four per visit? Four per order? Four per day, even if they come back after lunch with a different group? Before you touch a single setting in Altru, settle that question, because the answer decides whether Altru can enforce the rule for you or whether you’ll be enforcing it with process and reporting.
Two different kinds of limit
Member ticket limits fall into two buckets, and they behave very differently in practice.
- Per-transaction limits cap how many member-priced tickets can go into a single order. They’re the easier kind to set up, but they’re also easy to sidestep: a member who wants eight free tickets can simply place two orders, or come through the line twice.
- Per-membership (per-account) limits cap how many member-priced tickets a household can use across all its orders in a given window: per day, per event, per month, or per membership term. This is usually what leadership means when they ask for a limit, and it’s much harder to enforce automatically because the system has to look back at everything that membership has already redeemed.
Most organizations want the second kind and end up with the first, then wonder why members are still bringing large groups in on a dual membership.
What you can usually do in Altru
Altru gives you a few levers that shape who gets member pricing and how much of it lands in one sale. How much each lever can do depends on your configuration and version, so treat the list below as places to look, not promises.
Tie member pricing to membership levels
Member pricing in Altru generally runs through membership benefits and discounts associated with your membership programs and levels. If your Family level should get four admissions and your Individual level should get one, the cleanest starting point is making sure each level carries its own benefit or discount rather than sharing one generic “member” price. That way, whatever limits you can configure are at least scoped to the right level.
Look for quantity rules on the discount or benefit
Check whether the discount or benefit you use for member admission lets you set a maximum quantity, and then test what that maximum actually applies to. In a sandbox or test environment, run the same member through:
- One order that exceeds the limit.
- Two separate orders on the same day that together exceed it.
- The same pattern through your online sales channel, not just daily sales at the desk.
If the first test blocks the sale but the second doesn’t, you have a per-transaction limit, not a per-membership one. That’s worth knowing before you announce a policy that the system won’t back up.
Use membership cards as a natural ceiling
Many organizations already limit the number of cards issued per level. If your desk staff are trained to admit members by card (one card, one named adult) and sell member-priced guest tickets separately, the card count becomes a practical cap that’s easy for staff to see and explain.
When Altru won’t enforce it automatically
We’re not aware of a simple built-in switch in Altru that caps member tickets per household across every order and channel for a period you choose, and limits by specific event or ticket type add more complexity on top. Capabilities change, though, so confirm with Blackbaud support before you rule it out, and describe the exact scenario (for example, “Family members limited to four free general admission tickets per calendar day across desk and web sales”).
If it turns out the system can’t do it, the realistic options are a mix of policy, desk tools, and monitoring.
Give the desk something to check against
Staff can’t enforce a cumulative limit if they can’t see what a member has already redeemed. A query that pulls today’s member-priced admissions by constituent or membership, sorted by quantity, gives supervisors a quick look at who’s already used their allotment. Some teams display key details on the constituent record with a smart field or attribute so it’s visible during the sale.
Make the online path match the desk
Limits tend to break online first, because web forms rarely apply the same judgment a cashier does. Review how member pricing is unlocked on your web forms, and make sure the online quantity rules are at least as strict as the desk rules. If the web allows more than the desk, members will figure that out quickly.
Audit after the fact
A weekly or monthly query looking for memberships that exceeded the limit tells you whether the issue is widespread or limited to a handful of households. Often it’s a small number of repeat cases, and a friendly conversation or a note on the record does more than a system-wide restriction would.
Write the rule so staff can say it out loud
Whatever you configure, the policy needs to be something a part-time cashier can explain in one sentence. Compare these:
- “Your Family membership covers up to four people per visit.” Clear, and enforceable at the desk.
- “Your membership includes a set allotment of member-rate tickets per term, tracked across all purchases.” Fair, but only workable if staff can actually see the running count.
Pick the version that matches what your setup can really support. Put it in your membership level descriptions, your renewal communications, and your web form text, so members hear the same thing everywhere.
Quick answers
Can I set different limits for different membership levels?
Generally yes, as long as each level has its own benefit or discount rather than one shared member price. Scope the limit to the level, then test it.
Will a per-order limit stop members from splitting purchases?
No. A per-transaction cap only covers what’s in a single order. Stopping split purchases requires a cumulative limit or staff who can see prior redemptions.
Can I limit member tickets for a single special event?
Possibly, depending on how the event’s pricing and discounts are set up. Test it in a sandbox with your real event configuration before you commit to it publicly.
