A family books four timed-entry tickets for Saturday at 10:00, then emails Friday night to say they can’t make it. Your policy says tickets are non-refundable. You’re happy to keep the money, but you’d like those four spots back in inventory so someone else can buy them. In Altru, that turns out to be harder than it sounds.
The short version: Altru ties a sold ticket to the payment that bought it. The standard way to take a ticket off an order runs through a refund or return process, and nothing in the general workflow is labeled “cancel, keep the money.” That doesn’t mean you’re stuck. It means you need to be clear about what you actually want the cancellation to do, then pick the method that does that and nothing more.
Figure out what “cancel” has to accomplish
When staff say “cancel without refunding,” they usually mean one or more of these:
- Free up capacity for a timed program, tour, or event so the slot can be resold.
- Keep the revenue exactly where it is, because the policy says the sale is final.
- Give the guest a credit or a new date instead of cash back.
- Keep the record clean, so reports and the constituent’s history show what really happened.
Each goal has a different answer. Trying to hit all four with a single transaction is where things go sideways, usually with a refund that gets processed and then “un-done” by hand, which leaves your revenue reports and deposits out of balance.
Options that work with Altru as it is
1. Release capacity without touching the sale
If the money stays and the guest isn’t coming, the cleanest approach is often to leave the order alone and adjust the capacity on that program or event time instead. Raise it by the number of forfeited tickets. The original sale stays intact in revenue, and the freed spots become available to sell again through daily sales, advance sales, or your web forms.
Two cautions. First, write down who is allowed to change capacity and why, because an unexplained capacity bump looks like an error a month later. Second, the guest’s tickets are still valid in the system. If they show up after all, decide in advance whether staff honor them. Many organizations add a note on the constituent record or order so the desk can see the tickets were forfeited.
2. Exchange instead of cancel
When the guest wants another date, an exchange is usually better than a cancellation. Moving the tickets to a different time keeps the payment in place and releases the original slot in one step. Check how your Altru setup handles exchanges between programs with different prices before you promise it at the desk, especially if the new date is priced higher or lower.
3. Refund to a non-cash credit
If your policy is “no cash refunds, but we’ll give you credit,” some organizations process the return and apply the value to a credit the guest can use later, such as a gift certificate or a similar stored-value method, depending on what your organization has set up. This does move revenue, so involve whoever reconciles your deposits before you make it a habit. The accounting side matters more here than the ticketing side.
4. Leave it and report on no-shows
For general admission with no capacity limit, there may be nothing to cancel. The guest paid, didn’t come, and nothing needs to be freed up. A simple query on orders with no scan or redemption for a given date can tell you how often this happens, if that’s useful for forecasting.
Things to confirm before you choose
Altru configurations vary, and some of this depends on your version, your security roles, and how your programs are built. Before you write a desk procedure, test the method you picked in a sandbox or on a low-stakes order:
- Does the freed capacity actually show up as available on the web and at the desk?
- What appears in your daily sales and revenue reports afterward? Run them before and after.
- Can the role your front-line staff use perform the step, or does it need a supervisor?
- Does the change affect your batch or deposit reconciliation?
If you can’t tell whether there’s a native way to void a ticket while leaving the payment untouched in your specific setup, ask Blackbaud support directly and describe the outcome you want rather than the button you’re looking for. You’ll get a more useful answer.
Make it a policy, not a judgment call
The technical method matters less than consistency. Write a short rule your desk can follow, for example:
- Cancellations more than 48 hours out: exchange for another date, or issue a credit.
- Cancellations inside 48 hours: no refund; a supervisor releases the capacity if the program is sold out.
- Weather or organization-initiated closures: full refund or exchange, guest’s choice.
Put the same language on your ticketing pages and confirmation emails. When guests know the rule before they buy, the “can I just cancel?” conversation gets much shorter, and staff aren’t inventing exceptions one guest at a time.
Quick answers
Can I delete a paid ticket from an order without refunding?
Not through the usual workflow, as far as most Altru administrators can tell. Removing a paid item generally runs through a return or refund. Releasing capacity separately is the common workaround.
Will raising capacity overbook the event?
Only if the original guests also show up. That’s why a note on the order and a clear desk rule matter.
Does a zero-dollar refund work?
Some teams try it. Results depend on your configuration and what your reports expect, so test it in a sandbox and check with your finance team before using it in production.
