Pass the Salesforce Consumer Goods Cloud Consumer-Goods-Cloud-Accredited-Professional Questions and answers with CertsForce

The Assessment Indicator Definition defines the KPI or measurable parameter that field representatives capture during Retail Execution. It provides the reusable definition of what must be measured, such as the number of products on a shelf, product facings, stock availability, promotional compliance, or another store-performance indicator.

Salesforce supports several data types for Assessment Indicator Definitions, including Number, Boolean, Date Time, Text, Decimal, and Picklist. The definition can then be associated with one or more Assessment Task Definitions covering products, product categories, promotions, planograms, or custom assessment scenarios.

The Assessment Indicator Definition works together with two additional KPI objects. A Retail Store KPI associates the indicator with its business context and defines the expected or target value. A Retail Visit KPI stores the actual result captured by the field representative during a specific visit. Salesforce therefore separates the reusable KPI definition, target configuration, and transactional result into distinct layers.

This design enables the same Assessment Indicator Definition to be reused across multiple store groups, products, locations, and visits while maintaining separate targets and actual values for each applicable context.

Study Guide Topics:Data Setup - > Assessment Indicator Definition - > Retail Store KPI - > Retail Visit KPI - > KPI Measurement

===============

The Action Plan Template must use Visit as the Target Object and must be published before it can be used to generate an Action Plan for a retail visit.

Salesforce defines the Action Plan Template as a reusable framework for activities that remain consistent across multiple visits. During template creation, the administrator specifies Visit as the Target Object and configures the required Action Plan Type. Assessment tasks, flows, delivery-related activities, or other supported work items are then added before the template is published.

Publishing is an essential lifecycle step because Salesforce permits only published templates to be used when associating an Action Plan with a Visit. To create the association, the user opens the Visit, navigates to the Action Plan related section, selects New Plan, and chooses the required published template. Salesforce displays the tasks defined by the template and creates the Visit-specific Action Plan after the configuration is saved.

The process therefore does not depend on activating the Visit or separately activating an Action Plan. The key configuration is ensuring that the reusable template is explicitly designed for Visit records and has been published for use.

Study Guide Topics:Visit Planning - > Action Plan Template - > Visit Target Object - > Publish Template - > Action Plan Association

===============

The Inventory Check Lightning component is available for placement directly on an Assessment Task record page. Salesforce allows administrators to create or customize an Assessment Task Record Page through Lightning App Builder and add Consumer Goods-specific components that support field execution.

For the Assessment Task object, Salesforce documents the available components as Planogram List, In-Store Products, Promotion List, Inventory Check, and Consumer Goods Survey List. The Inventory Check component provides the dedicated interface for inventory-related assessment tasks and can expose information such as progress, summary information, location filtering, and assessment sections.

The wording of the other choices is important. Salesforce provides Planogram List, rather than a component named Planogram Check, and Promotion List, rather than a component named Promotion Check. Likewise, the supported product component is named In-Store Products, not In-Store Products Check.

After adding the Inventory Check component, the administrator can configure its component properties and activate the Lightning Record Page for the appropriate application, record type, and user profiles. This configuration provides field representatives with the required mobile or desktop execution interface when they open an inventory-related Assessment Task.

Study Guide Topics:Platform - > Lightning App Builder - > Assessment Task Record Page - > Inventory Check Component

===============

Retail Execution Lightning Plus provides access to Consumer Goods Retail Execution functionality for strategic-sales users and is the applicable entitlement for users working with Visit Recommendation capabilities in the Retail Execution environment.

Salesforce identifies Lightning Retail Execution Plus PSL as the Consumer Goods Retail Execution permission set license for strategic-sales users. Retail Execution permission set licenses enable Consumer Goods functionality that is not included automatically in the user ' s standard Salesforce license.

Einstein Visit Recommendations allow sales managers and field representatives to request recommended stores for future visits. Administrators can configure either a Flow strategy or a Next Best Action strategy. When users request recommendations, they can select the strategy that best corresponds to their business requirement, and Salesforce returns the stores that should be considered together with the associated recommendation reasons.

Tableau CRM Plus User and Tableau CRM Plus Admin permissions apply to CRM Analytics capabilities and are not the Retail Execution entitlement represented by this question.

The Retail Execution access model can also include Action Plans and Industries Visit permissions where users need the associated visit and task functionality.

Study Guide Topics:Visit Planning - > Einstein Visit Recommendations - > Lightning Retail Execution Plus - > Recommendation Strategies - > User Access

===============

The Retail Store object represents an individual physical outlet within a retailer ' s organizational structure. Salesforce deliberately separates the customer organization represented by Account from the physical selling locations where field representatives execute retail activities.

The Account object stores information about the retailer, distributor, wholesaler, or other customer organization, while Retail Store stores information about each physical store. Salesforce identifies Retail Store as the location where products are stored and sold.

