<p>This is actually one of Commerce's best features IMO - that you CAN have separate dimensions/weights for variants - for us this is absolutely essential.</p>
<p>Of course, there are definitely times when it is not needed, too.</p>
<p>In these cases, we have a 'Standard Box' section that we store standardised entries in, with the appropriate data.</p>
<p>We then just relate these to the variant using a relations field.</p>
<p>Works really well...however, the behaviour is of course not the same as using the in-built fields - e.g. your shipping calculator needs to be aware of this etc.</p>

CC BY-SA 4.0
2020-07-15T07:44:46.360Z
Thank you for your idea, but I am afraid it is not optimal in my case. I have mobile phones and tablets and the number of "Standard boxes" will be almost the same as number of products probably. 

Maybe I can make custom fields for Dimensions and Weight for product and ignore default fields per variant, but would be nice to find native solution.
Duško Šobić
CC BY-SA 4.0
2020-07-15T11:20:58.660Z
Sure, was more commentary than a suggestion per se.  Clive's comment above is probably how I would look to do it in your case too...
Jeremy Daalder
CC BY-SA 4.0
2020-07-15T02:28:29.030Z
2020-07-15T02:28:29.030Z
Jeremy Daalder
<p>When I enable multiple variants for product type that has Dimensions and Weight, fields &quot;Dimensions and Weight&quot; become available for every single variant. Product is tablet and all variants have a same dimensions and weight.</p>
<p>Is it possible to have common &quot;Dimensions and Weight&quot; fields for a single product, not for every variant?</p>
<p>Application info:</p>
<ul>
<li>Craft Pro 3.4.27</li>
<li>Craft Commerce 3.1.11</li>
</ul>

CC BY-SA 4.0
2020-07-15T08:57:37.220Z
You might need a custom module that listens to the onSaveProduct or whatever it is? Have some custom fields on the product that contain your default dimensions, then if the variant dimensions are left blank populate them automatically from your custom field entered values? That's probably how I'd do it.
Clive Portman
<plugin-craftcommerce>
Make dimensions common for all variants in Craft Commerce
# Make dimensions common for all variants in Craft Commerce

(Asked by: username_0 on 2020-07-14)

When I enable multiple variants for product type that has Dimensions and Weight, fields "Dimensions and Weight" become available for every single variant. Product is tablet and all variants have a same dimensions and weight.

Is it possible to have common "Dimensions and Weight" fields for a single product, not for every variant?

Application info:

* Craft Pro 3.4.27
* Craft Commerce 3.1.11

**Tags:** plugin-craftcommerce

> **Comments:**
> **username_1**: You might need a custom module that listens to the onSaveProduct or whatever it is? Have some custom fields on the product that contain your default dimensions, then if the variant dimensions are left blank populate them automatically from your custom field entered values? That's probably how I'd do it.  

---

## 1 answers

### Answer by username_2 on 2020-07-15. Score: 1

This is actually one of Commerce's best features IMO - that you CAN have separate dimensions/weights for variants - for us this is absolutely essential.

Of course, there are definitely times when it is not needed, too.

In these cases, we have a 'Standard Box' section that we store standardised entries in, with the appropriate data.

We then just relate these to the variant using a relations field.

Works really well...however, the behaviour is of course not the same as using the in-built fields - e.g. your shipping calculator needs to be aware of this etc.

> **Comments:**
> **username_0**: Thank you for your idea, but I am afraid it is not optimal in my case. I have mobile phones and tablets and the number of "Standard boxes" will be almost the same as number of products probably.   Maybe I can make custom fields for Dimensions and Weight for product and ignore default fields per variant, but would be nice to find native solution.  
> **username_2**: Sure, was more commentary than a suggestion per se.  Clive's comment above is probably how I would look to do it in your case too...  

---

