Guidelines to define global and local attributes

Fredhopper uses attributes to define facets. Facets expose different angles to a group of products like facets in a diamond

Objectives

• Help form preference and support decisions
• Merchandise groups of products - sell, not just find

User requirements

• Users should not loose overview - not too many attributes
• User groups with different needs should be addressed

Tips for facet types

• Maximum 3-5 per group of products
• Specifications: focus decision drivers (so not: 1200 rpm washing machine)
• Features/benefits: typically used for arcane, complex categories, often based on compounded specs. 
• Task/event: typically to address non-informed users (gender, usage, ...)

Tips for facet values

• Limit the number of values (so don't present 1500 brands)
• Present normalized values (so not 2000 colors in all variations)
• Use bracketed values where applicable (price range, power range, megapixel range etc.)