Hi Filip & Everyone,
I also just searched at least 4 items that were left unanswered regarding this topic, and when I then found FilipsI immediately voted it up.
Please vote it up HERE!!!! :) Interestingly, it seems that the benefit would be huge to the community relative to the amount of time that I would anticipate it taking. Like you, I know that the NopDevTeam has their hands full and have been doing an absolutely outstanding job.
As I see it, an additional Boolean field for "use Percentage" (just like discounts do now) would be required where any price adjustment opportunity presents itself (e.g. product attributes price adjustment) and then the logic would just have to be change, probably an additional line of logic wherever the price adjustments are currently made in the code that challenges the status of the "percentage" Boolean and computes accordingly. Basically an if/then/else on the former. Lastly, you would have to run an update query on the DB to set all existing (actually new) Booleans to 'false' so that current pricing schemas would not be impacted. The 'order' concerns would be addressed in the additional logic statements but I would think should fall in place relatively smoothly.
I guess that I've been in the development business long enough to be very careful when I say things like "should only take a couple of hours" but that's what my gut tells me. Have you done anything on this yourself or has anyone else? I would be interested in collaborating on this to get it done, if anyone is interested. Also
Please reply if anyone has addressed this or feel free to PM me.
Thanks in advance for any input,
-HB