Catalog pricerules are not working with custom options as expected in Magento 2.3.0 product details page

[dcwnaveen]

Catalog price rules are not working with custom options as expected in Magento 2.3.0 product details page. We created the catalog price-rule 10% discount for some x products and expecting the results like a 10% discount on total price( (product price + options price) * 10%). But results are showing discounted price + custom options price.

Preconditions Magento 2.4-develop PHP 7.3

Steps to reproduce

1. Go to Admin->Marketing->Catalog Price Rule->Add New Rule;
2. Fill all required fields and set Discount Amount to 10 % for ex.; ;
3. Click on Save and Apply button;
4. Create simple product (Price = 1000 $) with a drop-down custom option (Size for example); Options for Size:

• Small price is 100$,
• Medium price is 200$,
• Large price is 500$.

5. Go to Storefront;
6. Open created before product;

Expected Result

We are expecting the 10% discount on the total price (product price + options price) * 10%). For:

• Small - 990$,
• Medium - 1080$,
• Large - 1350$

Actual result

Its showings final prices like:

• Small - 1,000$,
• Medium - 1,100$,
• Large - 1,400$

[m2-assistant[bot]]

Hi @dcwnaveen. Thank you for your report. To help us process this issue please make sure that you provided the following information:

• [ ] Summary of the issue
• [ ] Information on your environment
• [ ] Steps to reproduce
• [ ] Expected and actual results

Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:

@magento-engcom-team give me 2.3-develop instance - upcoming 2.3.x release

For more details, please, review the Magento Contributor Assistant documentation.

@dcwnaveen do you confirm that you were able to reproduce the issue on vanilla Magento instance following steps to reproduce?

• [ ] yes
• [ ] no

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

[m2-assistant[bot]]

Hi @AlexWorking. 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: :point_down:

• [ ] 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).

  Details

  If the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

• [ ] 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

• [ ] 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• [ ] 4. Verify that the issue is reproducible on 2.3-develop branch

  Details

  - Add the comment @magento-engcom-team give me 2.3-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.3-develop branch, please, add the label Reproduced on 2.3.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. Verify that the issue is reproducible on 2.2-develop branch.

  Details

  - Add the comment @magento-engcom-team give me 2.2-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.2-develop branch, please add the label Reproduced on 2.2.x

• [ ] 6. Add label Issue: Confirmed once verification is complete.

• [ ] 7. Make sure that automatic system confirms that report has been added to the backlog.

[dcwnaveen]

@magento-engcom-team give me 2.3-develop instance So I will create the product and catalog price rule.

[magento-engcom-team]

Hi @dcwnaveen. Thank you for your request. I'm working on Magento 2.3-develop instance for you

[magento-engcom-team]

Hi @dcwnaveen, here is your Magento instance. Admin access: https://i-22856-2-3-develop.instances.magento-community.engineering/admin Login: admin Password: 123123q Instance will be terminated in up to 3 hours.

[dcwnaveen]

@magento-engcom-team I have created one product with custom options and created the catalog price rule. please reindex and run the cron job for a discounted price. https://i-22856-2-3-develop.instances.magento-community.engineering/product-a.html

[dcwnaveen]

Hi @AlexWorking. Please check the issue and confirm. https://i-22856-2-3-develop.instances.magento-community.engineering/product-a.html

[magento-engcom-team]

:white_check_mark: Confirmed by @AlexWorking Thank you for verifying the issue. Based on the provided information internal tickets MAGETWO-99657, MAGETWO-99658 were created

Issue Available: @AlexWorking, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.

[m2-assistant[bot]]

Hi @p-bystritsky. Thank you for working on this issue. Looks like this issue is already verified and confirmed. But if you want to validate it one more time, please, go though the following instruction:

• [ ] 1. Add/Edit Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• [ ] 2. Verify that the issue is reproducible on 2.3-develop branch

  Details

  - Add the comment @magento-engcom-team give me 2.3-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.3-develop branch, please, add the label Reproduced on 2.3.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!

• [ ] 3. Verify that the issue is reproducible on 2.2-develop branch.

  Details

  - Add the comment @magento-engcom-team give me 2.2-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.2-develop branch, please add the label Reproduced on 2.2.x

