A family buys your holiday package: evening lights admission, a cocoa-and-cookies add-on, and a parking pass, all sold together at one price. The day before, they call to say they drove separately and won’t need parking. They want the parking money back and to keep everything else. That sounds like a two-minute fix. In Altru it often isn’t.
Why partial package refunds are awkward
A package in Altru is sold as a single unit with a single package price, even though it contains several items (event registrations, program tickets, merchandise or fees). Behind the scenes, Altru splits that package price across the items inside it so revenue lands in the right places. The refund process, though, is built around the order and its line items. Depending on your version and configuration, you may find that you can refund the whole package but can’t cleanly pull one component out of it and return only that piece’s share.
We’re not going to tell you exactly what your database will allow, because that depends on how your packages are built and how refunds are set up. Before you write a policy around it, test it: create a package in your sandbox (or a test order you can safely reverse in production), try to refund one component, and look at what happens to the order, the revenue, and the remaining tickets. If the result is unclear, Blackbaud support can confirm what’s supported for your setup.
Workarounds that hold up
1. Refund the whole package, then resell what the guest is keeping
This is the cleanest option for your books. Refund the full package, then create a new order for the items the guest still wants, priced so the difference equals what you meant to give back. The guest sees a refund for the full amount and a new charge, so tell them that’s coming before you do it. Otherwise it looks like a double charge on their statement.
The catch: if the event is near capacity, refunding first can release seats someone else grabs online before you rebook. Put the new order in right away, or hold capacity if your process allows it.
2. Refund a partial amount on the order, if your setup allows it
Some organizations can issue a refund for less than the full order total and leave the tickets in place. If that works in your sandbox test, it’s fast at the desk. Check two things before relying on it: which revenue designation or GL account the refund hits (it may not match the component you meant to refund), and whether the “unused” item still shows as valid for scanning or attendance counts.
3. Issue credit instead of cash
For small amounts, you can offer credit toward a future visit (a gift certificate or voucher, for example) instead of a refund. Nothing in the original order changes and revenue stays where it was. Whatever form the credit takes, record it somewhere finance can see it, ideally in Altru itself, so it doesn’t turn into an untracked IOU. If you aren’t sure how your database handles gift certificates or vouchers, test it in the sandbox first.
4. Refund through your payment processor, then record it in Altru
Avoid this one unless you have no other choice. A refund issued only in the processor’s portal won’t show up in Altru, so your deposits and revenue won’t reconcile. If you have to do it, record a matching adjustment in Altru the same day and leave a note on the constituent record explaining both sides.
Policy decisions to make ahead of time
- Are package components refundable at all? Many organizations price packages as a discount precisely because they’re all-or-nothing. If that’s your policy, say so on the sales page and at checkout.
- What does a component “cost” when refunded? If the package is discounted, refunding a component at its standalone price gives back more than the guest saved. Decide whether you refund the standalone price, a proportional share, or a fixed amount, and write it down for staff.
- Who is allowed to do it? Workaround 1 touches capacity and revenue. Limit it to staff who understand both, and keep a short written procedure next to the register.
- How will finance see it? Ask your finance lead how they want refunds and resales to look in batches and deposits, then stick to that pattern every time.
Build future packages so this is easier
If partial refunds come up often for one offering, the package itself may be the problem. Some alternatives are worth testing:
- Sell the items separately with a bundle discount instead of as a package, if your discount setup can apply that kind of rule (confirm in the sandbox). Each item stays its own line on the order, so refunding one is a normal single-item refund. You lose some of the neat package presentation, but the operational trade often pays off.
- Keep optional extras out of the package. Parking, meals, and add-ons are the components people most often want back. Put the core experience in the package and sell extras as separate add-ons.
- Review how the package price is allocated. If you do keep packages, make sure the price split across components reflects real value. That makes any proportional refund policy easier to calculate and explain.
Quick answers
Will refunding the whole package and reselling distort attendance numbers?
It can, briefly. The refunded tickets drop out and the new ones come in, so the net count is correct once both are done. Reports run in between can look off.
Should we just say “no partial refunds on packages”?
Plenty of organizations do, and it’s reasonable for discounted bundles. Just make the rule visible before purchase, and decide in advance when a manager can make an exception.
