Re: [mv] Inventory Control

[Mike Heins <mikeh@minivend.com>]

******    message to minivend-users from Mike Heins <mikeh@minivend.com>     ******

Quoting Chris Jesseman (chris@sitemajic.net):
> ******    message to minivend-users from Chris Jesseman <chris@sitemajic.net>     ******
> 
> 
> > 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.
> 
> Would this be easier to manage if the sku's can have children or 
> dependent sku's?

That is a very large question. How would you do this?

You say dependent, but dependent in what way? Can you describe the
mechanism in detail? Can you describe how it would be maintainable
without using the Interchange interface, i.e. with existing tools? What
about garbage collection?  Can you do it without using database-specific
features? For instance, segmented keys as supported by PostgreSQL is
a great way to do it, but you tie yourself to one database.

I have thought about several ways of doing it, but the one thing I
insist on is that Interchange's database tables be maintainable by
other programs.  Modular bill of materials works, but is a living hell to
maintain and to understand. If the item structure relies on its routines
to maintain, it isn't usable by many people.

No one has come up with a suggestion that I believe fits all the
requirements. If I see some scheme *detailed* that does, I will be 
the first to jump on it.

-- 
Akopia, Inc., 131 Willow Lane, Floor 2, Oxford, OH  45056
phone +1.513.523.7621 fax 7501 <heins@akopia.com>

Be patient. God isn't finished with me yet.  -- unknown
-
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