• [ ] 4. If the issue is not relevant or is not reproducible any more, feel free to close it.

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

[VladimirZaets]

Hi @dcwnaveen. Thank you for your report. The issue has been fixed in magento/magento2#22917 by @p-bystritsky in 2.4-develop branch Related commit(s):

• a8f3b9e8931d69a4bfa3af51483ed89b16292eea
• 4fb5da819cb2517de204e7dcf8c545505eeabd2c
• 56142aea26c20689ef2f36495c48b58d5417efcb
• 74892074f9bbed128a4c0c2e7c14a8f47d317755
• 20ae9e3f3c9b89afe9a7439728cb05f20c09080d
• 8b159d0e6e2d7d2034a2960cd484fe33a50ed2b3
• 4ac980bbb6783472f24295ac835723412de8680f
• fbea751258747182da71d1175e466405c80b01ab

The fix will be available with the upcoming 2.4.0 release.

[engcom-Alfa]

After multiple discussion and several attempts to fix consequences was decided to revert this PR #22917

Purpose for revert During internal regression testing for future 2.4.0 release Core team found two regression bugs

1. [MC-34245] Adding a Product with Customizable Option to Wish List results in a fatal error
2. [MC-34322] Adding a Product with Customizable Option to a "Gift Registry" results in a fatal error when loading shared Gift Registry page

Root cause analysis defined that changes from #22917 brought these regression bugs.

So, we will reopen and confirm this issue again.

[m2-assistant[bot]]

Hi @engcom-Alfa. 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: :point_down:

• [ ] 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).

  Details

  If the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

• [ ] 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

• [ ] 3. Add Component: XXXXX label(s) to the ticket, indicating the components 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.

[magento-engcom-team]

:white_check_mark: Confirmed by @engcom-Alfa Thank you for verifying the issue. Based on the provided information internal tickets MC-35065 were created

Issue Available: @engcom-Alfa, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.

[AbdulRahmanAbouzaid]

@magento give me 2.4-develop instance

[magento-engcom-team]

Hi @AbdulRahmanAbouzaid. Thank you for your request. I'm working on Magento 2.4-develop instance for you

[AbdulRahmanAbouzaid]

@magento-engcom-team give me 2.4-develop instance

[magento-engcom-team]

Hi @AbdulRahmanAbouzaid. Thank you for your request. I'm working on Magento 2.4-develop instance for you

[sdzhepa]

The issue has been fixed by Magento team and delivered with internal PR Related commits https://github.com/magento/magento2/search?q=MC-35065&type=commits

[ashar01]

@sdzhepa @magento-engcom-team @VladimirZaets This ticket says the issue is fixed but i am bit confused after reading this https://experienceleague.adobe.com/docs/commerce-knowledge-base/kb/support-tools/patches/v1-1-23/acsd-47107-catalog-price-rule-is-applied-to-custom-options.html?lang=en This document says magento reverts this fix in m2.4.6 release.

[sprankhub]

@sdzhepa @magento-engcom-team, could you please check the last comment?

[engcom-Dash]

Hi @dcwnaveen

Thank you for reporting and collaboration.

Verified the issue in Magento 2.4.7-beta2 and 2.4 dev instances and the issue is reproducible in both the instances.

Catalog price rules are not working with custom options.

Please refer the attached screenshots.

[github-jira-sync-bot]

Unfortunately, not enough information was provided to create a Jira ticket. Please make sure you added the following label(s): Reproduced on 2.4.x, ^Area:.*

Once all required labels are present, please add Issue: Confirmed label again.

[github-jira-sync-bot]

Unfortunately, not enough information was provided to create a Jira ticket. Please make sure you added the following label(s): Reproduced on 2.4.x, ^Area:.*

Once all required labels are present, please add Issue: Confirmed label again.

[github-jira-sync-bot]

:white_check_mark: Jira issue https://jira.corp.adobe.com/browse/AC-10902 is successfully created for this GitHub issue.

[m2-assistant[bot]]

:white_check_mark: Confirmed by @engcom-Bravo. Thank you for verifying the issue.
Issue Available: @engcom-Bravo, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.