# confused by logic....would love a hand.

I have an interesting problem that I'm trying to wrap my head around.

I'm creating a subscription based service that will charge extra for
premium products. What does this mean?...ok, let's say I've created a
subscription based service that allows you to get any 5 standard
magazines of your choice shipped to you per month, where a standard
magazine is any magazine that costs less than \$7.99. Magazines more
expensive than that are considered premium.

Now if a subscriber selects a standard magazine, this is fine, the
order is created and the magazine is shipped, this order falls within
the terms of the subscription. However, if the subscriber selects a
premium magazIne, then I have to charge them the difference of the
magazine price from 7.99. So if they order a magazine worth 9.99, I
have to charge them 2 bucks, etc etc.

Now, I can't figure out where to put this logic check. What I've
the price, if it's standard, send to the create method(is that even
possible??). If the magazine price is high, I redirect to a confirm
page then back to the create method....this means that I have to store
my order in a session, right? Which just seems like over kill.

Has anyone had a problem like this before? How did you go about
solving it?

I have an interesting problem that I'm trying to wrap my head around.

I'm creating a subscription based service that will charge extra for
premium products. What does this mean?...ok, let's say I've created a
subscription based service that allows you to get any 5 standard
magazines of your choice shipped to you per month, where a standard
magazine is any magazine that costs less than \$7.99. Magazines more
expensive than that are considered premium.

Now if a subscriber selects a standard magazine, this is fine, the
order is created and the magazine is shipped, this order falls within
the terms of the subscription. However, if the subscriber selects a
premium magazIne, then I have to charge them the difference of the
magazine price from 7.99. So if they order a magazine worth 9.99, I
have to charge them 2 bucks, etc etc.

Now, I can't figure out where to put this logic check. What I've
the price, if it's standard, send to the create method(is that even
possible??). If the magazine price is high, I redirect to a confirm
page then back to the create method....this means that I have to store
my order in a session, right? Which just seems like over kill.

Add it to the order in the normal way but mark it as not confirmed,
then get the user to confirm it (or not).

Colin

Oh, good idea....Thanks Colin, tunnel-vision sucks, I'd have never
thought of that.

Oh, good idea....Thanks Colin, tunnel-vision sucks, I'd have never
thought of that.

Don't forget that if he does not explcitly accept or reject it (just
leaves the confirmation page for example) the record will be left in
the database unconfirmed. You must be able to cope with that when he
next comes along.