AP-204 Salesforce Accredited Agentforce Consumer Goods Professional Questions and Answers

Users who need to access the CRM Analytics application for Consumer Goods require both the CRM Analytics Plus User entitlement and the CG Analytics User permission set. In the terminology used by this question, CRM Analytics Plus User corresponds to Tableau CRM Plus User.

Salesforce separates platform analytics access from Consumer Goods-specific analytics permissions. CRM Analytics Plus User provides access to CRM Analytics capabilities, while CG Analytics User grants the permissions required to consume the Consumer Goods analytics application and its associated dashboards and datasets.

Salesforce ' s documented setup process instructs administrators to open the user ' s Permission Set Assignments and assign CG Analytics User together with CRM Analytics Plus User when the organization uses CRM Analytics for Consumer Goods Cloud.

This dual-permission approach ensures that the user has both the underlying analytics platform entitlement and the Consumer Goods application-level access required to view dashboards such as product, store, field-representative, and territory performance analytics.

Administrative permissions such as CRM Analytics Plus Admin are intended for administrators who configure and maintain analytics applications. They are not necessary for ordinary application consumers who only need to view and interact with Consumer Goods analytics.

Study Guide Topics:Analytics - > CRM Analytics - > CG Analytics User - > CRM Analytics Plus User - > User Permissions

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

The Delivery Task is the Consumer Goods Retail Execution object specifically designed to support Direct Store Delivery activities during a visit. It represents the delivery activity assigned to the field or delivery representative and provides the execution context through which shipments and individual product transfers are processed.

Salesforce separates the delivery process into several related records. The Delivery Task defines the activity that must be performed as part of the Action Plan associated with the Visit. A Shipment is then associated with that Delivery Task to identify the inventory that must be delivered. Products and quantities within the Shipment are represented through Product Transfer records.

This architecture allows the same delivery task framework to control execution while shipment records manage the physical movement of inventory. Salesforce specifies the Lightning Direct Store Delivery permission for users who perform Delivery Task functionality. When an Action Plan Template containing a delivery task is assigned to a visit, Delivery Task records are created and can subsequently be associated with shipments.

Therefore, Delivery Task is the purpose-built Consumer Goods object for initiating and managing Direct Store Delivery execution.

Study Guide Topics:Visit Execution - > Direct Store Delivery - > Delivery Task - > Shipment - > Product Transfer

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

The Store Performance Dashboard is designed for sales managers who need to evaluate store-level Retail Execution performance and identify locations requiring intervention. It provides consolidated analysis of store KPIs, compliance trends, visits, and business performance rather than limiting the analysis to one representative, product, or individual visit.

Salesforce describes the Store Performance dashboard as answering two fundamental questions: how stores are performing based on Retail Execution KPIs and which stores need attention. It also provides correlation analysis showing how Retail Execution KPIs affect store performance and how store visits influence compliance and revenue.

The underlying metrics include Average Store Compliance and changes in compliance over the selected comparison period. Salesforce calculates these measurements from Retail Visit KPI records, allowing managers to identify stores whose compliance is deteriorating relative to an earlier period. Metrics such as facing compliance, price compliance, share-of-shelf compliance, inventory compliance, and out-of-stock compliance can contribute to the analysis.

Consequently, the Store Performance Dashboard provides the appropriate management-level view for locating stores with declining Retail Execution KPI performance.

Study Guide Topics:Analytics - > Store Performance - > Retail Execution KPIs - > Compliance Trends - > Stores Needing Attention

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

The Retail Store object should be used as the base object because Retail Stores represent the physical customer locations that field representatives need to visit. Salesforce Maps requires a mappable business object containing, or resolving to, geographic information so that records can be plotted, filtered, routed, and scheduled.

In Consumer Goods visit planning, Retail Store records supply this geographic and operational context. Store records contain the address and related location information required by Salesforce Maps. Salesforce states that the address entered when creating a Retail Store provides the location coordinates used by Salesforce Maps and also appears in the representative ' s visit list.

