Required Product Data Fields
There are 3 kinds of Items, Assets, Product Groups, and Product Shades. They share many of the same fields but also have unique ones.
Before you begin adding lots of products or Looks in the Portal we recommend reading the Best Practices & Tips.
Controlling Content & Assortment In Applications
The Info tab has many fields that can be used for multiple purposes:
add info to names for use in searching Portal
add display info for UI including localisation & regionalisation
add logic fields for filter/advanced UX/display in UI
add Looks product groups and complex products combinations (palettes, multi-SKU packages, etc)
Required Item Data Fields
1. NAME
usable in search bars. See how best to use this in 'Tips on naming items'
can be used in applications, but we recommend using Optional Fields
2. DESCRIPTION
can be used in applications, but we recommend using Optional Fields
3. PORTAL ID (unique identifier used by the API)
unique 4 digits, created by the portal when item is first saved
usable in search bars
used in API
viewable in URL
Assets, Product Groups, and Product Shades Data Fields
Other Data Fields
Before using these you should probably know what your use case is. The design and requirements of your application/website will determine what and how to use these fields.
typically used to display item info in UI (names, prices, images), or to add tagging for application logic, or both
like above, but generally more for background logic for advanced use cases and functionalities