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

Actual KPI values captured by a field representative during visit execution are stored in the Retail Visit KPI record. Salesforce separates KPI configuration from transactional execution data so that planned or target values remain distinct from values observed during individual visits.

The Retail Store KPI defines the target or expected value for a particular Assessment Indicator Definition. It provides the planning context, including the Retail Store Group, product or product category, In-Store Location Category, Custom Context, and target value. When an assessment task is generated for a visit, Salesforce creates the corresponding Retail Visit KPI records that represent the runtime measurements.

During execution, the field representative records the observed value. Salesforce stores fields such as the Actual Value, Target Value, Assessment Indicator Definition, Product, In-Store Location, and Custom Context on the Retail Visit KPI.

This architecture allows Salesforce to compare expected performance with actual field results across multiple visits. The custom object can supply the business context for a custom task, but it does not replace the Retail Visit KPI as the repository for actual assessment measurements.

Study Guide Topics:Data Setup - > Custom Tasks - > Retail Store KPI - > Retail Visit KPI - > Actual Values

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

Consumer Goods can be customized declaratively through Lightning App Builder and Flow, while Lightning Web Components provide the component-level extensibility required for specialized user experiences.

Lightning App Builder allows administrators to configure Salesforce record pages by placing and configuring standard components without rebuilding the underlying application. This supports customer-specific page composition while remaining within the Salesforce Platform configuration model.

Where more specialized behavior is required, Lightning Web Components provide an extensibility layer. Salesforce supports custom LWCs that interact with standard components and extend or modify business functionality. For example, Salesforce ' s Consumer Goods extensibility documentation describes using custom LWCs alongside standard components so custom interactions and data changes can be reflected in the standard experience.

For process-oriented customization, administrators can create Flows and associate them directly with an Action Plan Template. Salesforce states that flows can implement activities specific to a business that are not covered by standard Consumer Goods task types. Once associated with the template, those flows become available to field representatives during store visits.

The Consumer Goods mobile platform also supports LWC-based mobile extensions through its integration framework, keeping customization aligned with Salesforce Platform technologies rather than requiring Apache Cordova development.

Study Guide Topics:Platform - > Mobile Customization - > Lightning App Builder - > Lightning Web Components - > Flow - > Action Plan Templates

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

In-Store Survey execution depends on both an available Salesforce Survey and a corresponding Survey Invitation. The survey supplies the questionnaire that the field representative must complete, while the invitation creates the specific survey instance that becomes available in the context of the visit, retail store, or contact.

Salesforce ' s Consumer Goods configuration process requires the administrator to set up and activate the survey before it can be distributed. An Assessment Task Definition of type In-Store Survey is then incorporated into the Action Plan Template used for the visit. To expose the actual survey instance, Salesforce requires a Survey Invitation to be generated, commonly through the Retail Store ' s primary contact. The invitation is associated with the relevant records so that it appears within the survey task during visit execution.

Field representatives do not require permission to create surveys merely to respond to them. Survey authoring is an administrative function. Likewise, the standard process does not depend on creating a custom task definition or on a separate Retail Execution Survey Lightning Flow.

Therefore, absence of either the activated Survey or the related Survey Invitation prevents the survey from being available to the field representative.

Study Guide Topics:Visit Execution - > In-Store Survey - > Salesforce Surveys - > Survey Invitations - > Visit

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

The Sales Manager persona is responsible for managing the day-to-day Retail Execution processes performed by the field organization. Salesforce explicitly defines the Sales Manager as a standard Retail Execution user who can create visits, create tasks, and assign visits to field representatives.

This division of responsibilities is fundamental to the Agentforce Consumer Goods operating model. Sales managers coordinate retail coverage and determine what activities field representatives should perform at each store. They typically work with Retail Stores, Visits, Action Plans, Assessment Task Definitions, and Action Plan Templates to organize execution activities. By contrast, field representatives have a more execution-focused role: they review assigned visits, complete assessment tasks, capture observations, process orders, and record the results of store activities.

The permission model is designed around these personas. Salesforce recommends establishing separate permission configurations for Sales Managers and Field Reps so that each role receives the appropriate object-level and feature access. Delivery representatives can also be configured separately when the organization uses Direct Store Delivery.

Consequently, responsibility for creating and coordinating visits and assigning field work belongs to the Sales Manager persona.

Study Guide Topics:Platform - > User Personas - > Sales Manager - > Visit Management - > Task Assignment

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

Promotions can be defined at the Product Category level or the individual Product level when the promotion has a product-specific commercial context. Salesforce also supports a general promotion with no product or product-category context, but among the listed options, Product Category and Product are the applicable promotion-definition levels.

A Product Category promotion applies the promotional activity to a collection of related products. This design is appropriate when the same commercial offer applies across an entire category, such as discounted beverages or energy bars. A Product-level promotion applies to one or more specific products, such as a new-product launch, sampling campaign, or SKU-specific discount.

