Import. Simple becomes Out of Stock when it should be in stock because of backorder

[VladyslavSikailo]

Preconditions

1. Pure Magento 2.4.1
2. Magento 2.4-develop

Steps to reproduce

1. Create simple product (in stock, qty bellow 0)
2. Copy sku of this simple
3. Go to System->Import. Choose Entity Type: Product, Import behaviour: Add/Update
4. Create an csv with following content (replace simple2 by your own)
5. Select File to import -> select created csv file.
6. Import.

Expected result

1. Imported simple product has Stock Status: In Stock (because it has Backorders: Allow Qty Bellow 0 so it's buyable)

Actual result

1. Simple product has Stock Status: Out of Stock

---

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.
• [x] 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 @Dren7755. 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.

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

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

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

[duckchip]

Can be reproduced on 2.3.6

[duckchip]

I think this is caused by the following changes: https://github.com/magento/magento2/pull/20180 https://github.com/magento/magento2/pull/24053

[stale[bot]]

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!

[hostep]

Not stale, somebody on Slack complained about this issue one day ago. There's even a PR open for this: https://github.com/magento/magento2/pull/32366

@sidolov, @Den4ik, @gabrieldagama: can we have somebody verify this please? So that this stalebot monstrosity stops complaining.

[iphigenie]

Not stale, somebody on Slack complained about this issue one day ago. There's even a PR open for this: #32366

@sidolov, @Den4ik, @gabrieldagama: can we have somebody verify this please? So that this stalebot monstrosity stops complaining.

I've had confirmed issues closed on me so not sure it'd help

[m2-assistant[bot]]

Hi @Den4ik. 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.

[m2-assistant[bot]]

Hi @engcom-Dash. 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 Area: XXXXX label to the ticket, indicating the functional areas 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-Dash]

Hi @VladyslavSikailo

Thanks for reporting and collaboration.

Verified the issue on magneto 2.4 dev instance but the issue is not reproducible.

Steps to reproduce

1. Create simple product (in stock, qty bellow 0)
2. Copy sku of this simple
3. Go to System->Import. Choose Entity Type: Product, Import behaviour: Add/Update
4. Create an csv with following content (replace simple2 by your own)
5. image
6. Select File to import -> select created csv file.
7. Import.

Seeing Imported simple product as Stock Status: In Stock (because it has Backorders: Allow Qty Bellow 0 so it's buyable)

Please verify the attached screenshots.

[Den4ik]

@magento give me 2.4-develop instance

[magento-deployment-service[bot]]

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

[magento-deployment-service[bot]]

Hi @Den4ik, here is your Magento Instance: https://250d7ece94a364597ab455135e8f14a3.instances-prod.magento-community.engineering Admin access: https://250d7ece94a364597ab455135e8f14a3.instances-prod.magento-community.engineering/admin_5ac2 Login: 78b6f8b4 Password: 5f61fb33d934

[engcom-Dash]

Hi @VladyslavSikailo

As there is no activity on this issue for a long time, we believe the issue has been resolved, hence closing this issue. Feel free to raise a new issue or reopen this if you still face it.

Thank you.