Re: Price override

This WebDNA talk-list message is from

2004


It keeps the original formatting.
numero = 60096
interpreted = N
texte = Hi Donovan I hope you didn't think I was ignoring this insightful mail, I now undertand what you mean by an orderfile tracking system and you have certainly made a strong arguement for changing the way that I have implemented my discount system . If I were to be honest I would say that I am going to run with the ball on the system that I have built (due to time restrictions etc) but when I have more time I will look into strengthening the integrity of my orderfile and modifying lineitem prices... I may even change it once I have it plugged into all areas & before I go live as realistically I have already put into place all the lineitem calculations I would require to change the prices but I will have to see how it goes ;-) Some interesting ideas on discounting methods also too so thankyou for steering me towards a better way of doing things and giving me food for thought. Oh, one last note... I should also thank John also for his explaination on the matter, between the pair of you I think I have learned another valuable lesson in WebDNA. Cheers Alan ------------------------------------------- Always learning back to front Donovan Brooke wrote: > Alan, > I don't have your code so I don't know your exact situation. > > But if your worried about being able to do multiple discounts, > or, if you have multiple variables that create a discount, know > that you don't need to keep the lineitem price at default, as the > default price is always in the database for reference. > > Discounting is a bit tricky when it comes to protecting against > cracking. I think it was John P. (and probably others) who described > to me a few years ago that discounts work best when they are always > created on the fly from the base price in the .db and the given > variables. They need to be recalculated upon any editing of the cart > and need to be invonurable to back stepping or refreshing. > This may be difficult to understand at first as it was for me. > > I think you are familiar with the modular coding philosophy. > I like to put most all of my discounting in a module (.inc file) > to be referenced when needed. > > For instance, > For one site I worked on, I incorporated all these types of discounts. > > 1. Tabled discount - Each product has a table of prices based on > quantity. > Most every product that is added or changed goes through riggers of > checking against this table (really doesn't slow anything down). > > 2. Date based discount for a certain category of product - > Any of this particular category of product gets discounted when > the date is between a certain range. > > 3. Category discount also based on quantity - > If 6 or more of this category of product is added to the cart, > there is a 15 percent discount to all the lineitems in the cart > that are of that category. > > 4. Subtotal Discount - > A 5 tiered discount based on subtotal. > > 5. Various promotional discounts - > I use the method John described for this type of discount... ie. > "grand opening discount" is what is seen as a line item in the cart. > > > Basically, when the cart is edited, this module is triggered (other than > the subtotal discount) and the orderfile prices are re-caculated based > on category, date, contents of cart and base price of product. > > Having said all that, you may very well be O.K. with the direction you > are going as you may not need a picture perfect orderfile that is saved. > > If you think that you may want access to the orderfile in the future > for "Order history" or future payment through a gateway, its best to > proceed with the philosophy of keeping the orderfile in tact. > > I guess I felt the need to speak that warning because I have had to > charge a significant amount to some of my customers to correct the code > used for the orderfile to impliment new features. > > Donovan > > > > > ------------------------------------------------------------- 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://webdna.smithmicro.com/ Associated Messages, from the most recent to the oldest:

    
  1. Re: Price override ( Alan White 2004)
  2. Re: Price override - solved ( Daryl Mitchell 2004)
  3. Re: Price override - solved ( Stuart Tremain 2004)
  4. Re: Price override ( Donovan Brooke 2004)
  5. Re: Price override ( John Peacock 2004)
  6. Re: Price override ( Alan White 2004)
  7. Re: Price override - solved ( Donovan Brooke 2004)
  8. Re: Price override - solved ( Daryl Mitchell 2004)
  9. Re: Price override ( Donovan Brooke 2004)
  10. Re: Price override - solved ( Daryl Mitchell 2004)
  11. Re: Price override ( Daryl Mitchell 2004)
  12. Re: Price override ( Daryl Mitchell 2004)
  13. Re: Price override ( Donovan Brooke 2004)
  14. Re: Price override ( Alan White 2004)
  15. Re: Price override ( Stuart Tremain 2004)
  16. Re: Price override ( "Sal D'Anna" 2004)
  17. Re: Price override ( Donovan Brooke 2004)
  18. Price override ( Daryl Mitchell 2004)
Hi Donovan I hope you didn't think I was ignoring this insightful mail, I now undertand what you mean by an orderfile tracking system and you have certainly made a strong arguement for changing the way that I have implemented my discount system . If I were to be honest I would say that I am going to run with the ball on the system that I have built (due to time restrictions etc) but when I have more time I will look into strengthening the integrity of my orderfile and modifying lineitem prices... I may even change it once I have it plugged into all areas & before I go live as realistically I have already put into place all the lineitem calculations I would require to change the prices but I will have to see how it goes ;-) Some interesting ideas on discounting methods also too so thankyou for steering me towards a better way of doing things and giving me food for thought. Oh, one last note... I should also thank John also for his explaination on the matter, between the pair of you I think I have learned another valuable lesson in WebDNA. Cheers Alan ------------------------------------------- Always learning back to front Donovan Brooke wrote: > Alan, > I don't have your code so I don't know your exact situation. > > But if your worried about being able to do multiple discounts, > or, if you have multiple variables that create a discount, know > that you don't need to keep the lineitem price at default, as the > default price is always in the database for reference. > > Discounting is a bit tricky when it comes to protecting against > cracking. I think it was John P. (and probably others) who described > to me a few years ago that discounts work best when they are always > created on the fly from the base price in the .db and the given > variables. They need to be recalculated upon any editing of the cart > and need to be invonurable to back stepping or refreshing. > This may be difficult to understand at first as it was for me. > > I think you are familiar with the modular coding philosophy. > I like to put most all of my discounting in a module (.inc file) > to be referenced when needed. > > For instance, > For one site I worked on, I incorporated all these types of discounts. > > 1. Tabled discount - Each product has a table of prices based on > quantity. > Most every product that is added or changed goes through riggers of > checking against this table (really doesn't slow anything down). > > 2. Date based discount for a certain category of product - > Any of this particular category of product gets discounted when > the date is between a certain range. > > 3. Category discount also based on quantity - > If 6 or more of this category of product is added to the cart, > there is a 15 percent discount to all the lineitems in the cart > that are of that category. > > 4. Subtotal Discount - > A 5 tiered discount based on subtotal. > > 5. Various promotional discounts - > I use the method John described for this type of discount... ie. > "grand opening discount" is what is seen as a line item in the cart. > > > Basically, when the cart is edited, this module is triggered (other than > the subtotal discount) and the orderfile prices are re-caculated based > on category, date, contents of cart and base price of product. > > Having said all that, you may very well be O.K. with the direction you > are going as you may not need a picture perfect orderfile that is saved. > > If you think that you may want access to the orderfile in the future > for "Order history" or future payment through a gateway, its best to > proceed with the philosophy of keeping the orderfile in tact. > > I guess I felt the need to speak that warning because I have had to > charge a significant amount to some of my customers to correct the code > used for the orderfile to impliment new features. > > Donovan > > > > > ------------------------------------------------------------- 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://webdna.smithmicro.com/ Alan White

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:

HomePage Caution (1997) Questions To Answer (1997) Are you an WC expert? (1997) emailer on Windows Beta 18 (1997) This is an odd error (2001) [ShowNext] (1997) Protect (1997) emailer and bad addresses (1997) pictures / referrer etc. (1998) [format 40s]text[/format] doesn't work (1997) Secure Server (1997) New WebDNA Solutions ... (1997) error -571 (2004) attachment (2000) summ=T (2003) Creating main- and sub-category search (1997) [math] show=F exists? (1997) .htaccess to make WebDNA serve HTML (2007) Ready,Set; Print! (1999) WebStar5 and realm authentication (2003)