Create Order in the admin panel: wrong price is displayed for Configurable Products with Customizable Options

[bgorski]

Preconditions (*)

1. Magento 2.3.3 (2.3.2 is affected as well, not tested on any other version)

Steps to reproduce (*)

1. Create a configurable product with a Customizable (customizable, not configurable!) Option added to the parent product. The option should have at least one value that increases price of the product
2. Go to the Create Order page in the admin panel. Select/create a customer and proceed to the page where you add all the information (products, addresses etc.)
3. Click Add Products to see a grid of products. Your product should be on it (use filters if necessary)
4. You should see no price associated with the product on the products grid (this is the expected behavior as it's not configured yet)
5. Click Configure
6. Select the child product and the custom option's value that increases the price of the product.
7. Click OK to go back to the main view
8. Notice that the product's price displayed on the grid is now available

Expected result (*)

1. The price should be a sum of the child product's price and the custom option's price (for example if the product costs $200 and there's additional $20 for the custom option, it should show $220)

Actual result (*)

1. The displayed price is only the custom option's price. The actual product price is not included (for example if the product costs $200 and there's additional $20 for the custom option, only $20 is actually displayed)

Additional information

1. This is broken only for configurable products that have Customizable Options.
2. Configurable Products without Customizable Options display their price correctly after a child product is chosen in Configure
3. Simple/Virtual Products with a Customizable Option also correctly add its price to the product price
4. Even if a wrong price is displayed before adding a product to order, when it gets added (the Add Selected Product(s) to Order button is clicked), product price gets computed correctly
5. Not tested on product types other than simple/virtual and configurable

Attaching a few screenshots to make it clearer what this is about:
https://i.ibb.co/sjvwW4R/Price0.png - before a product gets configured
https://i.ibb.co/1GwP2RQ/Price1.png - during configuration
https://i.ibb.co/Y3b3Zrx/Price2.png - after it's configured, with a wrong price shown

[m2-assistant]

Hi @bgorski. 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.

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

[bgorski]

@magento give me 2.3-develop instance

[magento-engcom-team]

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

[magento-engcom-team]

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

[bgorski]

Tested on the development instance provided above and I can confirm that the issue is still there.

[m2-assistant]

Hi @krishprakash. 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 @krishprakash
Thank you for verifying the issue. Based on the provided information internal tickets MC-29882 were created

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