Variable Weight

General ShopSite user discussion

Variable Weight

Postby Vince Salese » Fri Mar 17, 2006 5:18 pm

We have products that come in different sizes: for instance paint is
available in pints, quarts and gallons. I currently use one product page and
use the Order Options for pricing each size. Here's and example
http://www.ahoycaptain.com/shop/product64.html My problem is the shipping
weight. The pint weighs 1 lbs but the gallon weighs 10lbs. If I set the
Product Weight to 10 lbs the customer shooping for a pint gets tuned off by
the high shipping charge. Is there any way to set a variable weight for a
product depending on the choice he/she makes in the Order Option?

Thanks
Vince
Vince Salese
 

Re: Variable Weight

Postby Gary » Fri Mar 17, 2006 5:59 pm

What if you included the shipping cost of the larger containers in their
price so the estimated shipping would be accurate for pints, but low for the
others, but the total price would still be OK. That would mean putting a
note on the More Info page for products with this way of pricing and also
something on your shopping cart page that explains it since the estimated
shipping would be way to low if you charged someone the actual shipping for
a gallon.

This doesn't help, but I am curious why you don't have actual calculated
shipping from UPS or FedEx on your site? That wouldn't help with the pint,
qt, gal. problem, but the above method would work for that, too since the
weight would be based on pints.

Hope this helps.

Gary

"Vince Salese" <vince@ahoycaptain.com> wrote in message
news:dvfg4m$bhj$1@eval.shopsite.com...
We have products that come in different sizes: for instance paint is
available in pints, quarts and gallons. I currently use one product page
and
use the Order Options for pricing each size. Here's and example
http://www.ahoycaptain.com/shop/product64.html My problem is the shipping
weight. The pint weighs 1 lbs but the gallon weighs 10lbs. If I set the
Product Weight to 10 lbs the customer shooping for a pint gets tuned off
by
the high shipping charge. Is there any way to set a variable weight for a
product depending on the choice he/she makes in the Order Option?

Thanks
Vince

Gary
 

Re: Variable Weight

Postby jim » Fri Mar 17, 2006 9:09 pm

I would use subproducts and a custom template that displays the
subproducts as a dropdown list (like order options) to handle this
situation. That way each product will be ordered with its own weight
and shipping charges will be more correct.

First you would create a main product that describes the paint and
mentions the sizes available. Then you would create subproducts for
each size of container and color combination and assign them to the
main products. The custom template creates the pulldown options for
each of the subproducts assigned to the main product.

You might want to create a main product for each color or size and just
have the other as the pulldown list.

Here is a sample of a template that will create the subproducts as
pulldown options. You will need to do some tweaking to get it to work
for your store but I know of a number of sites that are using modified
versions of this template.

Jim

------------------------------------------
[-- DEFINE SUBPRODUCT --]
# A subproduct in this template is just an option for a pull down list
# Note1: Field1 is used to hold the name used for the pull down list
# such as "Brown, Size 8" instead of the actual name which
# might be "Wing Tip - Brown, Size 8".
# Note2: In order to turn off the master:subproduct naming feature used
# by ShopSite's shopping cart place
# cross_sell: checked
# in the sbdata.aa file found in the data directory
[--IF PRODUCT.SaleOn--]
<option value="[--PRODUCT.RECORDNUMBER--]">[-- PRODUCT.FIELD1 --] [--
PRODUCT.SaleAmount --]</option>
[-- ELSE --]
<option value="[--PRODUCT.RECORDNUMBER--]">[-- PRODUCT.FIELD1 --] [--
PRODUCT.PRICE --]</option>
[-- END_IF --]
[-- END_DEFINE SUBPRODUCT --]

