API add to cart with simple product but different options increases qty instead of adding new cart item

[DavidLambauer]

We're trying to add the same simple product into the cart, but with custom options through the api. The expected result would be to have 2 items in the cart with different custom options. Actual result is the first item is in cart with qty of 2.

Preconditions

Magento Version 2.4.2

Steps to reproduce

You might want to check the video attached below

Capto_Capture.2021-02-26_01-44-29_PM.mp4

.

1. Create a cart via rest call: POST | {{ base_url }}guest-carts
2. Receive the cart to make sure no items are in the cart: GET | {{ base_url }}guest-carts/cartId
3. Add a simple product with custom options to the cart: POST | {{ base_url }}guest-carts/cartId/items

Example Payload:

{
  "cartItem": {
    "sku": "THE-SKU-OF-YOUR-SIMPLE-PRODUCT",
    "qty": 1,
    "product_option": {
      "extension_attributes": {
        "custom_options": [
          {
            "option_id": "1",
            "option_value": "abc"
          },
          {
            "option_id": "2",
            "option_value": "abc"
          }
        ]
      }
    },
    "quoteId": "YOUR-QUOTE-ID"
  }
}

4. (optional) Re-do step 2 to validate that the product was added to the cart.
5. Re-do step 3 but change the custom option values in the payload.
6. Re-do step 2 to again to see that two different products got merged into one but the qty was increased.

Expected result (*)

Actual result (*)

The cart should contain two items, each one with the custom options that were selected.

---

Please provide Severity assessment for the Issue as Reporter. This information will help during Confirmation and Issue triage processes.

• 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 @DavidLambauer. 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.4-develop instance - upcoming 2.4.x release

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

Please, add a comment to assign the issue: @magento I am working on this

---

• 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, please join the Community Contributions Triage session to discuss the appropriate ticket.

🎥 You can find the recording of the previous Community Contributions Triage on the Magento Youtube Channel

✏️ Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel

[simonmaass]

@magento give me 2.4-develop instance

[magento-deployment-service]

Hi @simonmaass. Thank you for your request. I'm working on Magento instance for you.

[magento-deployment-service]

Hi @simonmaass, here is your Magento Instance: https://3602337306b255225a946d85e1af32b3-2-4-develop.instances.magento-community.engineering
Admin access: https://3602337306b255225a946d85e1af32b3-2-4-develop.instances.magento-community.engineering/admin_9eab
Login: e4040df7
Password: 7d4a2860588b

[simonmaass]

@magento I am working on this

[m2-assistant]

Hi @simonmaass! 👋
Thank you for collaboration. Only members of Community Contributors Team are allowed to be assigned to the issue. Please use @magento add to contributors team command to join Contributors team.

[simonmaass]

@magento add to contributors team

[m2-assistant]

Hi @simonmaass! 👋
Thank you for joining. Please accept team invitation 👉 here 👈 and add your comment one more time.

[simonmaass]

@magento I am working on this

[simonmaass]

can confirm issue

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed after 14 days if no further activity occurs. Is this issue still relevant? If so, what is blocking it? Is there anything you can do to help move it forward? Thank you for your contributions!

[simonmaass]

this is not fixed and should not be stale!

[m2-assistant]

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: 👇

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

[engcom-Alfa]

Hi , Tried on Magento 2.4 Develop , issue is replicable , Hence request to look into it.

[magento-engcom-team]

✅ Confirmed by @engcom-Alfa
Thank you for verifying the issue. Based on the provided information internal tickets MC-42474 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.

[m2-assistant]

Hi @gabrieldagama. 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.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!
• 3. 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.

[m2-assistant]

Hi @engcom-Hotel. 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.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!
• 3. 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.

[engcom-Hotel]

Hi @DavidLambauer,

We have tried to reproduce this issue in 2.4-develop branch, but this is not reproducible. May be this issue has been fixed in this branch.

So we request you to please try to reproduce this in 2.4-develop branch and let us know, if you are able to reproduce this issue in this branch.

Thanks

[DavidLambauer]

Well, maybe we wait two more weeks if the next person confirms the issue again? A couple of people mentioned that this is still valid and has not been fixed yet. I can't provide even more information. I think the description and how you reproduce this issue is pretty clear.

[emanuelcorrea]

@magento I am working on this

[m2-assistant]

Hi @emanuelcorrea! 👋
Thank you for collaboration. Only members of Community Contributors Team are allowed to be assigned to the issue. Please use @magento add to contributors team command to join Contributors team.

[emanuelcorrea]

@magento add to contributors team

[m2-assistant]

Hi @emanuelcorrea! 👋
Thank you for joining. Please accept team invitation 👉 here 👈 and add your comment one more time.