Salesforce ' s Consumer Goods optimized-routing process likewise uses Retail Store as the Maps base object. The planner selects relevant stores, applies business filters, identifies representatives and planning dates, and allows Maps to generate optimized visit schedules and routes.

The Visit subsequently represents the scheduled engagement with the selected Retail Store, but the physical destination being routed is the Retail Store itself. Account represents the broader customer organization and may encompass several stores, while Contact represents an individual person. Warehouse serves a different inventory and logistics purpose.

Using Retail Store therefore gives Salesforce Maps the correct geographic granularity for store-level visit planning and route optimization.

Study Guide Topics:Visit Planning - > Salesforce Maps - > Base Object - > Retail Store - > Route Planning

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

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

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

Object Metrics and Model Metrics provide complementary mechanisms for evaluating the accuracy and performance of an Einstein object-detection implementation. Object-level metrics focus on how accurately individual object classes are being recognized, while model-level metrics provide an overall view of the trained model ' s predictive quality.

Salesforce ' s Einstein Vision model APIs expose model-performance information so administrators and developers can evaluate whether a trained model is sufficiently accurate for production use. Model metrics include measurements that quantify detection quality and allow implementers to identify weaknesses before relying on predictions operationally. Salesforce ' s Einstein Vision API specifically provides a Get Model Metrics operation for vision models, allowing performance information to be retrieved for an object-detection model.

Object-level analysis is equally important because overall accuracy can hide differences between individual classes. For example, a model may reliably identify one product but repeatedly confuse another product with visually similar packaging. Reviewing object-specific performance identifies those classification weaknesses and indicates where additional or improved training examples are required.

Together, Object Metrics and Model Metrics provide both granular and aggregate perspectives on detection accuracy, supporting systematic evaluation and refinement of product-recognition models.

Study Guide Topics:Platform - > Einstein Vision - > Object Detection - > Object Metrics - > Model Metrics - > Detection 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

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

The computer display unit should be represented as the business object being inspected, while its operational condition should be captured through an Assessment Task and associated KPI. This aligns with Salesforce ' s custom-task model for Retail Execution.

Salesforce supports custom tasks specifically for business scenarios that do not fit the standard Inventory Check, Promotion Check, Planogram Check, Order Creation, or Survey task types. Salesforce gives the example of capturing maintenance information for a refrigerator placed in a store, which is directly analogous to assessing the condition or functionality of a computer display unit.

For a custom assessment, administrators define Assessment Indicator Definitions representing the values that field representatives need to capture. The associated Retail Store KPI provides the target and business context, while the Retail Visit KPI stores the actual observation entered during execution. Custom Context can connect the KPI configuration to the relevant standard or custom business object.

An In-Store Survey is intended for collecting feedback from customers or store personnel and is not the appropriate mechanism for recording equipment-performance KPIs. Creating a dedicated task record type also does not replace the assessment/KPI architecture.

Study Guide Topics:Visit Execution - > Custom Tasks - > Assets - > Assessment Indicators - > Retail Visit KPI

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

Einstein Visit Recommendations support Next Best Action strategies for determining which retail stores should be recommended for visits. Salesforce allows administrators to configure a recommendation strategy that evaluates relevant records and business criteria and produces prioritized visit recommendations for sales managers and field representatives.

A Next Best Action strategy can load relevant data, apply business rules, generate scores and reasons, and return recommendations that support store-visit planning. When a user creates a Visit Recommendation Request, the selected recommendation strategy is executed for the specified store and date context. Salesforce can also incorporate prediction information from Einstein Discovery when organizations require model-based recommendations.

The architecture separates recommendation logic from visit execution. Administrators can therefore create multiple strategies for different business priorities-for example, prioritizing stores with declining inventory, important upcoming promotions, or revenue opportunities. Salesforce documentation specifically supports both flow-based strategies and Next Best Action strategies for Einstein Visit Recommendations, enabling organizations to select the implementation approach that aligns with their planning logic and scalability requirements.

