Re: Size/Color Options
This WebDNA talk-list message is from 2002
It keeps the original formatting.
numero = 43396
interpreted = N
texte = On 9/13/02 2:13 PM, Clint Davis
wrote:> Unfortunately, the example I gave below was pulled directly from my a$$. I > have idea how the SKUs are organized in the client's actual inventory right > now. I'll try to find out ASAP to see how complicated this is going to get. > > > > > On 9/13/02 12:01 PM, John Peacock wrote: > >> Clint Davis wrote: >>> >>> 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 >>> >>> >> >> It would appear that the following relations hold >> >> Color Code >> Red 0 >> Blue 2 >> Gray 3 >> White 4 >> >> Size Code >> M 1 >> L 3 >> XL 5 >> XXL 7 >> >> so store only the base SKU (in your example 1314) in the product database (so >> there is only a single record for each type/style of shirt). When you add a >> line item to the shopping cart, use an [addlineitem] context on the target >> page which combines the SKU, COLOR, and SIZE into the SKU that is stored in >> the cart. >> Use a formulas database to calculate the price based on the style and size >> (being the first 4 characters and last 1 character of the cart SKU). I'm >> assuming that color is not a price differential. >> >> Be thankful that your client has sensible SKU's, or else you would be >> hard-pressed to do it this way... >> >> John > > We do something of the sort for the St. Louis Rams. But we don't worry about the sku's until we export the orders to the customer. We maintain a database of sku's and a database of options. The options can affect price, but regardless we have a base sku like 1234 for products without options they have a sku of 1234999. If the customer orders something with an option then they order 1234 with the option of 010. When this gets exported to the accounting program its gets appended together like so 1234010. But we maintain the option as a separate modifier of the base sku. See store.stlouisrams.com for the view, but you don't see anything there relating to the sku. Robert Minor Director of Internet Services ------------------------------------------------------------ Cybermill Communications http://www.cybermill.com http://www.merchantmaker.comProviding Ecommerce and interactive website development and hosting services on Macintosh, Windows NT, Unix, and AS/400.All your websites are belong to us! ------------------------------------------------------------- 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:
On 9/13/02 2:13 PM, Clint Davis wrote:> Unfortunately, the example I gave below was pulled directly from my a$$. I > have idea how the SKUs are organized in the client's actual inventory right > now. I'll try to find out ASAP to see how complicated this is going to get. > > > > > On 9/13/02 12:01 PM, John Peacock wrote: > >> Clint Davis wrote: >>> >>> 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 >>> >>> >> >> It would appear that the following relations hold >> >> Color Code >> Red 0 >> Blue 2 >> Gray 3 >> White 4 >> >> Size Code >> M 1 >> L 3 >> XL 5 >> XXL 7 >> >> so store only the base SKU (in your example 1314) in the product database (so >> there is only a single record for each type/style of shirt). When you add a >> line item to the shopping cart, use an [addlineitem] context on the target >> page which combines the SKU, COLOR, and SIZE into the SKU that is stored in >> the cart. >> Use a formulas database to calculate the price based on the style and size >> (being the first 4 characters and last 1 character of the cart SKU). I'm >> assuming that color is not a price differential. >> >> Be thankful that your client has sensible SKU's, or else you would be >> hard-pressed to do it this way... >> >> John > > We do something of the sort for the St. Louis Rams. But we don't worry about the sku's until we export the orders to the customer. We maintain a database of sku's and a database of options. The options can affect price, but regardless we have a base sku like 1234 for products without options they have a sku of 1234999. If the customer orders something with an option then they order 1234 with the option of 010. When this gets exported to the accounting program its gets appended together like so 1234010. But we maintain the option as a separate modifier of the base sku. See store.stlouisrams.com for the view, but you don't see anything there relating to the sku. Robert Minor Director of Internet Services ------------------------------------------------------------ Cybermill Communications http://www.cybermill.com http://www.merchantmaker.comProviding Ecommerce and interactive website development and hosting services on Macintosh, Windows NT, Unix, and AS/400.All your websites are belong to us! ------------------------------------------------------------- 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/
Bob Minor
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:
Banner Ad (1998)
WebCat2b13MacPlugin - [math][date][/math] problem (1997)
Nested tags count question (1997)
Sendmail strangie (2002)
Moving Files (2000)
Sorting by type=date (1999)
missing records (1998)
Re:Can this be done? (1997)
WebCat2 beta 11 - new prefs ... (1997)
Error & Problem (1997)
Formatting a .txt file (1998)
wierd [cart] action! (1997)
[LOOKUP] (1997)
[cart]= (2004)
Bug Report, maybe (1997)
[WebDNA] HTTP Streaming -- impossible? (2010)
WebDelivery downloads alias, not original ? (1997)
WebCat2b13 Mac plugin - [sendmail] and checkboxes (1997)
MacAuthorize hub, no modal password dialog? (1997)
RE: Emailer prefs in two places ... (1997)