Multi Source Inventory - Stocks sources of other website's showing on applying store switcher in admin
Preconditions (*)
- Magento CE 2.3.4
Steps to reproduce (*)
- Create 2 websites - UAE(default) & Oman
- Create 2 inventory sources one each for the above websites under Stores > Inventory > Sources
- UAE
- Oman
- Create 2 inventory stocks under Stores > Inventory > Stocks and assign them to above websites (Sales Channel) and assign one source to each UAE and Oman respectively
- UAE (Stock) => UAE (Source) - UAE (Sales Channel)
- Oman (Stock) => Oman (Source) - Oman (Sales Channel)

- Go to any product under Catalog > Products and tag it to both the websites
- Assign and Set qty per source (UAE & Oman)
- Do reindexing
- Now in Product Edit form in store switcher, switch store to Oman in the backend

- Product shows both the sources (UAE & Oman)

Expected result (*)
- On switching to Oman store in product edit form, it should show only inventory source Oman. Since we had assigned Sales Channel Oman to the Oman stock in Step 2 above. This is creating confusion for our client.
Actual result (*)
- On switching to Oman store in product edit form, it is showing both the inventory sources UAE & Oman.
Hi @lokeshvnaik. 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
Hi @engcom-Delta. 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 labelIssue: Format is validwill be added to the issue automatically. Please, edit issue description if needed, until labelIssue: Format is validappears. -
[ ] 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add
Issue: Clear Descriptionlabel to the issue by yourself. -
[ ] 3. Add
Component: XXXXXlabel(s) to the ticket, indicating the components it may be related to. -
[ ] 4. Verify that the issue is reproducible on
2.4-developbranchDetails
- Add the comment@magento give me 2.4-develop instanceto deploy test instance on Magento infrastructure.
- If the issue is reproducible on2.4-developbranch, please, add the labelReproduced 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: Confirmedonce verification is complete. -
[ ] 6. Make sure that automatic system confirms that report has been added to the backlog.
Issue should be transferred to MSI repo for further discussion
Hi @lokeshvnaik. Thank you for your report. To help us process this issue please make sure that you provided sufficient information.
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.