No 'low stock' warning?

[Johnny]

I have just decided to put inventory tracking on.

I have imported the quantities using emporiums $10 utility which seems to
have worked. I have switched on inventory tracking, set the 'low' level to 5. I have tested it on a specific product which has a quantity of 2 left, but on the site it gives the standard 'in stock' message - "2 available for immediate delivery".

On the inventory part of the product itself 'track inventory' is ticked, and 'track low' is set to 'default' (so I assume 5).

So what's the problem? Why isn't it giving the low warning message?

Here's the link (adult content (condoms)) -

http://www.condommegastore.com/mm5/merchant.mvc?Screen=PROD&Product_Code=DUREX-TNG-12-R

[wcw]

There is a bug in MM5 inventory. See the thread
http://extranet.miva.com/forums/showthread.php?t=6491
Near the end of the thread, there is a post on what someone had to do to get the inventory system to work.

[Dan - Kemper Strategic]

Just out of curiousity, what type of database are you running with your MM5 store? (MivaSQL or MySQL)

[Johnny]

errrr... no idea. probably whichever is default... set it up ages ago and haven't touched it since...

[Dan - Kemper Strategic]

Go into your admin and look in the upper left corner, you will see something similar to this:

Production Release 3
MIVA Engine v5.06
Database API: mysql

What does yours say?

[Johnny]

mivasql.

And the answer from the other thread is that it's a big buggy pile of crap. Looks like the fix is to set all the values for every product rather than set the defaults in one central place and then set everything to 'use defaults'...:mad:

[Dan - Kemper Strategic]

That's what I figured... So it looks like so far everyone that has reported this issue is running MivaSQL.

Bill, this would explain why you are only seeing it in certain stores and not others.

[dsisaacs]

I posted the detailed fix in the other thread...and I am also running mivasql

Note to Johnny...You can use the default settings for manually created products. It just won't work for imported products.

As for setting the levels & messages for imported products, you just need to fill this out once in your spreadsheet and copy down all the columns for all the products in the import.

If you create a template spreadsheet with this info, then you only need to set it up once. Here are the column headers, copy and paste this into excel.
ProductCode| ProductName |CategoryCode |Price |Cost |Weight |Description |Taxable |Active |ThumbnailUrl |ImageUrl |AttributeTemplateCode |AdjustStockBy |TrackProductInventory |InStockMessage(Short) |InStockMessage(Long) |TrackLowStockLevel |LowStockLevel |LowStockMessage(Short |LowStockMessage(Long) |TrackOutofStockLevel |OutofStockLevel |HideOutofStockProducts |OutofStockMessage(Short) |OutofStockMessage(Long) |LimitedStockMessage

and a set of sample data

test123| test product| test| 0.01| 0.01| 0| test product for import| No| Yes| graphics/00000001/defaultth.jpg| graphics/00000001/default.jpg| | 5| yes| In Stock| %inv_instock% in stock| No| 1| Only one left| Note: '%product_name%' has <b>only 1 left.</b>| yes| 0| yes| Sold Out| Sorry, we are sold out of '%product_name%'.| Sorry, we do not have enough '%product_name%' to fill your order. Please adjust the quantity and try again. <br>Quantity Available: %inv_available%

[wcw]

That's what I figured... So it looks like so far everyone that has reported this issue is running MivaSQL.

Bill, this would explain why you are only seeing it in certain stores and not others.
I found the problem. It is not related to mivasql vs mysql. It is a broken API function in the merchant core files. The function InventoryProductSettings_Insert() is not properly setting the values in newly added records that are imported. That would explain why my module didn't help with the bug, as it was using the same buggy function that is used in the core import.

I changed my module to import newly established inventory settings to match the default by not using the built-in function. It does not change individual configurations already in the inventory settings when updating. I've tested and it has worked around the issue for products that did not previously have inventory settings established.

The inventory counts still work as before, ie set new level or adjust (+ or -) the existing level.