Answers.Body: <p>At the moment there is no Commerce variants field type unfortunately.   It comes up a lot, someone should post it here: <a href="https://github.com/craftcms/commerce/issues" rel="nofollow noreferrer">https://github.com/craftcms/commerce/issues</a>. </p>
  
  <p>Edit - I've gone ahead and posted this here - <a href="https://github.com/craftcms/commerce/issues" rel="nofollow noreferrer">https://github.com/craftcms/commerce/issues</a></p>
  
  <p>In the meantime yes a text or eg table field could store variant IDs...which I suppose is ultimately what a proper field type would do basically.  </p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-11-23T00:09:43.757Z
Answers.Text: I'd say "annotated relations" would be a massive step forward in Craft land— relations that can have data attached to them, like other Element types. Not sure it would exactly help here (since the variations still wouldn't be available for selection), but the concept is similar in nature, I'd imagine?
Answers.UserDisplayName: August Miller
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-11-23T00:25:29.527Z
Answers.Text: Well annotated relations is quite easy to achieve currently with e.g. a matrix field (or a supertable or I imagine Neo as well) - a relation plus other fields with data about that relation.  We do that currently.  
  
  Doesn't help here really, where you specifically need a way to target a variant element instead of a product one (a variant being a child of a product, really)
Answers.UserDisplayName: Jeremy Daalder
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-11-22T21:55:57.400Z
Answers.LastActivityDate: 2018-03-28T23:26:16.137Z
Answers.LastEditDate: 2018-03-28T23:26:16.137Z
Answers.UserDisplayName: Jeremy Daalder
Body: <p>The client wants related products on individual product pages.</p>
  
  <p>Is it possible to have the “Commerce Products”-field allow for selection of variants rather than products as a whole? Or is there another way to achieve this functionality?</p>
  
  <p>If not, I was thinking about letting the client paste the variant ids into a table field or something, then pull the variants onto the product page with ajax. Seems quite hacky though, so any alternatives are most welcome!</p>
  
  <p>Thank you kindly</p>
  
Tags: <plugin-craftcommerce>
Title: Can the “Commerce Products”-field allow for selection of variants?
ThreadText: # Can the “Commerce Products”-field allow for selection of variants?
  
  (Asked by: username_0 on 2016-11-22)
  
  The client wants related products on individual product pages.
  
  Is it possible to have the “Commerce Products”-field allow for selection of variants rather than products as a whole? Or is there another way to achieve this functionality?
  
  If not, I was thinking about letting the client paste the variant ids into a table field or something, then pull the variants onto the product page with ajax. Seems quite hacky though, so any alternatives are most welcome!
  
  Thank you kindly
  
  **Tags:** plugin-craftcommerce
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2016-11-22. Score: 2 | Accepted answer
  
  At the moment there is no Commerce variants field type unfortunately. It comes up a lot, someone should post it here: <https://github.com/craftcms/commerce/issues>.
  
  Edit - I've gone ahead and posted this here - <https://github.com/craftcms/commerce/issues>
  
  In the meantime yes a text or eg table field could store variant IDs...which I suppose is ultimately what a proper field type would do basically.
  
  > **Comments:**
  > **username_2**: I'd say "annotated relations" would be a massive step forward in Craft land— relations that can have data attached to them, like other Element types. Not sure it would exactly help here (since the variations still wouldn't be available for selection), but the concept is similar in nature, I'd imagine?  
  > **username_1**: Well annotated relations is quite easy to achieve currently with e.g. a matrix field (or a supertable or I imagine Neo as well) - a relation plus other fields with data about that relation.  We do that currently.    Doesn't help here really, where you specifically need a way to target a variant element instead of a product one (a variant being a child of a product, really)  
  
  ---
  
  