Re: [ic] Variable/Attribute Pricing

["Nathan Wiger" <nate@nateware.com>]

Doug Alcorn (doug@lathi.net) wrote:
>
> Nathan Wiger (nate@nateware.com) wrote:
>
> > So, when creating/editing an item, a person would say:
> >
> >    Price:  25.00
> >    Size:   S, M: -$5, L: +$10, XL: +$15
> >    Color:  Blue, Green, Red: +$35
> >
> >[snip]
> >
> > Then, I wrote a simple UserTag routine called "nw_modprice" which was
> > sensitive to the colon, and added/subtracted the appropriate values from
the
> > base price. The part that caught me was I had to set the following
variables
> > in catalog.cfg:
> >
> >    CommonAdjust  [nw_modprice] ;:price
> >    PriceField    no_price
> >
>
> This is probably the nicest solution I've seen to this problem.
> Congratulations.

Cool, thanks for the compliment! :-)

So, would you (and others) think something like this should be integrated
into Interchange? I'm thinking of something like an option such as:

   UseModifier         size color
   UseModifierPricing  1

Where the second option would turn on the colon-sensitive pricing thingy
similar to what I wrote. If not set, then Interchange's current behavior
could be maintained (it's off by default). Or, maybe there's a new option to
CommonAdjust, which may be more appropriate.

Mike Heins provided some good feedback on the fact that this is a problem
which is solvable with CommonAdjust (as I did). My only counterpoint would
be that this is a frequently-visited issue, and IMO Interchange's current
pricing db scheme is not up to par with other e-commerce offerings (at least
out-of-the-box, though it is very flexible).

Thoughts?

-Nate

--
Nathan Wiger
Systems Integrator and Perl Hacker
Nateware, Inc. -- www.nateware.com