Accordingly, the ability to create Visit Recommendations through a Next Best Action Strategy is a standard supported configuration.

Study Guide Topics:Visit Planning - > Einstein Visit Recommendations - > Next Best Action - > Recommendation Strategies - > Visit Prioritization

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

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

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

The Maximize Store Sales Einstein Discovery story is designed to identify factors that influence product sales and provide actionable insights that can help sales managers improve store performance.

Salesforce provides preconfigured Einstein Discovery stories within Analytics for Consumer Goods. The sales-focused story analyzes historical data to identify variables that have a positive or negative impact on product sales. Salesforce currently describes this capability as Maximize Store Product Sales, which provides insights into the factors affecting product sales and helps organizations devise strategies to increase sales at a store or store-group level.

Einstein Discovery uses the available analytics dataset to identify statistically relevant relationships and present explanations that business users can act upon. These insights can assist sales managers in understanding how factors such as product availability, assortment, store characteristics, and other operational conditions correlate with sales performance.

The Minimize Out-of-Stock story serves a different objective: it predicts products that are likely to run out of stock so representatives can mitigate availability problems. While out-of-stock conditions can affect revenue, the scenario specifically asks for broader insight into the factors affecting store sales, making the sales-maximization story the appropriate functionality.

Study Guide Topics:Analytics - > Einstein Discovery - > Maximize Store Sales - > Predictive Insights - > Sales Performance

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

Administrators review object-detection results through Detected Objects. Each object identified by the vision model is represented as a Detected Object record, providing administrators with the information required to examine how the model is performing against actual images.

A Detected Object record contains operational details about a particular detection, including the source image, the model responsible for identifying the object, the object ' s coordinates within the image, and the probability or confidence associated with the detection. Reviewing these records allows administrators to determine whether products are being identified correctly and to recognize patterns of incorrect classification or missed detections.

This review process is also important for continuous model improvement. When model output is inaccurate, additional representative examples can be incorporated into the training dataset and the model can be trained again. Salesforce ' s Einstein Vision architecture supports iterative model development because a dataset can generate multiple models, enabling implementers to compare model performance and refine training data over time.

Creating an unrelated custom object, enabling a feature, or using Einstein Bots does not provide the detection-result records required to assess object-recognition performance.

Study Guide Topics:Platform - > Einstein Vision - > Detected Objects - > Model Performance - > Model Refinement

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

The Retail Visit KPI provides the visit-level relationship between the configured KPI framework and the Assessment Task that is executed in the field. Retail Store KPI defines expected values, while Retail Visit KPI captures the actual measurement generated during a specific Visit and Assessment Task.

Salesforce ' s Consumer Goods data model shows that Retail Visit KPI includes references to Assessment Task, Visit, Assessment Indicator Definition, Product, Product Category, In-Store Location, Promotion, Planogram, and other assessment context. It also contains the Target Value and Actual Value used to evaluate store performance.

The records are created as part of the assessment-task generation process. When an Action Plan Template is assigned to a Visit, Salesforce creates Assessment Tasks based on the included Assessment Task Definitions and creates Retail Visit KPIs based on the applicable Retail Store KPIs.

This design enables one centrally configured Retail Store KPI to drive repeated measurements across many store visits. Each individual visit receives its own Retail Visit KPI record, allowing the actual execution result to remain associated with the Assessment Task that produced it.

Study Guide Topics:Data Setup - > Retail Visit KPI - > Retail Store KPI - > Assessment Task - > Actual and Target Values

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

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

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

For a product-level Inventory Check, the product must be associated with the Retail Store where the assessment will be executed. Retail Execution needs a store-specific product relationship so Salesforce can determine which products are available for assessment when the field representative opens the Inventory Check.

