Re: Discounts: Buy One, Get One =?ISO-8859-1?Q?99=A2?=

This WebDNA talk-list message is from

2004


It keeps the original formatting.
numero = 55463
interpreted = N
texte = On 1/13/04 1:45 PM, "Donovan Brooke" wrote: > Clint Davis wrote: >=20 >> Well, the more I ask the account executive about this, the more complex = it >> gets. Here's the basic structure: >>=20 >> 1. Lineitems with quantity greater than one are split into as many linei= tems >> as the quantity. >> 2. Is there more than one lineitem? >> a. If there is, is there already a discounted item? >> i. If there is, check out. >> ii. If there isn't, is the promotion code correct? >> 1. If it is, change the price of the least expensive item to= 99=A2 >> and check out. >> 2. If it isn't, check out. >> b. If there isn't, is there already a discounted item? >> i. If there is, reset it's price by doing a [lookup]. >> ii. If there isn't, check out. >=20 > :-) >=20 > regarding 2aii: depending on how your ordering flow goes, you might not h= ave > to go through as much trouble as above. I would incorporate a system simi= lar > to above IF you always need the correct values the cart each time its edi= ted > (for example, the cart is on the same page as the results). In this case,= I > would incorporate [setlineitem], [switch] and a flag variable that initia= tes > code depending on "deleting" or "updateing" (editing). >=20 > If you don't need the correct values until the invoice page then I would = do > the promotion code lookup first. In this case, you wouldn't have to reset= the > price in the above way because the prices would always be reset dynamical= ly IF > the code is valid. If the code is not valid, then you don't have to mess= with > any of the dicounting stuff (hide it entirely to save processing power). On my shopping cart page, I have a summary of the cart contents with the option of updating quantities and removing lineitems. So, I need to do the checking each time the page is accessed to make sure customers aren't try t= o cheat. ------------------------------------------------------------- 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: Discounts: Buy One, Get One =?ISO-8859-1?Q?99=A2?= ( Clint Davis 2004)
  2. Re: Discounts: Buy One, Get One =?ISO-8859-1?Q?99=A2?= ( Donovan Brooke 2004)
  3. Re: Discounts: Buy One, Get One =?ISO-8859-1?Q?99=A2?= ( Clint Davis 2004)
  4. Re: Discounts: Buy One, Get One =?ISO-8859-1?Q?99=A2?= ( Donovan Brooke 2004)
  5. Re: Discounts: Buy One, Get One =?ISO-8859-1?Q?99=A2?= ( Clint Davis 2004)
  6. Re: Discounts: Buy One, Get One =?ISO-8859-1?Q?99=A2?= ( Donovan Brooke 2004)
  7. Discounts: Buy One, Get One =?ISO-8859-1?Q?99=A2?= ( Clint Davis 2004)
On 1/13/04 1:45 PM, "Donovan Brooke" wrote: > Clint Davis wrote: >=20 >> Well, the more I ask the account executive about this, the more complex = it >> gets. Here's the basic structure: >>=20 >> 1. Lineitems with quantity greater than one are split into as many linei= tems >> as the quantity. >> 2. Is there more than one lineitem? >> a. If there is, is there already a discounted item? >> i. If there is, check out. >> ii. If there isn't, is the promotion code correct? >> 1. If it is, change the price of the least expensive item to= 99=A2 >> and check out. >> 2. If it isn't, check out. >> b. If there isn't, is there already a discounted item? >> i. If there is, reset it's price by doing a [lookup]. >> ii. If there isn't, check out. >=20 > :-) >=20 > regarding 2aii: depending on how your ordering flow goes, you might not h= ave > to go through as much trouble as above. I would incorporate a system simi= lar > to above IF you always need the correct values the cart each time its edi= ted > (for example, the cart is on the same page as the results). In this case,= I > would incorporate [setlineitem], [switch] and a flag variable that initia= tes > code depending on "deleting" or "updateing" (editing). >=20 > If you don't need the correct values until the invoice page then I would = do > the promotion code lookup first. In this case, you wouldn't have to reset= the > price in the above way because the prices would always be reset dynamical= ly IF > the code is valid. If the code is not valid, then you don't have to mess= with > any of the dicounting stuff (hide it entirely to save processing power). On my shopping cart page, I have a summary of the cart contents with the option of updating quantities and removing lineitems. So, I need to do the checking each time the page is accessed to make sure customers aren't try t= o cheat. ------------------------------------------------------------- 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/ Clint Davis

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:

HELP WITH DATES (1997) & Aftermath (1999) [SQL] - COUNT, SUM retrieval (2000) WebStar Questions ... (2000) back button problem (1999) supressing math results (1997) Trouble with Category search (2000) WebCatalog for guestbook ? (1997) Show if time tags (1997) Date problems-more (1997) WebTen and WebCat (1997) Sorting by date (1997) AE aware WebCatalog.acgi? (1997) how to do multiple prices/item? (1998) CSS positioning!!! (2001) Summing fields (1997) [BoldWords WordList]Any Text[/BoldWords] (2000) Checking for blank form fields (sort of...) (1998) [ShowIf] if the varieable exists (1998) Explorer oddities (1997)