Product2 as the sellable unit in retail execution
Key Takeaway
Every SKU, or sellable unit, is a record in the Product2 object, so a new SKU needs a Product2 record before it can be associated with a retail store.
In Agentforce Consumer Goods, every product your company sells is a record in the Product2 object. Each of those records is one SKU, or sellable unit. Other objects connect the products to prices, product categories, assortments, retail stores, and in-store locations. Together, these records tell field reps what each store sells and what to check during a visit.
Product2: one record per sellable unit
The Product2 object represents a product that your org sells. Each product record is stored in Product2 and counts as one SKU.
What counts as a product depends on context. The company decides what its products are. Whatever the company defines as a product is stored as a Product2 record.
A beverage company sells sparkling water. Stores order it in cases of 12 bottles, because buying in bulk earns them a discount. So in shipping, the product is the case. On the shelf, shoppers buy one bottle at a time, so there the product is the single bottle. If the company defines both the case and the single bottle as products, each one gets its own Product2 record and is its own SKU.
You can create product records one at a time in the application. For high-volume product information, you can import the data using Data Loader. Retail execution, sales planning, and analytical insights need basic product attributes.