Add to cart configurable product from quickorder create hybrid items in checkout cart

[Nolwennig-Jeulin]

Preconditions and environment

• Magento 2.4.5-p10
• customer logged in or not
• cart empty or not
• have quickorder feature

Steps to reproduce

1. Go to product page
2. Add to cart product by click on addtocart btn
3. Go to checkout/cart page
4. Add to cart the same product with quickorder

Expected result

Add a product in cart from quickorder and cart show correctly configurable options informations

Actual result

Hi,

I find a curious behavior on Website and we should like have a way of explanation.

When add to cart a product from product page - the checkout /cart show additionnal informations from product => it's expected result and it's OK

When add product from quickorder (same product indeed) - the checkout/cart do not show additionnal informations about product => it's unexpected result

Products are separated like this because first item is added as part of configurable and second one is directly added as simple product (without linking to the parent).

So when you add configurable to the cart, it actually includes two products: parent and child according to selected configuration.

When you add a child directly, it's added as regular simple product, because child product itself doesn't contain information about its parent.

Here's the example of the same behavior on magento demo site:

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.
• 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 @Nolwennig-Jeulin. 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.

• 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-Bravo. 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

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

Hi @Nolwennig-Jeulin,

Thanks for your reporting and collaboration.

We have tried to reproduce the issue in Latest 2.4-develop instance and we are able to reproduce the issue.Kindly refer the screenshots.

Products are separated like this.Hence Confirming the issue.

Thanks.