Skip to content

Product fields ​

Each marketplace needs to be tailored to its industry. Marketplaces can request vendors to add additional data to their products to boost their marketplace.

Here are some use cases:

  • automatically add products to a collection
  • display more product context to the end customer
  • use additional information in internal automation

Where are product fields used? ​

When creating a new product, vendors set the product fields in the product form. Note that if you don't have any product field set, the Product fields section is hidden.

Product field page view

Moreover, when uploading a CSV, all product fields will be available for mapping the data from the CSV to Garnet.

Internally, a product field is a Shopify metafield definition. It is accessible in the Shopify admin console, in Shopify collections, theme templates, and in the liquid code.

View product fields ​

Product fields can be viewed by the marketplace following Garnet > Admin panel > Products > Product fields.

Add product fields screenshot

Product fields can be of different types:

TypeDescriptionExamples
RadioSingle choice from predefined optionsSize: S/M/L
DropdownSingle choice from dropdown listCategory selection
CheckboxMultiple choices from predefined optionsFeatures: Waterproof, UV protection
Short textSingle line of textModel number
Multiple short textMultiple free text entriesTags, keywords
Long textMultiple lines of textProduct highlights
Rich textText with formattingTell us your story
URLWeb address, email, or phone linkSocial profile, product page link
Image or videoSingle media uploadProduct photo
Image onlySingle image upload, videos are refusedSize chart, certificate scan
Multiple imagesMultiple media uploadsProduct gallery
FileFile uploadTechnical specifications PDF
DateDate selectionManufacturing date
Date & TimeDate and time selectionRelease date and time
IntegerWhole numberStock quantity
NumberDecimal numberWeight in kg
MoneyCurrency amountCost price
Product referenceLink to another productRelated product
Multiple productsLink to several productsBundle items, cross-sells
MetaobjectLink to a metaobject entryArtist, exhibition, brand

Each type is described with a screenshot in field types.

Add product fields ​

It's easy to add a product field from Garnet, see the video below:

Add product field demonstration

Technical tip

Since product fields are product metafield definitions, you can define them in Shopify > Settings > Metafields > Products. Only metafields with namespace custom will show in Garnet.

If you need a metafield type not supported by Garnet, please contact us.

Edit multiple options ​

You can edit multiple options by using Edit multiple button in the option list.

Edit multiple options

Delete product fields ​

To delete a product field, simply click on the Delete button. A confirmation will be prompted.

Warning

Removing a product field is irreversible. When deleted, all its data associated with products is also deleted.

Can't delete a product field?

Sometimes you may receive an error message like Metafield definition cannot be deleted because of the smart_collection_condition capability. In this case, the associated metafield is used in a smart collection and you must remove it from the smart collection first.

Reorder product fields ​

Product fields can be reordered with drag and drop. It is possible to move a product field from one section to another, within the same section, and reorder sections themselves!

How to reorder and move sections in product fields

Garnet supports linking metafields with variants. It enables the marketplace to have strictly defined variations and to prevent vendors from adding options inconsistent with the marketplace. Learn more about variations.

Product fields are Shopify metafields ​

In the background, Garnet's product fields are Shopify metafields under the custom namespace. These metafields can be edited in Shopify > Settings > Customer Data > Products.

Metafields vs tags

Metafields are better than tags as they are:

  • Typed checked: metafields have the required type (number, date, file...)
  • Private: metafields are not displayed in the front-end code unless explicitly used
  • Easily accessible: link the value in your theme, and access the value in your liquid code. :::