Magento Multi Source Inventory, 3 Nov 2017

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: MSI Open Demo. November 3, 2017

Description

Description of SalesChannel to Stock relation in Magento Multi-Source Inventory

A

A

All right welcome to our MSI demo, OMSI weekly. We have a short agenda for today and I think we should start right now. The first part is presented by Lars. It's about the whole stock assignment, so Lars. It's your stage.

B

Yes, this ticket is currently a work in progress, arrived yesterday, some a question to the chat because we I had some problems with the implementation, because the default tables are not set in any case, and now we find a solution for this problem and I will implement this and yeah. I must also extend a new creation test with some features for odd inventory status and inventory item table, and then it's yeah I can finish this task yeah.

B

It's currently working progress, so thank.

A

You, the next, is Belinda no agendas, so she tells us something about the sectional integration. We currently just can talk about the implementation itself, but not about the UI part, because, as still in refactoring.

B

C

C

This is better not much.

B

C

So last week we had the contribution week here. Tech division and my part was to implement the sales channels which are a connection between websites and.

C

And we solved that issue, or mainly I solved that issue and by using extension attributes for the stock, so it is like an own little table that is part of the stock and will be saved on it by the normal, safe of stock. I I, don't know if you want to see my coat for the chair. My screen.

C

So just quickly.

C

Can you see my mouse okay, so we have two modules: one for the inventory sales and one for the inventory sales EDI and the implementation of courses here in sales and for the API you have like set type get time and code and so on.

C

And also the receiving of the sales channels for stock, that's mainly all we gave to the outside because due to database inconsistency, it's better to not change the sales channels by themselves, separate from the stock.

C

mmm Yes, so for now we defined the type of website as as the constant, so I, don't I can't find it now, maybe in selfie and of interface, those channels interface, oh yeah, yeah. So for now we are in an our table. We using the string website because it's only limited for websites in the beginning and later can easily.

C

You oops, for example, is that so.

D

I have questions so we love, if answered correctly, you introduce this sales channel interface in this in this one right. Yes,.

C

D

So which services it's used in.

C

And it is currently only meant to be used and and stopped managed and like. If you.

A

Believe that I can help. Oh you.

C

Don't smash screen right so.

A

Actually, we inject end of the sales channel into this talk, so we have the stock and we have extension and attribute in the stock entity and there is a possibility that assigned sales. You know some particular stock can.

D

C

So, do you see my browser now, what am I can't a second.

D

D

C

Basically, basically we're doing plugins here. So if you have to save method from stock, we are having in around plugin around safe plug-in, that is getting the stock itself and putting our extension attributes, which are the type and decode on it. So it's kind of harder to stock itself.

C

D

So you decided.

C

D

So, sales channels, as a separate as a wonderful module right.

D

And there will be no such thing as sales channel on stop. Yes and the house magenta behaved in that case. I'm. Sorry, I'm, asking all these questions. I didn't participate in previous demos and I'm being fined under viewing the designs, but I think it might be useful. Not for me only so.

C

I, don't really get the question you you think about the case where you had sales channels and letter remove them. So.

D

If I remove the.

C

D

Module or battery cells, PPI model magenta behave without sales channels, I create multiple, sell. My multiple stocks right and I, don't assign sales channels to them. What does it mean functionally and.

C

So one one stock can have several sales channels and it doesn't have to have any in. So it's not a narrow case anyway.

D

C

I assign a census option: okay,.

D

I've assigned a sales channel to stock. So what.

A

D

It mean what happens.

A

So in this case, so if you assign the sales channel to some particular stock, we create a linkage and that linkage is represented as an exit, an attribute added to the stock entity and that behavior brought by the inventory sales module.

D

So you have this link and how it is linked used.

A

Yeah, so actually we have bunch of like I already mentioned. We have an idea that any like sales channel and there could be different. So you know, and the magenta side, so out of the books, we will go with the website sales channel, so any sales channel should be assigned to some particular stock, that's actually the business rule and we supposed to holiday. For example, when the website you know created the website, it's created.

