Re: how to do multiple prices/item?
This WebDNA talk-list message is from 1998
It keeps the original formatting.
numero = 17351
interpreted = N
texte = Sandy,Thanks, I took a look, and see what you needed to do with the different variations (essentially, adding a delta or change in price to the base price).But I (think) I need something simpler. At least I hope so. ;-)Basically, I would like the customer to be able to search and select items that may have one or more SKUS associated with them. The CD vs. cassette format that I mentioned, for example. The photo and product copy would be the same for both formats, and the customer simply chooses the desired format (SKU level format and price) at the product detail.tmpl level.I recall a thread from long ago where someone suggested an item db with SKU info associated with each item but I couldn't find it in the Pac Coast archives. Anyone recall that thread? Or can anyone provide some insight into alternative ways to skin this pricing cat? TIA,Dale dstokdyk@dvs.mv.com>Look at www.musicianstore.com. I did this for the cables, drumsticks, >cymbals and software. Different items may have different prices for >specific options, or perhaps just an option with no price delta. >Basically you need to add an option.db related to inventory.db by SKU. >Each option has its own SKU, which may have a price delta with it. For >cables, there can be up to three options chosen, so there's three >option.dbs. > >The option fields are hidden if that item doesn't have options. > >It gets quite tricky carrying it through the shopping carts and figuring >how much is being saved from list. But it can be done. > >Sandy > > >>Hi all, am seeking advice/tips on how to add the ability to offer multiple >>price points on an item. Let me describe where I am and what I'd like to go >>briefly... >> >>CURRENT: one sku = one price (same as General Store example) >> >>DESIRE: one item may have several versions with different prices >> >> >> Example A: music item has: >> * CD version ($15.99) and >> * casette version ($9.99) >> >> >> Example B: jewelry item has: >> >> * silver version >> -- sizes A-B ($30) >> -- sizes C-D ($35) >> >> * 14K gold version >> -- sizes A-B ($150) >> -- sizes C-D ($175) >> >> * 18K gold version >> -- sizes A-B ($225) >> -- sizes C-D ($250) >> >> >> I know it would be easy to assign a different SKU to each one (and >>shoppers would see multiple versions in the search results), but I'd prefer >>to have searches return the item then let shoppers choose the particular >>version/price when viewing the details page. >> >>TIA for advice and tips, >> >>Dale Stokdyk >>World Romance >>Romantic Gifts from Around the World >>http://www.me2u.com >> >> >> >> >> >>
Associated Messages, from the most recent to the oldest:
Sandy,Thanks, I took a look, and see what you needed to do with the different variations (essentially, adding a delta or change in price to the base price).But I (think) I need something simpler. At least I hope so. ;-)Basically, I would like the customer to be able to search and select items that may have one or more SKUS associated with them. The CD vs. cassette format that I mentioned, for example. The photo and product copy would be the same for both formats, and the customer simply chooses the desired format (SKU level format and price) at the product detail.tmpl level.I recall a thread from long ago where someone suggested an item db with SKU info associated with each item but I couldn't find it in the Pac Coast archives. Anyone recall that thread? Or can anyone provide some insight into alternative ways to skin this pricing cat? TIA,Dale dstokdyk@dvs.mv.com>Look at www.musicianstore.com. I did this for the cables, drumsticks, >cymbals and software. Different items may have different prices for >specific options, or perhaps just an option with no price delta. >Basically you need to add an option.db related to inventory.db by SKU. >Each option has its own SKU, which may have a price delta with it. For >cables, there can be up to three options chosen, so there's three >option.dbs. > >The option fields are hidden if that item doesn't have options. > >It gets quite tricky carrying it through the shopping carts and figuring >how much is being saved from list. But it can be done. > >Sandy > > >>Hi all, am seeking advice/tips on how to add the ability to offer multiple >>price points on an item. Let me describe where I am and what I'd like to go >>briefly... >> >>CURRENT: one sku = one price (same as General Store example) >> >>DESIRE: one item may have several versions with different prices >> >> >> Example A: music item has: >> * CD version ($15.99) and >> * casette version ($9.99) >> >> >> Example B: jewelry item has: >> >> * silver version >> -- sizes A-B ($30) >> -- sizes C-D ($35) >> >> * 14K gold version >> -- sizes A-B ($150) >> -- sizes C-D ($175) >> >> * 18K gold version >> -- sizes A-B ($225) >> -- sizes C-D ($250) >> >> >> I know it would be easy to assign a different SKU to each one (and >>shoppers would see multiple versions in the search results), but I'd prefer >>to have searches return the item then let shoppers choose the particular >>version/price when viewing the details page. >> >>TIA for advice and tips, >> >>Dale Stokdyk >>World Romance >>Romantic Gifts from Around the World >>http://www.me2u.com >> >> >> >> >> >>
Dale Stokdyk
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:
Shipcost Prob solved, new one arises (1998)
Just Testing (1997)
Search Engine questions ... (2002)
Fwd: Problems with Webcatalog Plug-in (1997)
all records returned. (1997)
PCS Frames-Default page is solution! (1997)
default error on NT? (1997)
Local redirects ... (2005)
Basics of tcpconnect (2006)
using showpage and showcart commands (1996)
This list needs a digest: rant, rave... (1997)
Weird problems with [SHOWIF]s (1997)
Reversed words (1997)
transferring values (1998)
emailer w/F2 (1997)
Version f1 status (1997)
PSC recommends what date format yr 2000??? (1997)
Interpreting WebDNA tags (2004)
Sorting when searching with grouped fields (2002)
[OT] Happy Turkey Day! (2003)