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

My[parcel compatibility with Wyomind Advanced MSI Suite #642

Closed
Daniel304 opened this issue Feb 3, 2022 · 3 comments
Closed

My[parcel compatibility with Wyomind Advanced MSI Suite #642

Daniel304 opened this issue Feb 3, 2022 · 3 comments
Labels
compatibility Compatibility issues Next version

Comments

@Daniel304
Copy link

Plugin/theme name

wyomind advanced msi suite

Pricing

Premium

What problem does this feature solve?

We are using myparcel together with MSI on magento 2.4.3-p1.
To get some much needed extra options we are using advanced MSI suite of Wyomind.
This suite is enabling pre-allocation over multiple sources for different sales channelsit can but is not limited to one single store.

The pre-allocation is done using their own algorithm, which work just fine on new orders. ho ever when we are choosing to ship the order somehow the product will suddenly reallocated to a source that is not connected to the sales channel.

This most likely is done by the myparcel extension. This unfortunately messes up our complete order system currently.

What should the solution look like?

The allocation should not be changed during the shipment process.

Relevant log output

No response

Additional context

No response

@Daniel304 Daniel304 added the compatibility Compatibility issues label Feb 3, 2022
@Daniel304
Copy link
Author

Apparently this is not just a compatibility issue with wyomind but with Magento MSI

@RichardPerdaan
Copy link
Member

Hi @Daniel304,
This issue is solved in #633
This adjustment will be included with the next version and is expected to be live next week.

@RichardPerdaan
Copy link
Member

This issue is solved on 17 feb 2022 in version: 4.3.0-alpha.1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
compatibility Compatibility issues Next version
Development

No branches or pull requests

2 participants