[ 
https://issues.apache.org/jira/browse/OFBIZ-228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jacopo Cappellato closed OFBIZ-228.
-----------------------------------

    Resolution: Won't Fix

> Chained promotions
> ------------------
>
>                 Key: OFBIZ-228
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-228
>             Project: OFBiz
>          Issue Type: Wish
>          Components: product
>            Reporter: Jacopo Cappellato
>            Priority: Minor
>
> It would be nice to add support for chained promotions, i.e. promotions 
> applied one after the other to the result of the preceding promotion.
> For example:
> promo1 = 20% discount
> promo2 = 10% discount
> If I create an order item with amount = 500
> I'd like to have promo1 applied to it:
> 20% of 500 = 100
> So 500 - 100 = 400
> And then promo2 applied to the result:
> 10% of 400 = 40
> Total discount: 100 + 40
> This is taken from a message by David Jones to the user list about this 
> subject.
> **********************************************************
> If I remember right the promotions calculations are all handled 
> independently, in other words all percentages are based on the items 
> sub-total and don't compound. This was done because there is no facility to 
> specify in which order the promotions are applied, and if compounded like 
> this the order makes a big difference.
> It does get a bit complicated and a lot more options could be introduced to 
> the promotions stuff to make them even MORE complicated, like an explicit 
> application order (be careful there though... if they aren't applied in the 
> order that maximizes value to the customer, sometimes they get a little bit 
> ticked off... so for the most part the promo stuff is coded to be the most 
> generous to the customer), or another feature that could be added is to 
> specify for each percentage whether it includes various other promotions or 
> not (this could lead to quite complicated promotion interaction settings...). 



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to