[-- DEFINE PRODUCT --]
<CENTER>
[--PRODUCT.Name--]
<br>
[-- IF product.subproduct --]
<form action="[-- SHOPPING_CART_URL BASE --]/order.cgi" method=post>
<input type=hidden name=storeid value=[--Store.id--]>
<input type=hidden name=dbname value=products>
<input type=hidden name=function value=add>
<TABLE>
<TR><TD>
<SELECT name=itemnum>
[-- LOOP SUBPRODUCTS --]
[-- SUBPRODUCTS --]
[-- END_LOOP SUBPRODUCTS --]
</SELECT></TD><TD>
<input type=image src="[-- OUTPUT_DIRECTORY_URL
--]/media/add_to_cart.gif" width=83 height=20 alt="add_to_cart.gif"
hspace=3 vspace=3 border=0 align="bottom" name="Add to Cart" alt="Add to
Cart">
<input type=image src="[-- OUTPUT_DIRECTORY_URL --]/media/view_cart.gif"
width=71 height=20 alt="view_cart.gif" hspace=3 vspace=3 border=0
align="bottom" name="View Cart" alt="View Cart">
</TD></TR></TABLE>
</form>

[-- ELSE --]
# Need to treat as regular product
# this code still needs to be added
[-- END_IF --]
</CENTER>

[-- END_DEFINE PRODUCT --]
[-- DEFINE MORE_INFO_PAGE --]
[-- END_DEFINE MORE_INFO_PAGE --]

------------------------------------------

Vince Salese wrote:
We have products that come in different sizes: for instance paint is
available in pints, quarts and gallons. I currently use one product page and
use the Order Options for pricing each size. Here's and example
http://www.ahoycaptain.com/shop/product64.html My problem is the shipping
weight. The pint weighs 1 lbs but the gallon weighs 10lbs. If I set the
Product Weight to 10 lbs the customer shooping for a pint gets tuned off by
the high shipping charge. Is there any way to set a variable weight for a
product depending on the choice he/she makes in the Order Option?

Thanks
Vince

jim
 

Re: Variable Weight

Postby Rick Steven » Fri Mar 24, 2006 8:22 am

Wouldn't it be a better solution to add a weight parameter to the Order
Options? This is a very common situation in nearly every retail market -
sell by the item or sell by the case. Seems almost a necessity...

Jim, can you please add this to the shopsite wish list for future
enhancements?

Thanks,
Rick

"jim" <jstavast@xmission.com> wrote in message
news:dvftl4$nv5$1@eval.shopsite.com...
I would use subproducts and a custom template that displays the subproducts
as a dropdown list (like order options) to handle this situation. That way
each product will be ordered with its own weight and shipping charges will
be more correct.

First you would create a main product that describes the paint and
mentions the sizes available. Then you would create subproducts for each
size of container and color combination and assign them to the main
products. The custom template creates the pulldown options for each of
the subproducts assigned to the main product.

You might want to create a main product for each color or size and just
have the other as the pulldown list.

Here is a sample of a template that will create the subproducts as
pulldown options. You will need to do some tweaking to get it to work for
your store but I know of a number of sites that are using modified
versions of this template.

Jim

------------------------------------------
[-- DEFINE SUBPRODUCT --]
# A subproduct in this template is just an option for a pull down list
# Note1: Field1 is used to hold the name used for the pull down list
# such as "Brown, Size 8" instead of the actual name which
# might be "Wing Tip - Brown, Size 8".
# Note2: In order to turn off the master:subproduct naming feature used
# by ShopSite's shopping cart place
# cross_sell: checked
# in the sbdata.aa file found in the data directory
[--IF PRODUCT.SaleOn--]
option value="[--PRODUCT.RECORDNUMBER--]">[-- PRODUCT.FIELD1 --] [--
PRODUCT.SaleAmount --]</option
[-- ELSE --]
option value="[--PRODUCT.RECORDNUMBER--]">[-- PRODUCT.FIELD1 --] [--
PRODUCT.PRICE --]</option
[-- END_IF --]
[-- END_DEFINE SUBPRODUCT --]