A retailer can therefore have one Account associated with multiple Retail Store records. Each store can maintain its own operational characteristics, including location, delivery method, recommended visit frequency, store type, products, in-store locations, visits, orders, and other Retail Execution data. Retail Stores can also be organized into Retail Store Groups when multiple outlets share characteristics such as format, geographic area, size, or membership in a retail chain.

Assortments serve a different function: they define collections of products eligible or targeted for sale. They do not represent physical retail outlets. Therefore, Retail Store is the standard Consumer Goods object used to model each specific store operated within a retailer.

Study Guide Topics:Data Setup - > Account - > Retail Store - > Retail Store Group - > Retail Hierarchy

===============

A Store Product represents the relationship between a Product2 record and a particular Retail Store or In-Store Location. This relationship supplies the store-specific product context required by several Retail Execution processes.

For Inventory Checks, Salesforce must determine which products are relevant to the store being visited. Store Product records provide that relationship, allowing the Inventory Check experience to present applicable products rather than the entire enterprise product catalog. The same store-level product context supports the Search and Scan experience, where field representatives locate a product directly or scan its barcode while performing an inventory assessment.

Store Products also contribute to order capture. Salesforce stores operational attributes on the Store Product relationship, including the associated Product, Retail Store, In-Store Location, default order quantity, and favorite-product indicator. These fields allow the order experience to identify products that are relevant to a specific outlet and facilitate efficient repeat ordering.

Salesforce distinguishes Store Product from Store Assortment: Store Product represents products directly associated with a store or in-store location, while assortments define broader groups of products eligible for sale.

Study Guide Topics:Data Setup - > Store Product - > Inventory Check - > Search and Scan - > Order Capture

===============

CRM Analytics for Agentforce Consumer Goods requires a minimum set of records before the Analytics for Consumer Goods app can be successfully created. Salesforce identifies the required data objects as Account, RetailStore, Visit, RetailVisitKpi, and Product2. An Order record is additionally required when the organization wants to include both Retail Execution and sales data.

The Retail Visit KPI requirement is particularly important because Retail Visit KPI records contain actual information captured during visits against the Assessment Indicator Definitions and targets configured for Retail Execution. These records provide the analytics layer with visit-level compliance and performance measurements that can be used in dashboards for store performance, product performance, territory analysis, and other Retail Execution insights.

Retail Visit KPI records are generated as part of the assessment-task process based on the underlying Retail Store KPI configuration. Salesforce therefore requires at least one RetailVisitKpi record in the organization when validating the data prerequisites for the CRM Analytics application.

The analytics setup process validates these minimum data requirements and displays a message when required records are missing.

Study Guide Topics:Analytics - > CRM Analytics for Agentforce Consumer Goods - > Data Requirements - > Retail Visit KPI - > Retail Execution Analytics

===============

The frozen food aisle should be modeled as an In-Store Location. In-Store Location represents a specific physical area inside a retail store where products are displayed, stored, or evaluated. Salesforce identifies aisles, shelves, checkout counters, endcaps, and back rooms as typical examples.

Once the Frozen Food Aisle record is created, products can be associated with that location through Store Product. Store Product establishes the relationship among the Retail Store, Product2, and the applicable In-Store Location. This gives the Inventory Check sufficient context to tell the field representative exactly where the product should be inspected.

The In-Store Location can also be assigned an In-Store Location Category. Categories make it possible to group equivalent locations across multiple stores and configure Retail Store KPIs consistently for a store group. For example, all frozen-food aisles could share a category and common inventory-assessment rules.

Adding a custom picklist or task/store record type would duplicate functionality already provided by the standard Consumer Goods data model. Product2 identifies the commercial product; it does not by itself describe the product ' s physical placement within an individual store.

Study Guide Topics:Data Setup - > In-Store Location - > Store Product - > Inventory Check - > Store Layout

===============

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

===============

The In-Store Survey experience uses contextually associated Survey Invitations rather than displaying every open survey invitation in the organization. The relevant contexts are the Visit, Retail Store, and Store Primary Contact.

Salesforce allows a Survey Invitation to be generated for a contact and associated with a Visit as the related record. When the Action Plan Template assigned to the visit contains an In-Store Survey task, this association makes the invitation available within the visit ' s survey execution context. Salesforce also supports generating the invitation from the Retail Store ' s primary contact and associating the survey with the applicable account or store context.

This design ensures that field representatives see surveys relevant to the specific retail engagement they are executing. Showing all open invitations or every invitation targeted to any contact or user would introduce unrelated survey records and would not preserve the visit-level execution context.

The relationship between the Survey, Survey Invitation, Primary Contact, Retail Store, and Visit therefore provides controlled survey distribution while ensuring that the correct questionnaire is available during the appropriate store visit.

Study Guide Topics:Visit Execution - > In-Store Survey - > Survey Invitation - > Visit - > Retail Store - > Primary Contact

===============