Different Perfect partner product promotion with one common product in target container consuming same entry.

[Former Member]

HI,

When we are trying to create two different perfect partner percentage discount promotion which has one common product in target containers in both of the promotion and both promotion can be applied together. In this scenario if that common target product and different products from qualifying containers are added to cart than both promotions are getting fired using same entry. Which is misleading and if we try to add some other product from target container still common one gets consumed. Since its cheaper.

Ex- Promotion 1: Qualifying prod: A,B Target Prod: C

Promotion B: Qualifying prod: X,Y,Z, Target Prod: C,D,E

And product C is cheapest among all target products.

So if A,C,Z are added both promotions getting fired with C as free product. Even if we add D or E still C gets consumed.

Expected is C will ink to A and D will link to Z. If there is only C then highest promotion only should get triggered. SInce C is already consumed.

[Former Member]

Hi Abishek,

I reproduced your scenario in OOTB 6.7 B2B. I was also able to get your expected behaviour. Simple fix is to make your Promotion 1's priority higher than that of your promotion 2.

Best regards,

[Former Member]

HI Bartosz,

Thanks for trying it out this issue i am facing in 6.2 as i have mentioned in tag. If i am not wrong in 6.7 order entry consumed approach has been re-introduced. Is there any solution without migrating it?

[Former Member]

Hi Abhishek,

I reproduced it on 6.2 and both promotions are getting applied on C after adding Z to cart. However after adding D to cart the promotion 2 is getting applied to it and not to C. Both of my promotions have the same priority and promotion 2 has Stackable set to true.

If you want I can share with you the exact promotions I created.

Best regards,

[Former Member]

HI Bartosz,

Thanks again for trying it out and yes if only is added both gets applied which is misleading any solution for this? And for second scenario it depends on priority its getting executed because for me also it failed in some permutations and works in some specific combination,