Product Family
A Product Family is a picklist value on the Product2 object that lets you group products into broader merchandise categories for forecasting, reporting, and quota allocation.
Definition
A Product Family is a picklist value on the Product2 object that lets you group products into broader merchandise categories for forecasting, reporting, and quota allocation. Salesforce Sales Cloud uses Product Family to slice the standard Customizable Forecast and the Forecasts hierarchy by category, so a sales leader who sells hardware, software, and services can see a separate forecast number for each line of business instead of one blended total.
Product Family is a single picklist field, not a separate object, and a product can belong to exactly one family. The values are admin-defined and used wherever a forecast or report rolls revenue up by category. The same field also drives Quotas in Forecast Categories, lets sales ops set different commission accelerators by family, and acts as a natural filter on Opportunity Product reports when leadership asks how the new SaaS line is pacing versus the legacy hardware book.
Why Product Family is the cheapest forecasting lever in Sales Cloud
One picklist, three downstream uses
Product Family is technically just a picklist on Product2, but Salesforce reads it in three different parts of Sales Cloud. Forecasts by Product Family give each sales manager a separate number for each family they sell. Reports group opportunity revenue by family with a single column drag. Quotas can be set per family, so a rep who sells both Software and Services can carry a $400k Software quota and a $200k Services quota that roll up separately. The picklist defines all three uses; you change the values once and every downstream consumer follows.
Forecasts by Product Family and how the hierarchy reads it
To use Product Family in forecasting, an admin enables Customizable Forecasts (or the newer Collaborative Forecasts) and turns on the Product Family forecast type. Salesforce then renders one forecast tab per family the rep has open opportunities in. A manager looking at their team sees each rep with three rows (one per family) instead of one blended row. The roll-up still respects the role hierarchy, so the VP of Sales sees the sum of all family forecasts under them. The toggle is per-org, not per-user, so once enabled it shapes the forecast page for everyone.
Quotas in Product Family forecasts
When Product Family forecasts are turned on, each rep gets a quota record per family per month or quarter, depending on the forecast period. Sales ops loads these via the Forecasting Quota object or the Data Loader. A rep with no quota in a family still sees the forecast tab for that family but the attainment percent is blank. Sales ops uses this to control which reps are accountable for which family, and to set differential targets (for example, a strong Software quota but a stretch Services quota for the same rep).
Product Family on the Product object
The field lives on Product2 (the standard Salesforce object behind every product), not on PricebookEntry. Each product carries exactly one family value. When a rep adds a product to an opportunity, the OpportunityLineItem inherits the family from the parent Product2, and forecast roll-ups read it from there. If you change a product family later, existing opportunity line items keep their original family unless you write a script or flow to backfill. Most orgs leave family values stable and only add new values when launching a new line of business.
Reports, dashboards, and Einstein
Outside of forecasts, Product Family appears as a filterable and groupable field on every Opportunity-with-Products report. A pipeline dashboard can show a bar chart of bookings by family, an aging report can split deals by family, and a forecast accuracy report can compare commit to closed per family. Einstein Opportunity Scoring also reads Product Family as one of its training features, so adding granular family values can improve the score's separation between high-converting and stalled deals if revenue mix matters in your sales motion.
Operating discipline: who owns the values
Sales ops or revenue ops owns the Product Family picklist values, not marketing and not the product team. The reason is that families show up in quotas, forecast tabs, and commission accelerators; an unannounced change breaks all three. Most orgs have between three and eight values, mapped one-to-one to lines of business that the finance team books revenue against. Adding a new value mid-quarter triggers a downstream backfill: existing products need a family, existing quotas need a row, existing forecast configurations need a refresh.
When Product Family is the wrong tool
Product Family is one shallow categorization per product. If you need a tag-style classification (a product that belongs to both Cloud and Subscription), use a custom multi-select picklist or a junction object, not Product Family. If you need a deep hierarchy (Cloud > Cloud-AWS > Cloud-AWS-Storage), use a custom lookup to a Product Category object you own. Forecasts will still read Product Family, but reporting and analytics can use the richer field for slicing. Treat Product Family as the forecast hook and put nuance somewhere else.
Set up Product Family for forecasts and reporting
Enable Product Family on Product2, set the picklist values to your lines of business, and turn on Product Family forecasts so quotas and roll-ups split by family.
- Define the families with sales and finance
Meet with sales ops and revenue accounting. Agree on the picklist values that match the books finance reports on. Keep the list short, three to eight values is normal. Document each value with a one-line definition so reps know which product goes where.
- Add picklist values
Setup, Object Manager, Product, Fields and Relationships, Product Family. Edit the picklist. Add each family value. Leave the API name aligned with the label. Add a default value only if 80 percent of products fall into one family.
- Stamp existing products
Use Data Loader or a flow to set Product Family on every active product in your catalog. Open products with no family will not roll up correctly, so this backfill is mandatory before forecasts are turned on.
- Enable Product Family forecasts
Setup, Forecasts Settings, Forecast Types, New. Choose Revenue or Quantity, then choose Product Family as the rollup. Activate. The org now shows one forecast tab per family for each rep with open pipeline in that family.
- Load quotas by family
Build a CSV with one row per user per family per period. Use Data Loader to insert into the Forecasting Quota object. Each rep now sees a quota number on each family forecast tab, and attainment percent calculates correctly.
- Build a family pipeline report
Create an Opportunity-with-Products report grouped by Product Family. Add a forecast-category column. This is the report sales ops uses to compare forecast commit to actual pipeline per family every Monday morning.
Revenue or Quantity. Revenue rolls dollar amount; Quantity rolls unit count. Most orgs pick Revenue.
The value applied to new products if the admin does not pick one. Set this only if one family covers most of the catalog.
Deactivating a family value hides it from new selections but preserves it on existing records. Use this to retire a line of business without breaking history.
Monthly or Quarterly. Aligns with your forecast period. All families share one period setting.
- An opportunity line item inherits Product Family from the parent Product2 at the time the line is added. Changing the family on Product2 later does not retroactively update old line items.
- Open opportunities with products that have no family value are excluded from the family forecast. Run a periodic report for OpportunityLineItem where Product2.Family is null and fix the source product before close.
- Reps in a multi-currency org see family forecasts in their personal currency. Multi-currency conversion happens on the line item amount, not on the family aggregation, so dated exchange rates apply per line.
- Do not confuse Product Family with the Product Category Data field used in CPQ. CPQ has its own taxonomy that drives quote templates; Product Family drives Sales Cloud forecasts.
Trust & references
Cross-checked against the following references.
- Forecast by Product FamilySalesforce Help
- Products OverviewSalesforce Help
- Manage QuotasSalesforce Help
Straight from the source - Salesforce's reference material on Product Family.
- Forecast by Product FamilySalesforce Help
- Product2 Object ReferenceSalesforce Developer Docs
- Forecasts SettingsSalesforce Help
Hands-on resources to go deeper on Product Family.
About the Author
Dipojjal Chakrabarti is a B2C Solution Architect with 29 Salesforce certifications and over 13 years in the Salesforce ecosystem. He runs salesforcedictionary.com to help admins, developers, architects, and cert/interview candidates sharpen their fundamentals. More about Dipojjal.
Test your knowledge
Q1. What is Product Family?
Q2. What's the field type?
Q3. Why use product families?
Discussion
Loading discussion…