Re: how to do multiple prices/item?

This WebDNA talk-list message is from

1998


It keeps the original formatting.
numero = 17364
interpreted = N
texte = It is pretty easy to have a child table detail.db that is related to the inventory.db by a variable. Then all items sharing a description and photo would display the same information. This is also done for all items in musicianstore.com. The cables, etc. have one description and photo that match many different SKUs of cables of different lengths, etc. The hard part is deciding how the items are searched. What is the master database that is actually searched? It sounds like you want the detail.db to be the parent and inventory.db to be the child database. Then inventory.db, the child, would be used for the shoppingcarts item management (where SKU used for pricing, removing, adding to cart).You would have a field in your detail table called detailkey that is the unique identifier for that table. Then each item in inventory.db would also have a detailkey field that related to its description.Your customers would search the detail.db for items matching their descriptions. You'd have an embedded search under the description (from detail.db) for the inventory.db SKU and pricing information that is available. Because the majority of our inventory doesn't have options available, we kept inventory.db as the parent and just added option.db for the 3000 or so items that are customizable. Good luck! Hope this makes sense (my brain was on vacation yesterday and I hope it is on duty again today).Sandy>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:

    
  1. Re: how to do multiple prices/item? (Sandra L. Pitner 1998)
  2. Re: how to do multiple prices/item? (Dale Stokdyk 1998)
  3. Re: how to do multiple prices/item? (Sandra L. Pitner 1998)
  4. how to do multiple prices/item? (Dale Stokdyk 1998)
It is pretty easy to have a child table detail.db that is related to the inventory.db by a variable. Then all items sharing a description and photo would display the same information. This is also done for all items in musicianstore.com. The cables, etc. have one description and photo that match many different SKUs of cables of different lengths, etc. The hard part is deciding how the items are searched. What is the master database that is actually searched? It sounds like you want the detail.db to be the parent and inventory.db to be the child database. Then inventory.db, the child, would be used for the shoppingcarts item management (where SKU used for pricing, removing, adding to cart).You would have a field in your detail table called detailkey that is the unique identifier for that table. Then each item in inventory.db would also have a detailkey field that related to its description.Your customers would search the detail.db for items matching their descriptions. You'd have an embedded search under the description (from detail.db) for the inventory.db SKU and pricing information that is available. Because the majority of our inventory doesn't have options available, we kept inventory.db as the parent and just added option.db for the 3000 or so items that are customizable. Good luck! Hope this makes sense (my brain was on vacation yesterday and I hope it is on duty again today).Sandy>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 >>> >>> >>> >>> >>> >>> > > > > Sandra L. Pitner

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:

off topic fetch vs PCS photomaster (1997) date (1999) Bug? (1997) serial number generation (1997) SERIAL NUMBER PROBLEM *AGAIN*!!! (1998) Domain name & WebDNA 5.0 (2003) Formating Tables w/[founditems] (1998) [WebDNA] Receive JSON POST (2019) WebCatalog for Postcards ? (1997) Log-in Scheme (2003) Need relative path explanation (1997) Storebuilder Seems to have just died (2003) can WC render sites out? (1997) RE: [sendmail]- bcc? (1998) Instructions for Digest (1997) WebCat2b15MacPlugin - showing [math] (1997) Sending E-mail (1997) Can't use old cart file (was One more try) (1997) Problem with broken images (2004) 4.5.1 on Panther? (2004)