[-- DEFINE PRODUCT --]
CENTER
[--PRODUCT.Name--]
br
[-- IF product.subproduct --]
form action="[-- SHOPPING_CART_URL BASE --]/order.cgi" method=post
input type=hidden name=storeid value=[--Store.id--]
input type=hidden name=dbname value=products
input type=hidden name=function value=add
TABLE
TR><TD
SELECT name=itemnum
[-- LOOP SUBPRODUCTS --]
[-- SUBPRODUCTS --]
[-- END_LOOP SUBPRODUCTS --]
/SELECT></TD><TD
input type=image src="[-- OUTPUT_DIRECTORY_URL --]/media/add_to_cart.gif"
width=83 height=20 alt="add_to_cart.gif" hspace=3 vspace=3 border=0
align="bottom" name="Add to Cart" alt="Add to Cart"
input type=image src="[-- OUTPUT_DIRECTORY_URL --]/media/view_cart.gif"
width=71 height=20 alt="view_cart.gif" hspace=3 vspace=3 border=0
align="bottom" name="View Cart" alt="View Cart"
/TD></TR></TABLE
/form

[-- ELSE --]
# Need to treat as regular product
# this code still needs to be added
[-- END_IF --]
/CENTER

[-- END_DEFINE PRODUCT --]
[-- DEFINE MORE_INFO_PAGE --]
[-- END_DEFINE MORE_INFO_PAGE --]

------------------------------------------

Vince Salese wrote:
We have products that come in different sizes: for instance paint is
available in pints, quarts and gallons. I currently use one product page
and use the Order Options for pricing each size. Here's and example
http://www.ahoycaptain.com/shop/product64.html My problem is the shipping
weight. The pint weighs 1 lbs but the gallon weighs 10lbs. If I set the
Product Weight to 10 lbs the customer shooping for a pint gets tuned off
by the high shipping charge. Is there any way to set a variable weight
for a product depending on the choice he/she makes in the Order Option?

Thanks
Vince
Rick Steven
 

Re: Variable Weight

Postby jim » Fri Mar 24, 2006 11:20 pm

In most if not all situation there will be different SKU for a single
item than for a case of that same item. So they really should be
individual items in the store. I would think that there would be a
different SKU for a quart, pint or a gallon of paint so why try to fit
them all into the same product? Having them as separate products and
using them as subproducts has definite advantages such as tracking
inventory which couldn't be done if they are listed as order options.

We have the suggestion for weight as part of the order options logged as
an enhancement request already and it will be reviewed to see if it
could be implemented in future versions. But for the time being my
suggestion below would be the easiest solution.

Jim

Rick Steven wrote:
Wouldn't it be a better solution to add a weight parameter to the Order
Options? This is a very common situation in nearly every retail market -
sell by the item or sell by the case. Seems almost a necessity...

Jim, can you please add this to the shopsite wish list for future
enhancements?

Thanks,
Rick

"jim" <jstavast@xmission.com> wrote in message
news:dvftl4$nv5$1@eval.shopsite.com...
I would use subproducts and a custom template that displays the subproducts
as a dropdown list (like order options) to handle this situation. That way
each product will be ordered with its own weight and shipping charges will
be more correct.

First you would create a main product that describes the paint and
mentions the sizes available. Then you would create subproducts for each
size of container and color combination and assign them to the main
products. The custom template creates the pulldown options for each of
the subproducts assigned to the main product.

You might want to create a main product for each color or size and just
have the other as the pulldown list.

Here is a sample of a template that will create the subproducts as
pulldown options. You will need to do some tweaking to get it to work for
your store but I know of a number of sites that are using modified
versions of this template.

Jim

------------------------------------------
[-- DEFINE SUBPRODUCT --]
# A subproduct in this template is just an option for a pull down list
# Note1: Field1 is used to hold the name used for the pull down list
# such as "Brown, Size 8" instead of the actual name which
# might be "Wing Tip - Brown, Size 8".
# Note2: In order to turn off the master:subproduct naming feature used
# by ShopSite's shopping cart place
# cross_sell: checked
# in the sbdata.aa file found in the data directory
[--IF PRODUCT.SaleOn--]
option value="[--PRODUCT.RECORDNUMBER--]">[-- PRODUCT.FIELD1 --] [--
PRODUCT.SaleAmount --]</option
[-- ELSE --]
option value="[--PRODUCT.RECORDNUMBER--]">[-- PRODUCT.FIELD1 --] [--
PRODUCT.PRICE --]</option
[-- END_IF --]
[-- END_DEFINE SUBPRODUCT --]

