Custom option (Required type) price is not included in product display price

[adarshkhatri]

I just noticed, by default required custom option's price is not added to product display price.

For example:
Product Price: $100 (config item's min price)
Custom Option 1: Required: $10

Product price displayed as $100 in the category as well as the view page.

Because Custom Option is required, the customer will need to pay min of $110 to buy this item.

But displaying only $100 is misleading.

Any suggestions on this?

Preconditions (*)

1. Magento 2.3.x & 2.3-develop
2. Config item (color: Black, Red)
3. Price $100
4. Custom option (required, Option 1: Price $10, Option 2: Price $20)
5. Assign this product to a category

Steps to reproduce (*)

1. Go to product associated category OR
2. Go to the product view page.

Expected result (*)

We need to display the price on the storefront in a different format, something similar like we are currently doing for configurable or bundle products.

Example:

1. "As low as $110" if there is only one available required option or "From $110 to $150" if there are a couple of options available. The calculation formula for these prices should be the following:

Final Min Price Formula: 
Min(Regular Price, Special Price) + Sum(Min price per each required custom option)

Final Max Price Formula:
Min(Regular Price, Special Price) + Sum(Max price per each required custom option)

Actual result (*)

1. Display price is $100

[m2-assistant]

Hi @adarshkhatri. 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 give me 2.3-develop instance - upcoming 2.3.x release

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

@adarshkhatri 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.

[adarshkhatri]

@magento give me 2.3-develop instance

[magento-engcom-team]

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

[magento-engcom-team]

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

[m2-assistant]

Hi @engcom-Charlie. 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).

  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 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. 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]

✅ Confirmed by @engcom-Charlie
Thank you for verifying the issue. Based on the provided information internal tickets MC-22162 were created

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