Salesforce ' s Inventory Check prerequisites explicitly require administrators to associate Products with the Retail Store and associate the applicable In-Store Locations with that same Retail Store. The Retail Store must also belong to the Retail Store Group selected on the Retail Store KPI.

The Retail Store KPI then defines the assessment target by combining the Retail Store Group, applicable In-Store Location Category, Assessment Indicator Definition, and Product or Product Category. Salesforce separately specifies that the Product field is required on a Retail Store KPI when inventory-check tasks are configured for the store group.

The Store Product relationship provides the standard data-model mechanism for associating an individual Product2 SKU with a Retail Store or particular In-Store Location. A Promotion or Product Category relationship serves a different business purpose, while an Assortment defines a collection of products eligible for sale rather than replacing the required store-product association for Inventory Check execution.

Study Guide Topics:Data Setup - > Inventory Check - > Product - > Retail Store - > Store Product - > Retail Store KPI

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

Frequently purchased products can be prioritized for a specific outlet by associating them through Store Product and marking the appropriate products as Favorite. Store Product represents the relationship between Product2 and a Retail Store or specific In-Store Location, which allows Salesforce to maintain outlet-specific merchandising and ordering attributes.

The Store Product data model includes both Is Favorite and Default Order Quantity. These attributes are designed to streamline recurring order capture. Salesforce explains that field representatives can prioritize favorite products when creating orders so commonly purchased items are replenished efficiently and remain in stock. Default Order Quantity can further reduce data entry by predefining the quantity normally ordered for the product.

Salesforce ' s Retail Execution configuration also allows products associated with a store to be marked as favorites. The Inventory and ordering user interfaces can expose favorite products as a focused subset, reducing the time required to create routine orders.

This makes Store Product the correct outlet-specific mechanism for modeling frequently ordered products rather than creating artificial Order records with a template status.

Study Guide Topics:Visit Execution - > Order Capture - > Store Product - > Favorite Products - > Default Order Quantity

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

Flow-based tasks operate within the Visit and Assessment Task execution context and require the business context necessary to determine the applicable KPI configuration. The Retail Store KPI represents the target definition for an Assessment Indicator Definition and provides information such as store group, product, location category, target value, and other assessment context.

The flow also operates with the relevant Assessment Task and Visit identifiers so that automation can execute against the correct task instance and scheduled retail visit. This maintains the relationship between the reusable configuration and the transaction generated for an individual field visit.

Salesforce ' s broader assessment architecture reflects the same hierarchy: assigning an Action Plan Template to a Visit creates Assessment Tasks based on Assessment Task Definitions, while Retail Visit KPIs are generated using the applicable Retail Store KPI configuration.

This separation is essential. Retail Store KPI supplies expected business targets, Assessment Task provides the executable activity, and Visit supplies the store-engagement context in which the Flow runs.

Study Guide Topics:Visit Execution - > Flow-Based Tasks - > Retail Store KPI - > Assessment Task - > Visit Context

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

Salesforce Maps Advanced supports sophisticated store-visit planning through traffic-aware routing, routing constraints, and Visit Windows.

Traffic information helps field representatives and planners account for expected travel conditions. Agentforce Consumer Goods optimized-route functionality uses travel time between visits and provides real-time traffic information and route suggestions so representatives can react to congestion, roadworks, and other delays.

Maps Advanced also performs constraint-based optimization. Route generation considers operational constraints such as the planning period, required visit frequency, working schedules, travel time, maximum segment length, and other optimization criteria. These constraints allow the routing engine to generate routes that balance customer-coverage requirements with the practical capacity of field representatives.

Visit Windows define when a customer or retail location can accept a visit. Administrators can establish specific days and times, such as weekdays between 9:00 AM and 11:00 AM. Maps Advanced then attempts to schedule future visits inside those windows while generating optimized routes.

Together, these capabilities allow sales managers to create realistic multi-stop schedules that account for travel conditions, operational restrictions, and customer availability.

