Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Negative Salable quantity #38700

Closed
1 of 5 tasks
JJupi opened this issue May 7, 2024 · 8 comments
Closed
1 of 5 tasks

Negative Salable quantity #38700

JJupi opened this issue May 7, 2024 · 8 comments
Assignees
Labels
Issue: needs update Additional information is require, waiting for response Reported on 2.3.7-p3 Indicates original Magento version for the Issue report.

Comments

@JJupi
Copy link

JJupi commented May 7, 2024

Preconditions and environment

  • Magento version 2.3.7-p3
  • Negative salabale quantity makes it unpurchaseable by customers on the website. The stock and quantity is correct however the salable quantity is incorrect and messes with the availability of the products. Is there a way to adjust and fix the salabla quantity in magento?

Steps to reproduce

Unable to add products to the cart. = quantity unavailable

Expected result

Screenshot 2024-05-07 at 3 46 27 pm Quantity added and 12 units in stock therefore this should not generate any errors.

Actual result

Screenshot 2024-05-07 at 3 44 41 pm Screenshot 2024-05-07 at 3 44 20 pm

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”.
Copy link

m2-assistant bot commented May 7, 2024

Hi @JJupi. 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. To deploy vanilla Magento instance on our environment, Add a comment to the issue:


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.

Copy link

m2-assistant bot commented May 7, 2024

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- 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-Bravo engcom-Bravo added the Reported on 2.3.7-p3 Indicates original Magento version for the Issue report. label May 7, 2024
@engcom-Bravo
Copy link
Contributor

@magento give me 2.4-develop instance

Copy link

Hi @engcom-Bravo. Thank you for your request. I'm working on Magento instance for you.

Copy link

@JJupi
Copy link
Author

JJupi commented May 9, 2024

Hi @engcom-Bravo, here is your Magento Instance: https://3eb067a92136416c45ca1126c86ab48d.instances-prod.magento-community.engineering Admin access: https://3eb067a92136416c45ca1126c86ab48d.instances-prod.magento-community.engineering/admin_e9b2 Login: 5b982905 Password: d2035a4f680a

Thanks for this, but I'm still struggling with the salable quantity going into negative values and not allowing me to add products to the cart.
Screenshot 2024-05-09 at 4 42 46 pm
Screenshot 2024-05-09 at 4 42 25 pm

@engcom-Bravo
Copy link
Contributor

Hi @JJupi,

Thanks for your reporting and collaboration.

Kindly refer this https://magento.stackexchange.com/questions/366949/scable-qty-going-to-nagative-value regarding salable quantity and check any third party modules causing this issue.

Thanks.

@engcom-Bravo engcom-Bravo added the Issue: needs update Additional information is require, waiting for response label May 9, 2024
@m2-community-project m2-community-project bot moved this from Ready for Confirmation to Needs Update in Issue Confirmation and Triage Board May 9, 2024
@engcom-Bravo
Copy link
Contributor

Hi @JJupi,

We have noticed that this issue has not been updated since long time.
Hence we assume that this issue is fixed now, so we are closing it. Please feel to raise a fresh ticket or reopen this ticket if you need more assistance on this.

Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue: needs update Additional information is require, waiting for response Reported on 2.3.7-p3 Indicates original Magento version for the Issue report.
Projects
None yet
Development

No branches or pull requests

2 participants