Re: [mv] different prices for different attributes and more

[Ed LaFrance <newmedia@newmediaems.com>]

******    message to minivend-users from Ed LaFrance <newmedia@newmediaems.com>     ******

At 10:31 PM 3/30/00 -0800, you wrote:
>******    message to minivend-users from "Joe McDonald" 
><joe@vpop.net>     ******
>
>
>Hello,
>
>I am new to Minivend.  It looks to be quite powerful.
>I have a couple of requirements that I'm wondering if
>someone has already tackled:
>
>I see that you can have attributes with multiple values
>such as: Size: S/M/L/XL.  What I need to do is display
>to the user that a particular size (say L) costs more
>than the other sizes.  So the drop down will look like:
>
>Small
>Medium
>Large -- 19.95
>X-Large
>
>And of course this should be reflected in the "basket".

Take a look at the way size data is kept in products.  You should be able 
to edit it on an -item-by-item basis to include a price next to any desired 
size.  To actually change the price of the ordered item based on size 
selection, you will need to make corresponding changes to the database 
which stores price adjustments for the item by size - this is all 
documented, and the T-SHIRT in the simple demo catalog demonstrates the 
feature.


>Also, I need to have a seperate SKU for the various combos
>such that a LARGE-RED and a LARGE-GREEN and a SMALL-RED
>all have different sku's but are just shown as 1 item on
>the item page.

If you want to make many skus appear to be one, you are going to need to 
play around with how you display items in your search results and 
flypage.  Basically, you will probably want to use sorting and the [on 
change] tags to make a group of items with one value in common look like 
one item with several options.  When the user orders an "option", they are 
actually ordering the unique sku from the group which meets their needs.


>------------------
>Another requirement is to have a completely different
>look-and-feel based on a variable passed in as the
>user enters the store.  That is, if they enter:
>
>http://www.mystore.com/simple.cgi/index.html&affiliate=bigAffiliate
>
>Then the store should look like bigAffilate designed it
>(bigAffiliate would of course have created their own
>templates).
>
>Does anyone have any pointers to get started on the above?

The documentation describes how to get affiliate info from an inbound URL 
(I think, either in the docs or in the list archives...).  From there it is 
your baby.  If I was doing it I would probably have my catalog entry point 
be a page which gets the affiliate code from the URL, looks it up in an 
affiliate database, and sets a bunch of scratch and session variables based 
on values in that database, which describe what colors, graphics, pages, 
etc to use for the session for that affiliate.  Then that page forwards the 
user to their welome page.

- Ed L.





>Thanks,
>-joe
>
>-
>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