Price is always 0 for bundle product items without dynamic price in order rest API

[aaqtgft]

Preconditions and environment

• 2.4.6

Steps to reproduce

1. Create a bundle product with a dynamic pricing option
2. Create a bundle product without dynamic price option
3. Add both items to the cart
4. Complete the checkout process
5. Export the order using the REST API

When exporting an order containing a bundle product without the dynamic price option, the price of the single product is always exported as 0. The price of the single product is only exported correctly when the bundle product is created with a dynamic price.

Expected result

Simple products included in a bundle should always have the actual price in the order export. Those with dynamic price should have the original price, those without should have the price shown on the bundle page.

Actual result

The price of the single product included in a bundle without dynamic price is always exported as 0, while the price of the product included in a bundle with dynamic price is correct.

Additional information

No response

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.
• [X] Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
• [X] 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[bot]]

Hi @aaqtgft. 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. :warning: According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting. :clock10: You can find the schedule on the Magento Community Calendar page. :telephone_receiver: 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[bot]]

Hi @engcom-Delta. 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).
• [ ] 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.

[engcom-Delta]

@magento give me 2.4-develop instance

[magento-deployment-service[bot]]

Hi @engcom-Delta. Thank you for your request. I'm working on Magento instance for you.

[magento-deployment-service[bot]]

Hi @engcom-Delta, here is your Magento Instance: https://c9541caf779acc04de7439fa43c11cc2.instances-prod.magento-community.engineering Admin access: https://c9541caf779acc04de7439fa43c11cc2.instances-prod.magento-community.engineering/admin_f6ca Login: 410940b8 Password: edd5441a7332

[engcom-Delta]

@magento give me 2.4-develop instance

[magento-deployment-service[bot]]

Hi @engcom-Delta. Thank you for your request. I'm working on Magento instance for you.

[magento-deployment-service[bot]]

Hi @engcom-Delta, here is your Magento Instance: https://c9541caf779acc04de7439fa43c11cc2.instances-prod.magento-community.engineering Admin access: https://c9541caf779acc04de7439fa43c11cc2.instances-prod.magento-community.engineering/admin_2e0b Login: b9462d57 Password: 89f856b955e8

[engcom-Delta]

Hi @aaqtgft ,

Verified the issue on 2.4-develop and it is reproducible.

Hence, Confirming the issue.

Steps to reproduce:-

1.Create a bundle product with a dynamic pricing option 2.Create a bundle product without dynamic price option 3.Add both items to the cart 4.Complete the checkout process 5.Export the order using the REST API

Bundle product with dynamic price

Bundle product without dynamic price

added both products to cart

Placed order

Bundle product without the dynamic price option, the price of the single product is exported as 0.

Bundle product is created with a dynamic price

[github-jira-sync-bot]

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

[m2-assistant[bot]]

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