Study Guide Topics:Visit Planning - > Salesforce Maps Advanced - > Route Optimization - > Constraints - > Visit Windows - > Traffic

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

An Einstein object-detection implementation depends on three essential elements: a suitable training dataset, a properly trained and evaluated model, and appropriate user access to the functionality.

The implementation begins by collecting representative images of the products or objects that must be detected. For object detection, the training images require labeled bounding boxes identifying the position and dimensions of each object. These examples are uploaded as a dataset and used by the training process to create an object-detection model.

The trained model should then be evaluated before deployment. Salesforce ' s model-training architecture reserves data for testing and provides model information that allows implementers to evaluate the model ' s detection performance. Reviewing model quality before exposing the capability to field representatives is essential because representative training data and adequate model performance directly affect detection results.

Finally, the field users who execute the functionality require the relevant access and permissions. Permissions are part of the Salesforce security model and determine whether users can access the required Consumer Goods and Einstein functionality.

OCR configuration and competitor-suppression datasets are not baseline requirements for this object-detection setup.

Study Guide Topics:Platform - > Einstein Vision - > Object Detection - > Dataset - > Model Training - > User Permissions

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

Salesforce Maps Mobile Check In provides the field representative with the appropriate mechanism for recording arrival information at a customer or retail location. Salesforce Maps supports field activity tracking directly from map markers, routes, and schedules, enabling representatives to check in when they arrive and check out after the visit is complete.

Salesforce Maps Check In can capture the representative ' s location, check-in time, visit duration, and other activity information. Location information can be recorded as latitude and longitude, allowing the organization to verify where the representative was when the check-in occurred. Administrators can also configure a verification distance, requiring users to be within a defined distance of the record ' s geolocation before a check-in is accepted.

For a merchandiser performing an Inventory Check, this creates a reliable operational record of when the representative arrived at the store and the geographic coordinates associated with that event. The feature is integrated into the Salesforce Maps mobile experience and is designed specifically for field-based visit activity.

Einstein Vision performs image-analysis functions and does not provide visit check-in functionality. A generic location picker likewise does not provide the complete Maps activity-logging workflow.

Study Guide Topics:Visit Execution - > Salesforce Maps - > Mobile Check In - > Geolocation - > Visit Activity

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

Custom assessment tasks use the Consumer Goods Custom Task Measures component to expose KPI information on the related object ' s record page. For this experience to appear, the administrator must both place the component on the relevant Lightning Record Page and ensure that the intended users receive that page through the correct page assignment.

Salesforce instructs administrators to open the custom or standard object ' s Lightning Record Page in Lightning App Builder, drag the Consumer Goods Custom Task Measures component onto the page, configure its properties, and save the page. If the component has not been added, users naturally see the object ' s standard record-page experience instead of the custom KPI interface.

Lightning Record Pages must also be activated for the appropriate application, record type, and user profile. Salesforce ' s page activation framework supports assignments by app, record type, and profile, allowing different users to receive different record-page experiences. If the custom task page is not assigned to the field representative ' s profile, Salesforce can display another assigned or standard record page instead.

These two configuration layers-component placement and profile/page assignment-are therefore required for the KPI component to appear.

Study Guide Topics:Platform - > Lightning App Builder - > Custom Tasks - > Consumer Goods Custom Task Measures - > Record Page Assignment

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

Sales Rep Performance, Store Insights, and Product Performance are standard analytics dashboards provided for Consumer Goods Retail Execution.

The Sales Rep Performance dashboard enables sales managers to compare representatives, identify high- and low-performing team members, and analyze performance trends over time. Metrics can include revenue, product sales, visits, compliance, and other Retail Execution measurements.

The Store Insights dashboard provides store-focused analysis. It enables users to examine store sales, compliance metrics, product performance, visits, and related trends to identify outlets that require attention. Salesforce documents Store Insights as one of the embedded dashboards available within the Consumer Goods analytics experience.

