Product feed data needs guide - Stylitics/guide GitHub Wiki

All of these are are fields for a single product (or product+colorway). The field names below are examples for the type of data we're interested in -- you do not need to name your fields/columns exactly these.

Bold means required or strongly recommended -- if unable to provide, we'll need to discuss. Some non-bolded ones may be required for your particular use case (e.g., if you don't want us to outfit products that are on clearance sale / permanent markdown, we'll need some indicator of this in the feed)

  • Product Page URL
    • URL of the page where user can buy / order the product
  • Parent SKU / Retailer Item Number
    • An ID that we will use to identify the product variation to show outfits for. Typically this is at the color level, but can also be at the product level. (In contrast, it's not the SKU, which would typically incorporate size as well as which product & colorway)
  • Product Name
    • user-facing display name of the product
  • Brand Name
    • relevant if you sell multiple brands, can be omitted if all of your products are the same brand
  • Retailer Name
    • relevant if you offer products from multiple retailers, can be omitted if all of your products are from the same retailer
  • Availability
    • this can be an inventory count, inventory health metric, or other data - you just need to tell us what values indicate that a product is / is not available.
  • Inventory Count
    • Can be used in lieu of or in addition to Availability
  • Retailer Price
    • Regular price
  • Retailer Image URL
    • URL of the primary image of the product (or, ideally, image of front-facing off-model shot)
  • Sale Price
  • Gender
    • "unisex", or some value implying that, is valid
  • Region
    • only relevant if splitting products between regional accounts (ie, U.S. and Canada)
  • Size
    • sizes for the given product / colorway (optional, not used in standard offerings)
  • Item Style
    • mid- or low-level categorization for the product (ie, Tops > Sweater)
  • Category
    • mid- or high-level categorization for the product (ie, Tops > Sweater)
  • Color
    • color name
  • Color Hex Value
    • hex color code for the product's main color, if available
  • Material
    • product fabric
  • Brand Group
    • relevant if you have sub-brands / labels
  • Age Group
    • e.g. "children", "toddlers", etc
  • Size Group
    • e.g. "petite", "tall", "plus"
  • Color Family
    • if you have a hierarchy of colors, this would be the highest level (ie Blue > Light Blue > Aqua Swatch 2)
  • Color Code
    • if you use an immutable color code (not e.g. hex or rgb) for potentially changing color names (for example, "MBLK" for a color that used to be Midnight and is now Midnight Black)
  • On Sale
    • Indicator that the product is or is not currently on sale (markdown)
    • If you don't have a field like this, but do have sale price, our default logic is to assume that if sale price is present and less than price, AND the item is available (not out-of-stock or inactive) then the item is on sale and the sale price is operative currently.
  • Clearance Flag
    • Indicator of if the product is on clearance (if different than on sale)
  • Pattern
  • Occasion
    • If you designate occasions for which the product might fit. Rare; "Collection" below might be a better fit.
  • Theme
    • promotion or calendar based grouping
  • Collection
    • cross-category grouping that doesn't fall into "Theme"