[-- DEFINE PRODUCT --]
CENTER
[--PRODUCT.Name--]
br
[-- IF product.subproduct --]
form action="[-- SHOPPING_CART_URL BASE --]/order.cgi" method=post
input type=hidden name=storeid value=[--Store.id--]
input type=hidden name=dbname value=products
input type=hidden name=function value=add
TABLE
TR><TD
SELECT name=itemnum
[-- LOOP SUBPRODUCTS --]
[-- SUBPRODUCTS --]
[-- END_LOOP SUBPRODUCTS --]
/SELECT></TD><TD
input type=image src="[-- OUTPUT_DIRECTORY_URL --]/media/add_to_cart.gif"
width=83 height=20 alt="add_to_cart.gif" hspace=3 vspace=3 border=0
align="bottom" name="Add to Cart" alt="Add to Cart"
input type=image src="[-- OUTPUT_DIRECTORY_URL --]/media/view_cart.gif"
width=71 height=20 alt="view_cart.gif" hspace=3 vspace=3 border=0
align="bottom" name="View Cart" alt="View Cart"
/TD></TR></TABLE
/form

[-- ELSE --]
# Need to treat as regular product
# this code still needs to be added
[-- END_IF --]
/CENTER

[-- END_DEFINE PRODUCT --]
[-- DEFINE MORE_INFO_PAGE --]
[-- END_DEFINE MORE_INFO_PAGE --]

------------------------------------------

Vince Salese wrote:
We have products that come in different sizes: for instance paint is
available in pints, quarts and gallons. I currently use one product page
and use the Order Options for pricing each size. Here's and example
http://www.ahoycaptain.com/shop/product64.html My problem is the shipping
weight. The pint weighs 1 lbs but the gallon weighs 10lbs. If I set the
Product Weight to 10 lbs the customer shooping for a pint gets tuned off
by the high shipping charge. Is there any way to set a variable weight
for a product depending on the choice he/she makes in the Order Option?

Thanks
Vince

jim
 

Re: Variable Weight

Postby Rick Steven » Wed Mar 29, 2006 7:18 am

Hi Jim, well put.

I agree to everything you said.

Maybe you can help me figure out the best way to handle my dilemma.

We sell personalized wine - either by the bottle or by the case. I would
like to have a single page that gives our customers the ordering options
which would be:

1- Text Line 1 = (customer input)
2- Text Line 2 = (customer input)
3- Text Line 3 = (customer input)
4- Spell Check (Yes or No)
5- Qty
6- Wine Type
7- Order by the Bottle or Case (check box) - these would be the SKUs

The problem is that I can not figure out how to pass the ordering options
(finopt) to both SKUs depending on which one they choose. Right now we just
sell the wine by the bottle and give qty discounts. Here's a link
http://www.winegiftclub.com/personalize ... owers.html

Do you know of a good way that I can get this done on one page?

Thanks for any advice,
Rick

"jim" <jstavast@xmission.com> wrote in message
news:e02jtl$9sd$1@eval.shopsite.com...
In most if not all situation there will be different SKU for a single item
than for a case of that same item. So they really should be individual
items in the store. I would think that there would be a different SKU for
a quart, pint or a gallon of paint so why try to fit them all into the
same product? Having them as separate products and using them as
subproducts has definite advantages such as tracking inventory which
couldn't be done if they are listed as order options.

We have the suggestion for weight as part of the order options logged as
an enhancement request already and it will be reviewed to see if it could
be implemented in future versions. But for the time being my suggestion
below would be the easiest solution.

Jim

Rick Steven wrote:
Wouldn't it be a better solution to add a weight parameter to the Order
Options? This is a very common situation in nearly every retail market -
sell by the item or sell by the case. Seems almost a necessity...

Jim, can you please add this to the shopsite wish list for future
enhancements?

Thanks,
Rick

