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!