Catalog Price Rules not applying to Custom Options

[NetStorm84]

Preconditions and environment

Tested on version 2.4.6

Steps to reproduce

1. Create a product
2. Add some custom options
   
3. Save the product
4. Navigate to Catalog Price Rules - Marketing > Catalog Price Rules
5. Add new rule, making sure to set it to active with an action of 10% discount - apply as percentage of the original
6. Save and apply the new rule
7. Visit the product in the front end

Expected result

I would expect the 10% discount to be applied to the overall price, including the product option price

For example.

Product Price: $30.60
Option Price (Red) + $10

Total Price = $36.54

Actual result

The discount is being applied the product price and the custom option price is being added on top without being discounted

For example.

Product Price: $30.60
Option Price (Red) + $10

Total Price = $40.60

Additional information

It seems it used to work this way, ignoring the custom options but was then fixed in #22917 and worked as I would expect for a few versions, then it seems to have been removed again (a1aa4af) and works as I would not expect.

Surely, the best thing to have done was to have created a toggle in the options so that the store owner can decide how this should work, as now I have updated my store my discounts don't work as they have been previously.

In my mind the discount should apply to the custom options as this makes up the final price of the product, I don;t understand why these would not be included in the calculation.

Release note

No response

Triage and priority

• Severity: S0 - Affects critical data or functionality and leaves users without workaround.
• Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
• Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
• Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
• Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.

[m2-assistant]

Hi @NetStorm84. Thank you for your report.
To speed up processing of this issue, make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, Add a comment to the issue:

• @magento give me 2.4-develop instance - upcoming 2.4.x release
• For more details, review the Magento Contributor Assistant documentation.
• Add a comment to assign the issue: @magento I am working on this
• To learn more about issue processing workflow, refer to the Code Contributions.

---

Join Magento Community Engineering Slack and ask your questions in #github channel.
⚠️ According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.
🕙 You can find the schedule on the Magento Community Calendar page.
📞 The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket.

[m2-assistant]

Hi @engcom-November. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).
• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
• 3. Add Area: XXXXX label to the ticket, indicating the functional areas it may be related to.
• 4. Verify that the issue is reproducible on 2.4-develop branch
  Details

  - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!
• 5. Add label Issue: Confirmed once verification is complete.
• 6. Make sure that automatic system confirms that report has been added to the backlog.

[NetStorm84]

@abukatar Was there any discussion on why the catalog price rules should not apply to custom options? I am unable to find the reasoning for it.

[abukatar]

Hi @NetStorm84, it was discussed with and approved by the product owner.

[NetStorm84]

Hi @abukatar thanks so much for getting back to me.

Was it removed because there is an alternative method we should be using to discount custom options? If not then I am going to create a PR and put the code back in with a config option to give the store owner a choice as to whether or not the catalog price rules can discount custom options.

As stated previously this is a fundamental part of our website, we use custom options on all our products and have different prices for each option. For example, a list of different sizes. We then run a site wide discount of different amounts throughout the year.

[NetStorm84]

@magento I am working on this

[engcom-November]

Hello @NetStorm84,

Thank you for the report and collaboration!

We are awaiting for PO confirmation, before proceeding with the issue.
Hence putting this on hold.

Thank you.

[engcom-November]

Hello @NetStorm84,

As discussed with the PO, we've concluded that this change contradicts the essence of fixed-price custom options. Fixed-price custom options are designed in a way that they should never be affected by a Group Price, Tier Price, Special Price, or Catalog Price rules.
While we understand that adding a toggle will preserve the initial behavior, we've determined that there isn't enough scope to implement this feature.

Hence closing this issue.
Thank you.