I'm wondering if I'm implementing my products the right way.

As I understand it should be the following.

I have different product variations with each their specific fields and SKU. For example storage = 8 GB or 16GB

Then I have the main product to which these variations belong with main attributes such as the product name or compatibility. These are shared over the different variations.

So I consider I have my product nodes (or product displays?) with al my product information that is the same over the variations. And I have my product variations with the SKU's and fields that are specific to each variation of the main product.

For me personally I think this is the correct way because you don't have duplicate data in your database. And if some field data needs to change, if it's a product specific field and not variation specific, you don't need to edit it over all the variation entities.

But I'm not sure that this is the correct way to do this according to standards, advise, other things I'm missing, ... . Because I'm very new to drupal commerce.

2 Answers 2


I think you're on the right track. If I'm not mistaken, a product display could be something like "Tee Shirt". The product variants would then be something like color or size. It's the same product with the core information, but the variants would be what ever is different, be it storage size or any other kind of variation from the original.

Edit: The product display can display any products. The variants are dependent on the actual product but the display can show anything.

  • I'm confused because of the term "Product Display". It suggests it's just a node to display data not keep data. :/ Dec 7, 2015 at 12:58
  • It can be a little confusing, but here is good information on the topic. Essentially a product display can display any product, it's just a node-type entity used for displaying actual product information. drupalcommerce.org/user-guide/product-attributes-variations
    – discg0lfer
    Dec 7, 2015 at 16:59
  • 2
    The fun starts when you wonder "what about "category", where does that go? ...
    – Clive
    Dec 7, 2015 at 17:02
  • Damn it's confusing. So not really on the right track. :/ Dec 8, 2015 at 6:31
  • @discg0lfer where do you define the actual product then? Dec 8, 2015 at 12:39

In the end we decided to put all the fields on product variation level.

In this sense it also gives more flexibility to the product managers in which attributes define the variation instead of a hard coded limit on which attribute.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.