"jim" <jstavast@xmission.com> wrote in message
news:dvftl4$nv5$1@eval.shopsite.com...
I would use subproducts and a custom template that displays the
subproducts as a dropdown list (like order options) to handle this
situation. That way each product will be ordered with its own weight
and shipping charges will be more correct.

First you would create a main product that describes the paint and
mentions the sizes available. Then you would create subproducts for
each size of container and color combination and assign them to the
main products. The custom template creates the pulldown options for
each of the subproducts assigned to the main product.

You might want to create a main product for each color or size and just
have the other as the pulldown list.

Here is a sample of a template that will create the subproducts as
pulldown options. You will need to do some tweaking to get it to work
for your store but I know of a number of sites that are using modified
versions of this template.

Jim

------------------------------------------
[-- DEFINE SUBPRODUCT --]
# A subproduct in this template is just an option for a pull down list
# Note1: Field1 is used to hold the name used for the pull down list
# such as "Brown, Size 8" instead of the actual name which
# might be "Wing Tip - Brown, Size 8".
# Note2: In order to turn off the master:subproduct naming feature
used
# by ShopSite's shopping cart place
# cross_sell: checked
# in the sbdata.aa file found in the data directory
[--IF PRODUCT.SaleOn--]
option value="[--PRODUCT.RECORDNUMBER--]">[-- PRODUCT.FIELD1 --] [--
PRODUCT.SaleAmount --]</option
[-- ELSE --]
option value="[--PRODUCT.RECORDNUMBER--]">[-- PRODUCT.FIELD1 --] [--
PRODUCT.PRICE --]</option
[-- END_IF --]
[-- END_DEFINE SUBPRODUCT --]

[-- DEFINE PRODUCT --]
CENTER
[--PRODUCT.Name--]
br
[-- IF product.subproduct --]
form action="[-- SHOPPING_CART_URL BASE --]/order.cgi" method=post
input type=hidden name=storeid value=[--Store.id--]
input type=hidden name=dbname value=products
input type=hidden name=function value=add
TABLE
TR><TD
SELECT name=itemnum
[-- LOOP SUBPRODUCTS --]
[-- SUBPRODUCTS --]
[-- END_LOOP SUBPRODUCTS --]
/SELECT></TD><TD
input type=image src="[--
OUTPUT_DIRECTORY_URL --]/media/add_to_cart.gif" width=83 height=20
alt="add_to_cart.gif" hspace=3 vspace=3 border=0 align="bottom"
name="Add to Cart" alt="Add to Cart"
input type=image src="[-- OUTPUT_DIRECTORY_URL --]/media/view_cart.gif"
width=71 height=20 alt="view_cart.gif" hspace=3 vspace=3 border=0
align="bottom" name="View Cart" alt="View Cart"
/TD></TR></TABLE
/form

[-- ELSE --]
# Need to treat as regular product
# this code still needs to be added
[-- END_IF --]
/CENTER

[-- END_DEFINE PRODUCT --]
[-- DEFINE MORE_INFO_PAGE --]
[-- END_DEFINE MORE_INFO_PAGE --]

------------------------------------------

Vince Salese wrote:
We have products that come in different sizes: for instance paint is
available in pints, quarts and gallons. I currently use one product
page and use the Order Options for pricing each size. Here's and
example http://www.ahoycaptain.com/shop/product64.html My problem is
the shipping weight. The pint weighs 1 lbs but the gallon weighs 10lbs.
If I set the Product Weight to 10 lbs the customer shooping for a pint
gets tuned off by the high shipping charge. Is there any way to set a
variable weight for a product depending on the choice he/she makes in
the Order Option?

Thanks
Vince

Rick Steven
 

Re: Variable Weight

Postby jim » Wed Mar 29, 2006 11:22 pm

This would be much more difficult to do than just having subproducts in
a pulldown. You need to gather several different types of information
and stick them in input fields that vary depending on whether a case or
bottle is selected so you get the appropriate product number associated
with the item when added to the cart. It may be easier to put the
information into generic javascript variables and then using an on click
javascript to populate the final input fields that actually get
submitted to add the product to the cart depending on if the shopper
selected a radio button for Bottle or Case. This would have some draw
backs in that you couldn't allow say a case of 12 plus 2 bottles. I
don't know javascript so don't know how this would be done but assume
that it could be.

