Hi, I am testing on this Store module and I encounter a small problem that could easily be fixed.

The quantity for any given item can be set, and will be updated after every placed and confirmed order. This works fine, except that a customer can order more than het actual number of items in stock. This seems logical, but the order shows that the customer will get the odered number, while, in reality, the real number should be shipped, and the rest should be placed in backorder.

Another thing is the inability to see how many products are due to sink into the negative stock numbers. In logistics there are two figuresof importance: The LOW TRESHOLD and the HIGH TRESHOLD. (Where the HIGH TRESHOLD has a deliverytime attatched i.e. number of days to get the stuff from the manufacturer into my stock)

LOW TRESHOLD is used to get signalled when an item is going to sink under a certain number in stock. When I have a great number of different products, it would be nice that I could list the products that have reached this LOW TRESHOLD, in order to get them in stock in time, before my customers start complaining. On the other hand, the HIGH TRESHOLD gives me the maximum number of items that I have to order when my stock is getting low. (In fact this is the difference between the HIGH TRESHOLD and the actual stock, but I put that in my query for this purchase order)

When the stock of a certain product sinks under the LOW TRESHOLD, the status must automatically change to "Low". This will be the status to list the purchage items on.

So, in all my question:

Would it be possible to put these fields into the Store datamodel?

I'd like to see them called: "TresholdStatus"; "LowTreshold"; "HighTreshold" and "DeliveryTime" and, of course, "PurchagePrice".

With these extra fields I can build my own queries to get the purchase and stock management in the right place.

Cheers,

---

jos Richters www.visualdata.nl

Hi Jos,

I think that for a module like store, adding extra fields into the database, even if we do not explicitely use them, is a good idea.

We could include these change quickly, since there is little code to add, and limited bug risks.

Let's see what we can do.

We'll wait a bit to welcome comments about your suggestions.

 

 

---

Benoît Sarton
www.bsi.fr
www.dotnetnuke.fr

Hi Jos,

Your suggesions was usefull for everyone and well detailled, then I added them! Thanks to that.

1) I added new fields in the database (table StoreProducts: StockQuantity, LowThreshold, HighThreshold, DeliveryTime and PurchasePrice) and the corresponding code of course to manage them. ;-) You can create your own stored procedure to access and/or update them.

2) Yes, you have to use the last beta version 02.01.09.

3) Concerning the Dutch translation, we received at least 3 set of language pack! The Dutch community is very active. :-) It could be more productive to join you effort to produce only one set. I suggest to create a translation team on the Dutch DotNetNuke User Group. In all case, thanks for your effort to produce valuable resource for the community. I know how it's long to translate the toon of ressources availble in the Store module! :-)

Gilles

---

We (team members) are Humans offering their knowledge, their work and their spare time FOR FREE to benefit the community. It would be so particularly appreciated that your messages begin with "Hello" and end with "Thank you" or any other form of politeness. Ask yourself what your reaction would be, if you were approached by me (a total stranger) on the street to ask you something without saying "Hello" nor "Thank you"? After several years of services dedicated to the community, I begin to be tired to read requests without any form of politeness.