Data Property TypesĀ 

Learn about the available data types in Salsify and how they’re used.  For more information about data storage see Best Practices: Storing Data to Meet Your Organization's Needs.

Click here to learn more about managing properties.

Performance Best Practices

To preserve ideal performance within Salsify, please note the following limits:

  • Maximum number of properties: 10000
  • Maximum number of computed properties: 250
  • Maximum number of searchable properties: 50

String

[plain text, accepts alpha numeric and special characters, case sensitive]

String is the most commonly used property type and is the default unless another type is chosen. It stores plain-text alphabetical and numeric characters without any special formatting.

Product ID and Product Name are both string values. Note that product identifiers cannot start with an underscore _ character. We recommend not including non-alphanumeric special characters in product identifiers. Click here for more information about the product identifier.

Picklist/Category

[plain text, alpha numeric characters, hierarchical, fixed set, case sensitive]

Picklist/Category property type is used when there is a known set of property values to choose from like brands, colors or categories.  It presents users with a dropdown menu of available values, and those values can contain hierarchies.  

Picklists are used to categorize and consolidate property values.  For example, if you have a property called Category and one of the categories is Backpacks, without a dropdown available, a user might enter Backpacks, backpacks (which are different values because of case), Bags, etc.  With a dropdown menu, they’ll choose the Backpacks value that is attached to all other backpack products, making this information valuable for grouping products. 

Having all your “Backpacks” store the same Category property value allows you to accurately filter, base lists and workflows on it, map associations to retailer versions of the same information, and use it in catalogs to let users filter by the pick list options.

You can also build hierarchies with pick lists, so under Backpacks, you could store more specific sub-categories like Day Hiking Backpacks, creating more opportunities to categorize, filter and match data to retailer requirements.

Number

[plain, numeric characters only]

Number accepts only numeric characters, and is used for numeric data such as weight, dimensions, and quantity.  Setting a property to the number type allows you to standardize, easily use formulas to transform values, and helps avoid sending unexpected information to retailers.

Note that leading zeros are not stored with number property type. For example, UPCs that start with zero would drop the leading zero. Use the string data type to retain leading zeros.

For example, a product weight could be stored as string or number property type. If stored as a string, users could add many different versions of values that mean the same thing like 1 pound, one pound, 1 lb., or 1.  If stored as a number, users can only add 1, so your data becomes more consistent and properties less open to interpretation.  And 1 is the most useful version of the data, because retailers may require different units of measure like ounces or kilograms, and it’s easy to use a formula in Salsify to transform the number version of the data into whatever equivalent unit of measure the retailer requires.

Date

[yyyy-mm-dd format]

Date-formatted properties accept only dates, and are typically used for deadlines or activation dates. Users adding data inside Salsify are provided a calendar to select dates from.  Imported data should be formatted like 2016-12-01, in year, month, day order.

Yes/No

[boolean, accepts y, yes, n, no, true, false, not case sensitive]

Typically used to trigger workflows and as a filter data point for lists and syndication, the yes/no property type only allows two choices, Yes and No.  Exports to Excel and csv formats as Yes and No.  Exports to JSON format as true and false.

Rich Text

[accepts alpha-numeric and special characters with formatting, case sensitive]

Stores property values with formatting like bold, underline, italics, bullet points and numbered lists.  Users get a small WYSIWYG editor to format data they’re adding inside the interface. 

HTML

[accepts alpha-numeric and special characters with formatting, case sensitive]

Stores HTML formatting with property value.  Previews in Salsify interface with HTML applied without styling.

Link

[accepts alpha-numeric and special characters with formatting, case sensitive]

Creates property with clickable text.  The link text creates the URL the text will link to automatically and is clickable from the Salsify interface and catalogs.

Digital Asset

[upload of any file format, 300 MB file size maximum]

Special field type to store any digital asset file. Most image file types preview inside Salsify, are able to be viewed in catalogs and can be renamed and transformed via Salsify channel exports.  File types like pdf and other document formats can be stored and downloaded but not previewed. 

Supported Video

  • YouTube hosted
  • Vimeo hosted
  • mp4
  • webm
  • flv
  • mov
  • ogv
  • 3gp
  • 3g2
  • wmv
  • mpeg
  • avi

 All file types can be added to and shared via lightboxes*. 

Images

Most, but not all image types will show a preview inside the Salsify interface and catalogs.  Image types that can be transformed are:

  • GIF
  • PNG
  • JPG
  • BMP
  • ICO
  • PDF
  • TIFF
  • EPS
  • JPC
  • JP2
  • PSD
  • AI
  • SVG
  • WebP
  • JPEG-XR

*Feature available in select versions of Salsify.  Contact your Customer Champion or Contact Customer Success for more information or to add to your account.

The following data types may not currently be available in your organization. Please speak with your Customer Champion for more information or to request these data types are added to your organization.

Product Reference

[Product IDs]

Product references are one-way relationships between products, with no automatic inheritance. You can store product(s) in a reference property that relates them with each other. References can be used by parts of the platform, via formulas, to pull information about the products stored in the reference property to products storing the reference. 

Click here for more information about Product References. 

References properties store the referenced product IDs and display a thumbnail image, the product ID linked to the referenced product, and product name on the product details page.

Quantified Product Reference

[Product IDs]

Quantified Product References work like Product References, but you can manage a quantity of the referenced product on the product that references it. You store product IDs in the property, then you can set a quantity that should be included. Typically used in cases where you’re referring to products included in a kit or replacement parts needed for a product. Default quantity is 1.