Attributes, Options, & Custom Fields

Overview

Flxpoint has different unique fields that can be leveraged to create more detailed product listings. You can leverage Attributes, Options, and Custom Fields to house important pieces of data to your business!

What are Unique Fields?

  • Attributes are characteristics that describe a parent product. Attributes are shared amongst all the different variants of the parent. A shirt may have different sizes and colors, but consistently across all of those variations, the material of the shirt is cotton.
  • Options are required for Parent/Variant(s) relationships and represent the choice between variations of a parent product. Using the shirt example, options of the shirt could be the Size and Color. A Small, Red shirt etc.
  • Custom Fields are indicators on a product of any custom data point you want to be able to leverage within Flxpoint or send to your channel. On your publish listings template, you will need to assign these to a Channel supported specific field.

How to Use

The below sections will discuss how to apply the unique fields to your products, leverage within Flxpoint by using filters, and important information to know how the data points function within the system and interact with your channels.

Attributes

  • Attributes can be imported on a Get Inventory Primary integration mapping template. On a file import, your Column header would be Attribute Name 1 with the actual name of the attribute, i.e. Material in the rows beneath the header. The other column header would be Attribute Value 1 with the Value being in the rows beneath _i.e. Cotton _

  • Attributes are a Name/Value pair and reside on the Parent product record. Attributes can also be added by navigating to the parent record within the Product catalog and scrolling down to the attributes section and clicking the add button.

  • For more information on managing attributes, you can click here

Options

  • Options can be imported on a Get Inventory Primary integration mapping template. On a file import your Column header would be Option Name 1 with the actual name of the option, **i.e. Size **in the rows beneath the header. The other column header would be Option Value 1 with the Value being in the rows beneath_i.e. Small_

  • Options are a Name/Value pair where the Name resides on the Parent product record and the Option Value resides on the variant record. Options can also be added by navigating to the parent record within the Product catalog and scrolling down to the options section and clicking the add button. This is where you add the Option Name and the Variant view is where you will fill in the Option value

Flxpoint Pro Tip

Options are required for parent/variant relationships if the parent has more than one variant record

Option structure needs to be the same amongst all variants. i.e. If one variant has an option for Size, then the other variants under that parent need to have a value for that Size option as well

Custom Fields

  • Custom Fields can be imported on a Get Inventory Primary integration mapping template. On a file import, your Column header would be Custom Field Name 1 with the actual name of the custom field being in the rows beneath the header. The other column header would be Custom Field Value 1 with the Value being in the rows beneath that header.
  • Custom fields are supported at a Parent and a Variant level. Depending on if that Custom Field applies to a specific variant or the custom field is true for all the variants, so it can be housed on the Parent is up to you!
  • Custom Fields can also be mapped on the Get Inventory Primary by hard-coding a value for the Name of the Custom Field (this can be applied to Attributes and Options as well)

    If the file has a column for the value of the unique field, but not the actual name. The mapping template can look like the screenshot below, where you hard-code the Custom Field Name

 

  • Custom Fields can be added at the catalog level by navigating to the parent level and saving the parent once complete

Filtering with Unique Fields

  • Leveraging filters in Flxpoint to help guide your choices on what inventory to build, what listings to publish, etc. is a great use of Flxpoint's tools -- for more information on filters you can click here!
  • Custom Fields, Attributes, and Options can be filtered using Key/Value Pairs and Lists like you see below

Unique Fields & Channels

A common use case for using unique fields like options is to create the parent/variant relationship with multiple variants. Some Channels require all the options to be the same on related variants so using the filters above and method of adding those options is pivotal to successfully listings products.

  • Attributes and Custom Fields are commonly used to leverage metafields for Search Engine Optimization when pushing that information to your channel.

  • Different channels interact differently with Unique Fields in Flxpoint. You can reference your channel document by navigating here and selecting your channel to see if there is more detailed information specific to the channel
  • Checking your channel's publish mapping template will give you insight into whether the channel has a field that accepts the Attribute or Custom Field