A

We like implicitly assign it to the default talk, so any website would be assigned to some some web channel some sales shell, but we can, along with that, we can create a sales channel and not assign it to some to any of the two of the mmm sales channel. We have.

D

Verify is functionality of sales of sales channels used anyhow today in in current implementation,.

A

We already assigning the default website like any website which we create. We are funny to the default sales channel and actually that's assignment made with this linkage.

A

At least a website is also.

D

Not create a sales channel, so my understanding is that in current sprint on the last window last week you added the ability to create sales channels right. Yes,.

A

And assign it, and along with that, we had another story where we assign newly created web signed website to the default sales channel. Also, we had another story where we check that when we remove so drop some particular sales channel, we can't allow to do it.

A

While this, when we are trying to remove some particular stocks, we are making a validation and we don't allow to remove the stock well, it is assigned to some of the sales channel winner, so the merchant should unassigned the stock from all of the sales channel and adjust after that to remove it. Yeah.

D

Yeah, so data make sense. So, okay.

C

So I created the.

D

Stock yeah and I assigned it to some sales channel. Yes and.

A

D

C

Yes, yes, okay,.

D

So it's assigned and what does it mean so how is it used in? How is it used in magenta, so.

C

When I come to this site,.

D

I will automatically get stock only Blancas. Only from this channel.

A

So, actually, when you make this assignment that that provides you an opportunity when you come to the website that will give you a stock because actually like any any any sales channel, has one one-to-one relationship with with with with a stock. So actually we also along with that we have a resolver interface which provide you an opportunity to resolve current stock, which is supposed to be your stock. You should work with based on the type and the ID of the sales channel.

A

D

Understood so so stock resolver, it accept string actually.

A

For example, for the website that would be tight website and the code, the website code or website ad. So probably it would be website ID, because we already have the legacy code, the catalogue inventory', which rely on the website ad. So we.

D

C

D

When you come to website there's the current stock for this website is resolved by by the channel that it is linked by default. This channel adapts it I remember this is an OK book, but.

C

A

D

Stock ID is overused today, so.

A

Currently, we like in in in a current code base, we just started to apply the current code.

A

This was over to the checkout process to resolve the ID of the stock, from which we suppose to make a stock deduction.

D

Okay, so is, is it in progress or is in.

A

Progress now, okay,.

D

A

Gonna be when so it's now in progress, and actually we are just integrating this over to the catalog inventory and the catalog okay.

D

A

It really makes sense the efficient.

C

Okay, so I guess I'm done with my stuff.

A

So all right, thank you. Everybody Thank, You, Belinda and next part is presented by me. That's about refactoring we made for the expert part, so we already show the export completely in one of our last demos, I think in the last one, and in the last few or in our last week we did a little a lot of refactoring there. So we look into code now and the refactoring was in first place in order to be to provide better extension points for developers. So our export functionality is currently made up from.

A

The eav export behavior, so the legacy export always needs some kind of attribute collection. So this is why we simulate here attribute collection for our export, so in order to provide configuration grid- and so one of our SP is here- an extension point for developers is that this part can be extended by for for a plugin, for example, so you can add additional lines or add additional attributes which would be configurable in the grid for the export.

A

The next part is also provided by the validate Azure filters we have so each attribute can be also a filter for the export. So here we provide also an extensible part via di, so you can add additional valid data which are based on the database type of the attribute and.

A

All in one result of our refactoring was that we also match or past static, matrix or static tests, so that we don't have the dependency higher than 13, so I think it's so far from the.

A

Refactoring path, and maybe eager won't, say something more, but I can add several words just to make clear for maybe Antone so OPA deem during the last two or three strings implemented the stock import export functionality and taking into account that our stock import export is actually import, export functionality 3 to legacy, and actually it has a coupling on Eve. So we had to make some fake VB collection because we have especially for the export functionality, people for expert functionality. We are building agreed based on the heebie attributes.

A

