[Alan]

Hello Boomer.

We only have about 20 custom-tailored items in 1 category, so I didn't really want to run extra sql queries to lag out the site. Once customers gos into .php mode, our site will feel a little bit sluggish.

But still, would product options be better for it anyway?

If it's not too complicated to pass extra "non-param" "non product options" to the cart, then email notifications, I'd like to try it out.
But I'm open to suggestions!

*EDIT* I remember why I would want to do that now, because we have 16 fields for the page, and for each field, we have 10-36 dropdown options(eg 6'0", 6'1", ...6'5"...6'11"...). That would result in a very big sql data for us, even if it's only for 20 items. I guess I'm a minimalist, trying to keep things tight and tidy....
Unless if we can store smarty codes in the product options field itself? Then I can store a section loop to generate those numbers and save space..