Re: Site / Database Structure

This WebDNA talk-list message is from

2002


It keeps the original formatting.
numero = 42299
interpreted = N
texte = Hi, On Tue, 6 Aug 2002 11:00:35 Kimberly D Ingram wrote: > What exactly do you mean by WebCatalog's category > structure?Maybe he is referring to StoreBuilder? > Are there some docs that I'm missing? > > -----Original Message----- > From: WebCatalog Talk > [mailto:WebDNA-Talk@talk.smithmicro.com]On Behalf Of > Chris List Recipient > Sent: Tuesday, August 06, 2002 10:50 AM > To: WebCatalog Talk > Subject: Re: Site / Database Structure > > Why can't you use WebCatalog's category structure to > create your category > tree and assign the items? I find it very flexible and I > think it would > easily accomodate your 3-tier heirarchy. > > Regarding pricing... sounds like you may be better off > coding each customer > with a markup and then applying that to the price. For > example, wholesale > customers would be 0% and retail customers 100%. I could be way off here, but I would suggest entering the wholesale cost to the store owner in the database and then, depending on their business model, either having a markup to create the public wholesale and retail prices or just enter the actual otherwise calculated retail and wholesale prices.This way, having the actual cost to the store owner in the database allows any future discount calculations to make sure the selling price does not go under the actual cost of goods. You could also have a factor in your calculations to ensure there is at least a minimum markup on all sales.So I would end up with 2 prices per product in the database. You could also have a database such as:productCat productID baskets oreos seasonal oreosWhere the 'oreos' is replaced by the product code for oreos and the baskets is your actual basket code.This way you can do a quick search with (numfound) (yes, I know it should be square brackets, but typing them on this German keyboard is a pain!!!) to report results for that category. Also makes it easy to manage. While this doesn't quite answer your original question, I think this will give you an idea to make the site more safe for your customer.I imagine we have all heard of the stories of the $50.00 computers that were supposed to sell for $5,000.00 and so forth.And of course these cost of goods prices would be hidden from all but those that really need to see them.Hope this helps,Dale >Apply > the markup to > the price when it is added to the cart. This will give you > much better > flexibility later on. > > -Chris > (snip)Dale------------------------------------------------------------- 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:

    
  1. Re: Site / Database Structure (Chris List Recipient 2002)
  2. Re: Site / Database Structure (John Peacock 2002)
  3. Re: Site / Database Structure (Robert Wade 2002)
  4. Re: Site / Database Structure (dale 2002)
  5. Re: Site / Database Structure (Kimberly D Ingram 2002)
  6. Re: Site / Database Structure (Chris List Recipient 2002)
  7. Site / Database Structure (Kimberly D Ingram 2002)
Hi, On Tue, 6 Aug 2002 11:00:35 Kimberly D Ingram wrote: > What exactly do you mean by WebCatalog's category > structure?Maybe he is referring to StoreBuilder? > Are there some docs that I'm missing? > > -----Original Message----- > From: WebCatalog Talk > [mailto:WebDNA-Talk@talk.smithmicro.com]On Behalf Of > Chris List Recipient > Sent: Tuesday, August 06, 2002 10:50 AM > To: WebCatalog Talk > Subject: Re: Site / Database Structure > > Why can't you use WebCatalog's category structure to > create your category > tree and assign the items? I find it very flexible and I > think it would > easily accomodate your 3-tier heirarchy. > > Regarding pricing... sounds like you may be better off > coding each customer > with a markup and then applying that to the price. For > example, wholesale > customers would be 0% and retail customers 100%. I could be way off here, but I would suggest entering the wholesale cost to the store owner in the database and then, depending on their business model, either having a markup to create the public wholesale and retail prices or just enter the actual otherwise calculated retail and wholesale prices.This way, having the actual cost to the store owner in the database allows any future discount calculations to make sure the selling price does not go under the actual cost of goods. You could also have a factor in your calculations to ensure there is at least a minimum markup on all sales.So I would end up with 2 prices per product in the database. You could also have a database such as:productCat productID baskets oreos seasonal oreosWhere the 'oreos' is replaced by the product code for oreos and the baskets is your actual basket code.This way you can do a quick search with (numfound) (yes, I know it should be square brackets, but typing them on this German keyboard is a pain!!!) to report results for that category. Also makes it easy to manage. While this doesn't quite answer your original question, I think this will give you an idea to make the site more safe for your customer.I imagine we have all heard of the stories of the $50.00 computers that were supposed to sell for $5,000.00 and so forth.And of course these cost of goods prices would be hidden from all but those that really need to see them.Hope this helps,Dale >Apply > the markup to > the price when it is added to the cart. This will give you > much better > flexibility later on. > > -Chris > (snip)Dale------------------------------------------------------------- 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/ dale

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:

Summary search -- speed (1997) (1997) Problem displaying search result (1997) autocommit problem (1998) Re1000001: Setting up shop (1997) Summary layout (1997) Summing fields (1997) Passing info in [Addlineitem] (1997) Multiple prices (1997) Emailer (1997) Database of Tax Rates? (1997) Return records from another (1997) Yet another frames Question (1999) addlineitems (2003) HomePage Caution (1997) Up and running ... at last !! (1997) SOLUTION.... Balancing randomness (2000) View Source from cache (1997) Searching for all records (1998) WebCat2: Items xx to xx shown, etc. (1997)