Re: [mv] Inventory Control

[Scott Benson <scott@rant.tzo.com>]

******    message to minivend-users from Scott Benson <scott@rant.tzo.com>     ******

I ran into the same problem - our catalog is nothing but clothing so I just ended up
using separate sku's for different sizes and colors of the same item.  Then I added a
column to the products database containing the item (a different number - part of the
sku) and another database which holds the description and other info of the item. That
way I don't have to cut and paste the item's info into each entry in the products
database.

So far it seems to be working out pretty good - but I had to pretty much hack together
all the pages.

Scott


Mike Heins wrote:

> ******    message to minivend-users from Mike Heins <mikeh@minivend.com>     ******
>
> Quoting Chris Jesseman (chris@sitemajic.net):
> >
> > A similar problem exists when selling clothing. Couldn't the current size
> > pricing tools be converted to this type of inventory? So instead of a
> > size 10" brush pricing differently, there is just inventory data... Just
> > a quick thought. Seems like every merchant does their inventory
> > differently, so there is no easy solution! I say that ERP should take
> > care of all inventory management, and have MV/IC interface with the ERP
> > software.
> >
> > This has been a thread on this list recently too.
> >
>
> I think the way to do this is to have separate SKUs.
>
> One thing I think might be nice to add -- an mv_item_morph parameter
> in the shopping cart. When selected, it morphs the item into another
> SKU upon cart update. 8-)
>
> That way you could have a cart line which said:
>
> <INPUT TYPE=hidden NAME="[quantity-name]" VALUE="[item-quantity]">
> [item-accessories mv_item_morph]
>
> the mv_item_morph line in the database would say:
>
>         os28007=5 foot, os20995=10 foot, os20998=20 foot
>
> and the appropriate widget would be displayed.
>
> Then when selected, it changes the SKU.  The mv_ib_sku attribute
> would maintain the initial SKU ordered, perhaps even providing the
> "code" for an [item-data table column], etc., while [item-price] and
> [item-description] would stick with the item (kind of like on-the-fly
> items.)
>
> This is 4.7 stuff -- probably the best way to do it now is to use
> separate SKUs.
>
> --
> Akopia, Inc., 131 Willow Lane, Floor 2, Oxford, OH  45056
> phone +1.513.523.7621 fax 7501 <heins@akopia.com>
>
> Few blame themselves until they have exhausted all other possibilities.
>  -- anonymous
> -
> To unsubscribe from the list, DO NOT REPLY to this message.  Instead, send
> email with 'UNSUBSCRIBE minivend-users' in the body to Majordomo@minivend.com.
> Archive of past messages: http://www.minivend.com/minivend/minivend-list

-
To unsubscribe from the list, DO NOT REPLY to this message.  Instead, send
email with 'UNSUBSCRIBE minivend-users' in the body to Majordomo@minivend.com.
Archive of past messages: http://www.minivend.com/minivend/minivend-list