The Product Performance dashboard provides product- and category-level insights. Sales managers can identify high- and low-performing products, review revenue and quantity trends, analyze compliance, and determine which products require intervention.

The native analytics portfolio contains additional dashboards such as Store Performance, Territory Performance, Whitespace Analysis, and Sales Manager Home. Category Insights and Inventory Performance are not the corresponding standard dashboard names represented by these options.

Study Guide Topics:Analytics - > CRM Analytics - > Sales Rep Performance - > Store Insights - > Product Performance

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

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

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

Endcaps should be represented as In-Store Locations and In-Store Location Categories, with Retail Store KPIs specifically configured for that merchandising context. This allows NTO to measure endcap performance independently from primary shelves, checkout counters, backrooms, or other store areas.

Salesforce ' s Agentforce Consumer Goods data model supports In-Store Location categories precisely for this purpose. Similar physical locations across stores can be categorized-for example, Endcap Displays-and Retail Store KPIs can then use that category to define the measurements and targets applicable to those locations.

Salesforce ' s own Retail Execution configuration examples demonstrate creating Retail Store KPIs specifically for the Endcap Displays category. A promotion-compliance KPI can include the Retail Store Group, Endcap Displays as the In-Store Location Category, the relevant Assessment Indicator Definition, Promotion, Product Category, and a Boolean target value. This allows field representatives to capture endcap-specific performance during visits while managers analyze the resulting Retail Visit KPI data separately.

Creating Retail Store record types or unrelated custom objects would not provide the appropriate KPI granularity. Dedicated KPI configuration for the endcap context uses the standard Consumer Goods data model and provides targeted merchandising measurement.

Study Guide Topics:Data Setup - > In-Store Locations - > Endcap Displays - > Retail Store KPI - > Assessment Indicators

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

Salesforce supports Promotion Checks at three defined levels: General Promotion, Individual Product, and Product Category. These levels determine the commercial context against which a field representative performs the promotional compliance assessment.

A Product Category-level Promotion Check is appropriate when the promotion applies across a category of products. For example, an organization may discount all beverages or energy bars and assess compliance collectively rather than creating an independent promotion check for each SKU.

An Individual Product-level Promotion Check is used when a promotion applies to a specific product, such as the launch of a new flavor or an in-store sampling activity. The field representative evaluates execution specifically for that product.

A General Promotion does not require association with a particular product or product category. It is suitable for store-wide activities such as coupons, signage, or general promotional conditions that apply across the outlet.

These three levels allow promotion configuration to match the intended scope while avoiding unnecessary duplication of promotional records and assessment tasks. Salesforce uses the same levels when defining the promotion and when executing the corresponding Promotion Check in the field.

Study Guide Topics:Visit Execution - > Promotion Check - > General Promotion - > Product - > Product Category

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

Salesforce Lightning pages can combine standard platform components with components specifically provided for Consumer Goods Retail Execution. The applicable combination is Quip Documents, Einstein Predictions, and Custom Object Task List.

The Quip Document component allows administrators to embed collaborative Quip documents directly on Salesforce record pages. Users can create, view, and edit supporting documents without leaving Salesforce. The component is configured through Lightning App Builder and can use either individual documents or reusable templates.

The Einstein Predictions component displays deployed Einstein Discovery predictions and recommendations on standard or custom-object record pages. Administrators add the component using Lightning App Builder and select the applicable deployed prediction model.

For Retail Execution, Salesforce provides Custom Object Task List as one of the standard Consumer Goods mobile components. It is scoped to Assessment Task and can be incorporated into customized mobile pages together with other Consumer Goods components such as Inventory Check, Promotion List, Planogram List, and In-Store Products.

The other option sets contain capabilities that are not identified as corresponding Lightning page components for this configuration.

Study Guide Topics:Platform - > Consumer Goods Mobile App - > Lightning App Builder - > Quip - > Einstein Predictions - > Custom Object Task List

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