We actually take that functionality and making, like all the necessary refactoring and like using the only PIV we could use in this particular situation. Now: okay, that was inheritance API. So we provided the source import source item in import extra functionality, and now, why didn't describe was actually part of refactoring? He had to make to achieve the goal.

A

For example, even the default extra functionality needed more than certain dependency paranal, so that was a pretty challenges to make a reflector into to make our static test to be to be passed without suppression of warning, with the amount of it's around the penances.

D

C

The sources model.

D

Export sources is a source source or source items.

A

If it's possible, maybe you would show the how it works.

D

I can imagine how export works, so maybe anyone else wants to do and what confuses me a bit. It's called sources.

A

Export all source informations pair item, so we have source, ID and SKU for each row.

D

Ok, so just consider it's not important, it's not very important thing to that case. I would rename this to force items, but you understand that the main of this better, because.

A

In mind, ascending Dex,.

D

For source items right.

A

Yeah this character, this correct, yeah, okay,.

D

Okay, let's continue.

A

Right so the next parts also presented by me I just want to show what I have a short look into the first integration into a catalog inventory. So we just start working on them for that I have to switch my branch.

A

Yeah, alright, so, and also for for this I I, want to show you the current behavior in the backend. So we just add the first, the right behavior for the default Sox. So if I add a new product, the decision was that I can use still the old quantity field for the default. A stock assignment, so currently it will use P will be used in parallel. So, for example, I will add a product product ABC.

A

A

This information will be also as users, the stock status and the quantity will be automatically added to our assigned as a new to do all the default stock here. So that was the first integration here, so we capture this data and also persisted and new MSI data model, as you can see here the same we have. If we update this information out of stock, you.

A

So, as you can see, it was updated here currently what we don't have the final decision from the UI part. So the idea was to disable this field here and also remove the delete items so that default source assignment is in every product. After persisting it and the only place working. We edited this information as the old fields we have.

A

So what, therefore, we need the final decision for mark. Maybe he can provide us this information after he see our recall it meeting so we implement this stuff. In the same way, we saw it previously for the sales channels also for the import-export part. So we have our own module called inventory catalog, which is the linking part or a model which have dependency to the old catalog inventory and the new inventory module.

A

Any questions so.

D

We now we now have catalog inventory and inventory catalog modules.

C

D

So we need a plan yeah.

A

Actually, we have a plan, so actually we learned that during our work, inventory, catalog we'll get more and more logic and actually the logic supposed to couple the inventory functionality in the catalog and actually like catalog, inventory models of the old legacy module supposed to be dismantled along the way and after them alone, for my sole milestone. 3, probably it should be totally eliminated from the system when.

D

This milestone 3, so.

A

Currently, we are targeting milestone 1 as a minimal Viable Product of MSI supposed to be releasing at 2.3 and like and probably and actually like.

A

They did this mountain of the inventory of the Cadillac inventory will bring the backwards incompatible changes, so we can't it release earlier than into this, for, for example,.

C

The functionality.

D

That you showed looks cool, let's sync on naming modules and how, once one big question related to modularity, it's not that sir! It's not related to what you just showed, but but so you introduce the module inventory catalog and there is a some product type specific inventory management right.

D

Have you encountered a prototype specific inventory management so far to put that behavior to product type specific in rendering yeah.

A

Exactly we have actually three dedicated story for four configurable grouped and bundled products, and we supposed to put them to the dedicated modules cool.

D

A

There is also, for example, an observer which we override from the original inventory implementation in order to be compatible with interlocked inventory, so just an additional module which can be removed some some day, some days later, yeah. So actually our basic strategy to make two to three merchant release, with MSI on board as less backwards incompatible as possible. So we're trying to be backward compatible and actually actually, at the time of catalog inventory' dismantle it would be backwards, incompatible release. But it would be like milestone to a milestone. Three.

A

So all right, if we don't have any questions more I, think we are ready so far.

A

Well, thank you every for joining this meeting and see you next week. Thank you for the great demonstration, but him thank you. Yes, hi.