Jim

Rick Steven wrote:
Hi Jim, well put.

I agree to everything you said.

Maybe you can help me figure out the best way to handle my dilemma.

We sell personalized wine - either by the bottle or by the case. I would
like to have a single page that gives our customers the ordering options
which would be:

1- Text Line 1 = (customer input)
2- Text Line 2 = (customer input)
3- Text Line 3 = (customer input)
4- Spell Check (Yes or No)
5- Qty
6- Wine Type
7- Order by the Bottle or Case (check box) - these would be the SKUs

The problem is that I can not figure out how to pass the ordering options
(finopt) to both SKUs depending on which one they choose. Right now we just
sell the wine by the bottle and give qty discounts. Here's a link
http://www.winegiftclub.com/personalize ... owers.html

Do you know of a good way that I can get this done on one page?

Thanks for any advice,
Rick

"jim" <jstavast@xmission.com> wrote in message
news:e02jtl$9sd$1@eval.shopsite.com...
In most if not all situation there will be different SKU for a single item
than for a case of that same item. So they really should be individual
items in the store. I would think that there would be a different SKU for
a quart, pint or a gallon of paint so why try to fit them all into the
same product? Having them as separate products and using them as
subproducts has definite advantages such as tracking inventory which
couldn't be done if they are listed as order options.

We have the suggestion for weight as part of the order options logged as
an enhancement request already and it will be reviewed to see if it could
be implemented in future versions. But for the time being my suggestion
below would be the easiest solution.

Jim

Rick Steven wrote:
Wouldn't it be a better solution to add a weight parameter to the Order
Options? This is a very common situation in nearly every retail market -
sell by the item or sell by the case. Seems almost a necessity...

Jim, can you please add this to the shopsite wish list for future
enhancements?

Thanks,
Rick

"jim" <jstavast@xmission.com> wrote in message
news:dvftl4$nv5$1@eval.shopsite.com...
I would use subproducts and a custom template that displays the
subproducts as a dropdown list (like order options) to handle this
situation. That way each product will be ordered with its own weight
and shipping charges will be more correct.

First you would create a main product that describes the paint and
mentions the sizes available. Then you would create subproducts for
each size of container and color combination and assign them to the
main products. The custom template creates the pulldown options for
each of the subproducts assigned to the main product.

You might want to create a main product for each color or size and just
have the other as the pulldown list.

Here is a sample of a template that will create the subproducts as
pulldown options. You will need to do some tweaking to get it to work
for your store but I know of a number of sites that are using modified
versions of this template.

Jim

------------------------------------------
[-- DEFINE SUBPRODUCT --]
# A subproduct in this template is just an option for a pull down list
# Note1: Field1 is used to hold the name used for the pull down list
# such as "Brown, Size 8" instead of the actual name which
# might be "Wing Tip - Brown, Size 8".
# Note2: In order to turn off the master:subproduct naming feature
used
# by ShopSite's shopping cart place
# cross_sell: checked
# in the sbdata.aa file found in the data directory
[--IF PRODUCT.SaleOn--]
option value="[--PRODUCT.RECORDNUMBER--]">[-- PRODUCT.FIELD1 --] [--
PRODUCT.SaleAmount --]</option
[-- ELSE --]
option value="[--PRODUCT.RECORDNUMBER--]">[-- PRODUCT.FIELD1 --] [--
PRODUCT.PRICE --]</option
[-- END_IF --]
[-- END_DEFINE SUBPRODUCT --]

