It would be nice if Nitrosell can make the coupon section a little more robust then it is right now. NItrosell has already enhanced the coupon section a while ago but in order to keep to cutting edge there are still some features that would be very beneficial.
Allow in one coupon code a mix between percent off and free shipping
Allow multiple coupon codes at the checkout page
When creating a coupon, to be able to indicate if this coupon can be used with another coupon or not.
Set the coupon to start at a specific date and time. Currently the coupons can be set to a date (which it uses the server date and not the local date from the webstore) but not a time. It would be very helpful to use the date and time of where the store is located just like you have for the banners.
In general, I have to say that multiple coupon support is very uncommon on the web in general. I haven’t personally seen any web sites that do that. Multiple actions per coupon is also quite unusual. Do you have some example sites doing that?
We have always avoided multiple coupons for that reason.
The time-based expiries isn’t a big deal, and we can add that as a suggestion.
The only reason I would ever want multiple coupons would be when the store wants to give a coupon code for a discount off the shopping cart and also use a coupon code for free shipping. Both of these coupons would be active on the same cart and should be allowed.
That is the only time I have seen this and I personally used this when shopping on a few sites. There wouldn’t necessarily have to be multiple boxes to add multiple coupon codes, the way the other sites that I have used it on work, you enter the first coupon code, hit apply coupon and if the coupon is valid it adds it to the cart, now you can enter a second coupon code and if it does not conflict with the first one, it will add this second one as well.
Just to give you 1 site off the top of my head where I used this all the time, ctshirts.com
We get a lot of feature requests—every retailer prioritises features differently, and with 500+ customers, there is surprisingly little in common between requests, even when one user presumes a feature is “obvious” or a “glaring omission” (we get this a lot ).
Honestly, a feature request is basically a suggestion to us. We really cannot commit to a timeframe like 6 months when there are plenty of other customers willing to pay for features, and paid features will always be prioritised over suggestions.
So we can add the suggestion, but that doesn’t mean we’re planning to implement it any time soon; it doesn’t even mean we’re planning to implement it at all, I’m afraid. Suggestions are prioritised based on demand, from a combination of prospects and existing customers, as well as strategic considerations.
Unfortunately, everything takes dev time, including adding new sections to our web site. With a 5-person dev team, two web platforms with five different versions, multiple desktop apps with 8 different editions of each, our own web site, etc., and millions of lines of code between them, there is only so much we can get done…
It’s always better as a Feature request then a quote request 
).