Re: Size/Color Options
This WebDNA talk-list message is from 2002
It keeps the original formatting.
numero = 43475
interpreted = N
texte = In order to make this work with WebDNA's shopping cart routines (with minimal changes - there are always lots of different ways to do things) you must1. Designate a single database to contain your SKU, PRICE - in your case, this is probably store_options.db - products without size or color would have those fields empty. Add a PRODUCT_SKU field that can relate the record in the options database to the general information in the products database.2. Make sure all [addlineitems] etc. use the product_options database. You can place the product name in a TEXTA-E field using lookup when the product is added so that the shopping cart display doesn't have to do the lookup if you'd like.This is just one idea - there are lots of variations that really depend upon all the conditions necessary to put together your store.John.>John, > >My client provided a list of products/SKUs where some of products have >options (size/color) and some don't. Here's the strategy I've taken thus far >to set this up: > >1. I have a store.db database containing all the products listed with a >PRODUCTID, TITLE, DESCRIPTION, CATEGORY, PRICE, SIZES, COLORS, etc. >2. I also have a store_options.db database containing PRODUCTID, SKU, TYPE >OPTION, PRICE, ORDER, etc. >3. When adding products without any options, the client will input all the >information as normal, and the PRODUCTID will serve as the SKU. >4. When adding products with options, the client will input all the general >information about the product then add size/color options with their >respective SKUs. > >Here's a couple of abbreviated examples: > >*** SKU list from client *** >SKU Size Color Description >----------------------------------------- >743341 M Black Men's Polo Shirt >943340 L Black Men's Polo Shirt >543342 XL Black Men's Polo Shirt >343343 XXL Black Men's Polo Shirt >843345 M Navy Men's Polo Shirt >143344 L Navy Men's Polo Shirt >643346 XL Navy Men's Polo Shirt >443347 XXL Navy Men's Polo Shirt > > >*** Store.db *** >ProductID Title Price Sizes Colors >----------------------------------------------------------- >84458 Leather Purse 79.95 F F >43340 Men's Polo Shirt 29.95 T T > > >*** Store_options.db *** >ProductID SKU Size Color Price Order >----------------------------------------------------------------- >43340 743341 M Black 29.95 1 >43340 743340 L Black 29.95 2 >43340 743342 XL Black 31.95 3 >43340 743343 XXL Black 33.95 4 > > >I want to list the sizes and colors in separate pulldown menus: > >Select a size... >---------------- >M >L >XL >XXL > >Select a color... >----------------- >Black >Navy > > >...then check the database to see which SKU fits the size/color combination >selected by the customer and add it to the cart. > > > >On 9/17/02 1:03 AM, John Hill
wrote: > >> If you have a store structure similar to storebuilder this can be done quite >> easily. Let me know if you're still working on this problem and I'll post more >> info. Thanks. >> >> John. >> >>> Listmates, >>> >>> Happy Friday the 13th! >>> >>> I'm sure my question has been covered before, but I'm in a serious time >>> crunch, and I need some quick pointers to get a new store up and running. >>> So, bear with me please. >>> >>> My client has several types of products to sell including t-shirts. Each >>> size/color variation has it's own SKU, but I don't want to list every >>> variation on the category page. I would like to see a single listing for a >>> Friday the 13th shirt, then the detail page will include two pull-down >>> menus - size and color. >>> >>> >>> Category Page = T-Shirts >>> -------------------------------------- >>> Item - 1105 - Friday the 13th shirt >>> Item - 1231 - Jacksonville Jaguars shirt >>> Item - 1314 - I love my dog shirt >>> >>> >>> Detail Page = I love my dog shirt >>> -------------------------------------- >>> Item - 1314 >>> Desc. - I love my dog shirt >>> Colors - Red, Blue, Gray, White >>> Sizes - M, L, XL, XXL >>> >>> >>> SKUs for item 1314 >>> -------------------------------------- >>> Red/M = 131401 >>> Red/L = 131403 >>> Red/XL = 131405 >>> Red/XXL = 131407 >>> Blue/M = 131421 >>> Blue/L = 131423 >>> Blue/XL = 131425 >>> Blue/XXL = 131427 >>> Gray/M = 131431 >>> Gray/L = 131433 >>> Gray/XL = 131435 >>> Gray/XXL = 131437 >>> White/M = 131441 >>> White/L = 131443 >>> White/XL = 131445 >>> White/XXL = 131447 >>> >>> >>> Can someone PLEASE give me a few quick pointers to get this thing going? > > >--------------------------------------------------------------------- >Clint Davis >Webmaster / Interactive Media Specialist >Gray Loon Marketing Group, Inc. http://www.grayloon.com >204 Main Street | Evansville, IN 47708 | Phone:812-422-9999 >--------------------------------------------------------------------- > > >------------------------------------------------------------- >This message is sent to you because you are subscribed to > the mailing list . >To unsubscribe, E-mail to: >To switch to the DIGEST mode, E-mail to >Web Archive of this list is at: http://search.smithmicro.com/-- --------------------------------- John A. Hill Oak Hill Software Website Development/Consulting john@oakhillsoftware.com------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://search.smithmicro.com/
Associated Messages, from the most recent to the oldest:
In order to make this work with WebDNA's shopping cart routines (with minimal changes - there are always lots of different ways to do things) you must1. Designate a single database to contain your SKU, PRICE - in your case, this is probably store_options.db - products without size or color would have those fields empty. Add a PRODUCT_SKU field that can relate the record in the options database to the general information in the products database.2. Make sure all [addlineitems] etc. use the product_options database. You can place the product name in a TEXTA-E field using lookup when the product is added so that the shopping cart display doesn't have to do the lookup if you'd like.This is just one idea - there are lots of variations that really depend upon all the conditions necessary to put together your store.John.>John, > >My client provided a list of products/SKUs where some of products have >options (size/color) and some don't. Here's the strategy I've taken thus far >to set this up: > >1. I have a store.db database containing all the products listed with a >PRODUCTID, TITLE, DESCRIPTION, CATEGORY, PRICE, SIZES, COLORS, etc. >2. I also have a store_options.db database containing PRODUCTID, SKU, TYPE >OPTION, PRICE, ORDER, etc. >3. When adding products without any options, the client will input all the >information as normal, and the PRODUCTID will serve as the SKU. >4. When adding products with options, the client will input all the general >information about the product then add size/color options with their >respective SKUs. > >Here's a couple of abbreviated examples: > >*** SKU list from client *** >SKU Size Color Description >----------------------------------------- >743341 M Black Men's Polo Shirt >943340 L Black Men's Polo Shirt >543342 XL Black Men's Polo Shirt >343343 XXL Black Men's Polo Shirt >843345 M Navy Men's Polo Shirt >143344 L Navy Men's Polo Shirt >643346 XL Navy Men's Polo Shirt >443347 XXL Navy Men's Polo Shirt > > >*** Store.db *** >ProductID Title Price Sizes Colors >----------------------------------------------------------- >84458 Leather Purse 79.95 F F >43340 Men's Polo Shirt 29.95 T T > > >*** Store_options.db *** >ProductID SKU Size Color Price Order >----------------------------------------------------------------- >43340 743341 M Black 29.95 1 >43340 743340 L Black 29.95 2 >43340 743342 XL Black 31.95 3 >43340 743343 XXL Black 33.95 4 > > >I want to list the sizes and colors in separate pulldown menus: > >Select a size... >---------------- >M >L >XL >XXL > >Select a color... >----------------- >Black >Navy > > >...then check the database to see which SKU fits the size/color combination >selected by the customer and add it to the cart. > > > >On 9/17/02 1:03 AM, John Hill wrote: > >> If you have a store structure similar to storebuilder this can be done quite >> easily. Let me know if you're still working on this problem and I'll post more >> info. Thanks. >> >> John. >> >>> Listmates, >>> >>> Happy Friday the 13th! >>> >>> I'm sure my question has been covered before, but I'm in a serious time >>> crunch, and I need some quick pointers to get a new store up and running. >>> So, bear with me please. >>> >>> My client has several types of products to sell including t-shirts. Each >>> size/color variation has it's own SKU, but I don't want to list every >>> variation on the category page. I would like to see a single listing for a >>> Friday the 13th shirt, then the detail page will include two pull-down >>> menus - size and color. >>> >>> >>> Category Page = T-Shirts >>> -------------------------------------- >>> Item - 1105 - Friday the 13th shirt >>> Item - 1231 - Jacksonville Jaguars shirt >>> Item - 1314 - I love my dog shirt >>> >>> >>> Detail Page = I love my dog shirt >>> -------------------------------------- >>> Item - 1314 >>> Desc. - I love my dog shirt >>> Colors - Red, Blue, Gray, White >>> Sizes - M, L, XL, XXL >>> >>> >>> SKUs for item 1314 >>> -------------------------------------- >>> Red/M = 131401 >>> Red/L = 131403 >>> Red/XL = 131405 >>> Red/XXL = 131407 >>> Blue/M = 131421 >>> Blue/L = 131423 >>> Blue/XL = 131425 >>> Blue/XXL = 131427 >>> Gray/M = 131431 >>> Gray/L = 131433 >>> Gray/XL = 131435 >>> Gray/XXL = 131437 >>> White/M = 131441 >>> White/L = 131443 >>> White/XL = 131445 >>> White/XXL = 131447 >>> >>> >>> Can someone PLEASE give me a few quick pointers to get this thing going? > > >--------------------------------------------------------------------- >Clint Davis >Webmaster / Interactive Media Specialist >Gray Loon Marketing Group, Inc. http://www.grayloon.com >204 Main Street | Evansville, IN 47708 | Phone:812-422-9999 >--------------------------------------------------------------------- > > >------------------------------------------------------------- >This message is sent to you because you are subscribed to > the mailing list . >To unsubscribe, E-mail to: >To switch to the DIGEST mode, E-mail to >Web Archive of this list is at: http://search.smithmicro.com/-- --------------------------------- John A. Hill Oak Hill Software Website Development/Consulting john@oakhillsoftware.com------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://search.smithmicro.com/
John Hill
DOWNLOAD WEBDNA NOW!
Top Articles:
Talk List
The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...
Related Readings:
SiteGuard Admin Feature ? (1997)
SSL and reg web* (1997)
Converting characters to numbers ... (1997)
Return records from another (1997)
Change in Host? (1999)
Erotic Sites (1997)
iis 4.0 (1997)
Roundup function? (1997)
Resume Catalog ? (1997)
webcat NT (1998)
[isfolder] and [filename] (1997)
Look out kiwis! (2003)
Search returns all, not 20 (1997)
Re:Still More on EudoraPro Email (1998)
Practice runs ? (1997)
show all problem (1997)
[append] vs. [appendfile] delta + question? (1997)
Roundup function? (1997)
Time Remaining? (1998)
Moment of Thanks (1997)