Salesforce stores the relationship between a promotion and its individual products through Promotion Product. For category-based promotions, the relationship is represented through Promotion Product Category. Account, Retail Store Group, and Retail Store describe the reach or channel through which a promotion is distributed rather than the product level at which the promotion itself is defined. These destinations are associated through the Promotion Channel model.

This separation allows administrators to independently define what products a promotion concerns and where the promotion applies.

Study Guide Topics:Data Setup - > Promotions - > Product Level - > Product Category Level - > Promotion Product

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

The planogram Image record is associated with an In-Store Location. This relationship identifies the specific physical area of the retail store where the reference shelf arrangement applies.

Salesforce ' s Planogram Check prerequisites require administrators to create an Image record representing the planogram and then associate that Image with the appropriate In-Store Location. Typical In-Store Locations include primary shelves, aisles, checkout counters, endcaps, and other areas where products are displayed.

The association is important because a single Retail Store can contain many merchandising locations, each with a different expected layout. Linking the planogram directly to its In-Store Location enables Salesforce to present the correct reference image when a field representative performs a Planogram Check at that particular location.

The Retail Store KPI then references the corresponding In-Store Location Category, Assessment Indicator Definition, Image or planogram, product context, and KPI Type. During execution, the field representative can open Product Details within the Planogram Check and view both the products to be inspected and the associated reference image.

Therefore, the Image object containing the planogram is related to the In-Store Location where that planogram must be evaluated.

Study Guide Topics:Data Setup - > Planogram - > Image - > In-Store Location - > Planogram Check

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

Because the promotion applies to all energy bars, the Retail Store KPI should be configured at the Product Category level. Salesforce supports promotion checks at the Product Category, individual Product, and General Promotion levels. Product Category is the appropriate level when a promotional activity applies uniformly to a group of related products.

A category-level configuration minimizes administrative overhead because a single KPI configuration can represent the target for the complete energy-bar category rather than requiring individual KPI records for every SKU. Salesforce allows the administrator to associate a Product Category with a Retail Store KPI together with the Assessment Indicator Definition, Retail Store Group, In-Store Location Category, promotion, KPI type, and target value.

An SKU-level configuration would be appropriate when each individual product requires separate measurement or targets. In this scenario, however, the same BOGO promotion applies across the full energy-bar category, so SKU-specific records would unnecessarily increase data volume and maintenance.

Custom Context applies primarily to custom assessment tasks rather than standard promotion-check configuration. Consequently, Product Category provides the correct granularity while supporting scalable and maintainable Retail Store KPI administration.

Study Guide Topics:Data Setup - > Promotions - > Product Categories - > Retail Store KPI - > Promotion Checks

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

The representative should edit the product tags so that the detected object is associated with the correct product classification. Accurate tagging is fundamental to maintaining reliable object-recognition results, particularly when two products have visually similar packaging.

Object detection identifies objects within an image and maps those detections to labels or product classes. If a competitor changes packaging so that its product resembles another SKU, the resulting classification can incorrectly increase the measured facings or share-of-shelf for the wrong product. Correcting the tag provides accurate classification information and helps maintain the integrity of the shelf measurement.

Salesforce ' s Einstein Vision architecture supports a feedback process for incorrectly classified objects. When an object-detection model misclassifies an image, corrected examples and labels can be added back to the dataset and used in subsequent training or retraining. Salesforce describes this feedback mechanism specifically as a way to improve models after misclassification.

Creating a new planogram would only alter the expected shelf arrangement and would not correct product identity. Turning competitor products around manipulates the physical merchandising environment rather than correcting the data. Canceling the task similarly fails to improve future recognition.

Study Guide Topics:Platform - > Einstein Object Detection - > Product Tags - > Classification - > Share-of-Shelf Accuracy

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

The Nearby Map component on the Promotion record page provides the required functionality through standard Salesforce Maps configuration with minimal custom development.

Salesforce specifically documents the use of a Nearby Map component for Consumer Goods scenarios. Administrators create a Nearby Map configuration using an appropriate Maps layer and then place the Maps Nearby Maps component on a Lightning Record Page through Lightning App Builder. The layer determines which business records are displayed and how they are filtered.

For promotions, Salesforce gives this precise use case: administrators can configure a Nearby Map with a layer containing Retail Stores and place that component on the Promotion record page. When a sales manager views the Promotion record, the component displays retail stores participating in the promotion in a map-based interface. This allows the manager to visualize nearby participating stores without leaving the promotion context.

Because the capability is supplied through Salesforce Maps and Lightning App Builder, it avoids developing a custom visual mashup or modifying an unmanaged AppExchange package. Adding a generic map to the Home page would also lack the Promotion record context needed to display stores associated with the specific promotion.

Study Guide Topics:Visit Planning - > Salesforce Maps - > Nearby Map - > Promotion - > Retail Store Visualization

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