Vote up!
Vote down!

no product variations wanted

I am very familiar with ubercart, but am confused by the new commerce system. I am building an online store for an antiques store, who does not have any variations of sizes and colors, everything is a unique one of a kind product. I find this system very time consuming for entering products that have no size or color attributes offered. Any tips on how to speed up the process, and create what used to be a taxonomy for easy classification would be greatly appreciated.

Asked by: zenn
on October 30, 2013

2 Answers

Vote up!
Vote down!

Hello Zenn,

Product Variations is a just a saying really, and here is why.

To Create a New Product for Sale:

1) You need to define a Product Display and a Product Type

--- Product Display is the Content Type, the actual page someone lands on to purchase you product. This is where your title, body, etc lives.

--- Product Type is the entity that contains the SKU, Price, and any specific fields

2) Add a Product Reference field to your Product Display

3) In your case, with individual products, you would add 1 Product to each Product Display. So if you were selling a Rocking Chair, you would create a new Product Display with the Title, Description, etc. Then add a Product to the node, and in the product set the SKU and Price.

The option to set it to say Product Variation instead of Products is available. The reason why Product Variation is a good term is because there may be times where you have different pricing options, skus, etc for the same "product display".

For me, I have created an event/course registration system. Because each of my events may be offered in more than one location, I need to make sure the user registers and purchases the right one. I have only 1 Product Display being used because it the same event, but I add more than 1 "Product Variation", one for each location since they have different SKUs.

For some people it just makes more sense to call it that. It has nothing to do with HAVING to have a color or size, that is just an easy example of why calling it a Product Variation makes more sense to standard editors because they feel that a color is just a variant of a t-shirt, not an entirely different product.

I kinda went all over there but I hope that helps. There is also a bunch of documentation on here about it.

Answer by: Travis
Posted: Oct 31, 2013


Just to add, if you only add 1 Product Variation (or Product), you don't see a drop down or select list to choose from, its just the single product for sale. When you add more than 1 Product Variation, then you get a color/size look with a dropdown to choose what you want.

- Travis on October 31, 2013

Thank you for the help, what was messing me up the most was how it create a product display, i was starting by adding a content type for "product for sale" and I re-tried it by adding a product variation which creates the product display. I am going to work on it again today and will post back if I need more help, thank you so much!

- zenn on October 31, 2013
Vote up!
Vote down!

If you're using Inline Entity Form you can set the cardinality (allowed values) of the product reference field to 1, and the product will be shown as a fieldset on the product display (node) add / edit form.

Bojan Zivanovic
Answer by: Bojan Zivanovic
Posted: Nov 1, 2013