A visitor brings a mug to the gift shop counter along with three postcards and a plush animal. The mug has a chip in the glaze, and your shop manager has told staff to take 25% off anything damaged. The cashier wants to discount the mug and nothing else. In Altru, that simple request can turn into a puzzle, because merchandise discounts don’t always land where you expect them to.
This article covers why discounting a single line in a merchandise order is awkward, how to check what your own Altru setup will actually do, and the workarounds shop teams use when the built-in options don’t fit.
Why one-item discounts are harder than they sound
Altru’s discounts are built around rules. You define a discount, say what it applies to, and Altru decides which items in the order qualify. That works well for planned promotions: “10% off all books this weekend” or “member discount on all merchandise.” The rule does the thinking so the cashier doesn’t have to.
The trouble is that a rule doesn’t know which specific item the cashier is pointing at. If a discount applies to a category, a group of items, or the whole merchandise order, it can apply to every qualifying line in the cart, not just the chipped mug. Exactly how Altru picks the qualifying lines depends on how the discount is configured, and that’s where many shops get surprised.
We’re not going to claim Altru can or can’t do a true per-line manual discount in every configuration, because that varies with how your discounts and security roles are set up. The honest answer is: test it in your own environment before you train staff on it.
Test what your setup actually does
Spend twenty minutes on this before the next sale or damaged-goods situation. Use a sandbox if you have one; if not, run a test order and void it afterward, following your normal finance rules for test transactions.
- List your existing merchandise discounts. Note what each one is scoped to: a single item, a category or department, all merchandise, or the order total.
- Build a mixed cart. Add at least three different merchandise items, including two from the same category, so you can see whether a category-level discount spreads across both.
- Apply each discount and watch the line totals. Check whether the discount shows on one line, several lines, or as an order-level reduction.
- Look at the result in reporting. Run your usual merchandise sales report or a revenue query and confirm the discount shows up the way your finance team expects. A discount that looks right at the register but posts confusingly is still a problem.
If the results are unclear, ask Blackbaud support how item-level merchandise discounts behave in your version. Bring screenshots of the test cart so they can see exactly what happened.
Workarounds that hold up
Depending on what your test shows, one of these usually covers the gap.
Create a discount scoped to one item
If your discounts can be limited to a specific merchandise item rather than a category, set one up for items you discount often, such as a clearance book or last season’s T-shirt. It’s predictable and reports cleanly. It doesn’t help with one-off situations like a damaged mug, because you can’t build a discount for every item in the shop.
Ring the discounted item as its own order
For one-offs, the simplest fix is two transactions: the discounted item alone with the order-level discount applied, then everything else at full price. It costs the visitor a second card swipe, but the discount can’t spread to other items, and the audit trail is clear. Many shops keep this as the default instruction for damaged goods.
Add a “damaged” or “clearance” version of the item
Some shops create a separate merchandise item, or a variant if your setup uses them, at a reduced price for marked-down stock. The cashier rings up the clearance version instead of the regular one. This keeps inventory counts honest when you move damaged stock into its own bucket, and it needs no discount logic at all. The tradeoff is more items to maintain, so retire them once the stock is gone.
Use a price override, if your roles allow it
If your security setup lets certain staff change an item’s price in the order, a supervisor can adjust the one line directly. Check whether price changes are tracked the same way as discounts in your reports. Finance teams often prefer discounts because they show up as a distinct line of lost revenue, while an edited price can make it look like the item simply sold for less.
Write a short rule for the shop
Whatever you choose, put it in writing next to the register. Something like:
- Planned promotions: use the configured discount; it applies automatically to qualifying items.
- Damaged or one-off markdowns: ring the item as a separate order and apply the damaged-goods discount, or use the clearance item.
- Anything else: call a supervisor before changing a price.
Clear instructions matter more than the method. Most discount problems in reports trace back to three cashiers each solving the same situation a different way.
Quick answers
Why did my discount apply to every item in the cart?
The discount is probably scoped to a category or to all merchandise, so every qualifying line gets it. Narrow its scope, or ring the discounted item separately.
Is it better to discount or change the price?
Ask your finance team. Discounts usually make lost revenue easier to see in reports, which is why many organizations prefer them over manual price changes.
