karine:
If it helps to see the usage needed:
http://www.hausergallery.com/fabric.htm
The site now uses paypal buttons. We are moving to zencart.
There are 13 pages of fabrics but only some of them have 2 or more pieces. Does stock by attributes still look like the best solution? There are many other product categories that are one-of-a-kind, so I am hesitant to do stock by attributes.
I still don't understand the answer to my first question. Why can't I use "Number of items" and "1st piece, 2nd piece" as the option name and option values? Why does checkout not allow the purchase of the second item if someone wants both pieces?
karine
So, I'll try to provide as many of the settings expected to handle a situation like you are describing; however, I may miss something that needs to be switched to a different setting and would best be able to identify the incorrect setting by knowing/seeing what is going on. At the moment I am not where I have access to a test site.
So, I would first create a product. For what appears to be desired, I would set the product as priced by attributes. If I wanted to identify an unlimited supply I would make the quantity available some large number. (This is also because I would have. The store set to not be able to sell a product that I don't have as available, this is a store-to-store setting dependent onhow business is to be run/availability of a product. For some, once it's gone, it's gone for good. For others, there will be a delay.) I would more than likely leave the price of the product blank. (At least at first considering that there may not be some sort of "base" price for whatever is being chosen, but that the price would be fully dependent on the attribute). Also, I would not set a maximum value other than 0, so could add the same product (regardless of attribute type) more than once.m. If that value is set to 1, then can only request theone product one time and that attributes are basically something unique about the product, but has no impact on whetherproduct with attribute is different than the same product without that attribute. Ie, a shirt that is available in blue or white is more than likely two different shirts, unless the coloring is done by the business, and are therefore two different products; however, a shirt with an iron-on is basically the same as the same shirt without the iron-on. (Although iron-ons are also a stock related item)
So now that I have a product, I would create attribute data to be seen by the customers.
First would create an option name: this is the "heading " like select color or select size and is identified to a type of functionality (drop down, radio, checkbox, etc.)
After setting the other characteristics of it, I would then make option values that would be tied to that option name. Think big scale when working these two parts. Perhaps you only want a 2"x2" on one product, but 40"x36" on another. (Also want to consider measurements in one direction with quantity identified past that, but starting to get into some more setup things like price by foot or by inch. For now want to stick with the basic attributes.) Anyways the idea is that the option name could be applied to multiple products and only those option values desired can be assigned for that one product. One of the suggested values to add is something like please select one of the following or similar words. This will allow the product(s) to be setup to not allow adding the item(s) to the cart without the customer making a conscious decision about which attribute to select. (Otherwise, could end up with returns because they got something they didn't want, all because they didn't see something or make their own personal choice.) Typically this value is set to 0 in the sort order and other values follow. There is no requirement. For example could be set for the middle of the list if options (above are less than options below like a negative/positive setting).
After those two things, option name then option values have been assigned, then use the attribute controller to assign the option name to the product and whatever option value(s) desired. If a product only comes in one size, then basically there is no need to identify an name/value combination, just have to describe to customer what they are getting.
So in the attribute controller, would assign the price for each of the attributes (say small and large) and there's a few other aspects of which blocks to fill in, depending on how the price to be adjusted, but the please select me option value would be set as display only/required/default so that it is the first thing shown and prevent the customer from adding the item to the cart without picking something in that list. (Some attributes can be optional, like if offered something like free monogramming, then if nothing was entered in the text box, nothing would be monogrammed and the product could be added to the cart, but if required entry, then would ask the customer to state some standard terminology so that you know they don't want a monogram, but also so you are "100%" sure they didn't forget to monogram the item. That all is basically how you choose to run things and what you think will work as compared to others in your "area".
So, I think I've covered the basics through and through. I still don't know exactly the conditions you were in when you tried what you did. It was a little confusing. So instead of me asking multiple questions, I have stepped through what I would typically setup for what has been described. There are a lot. Of other settings that can be set depending on the desired outcome. Suggest reading through the FAQs about attributes. As for whether SBA is for you, again can be handled without it (product 1 avail in size 1, product 2 same product but in size 2). Again, ideally you want whatever will keep you selling and with minimal effort as your time really is money. Could be doing something more/better to continue making money.
