-
Notifications
You must be signed in to change notification settings - Fork 3
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
Multi Source Inventory isn't taken in consideration #74
Comments
@rexterkate-adwise thank you for opening this issue. Sorry for the late reply, but we are having a hard time reproducing this. We use the |
@Marvin-Magmodules we have reverted all our (multistore) shops to the 1.6.1 version of the plugin because of the problems since the 2.0.0 version. So I can't easily reproduce this currently. From what ik recall, the msi stock data is correctly read from the database and available in the productData array ('msi' key), but it isn't used in the feed (only 'qty' key is used). |
Hi there @rexterkate-adwise, apologies for the delay on this. We have just created a branch that should be compatible with the MSI environment where you’ve been experiencing these issues. Could you please test this in a staging/development environment and let me know if it meets your expectations and resolves the issue? Thanks a lot! |
Hi @rexterkate-adwise, |
Hi @rexterkate-adwise, happy to tell you we merged this into the v2.2.0 relaase so we will consider the issue closed. However, if you encounter any further problems related to this, please don't hesitate to inform us by re-opening this issue. |
Describe the bug
Stock definedin Multi Source Inventory isn't taken in consideration for the stock status
Used versions
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The product shows the product to be in-stock
Actual behavior
The product shows the product to be out-of-stock
Screenshots
n/a
Additional context
When productData is collected, the array contains a key 'msi' with the non default stock. It doesn't seem to be taken in consideration when creating the actual feed.
The text was updated successfully, but these errors were encountered: