Submitting Credit Memo reduces Quantity of inventory products

[blockedie]

Preconditions and environment

• Magento ver. 2.4.2-p2
• Anything else that would help a developer reproduce the bug

Steps to reproduce

1. Configure an inventories product that has a specific stock quantity and salable quantity. Make sure it is greater than or equal to two for the purpose of recreating this bug.
2. Create an order with one of these products and submit it. Note that the salable quantity and the quantity should be reduced by 1
3. From that order, create a credit memo and fully refund the inventoried product.
4. View the quantity of the product and note that is has been reduced by one where I would expect it to actually increase it by one.

Expected result

I would expect submitting credit memo to either have no change to the quantity of an inventoried product or to increase the quantity by the number of products refunded.

Actual result

Quantity of inventoried product decreases after a refund for the product is submitted and processed. For example it looks like the following example: Pre-purchase: Salable quantity=6, Quantity=6 Post-Purchase: Salable quantity=5, Quantity=5 Post-Credit Memo: Salable quantity=4, Quantity=4. As you can see, the quantity was reduced by 1 even though nothing has been purchased.

Additional information

Info on inventory reservations: https://devdocs.magento.com/guides/v2.3/inventory/reservations.html

Release note

Prior to a fix, an end user would see that the quantity of an inventoried product is reduced by the number of items refunded in a credit memo. Now (assumedly after fix) the quantity of an inventoried product will be unchanged after a credit memo refunding the item is placed.

Triage and priority

• [ ] Severity: S0 - Affects critical data or functionality and leaves users without workaround.
• [X] 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[bot]]

Hi @blockedie. Thank you for your report. To speed up processing of this issue, make sure that you provided the following information:

• Summary of the issue
• Information on your environment
• Steps to reproduce
• Expected and actual results

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.

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

[m2-assistant[bot]]

Hi @engcom-November. 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).

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

Hi @blockedie , Thank you for reporting and collaboration. Verified the issue on Magento 2.4-develop branch but could not reproduce the issue. Both qty and salable qty of the inventoried product are same before and after creating the credit memo.

Kindly check the issue on Magento 2.4-develop instance as it is the upcoming 2.4.x release and provide missing steps if any if the issue is still reproducible. Thank you.

[engcom-November]

Hi @blockedie , We are closing this issue as there has been no latest update on the same. Kindly reopen / create new issue if you are still facing any issues. Thank you.