Understand the working context

A useful family structure follows how the team searches and talks about the products. Keep names consistent and avoid adding levels that nobody uses. A product belongs in a specific part of the range while remaining connected to its ancestors. Review the hierarchy when ranges are retired or reorganised so that active items are not left in an unclear place. Descriptive categories and family relationships should serve a clear, maintainable purpose.

Put it into practice

  • Start with the top-level range.
  • Add sub-families that help distinguish the products.
  • Place each item in the most useful relevant family.
  • Review product status when archiving a family.

A practical example

A drinks catalogue uses Monster Energy as a top-level family, with Juiced, Java and Ultra below it. Individual products sit in the appropriate sub-family while still belonging to the overall range. A colleague can browse the range broadly or narrow the view to Ultra.

HOW THIS RELATES TO ATLAS

In the current workspace

Atlas supports nested product families, descendant filtering and archived-family checks. An inactive product must be detached or assigned to an available family before it can be reactivated.

Explore the product

Atlas feature scope reviewed 17 October 2026. Plan availability and connection setup apply.