[-- DEFINE PRODUCT --]
CENTER
[--PRODUCT.Name--]
br
[-- IF product.subproduct --]
form action="[-- SHOPPING_CART_URL BASE --]/order.cgi" method=post
input type=hidden name=storeid value=[--Store.id--]
input type=hidden name=dbname value=products
input type=hidden name=function value=add
TABLE
TR><TD
SELECT name=itemnum
[-- LOOP SUBPRODUCTS --]
[-- SUBPRODUCTS --]
[-- END_LOOP SUBPRODUCTS --]
/SELECT></TD><TD
input type=image src="[--
OUTPUT_DIRECTORY_URL --]/media/add_to_cart.gif" width=83 height=20
alt="add_to_cart.gif" hspace=3 vspace=3 border=0 align="bottom"
name="Add to Cart" alt="Add to Cart"
input type=image src="[-- OUTPUT_DIRECTORY_URL --]/media/view_cart.gif"
width=71 height=20 alt="view_cart.gif" hspace=3 vspace=3 border=0
align="bottom" name="View Cart" alt="View Cart"
/TD></TR></TABLE
/form

[-- ELSE --]
# Need to treat as regular product
# this code still needs to be added
[-- END_IF --]
/CENTER

[-- END_DEFINE PRODUCT --]
[-- DEFINE MORE_INFO_PAGE --]
[-- END_DEFINE MORE_INFO_PAGE --]

------------------------------------------

Vince Salese wrote:
We have products that come in different sizes: for instance paint is
available in pints, quarts and gallons. I currently use one product
page and use the Order Options for pricing each size. Here's and
example http://www.ahoycaptain.com/shop/product64.html My problem is
the shipping weight. The pint weighs 1 lbs but the gallon weighs 10lbs.
If I set the Product Weight to 10 lbs the customer shooping for a pint
gets tuned off by the high shipping charge. Is there any way to set a
variable weight for a product depending on the choice he/she makes in
the Order Option?

Thanks
Vince


jim
 

Re: Variable Weight

Postby Rick Steven » Thu Mar 30, 2006 11:08 am

Alrighty then,
I will keep testing things, and if I find a solution, I will let you know.
Rick

--
Thank you very much and have a great day,

Rick Steven
Gift Specialists Inc

www.GiftSpecialistsInc.com
"jim" <jstavast@xmission.com> wrote in message
news:e0fptc$kho$1@eval.shopsite.com...
This would be much more difficult to do than just having subproducts in a
pulldown. You need to gather several different types of information and
stick them in input fields that vary depending on whether a case or bottle
is selected so you get the appropriate product number associated with the
item when added to the cart. It may be easier to put the information into
generic javascript variables and then using an on click javascript to
populate the final input fields that actually get submitted to add the
product to the cart depending on if the shopper selected a radio button
for Bottle or Case. This would have some draw backs in that you couldn't
allow say a case of 12 plus 2 bottles. I don't know javascript so don't
know how this would be done but assume that it could be.

Jim

Rick Steven wrote:
Hi Jim, well put.

I agree to everything you said.

Maybe you can help me figure out the best way to handle my dilemma.

We sell personalized wine - either by the bottle or by the case. I would
like to have a single page that gives our customers the ordering options
which would be:

1- Text Line 1 = (customer input)
2- Text Line 2 = (customer input)
3- Text Line 3 = (customer input)
4- Spell Check (Yes or No)
5- Qty
6- Wine Type
7- Order by the Bottle or Case (check box) - these would be the SKUs

The problem is that I can not figure out how to pass the ordering options
(finopt) to both SKUs depending on which one they choose. Right now we
just sell the wine by the bottle and give qty discounts. Here's a link
http://www.winegiftclub.com/personalize ... owers.html

Do you know of a good way that I can get this done on one page?

Thanks for any advice,
Rick

"jim" <jstavast@xmission.com> wrote in message
news:e02jtl$9sd$1@eval.shopsite.com...
In most if not all situation there will be different SKU for a single
item than for a case of that same item. So they really should be
individual items in the store. I would think that there would be a
different SKU for a quart, pint or a gallon of paint so why try to fit
them all into the same product? Having them as separate products and
using them as subproducts has definite advantages such as tracking
inventory which couldn't be done if they are listed as order options.

We have the suggestion for weight as part of the order options logged as
an enhancement request already and it will be reviewed to see if it
could be implemented in future versions. But for the time being my
suggestion below would be the easiest solution.

Jim

