Developer forum

Forum » Ecommerce - Standard features » Stock Locations features

Stock Locations features

Nuno Aguiar
Reply

Hi,

 

I have a B2B project with the following requirements

  1. Multiple stock locations
  2. Prices per stock location
  3. Add to cart from a Stock location (related to Prices per stock location + actual stock)
  4. Stock control/valiation per location

 

I am not sure if we can do all of it with Stock locations. I need to determine how much is out-of-the-box and how much we have to develop. Maybe if we use Units, Where UnitA is only used by Location A and Unit B is only used by Location B, but I am not sure that's the best way to do it.

 

Can anybody point me in the right direction? 

 

Best Regards,

Nuno Aguiar


Replies

 
Nicolai Høeg Pedersen
Reply

Hi Nuno

1+3+4 is out of the box.

Prices cannot vary by stock location. Not sure it makes much sense to me.When you show the product, you get a list of stock locations and how many is in stock in that location. At this point stock location has not been chosen and therefore the price cannot reflect that.

If you want the entire order to only have products from one stock location, you should consider creating a catalog structure where each location has its own shop - but sharing the same products. This way you can handle the stock location based on the shop id and then you also get the posibility to handle the price according to stock location.

BR Nicolai

 
Nuno Aguiar
Reply

Hi Nicolai,

 

I don't know how to add products to the cart from a specific stock location. I am assuming I will get 1 orderline per stock location and I can identify from which location it is.

 

I will need an order to have products from multiple stock locations. A single Shop should be enough. I might have to use the UnitA to be exclusive to LocationA and UnitB to LocationB to overcome the pricing problem. I agree it does not make a lot of sense though, so I did not even bothered placing in a feature request smiley but it is an issue I have to solve.

 

Best Regards,

Nuno Aguiar

 
Nuno Aguiar
Reply

Hi Nicolai,

 

Can you help us out with this? We can't figure out how to do items 3 and 4

 

Best Regards,

Nuno Aguiar

 
Nicolai Høeg Pedersen
Reply

You have a loop on products where you get stocklevels at each location (and per unit). If neither of these location has a stock level, you can prevent adding the product to cart. When adding the product to cart and completing the order, DW will take the product from any of the stock locations where the product is in stock.

So if product a is in stock in 2 locations DW will take the first and the best of them and decrease stock level.

Your suggestion with units should do the trick though.

NP

 
Nuno Aguiar
Reply

Hi Nicolai,

 

So sounds like I cannot control from which stock location I add products in the cart from. I was hoping for something like this:

  • /Default.aspx?Id=000&productID=PROD1&VariantID=VO1&stocklocationID=LOC1&cartcmd=add

 

Either way, I need to go the "1 Unit per location" approach, because the client needs different prices per location. Might not even need locations if units are unique.

 

Thank you for yout thoughts.

Nuno Aguiar

 
Nicolai Høeg Pedersen
Reply

Hi Nuno

Different prices per location can be an issue depending on what you need. Consider a list of products - which price would you display there for a product where it has different prices per location?

NP

 
Nuno Aguiar
Reply

Hi Nicolai,

 

For this particular case we have variants (Color + Size) and we need to display them all at once in a product list, so the B2B customer can order anything directly from the product list (in fact, there not going to be a product detail page).

 

But I agree with you, it is weird that a product is more expensive at a different stock location. What I was really hoping for (and this should maybe a feature request) is the ability to control from which stock location I am purchasing from. The B2B customer might want to select the nearest to him, rather than have Dynamicweb handle it. moreover, in integration scenarios, DW should not be the one controlling it.

 

Anyway, we are using the "1 Unit to 1 Stock Location" approach.

 

Best Regards,

Nuno Aguiar

 

 
Nicolai Høeg Pedersen
Reply

Hi Nuno

The reason it is made this way is so we do not control it - we just make sure the product gets sold - where it is shipped from is handled by the ERP that has the logic already. That is the scenario we made it for and the one it has been impemented a couple of times. Usually when you want to lock a entire order to a specific location and account, we usually have more shops each connected to different ERPs.

And still in your example, listing all variant combinations in a list - if each combination is available in more than one location - then what about price? You would have to display stocklevel and price for each location?

 
Nuno Aguiar
Reply

Hi Nicolai,

 

Yes, I see what you mean about the stock locations management. I will not be the case for me right now (due to the pricing changes), but I will definately take it into account. Thanks.

 

About the combinations, we have to basically show them all. The client wants to have it all layed out and easy/fast to use for their B2B customers. Other than performance, I don't see a big issue with it. If you want to take a look check the wireframe http://mzvn0s.axshare.com/#p=product_list_with_variants

 

Best Regards,

Nuno Aguiar

 

You must be logged in to post in the forum