A family buys four tickets online for a special evening event. One child gets sick, so three people come and the parent emails asking for one ticket back. That sounds like a two-minute job. In Altru it can turn into a much longer one. Refunding a whole order is simple; refunding part of one depends on how the order came in, what was on it, and whether the money and the record stay in agreement afterward.
This guide covers how to think about partial refunds for event registrations, daily sales, and web orders, where the usual problems are, and how to keep your revenue and your payment processor from drifting apart.
Two kinds of “partial”
Before anyone touches a record, figure out which of these the guest is actually asking for:
- Return part of the order. They bought four items and want one returned. The refund amount matches the price of specific line items.
- Refund part of the money. They keep everything but get some money back: a goodwill credit after a weather closure, a price match, a discount someone forgot to apply. The refund doesn’t map to any one item.
The first is usually easier, because there is a specific line item to return. The second is where staff end up improvising, because there’s no item to return.
Returning some items from an order
For in-person and advance sales, staff can usually choose which items on an order to return instead of returning the whole thing. If your desk team only ever uses the full-order return, it’s worth showing them the item-level option in a sandbox or training database first. A lot of “Altru can’t do partial refunds” complaints come from staff who have only seen one path.
Event registrations need more care. When you remove a registrant from an event, decide ahead of time whether that also refunds the fee or only frees up the seat. Those are separate decisions, and it’s easy to do one without the other. Afterward, check the registrant list and the revenue record so both show what you meant.
Web orders are where behavior varies most. Depending on your setup and how the order was processed, you may not be able to return individual items on a web-originated order the same way you can at the desk. If you aren’t sure what your database allows, try it on a test web order in a sandbox, or ask Blackbaud support how web orders are handled in your version. Don’t learn it on a live order with a guest waiting for an answer.
Refunding an amount, not an item
If there’s no item to return, you have a few options. None of them is perfect, so pick one and use it every time:
- Return the full item, then resell at the adjusted price. The record stays accurate line by line. It takes more clicks, and the guest may see two charges on their statement, so let them know.
- Issue a credit or gift certificate rather than cash back, if your policy allows it. Before you adopt this, confirm in a sandbox how your Altru setup records credits and how they show up in revenue reports, so finance knows where to look.
- Refund through the payment processor and record an adjustment in Altru. This is the one that gets organizations in trouble. If someone refunds in the merchant portal and nobody records it in Altru, your revenue reports and your deposits will stop matching, and finance finds out at month-end.
If your team does use option three, make it a firm rule: whoever refunds in the processor also records the matching entry in Altru the same day, with a note that references the original order.
Keep the money and the record matched
Most partial-refund pain shows up at reconciliation, not at the desk. A few habits help:
- Refund to the original payment method whenever possible. Cash-back on a card sale makes the drawer and the deposit harder to tie out.
- Know which batch the refund lands in. A refund processed weeks after the sale can hit a different deposit or batch than the original payment. Your finance contact should know to expect that.
- Write the reason on the record. “1 of 4 tickets refunded, child ill, approved by J.” saves the next person a phone call.
- Run a short weekly query of refunds and returns. Look for refunds with no matching return, or returns with no refund. Those are the records that will cause trouble at month-end.
Decide the policy before a guest asks
Seasonal and part-time staff shouldn’t have to decide on the spot whether a guest gets cash, credit, or nothing when they call about a refund. A one-page policy should answer:
- Who can approve a partial refund, and up to what amount.
- Whether event registrations are refundable at all, and up to how many days before the event.
- When you offer credit instead of cash back.
- Which refund method from the list above your team uses for amount-only refunds.
Put the same policy on your event pages and order confirmations. Guests ask for fewer exceptions when the rules were clear before they paid.
Quick answers
Can I refund just one ticket from an online order?
Often yes, but how you do it can be different for web orders than for desk sales. Try it on a test web order in a sandbox first. If it doesn’t work as you expect, Blackbaud support can confirm what your version supports.
Is it okay to just refund in the merchant portal?
Only if the same refund also gets recorded in Altru. Otherwise your revenue reports and your bank deposits will no longer agree.
What about refunding part of an event fee but keeping the registration?
Handle it as an amount-only refund. Use whichever method your policy names, and add a note to the registration so the event coordinator knows the guest is still coming.
