Metadata versus Facets
Definition: Filters that help shoppers to find the product they are looking to purchase.
Scenarios when attributes should be a facet:
- You want a filter to be browsable for a shopper.
- You want to be able to searchandize (create boost/ bury/ slotting rules) this attribute and make it visible to the shopper.
- You want to be able to searchandize (create boost/ bury/ slotting rules) this attribute but not make it visible to the shopper.
- Age range for toys
- Sizes for clothes
- New products
- Price or price range
- Inventory levels (This would be a hidden facet)
Definition: Anything that should be displayed within the product results in the UI.
Scenarios when attributes should be metadata:
- You want shoppers to see the attribute when viewing the product.
- You want shoppers to be able to search based on an attribute and have that attribute show on the product results UI.
- You want shoppers to be able to search based on an attribute and not have that attribute show on the product results UI.
- “Hot Item”, “Bestseller”, or “New” badges on products
- Price or price range
- Allergen information (ex. Gluten free)
- Will I ever need to add the same attribute as both a facet and metadata?
- Yes, you may want the same attribute to show up as a filter and also display on the product UI.
- Example: Allowing the shopper to filter by “new items” and also displaying “new” on the products within the search results.
- I have an attribute that I want to make searchable for shoppers, but I do not want to searchandize or allow shoppers to browse for it. Should this be a facet or metadata?
- Metadata. No need to make this a facet if you do not want to allow for searchandizing or browsing.
- Example: You may want customers to be able to search “lactic acid” and find all items that contain lactic acid, but not have a specific filter in place for items containing lactic acid.
- Should I have the same facets/ metadata on both my items and variations?
- If the facet or metadata attribute is the same at both the item (parent) and variation (child) level, this only needs to be applied at the item level.
- You may have facets or metadata on the item level that do not exist at the parent level.
- Example: The item may be a bracelet and the variations may be different types of metal. The price for the different metals would be listed as a facet on the variation level.