Potential promotions - are there best practices?

[Former Member]

Hi experts,

I am researching the use of Potential Promotions in 6.*.

As we know, as of 6.*, the "could have fired" messages are not supported and can be modelled by using Potential Promotions. Apart from the flexibility that the Rule Engine gives in this respect, i am facing some challenges with the Potential Promotions, such as:

• for each promotion, i need to create 2 promotion rules - one for the actual promo, and one for the "could-have-fired" effect

• more promotion rules means more maintenance, manual work and performance hits

• with Potential Promotions it is difficult to cover all the cases where ‘could have fired’ message need to be displayed

• one must be very careful when having stackability of promotions and their corresponding potential promotions, as the complexity of combining promotions raises.
  

• where (i.e in which pages) are the Potential Promotions displayed on the front-end and how?

• can you create 2 or more Potential Promotions for one actual promotion?

Hence, i am wondering what your experience is with the Potential Promotions and your advice for best practices. Please share your opinions, tips and suggestions how to make best use of the Potential Promotions.

Thank you, Atanas

[Former Member · Accepted solution]

Atanas, here is my feedback:

 what do you think of all the manual maintenance that needs to happen for each promotion that requires "could-have-fired-messages"? How much work that is in a large scale - let
 us say with 100s of promotions per season?

Keep in mind there are import abilities for promotion rules to assist with a large number of promotions: https://help.hybris.com/6.6.0/hcd/cdaa0f3fb13e41e3b6c382bcd6d88b15.html

Cloning an existing promotion can also make creating a similar one more efficient: https://help.hybris.com/6.6.0/hcd/e79991d3f5394c0aa137acba9ae8ce93.html

 what guidelines do you have for the stackability?

Stackability information can be found here: https://help.hybris.com/6.6.0/hcd/b4f464062c6240cdb8e9bd7927ea4f1e.html

 have you measured performance when having 2 promotions for each actual
 promotion?

• have not done this, perhaps another expert or SI on this site may have first-hand knowledge. You could test this by writing multiple promotions against a product to see for yourself...I don't believe there is a known performance hit...however, I would caution/question against writing too many competing promotions against a specific product.*

  can you create 2 or more Potential Promotions for one actual promotion?

There is a 1:1 relationship. The Potential Promotion Rule must be linked to an existing Promotion Rule.

 have you encountered cases where you cannot cover "could have fired messages" with Potential promotions?

• have not, but another expert or SI on this site may have first-hand knowledge of this. You can test this by writing multiple promotions against a single product. I am not aware of any known performance hits, but I would, as a matter of promotion mangement, discourage too many competing promotions aimed at a single product.*

[Former Member · Accepted solution]

Thank you, .

[former_member614150]

Hi Atanas,

Are we facing any issues while using OOB potential promotions. The cases that you have mentioned above should work without any issues.

Thanks

[Former Member]

Hi Ravi,

I was listing challenges that i face and asking for a guidance or "best practices" tips.

For example:

• what do you think of all the manual maintenance that needs to happen for each promotion that requires "could-have-fired-messages"? How much work that is in a large scale - let
  us say with 100s of promotions per season?

• what guidelines do you have for the stackability?

• have you measured performance when having 2 promotions for each actual
  promotion?

[Former Member]

• can you create 2 or more Potential Promotions for one actual promotion?

• have you encountered cases where you cannot cover "could have fired messages" with Potential promotions?

All help is appreciated.

Atanas