We value your unique insight into our products and services and often receive ideas and feedback from our community in a variety of ways. To streamline this process, we’ve created an idea bank where you can post product suggestions, vote for those most important to you, and add comments to existing ideas.
Altru's discount controls would be greatly improved by a "global limit" feature - the ability to restrict the total number of times a discount may be applied overall (across all orders) before automatically deactivating.
Users can currently restrict the number of times a discount may be applied per order. While this is quite handy for the Daily Sales interface, it leaves a lot to be desired with regards to Online Sales: a purchaser can easily get around any per-order limits just by creating multiple orders.
The ability to globally limit a discount's usage should be an available feature for automatic-discounts and Promo-code discounts alike. It's a common strategy to market a promotion as available only to the first however-many purchasers or guests, but once an auto-discount is activated in Altru (or once a promo code's been released to the public) Altru-clients currently do not have an adequate means of enforcing a usage limit. The workaround solutions we've seen and/or tried have been clunky and far from ideal, and I've outlined two of those methods (and their shortcomings) for reference below if needed.
Assign some poor soul the task of constantly running and rerunning the Discount Performance Report, keeping an eye on the discount's usage numbers until your intended limit has been reached. If lucky, your "limited discount" can be manually deactivated at exactly the desired number of uses, but there's a strong chance that this might occur outside of regular business hours, or that the last eligible transaction might include more tickets than are able to receive the discount. Both of these introduce a hazard of going over-budget. The person monitoring the discount's performance will also have less time and attention to dedicate towards their usual tasks.
Temporarily reduce a scheduled program event's capacity before tickets go live for Online Sales, so that the discount may apply toward any/all tickets sold out of in that initial pool. Unfortunately, if the tickets "sell out" at any point outside of your operating hours, you risk losing sales. This route of enforcement can also lead to the same trap business hours, as an artificially-limited capacity may lead larger parties to skip out on purchasing altogether. People want things to work out on their schedule: if they're unable to reserve tickets for all of their guests when they first reach your webpage, they may not bother to return after the cap is raised, even if you decide to implement a quantity-based discount later!
Altru clients have been requesting the option to implement an overall-use limit on discounts for nearly a decade. I've included a (non-exhaustive) list of threads requesting this same feature below, in hopes that they might all be merged together.
Additional threads requesting this feature:
https://altru.ideas.aha.io/ideas/ALTRU-I-440 (created January 2016)
https://altru.ideas.aha.io/ideas/ALTRU-I-1411 (created October 2016).
Of the threads I found asking to limit the overall number of times a discount could be used, I-1411 is the only one to have received a dev/moderator tag. Unfortunately, there's nothing to indicate when the "Reviewed" tag was added, nor what it might imply for similar threads created in the 9 years since I-1411 was posted. Any demystification on this front is absolutely welcome.
https://altru.ideas.aha.io/ideas/ALTRU-I-2025 (created November 2019)
https://altru.ideas.aha.io/ideas/ALTRU-I-2150 (October 2020)
https://altru.ideas.aha.io/ideas/ALTRU-I-2162 (November 2020)
*edited to update thread list
| Customer references | Marketing teams from multiple institutions (see main post for inactive related threads) |