The consultant must identify the hierarchy level that represents the stock keeping unit (SKU). In the Consumer Goods Retail Execution data model, individual products are represented through Product2 records, and Salesforce describes each Product2 record as a SKU or sellable unit. Consequently, the ERP hierarchy level that contains SKU-level information provides the appropriate product granularity for product-specific retail execution processes.
Share-of-shelf measurement requires Salesforce to identify precisely which products occupy shelf space so that actual shelf presence can be evaluated against configured targets. Retail Store KPIs can associate Assessment Indicator Definitions such as Share of Shelf with products, product categories, planograms, store groups, and in-store location categories. The underlying product master therefore needs a level that reliably represents the individual sellable products being measured.
Salesforce product master data can contain multiple hierarchy levels such as categories, subcategories, brands, and SKUs. The numerical position of a tier is not itself significant; what matters is the business meaning of that tier. For this requirement, the tier representing SKUs provides the required product-level data for shelf measurement and Retail Execution processing.
Study Guide Topics:Data Setup - > Product2 - > Product Hierarchy - > SKU - > Share-of-Shelf KPI

The appropriate action is to edit the product tags so that the incorrectly detected object is associated with its correct product classification. Product identification depends on the relationship between the detected item and the product label assigned to it. When two packages have highly similar visual characteristics, a detected object can require correction to ensure subsequent shelf-analysis results reflect the correct SKU or competitor product.
Share-of-shelf measurements depend on accurate identification of the products occupying the shelf. If an item belonging to a competitor is classified as the company ' s own product, the calculated shelf presence becomes overstated and the resulting compliance data is unreliable. Correcting the product tag addresses the classification problem at its source rather than manipulating the physical shelf or abandoning the assessment.
This approach also aligns with the underlying object-detection model. Detection systems generate identified objects and associate those detections with product classifications. Accurate labels and representative examples are fundamental to reliable image-based object recognition. Where product appearance changes substantially, maintaining accurate classification information is essential to preserving measurement quality.
Creating a different planogram would change the expected merchandising arrangement but would not correct an incorrectly classified detected product.
Study Guide Topics:Platform - > Einstein Object Detection - > Product Recognition - > Product Tags - > Share-of-Shelf Accuracy

Action Plan Templates can contain both Assessment Task Definitions and Component Tasks, allowing organizations to combine standard Retail Execution activities with customized Lightning Web Component- based tasks in a reusable visit framework.
An Assessment Task Definition represents a recurring field activity such as an Inventory Check, Planogram Check, Promotion Check, In-Store Survey, Order Creation activity, or custom assessment. Salesforce allows administrators to add these Assessment Task Definitions to an Action Plan Template. When that template is used for a Visit, the corresponding tasks become associated with the visit and are presented to the assigned field representative.
Salesforce also supports Component Tasks. Administrators can select Add Component Task on an Action Plan Template, provide a name and description, select the required Lightning Web Component through its fully qualified name, and determine whether the task is mandatory. This allows organizations to extend store execution with specialized interactive experiences while continuing to use the standard Action Plan framework.
Action Plan Templates are configured administratively and function as reusable frameworks for repeatable business processes. Their ability to combine multiple task types is fundamental to creating consistent and scalable store-visit execution plans.
Study Guide Topics:Visit Planning - > Action Plan Templates - > Assessment Task Definitions - > Component Tasks - > Visit Execution

Inventory Check execution is scoped to the products associated with the specific Retail Store being visited.
Salesforce Retail Execution uses this relationship to ensure that the field representative works only with products relevant to that outlet rather than searching the organization ' s entire Product2 catalog.
The Store Product object establishes the association between a product and a Retail Store or a specific In- Store Location. This relationship provides the product context used during store-level execution. Inventory Checks allow representatives to capture real-time information such as stock quantities, facings, share of shelf, product placement, and other assessment indicators for products sold in the store.
Product ownership or the identity of the user who created a Product record does not determine whether it should appear during an Inventory Check. Those attributes are unrelated to the commercial assortment or stocking relationship between a product and the retail location. Searching every product in the organization would also introduce irrelevant records and reduce mobile execution efficiency.
Therefore, product search during an Inventory Check is based on products associated with the Retail Store, ensuring the representative receives an operationally relevant product list for that visit.
Study Guide Topics:Visit Execution - > Inventory Check - > Store Product - > Retail Store - > Product Association

Retail Execution Lightning Plus provides the Retail Execution entitlement associated with strategic sales functionality in Consumer Goods Cloud. Einstein Visit Recommendations operate within the Retail Execution environment and help sales managers and field representatives determine which stores should be visited based on configurable recommendation strategies.
Salesforce documents the Lightning Retail Execution Plus permission set license as the Retail Execution license for Consumer Goods strategic sales users. The Retail Execution license framework provides access to Consumer Goods capabilities that are not included in the underlying Salesforce user license.
Einstein Visit Recommendations must also be enabled in Setup. Once configured, authorized sales managers and field representatives can create recommendation requests and schedule store visits based on the recommendations returned by Salesforce. Recommendation logic can be implemented using either a Flow strategy or a Next Best Action strategy, enabling organizations to align the feature with specific business- planning requirements.
CRM Analytics permission sets govern access to analytics applications and dashboards, while Lightning Direct Store Delivery provides access to DSD-specific functionality. Action Plans provide access to the Action Plan framework. For Visit Recommendation execution within Retail Execution, Retail Execution Lightning Plus is the applicable choice.
Study Guide Topics:Visit Planning - > Einstein Visit Recommendations - > Retail Execution Permissions - > Recommendation Strategies