Rick Steven wrote:
Wouldn't it be a better solution to add a weight parameter to the Order
Options? This is a very common situation in nearly every retail
market - sell by the item or sell by the case. Seems almost a
necessity...

Jim, can you please add this to the shopsite wish list for future
enhancements?

Thanks,
Rick

"jim" <jstavast@xmission.com> wrote in message
news:dvftl4$nv5$1@eval.shopsite.com...
I would use subproducts and a custom template that displays the
subproducts as a dropdown list (like order options) to handle this
situation. That way each product will be ordered with its own weight
and shipping charges will be more correct.

First you would create a main product that describes the paint and
mentions the sizes available. Then you would create subproducts for
each size of container and color combination and assign them to the
main products. The custom template creates the pulldown options for
each of the subproducts assigned to the main product.

You might want to create a main product for each color or size and
just have the other as the pulldown list.

Here is a sample of a template that will create the subproducts as
pulldown options. You will need to do some tweaking to get it to work
for your store but I know of a number of sites that are using modified
versions of this template.

Jim

------------------------------------------
[-- DEFINE SUBPRODUCT --]
# A subproduct in this template is just an option for a pull down list
# Note1: Field1 is used to hold the name used for the pull down list
# such as "Brown, Size 8" instead of the actual name which
# might be "Wing Tip - Brown, Size 8".
# Note2: In order to turn off the master:subproduct naming feature
used
# by ShopSite's shopping cart place
# cross_sell: checked
# in the sbdata.aa file found in the data directory
[--IF PRODUCT.SaleOn--]
option value="[--PRODUCT.RECORDNUMBER--]">[-- PRODUCT.FIELD1 --] [--
PRODUCT.SaleAmount --]</option
[-- ELSE --]
option value="[--PRODUCT.RECORDNUMBER--]">[-- PRODUCT.FIELD1 --] [--
PRODUCT.PRICE --]</option
[-- END_IF --]
[-- END_DEFINE SUBPRODUCT --]

[-- DEFINE PRODUCT --]
CENTER
[--PRODUCT.Name--]
br
[-- IF product.subproduct --]
form action="[-- SHOPPING_CART_URL BASE --]/order.cgi" method=post
input type=hidden name=storeid value=[--Store.id--]
input type=hidden name=dbname value=products
input type=hidden name=function value=add
TABLE
TR><TD
SELECT name=itemnum
[-- LOOP SUBPRODUCTS --]
[-- SUBPRODUCTS --]
[-- END_LOOP SUBPRODUCTS --]
/SELECT></TD><TD
input type=image src="[--
OUTPUT_DIRECTORY_URL --]/media/add_to_cart.gif" width=83 height=20
alt="add_to_cart.gif" hspace=3 vspace=3 border=0 align="bottom"
name="Add to Cart" alt="Add to Cart"
input type=image src="[--
OUTPUT_DIRECTORY_URL --]/media/view_cart.gif" width=71 height=20
alt="view_cart.gif" hspace=3 vspace=3 border=0 align="bottom"
name="View Cart" alt="View Cart"
/TD></TR></TABLE
/form

[-- ELSE --]
# Need to treat as regular product
# this code still needs to be added
[-- END_IF --]
/CENTER

[-- END_DEFINE PRODUCT --]
[-- DEFINE MORE_INFO_PAGE --]
[-- END_DEFINE MORE_INFO_PAGE --]

------------------------------------------

Vince Salese wrote:
We have products that come in different sizes: for instance paint is
available in pints, quarts and gallons. I currently use one product
page and use the Order Options for pricing each size. Here's and
example http://www.ahoycaptain.com/shop/product64.html My problem is
the shipping weight. The pint weighs 1 lbs but the gallon weighs
10lbs. If I set the Product Weight to 10 lbs the customer shooping
for a pint gets tuned off by the high shipping charge. Is there any
way to set a variable weight for a product depending on the choice
he/she makes in the Order Option?

Thanks
Vince

Rick Steven
 


Return to User Forum

Who is online

Users browsing this forum: Bing [Bot] and 165 guests