Skip to content

Why does «Manage Stock» setting have the GLOBAL scope? Need set it per website. #2012

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

Closed
dmitrii-fediuk opened this issue Oct 3, 2015 · 9 comments
Assignees

Comments

@dmitrii-fediuk
Copy link

Two different websites could have totally different kind of products: virtual for a one and physical for another.
What was the sense to make the scope of «Manage Stock» option global?

2015-10-03_19-33-53

@piotrekkaminski
Copy link
Contributor

@mbrinton01 please check this one

@NadiyaS NadiyaS added MX labels Oct 7, 2015
@mbrinton01
Copy link

Thank you for your feedback @dfediuk, we will consider this for a future update. It was originally created this way because the stock management option was created before it was possible to have multiple webstores and has the same configuration as Magento 1.

@katmoon
Copy link
Contributor

katmoon commented Mar 12, 2016

I'm closing the ticket due to @mbrinton01 comment.

@dfediuk thank you for sharing the idea for improvement!

@katmoon katmoon closed this as completed Mar 12, 2016
@katmoon
Copy link
Contributor

katmoon commented Mar 17, 2016

Internal ticket MAGETWO-50583 has been created for this issue.

@qrz-io
Copy link
Contributor

qrz-io commented May 17, 2016

Hey @katmoon - can you share clarify if this will include the ability to have different product stock per website? Is there an ETA?

@katmoon
Copy link
Contributor

katmoon commented May 17, 2016

I don't have this knowledge. Maybe @mbrinton01 knows.

@mbrinton01
Copy link

Hello @qrz-io, we are working on building Multi-Node Inventory that will include the ability to set stock for multiple sources and assign these sources to websites, but do not have an exact ETA. More detail is in #473

@mbrinton01 mbrinton01 self-assigned this May 26, 2016
@tuyennn
Copy link
Member

tuyennn commented Oct 1, 2018

Hi @magento-engcom-team any ref to this issue as you marked it was done on branch [2.3-develop]?

@mbrinton01
Copy link

@tuyennn Please see the MSI project for more information: https://github.com/magento-engcom/msi

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants