Alex
Merged in a post:
multi-inventory with Magento
J
John Regalado (DHL AE), external
Good day to you team and hope you are doing well. We have a user having some issue with writeback for their Magento 2 platform, now they have found out the situation why it happens , however, they have stated:
QUOTE*/
• This error is coming when you send stock id=> 1 (default Warehouse). If anyone not using default warehouse it will give the error. Please note that from Magento 2.4 there is new Magento built-in feature called Multi source inventory system where you can have as many sources as you want.
• Quick Fix for Us: if you are sending stock id or even not, please send stock_id=9 instead of 1.
• Actual Fix: Your DHL Express Commerce system must be compatible with Magento Multi Source Inventory.
Please note that quick fix will only work for us and it can cause the issues with your other clients. So we strongly recommend the developers meeting in this case.
Thanks,
/*QUOTE
G
Greg Greg Dale
Absolutely second this. Multi-Source Inventory (MSI) is a core feature of Magento 2.4.
Shipping writeback does not work at all if MSI is enabled in Magento.
Ideally StarshipIT would allow the user to configure which source the stock is deducted from, but at a minimum, it should deduct from the default source.
A
Anthony Davies
Greg Greg Dale: Hi Gregory,
Not sure if you know the answer - but if you have any insight please let me know.
Is there a way to setup Magento2 to automatially assign each orders stock based on priority and availability across locations?
That way we could then pull through orders with their stock automatically assigned?
G
Greg Greg Dale
Anthony Davies: It does. Have a look at this... https://devdocs.magento.com/guides/v2.4/inventory/source-selection-algorithms.html
b
babak
Anthony Davies: When the intergration is setup you should just be able to pick which Source Selection Algorithm to use..
Then Magento should be able to manage the rest.
S
Sven
Has there been any progress on this? Can't believe this is still an issue with StarShipIT
Alex
Hi Sven,
The reason we haven’t pursued this is that how Magento 2's Multi-Source Inventory is designed isn’t really compatible with Starshipit’s workflow. Most systems managing stock allocate stock before dispatching. Magento, however, does this at the writeback/dispatch stage.
For us, trying to figure out where stock should be deducted from after the label is already generated doesn’t really make sense in the context of how Starshipit operates. Magento’s source selection algorithm would recommend locations at that point, but we’d have no natural way to allow users to confirm or override those recommendations within our workflow.
Would an approach where Starshipit always accepts Magento's recommendation (without overrides) work for you? Let us know your thoughts!
Cheers,